What a green status indicator actually checks

A green status indicator is only as informative as the check behind it. If it only requests the homepage, it initially describes that page's availability. It does not establish whether an order succeeds.

I would therefore name the checked task clearly for every important indicator. “Homepage reachable” is more precise for an operational decision than a blanket “Everything works”.

The same shop, two outcomes

In a hypothetical portal, the homepage is served successfully while the order request fails. The table describes invented outcomes, rather than a measured ASES incident.

An indicator evaluating only the first row can remain green. That is not a contradiction in the measurement. The check never examined the second task. Even a successful technical response must contain the expected content.

Check the business task deliberately

For this example, a separate planned test case would help: a test account selects a known product and follows the order through to a confirmed outcome in the destination system. An isolated test environment can support this flow without real orders.

The test initially proves the selected flow in that environment. It does not automatically cover every customer group, product or dependency in production. Before running such a check there, define how real inventory movements, invoices and payments will be avoided. A “test” label alone does not guarantee this.

Internal metrics and logs can then help investigate a cause. A reachability indicator alone does not explain whether the ordering application or a connected system caused the failure.

Different websites need different checks

For a page that only provides information, a basic reachability check can be a useful starting point. An order test would not be an appropriate task there. The effort should reflect the functions that actually matter.

For a green indicator, record which request, content and flow were checked. Then decide what extra information is missing for an operational decision. The signal gains an understandable connection to users' work.

Sources

• Google SRE — Monitoring Distributed Systems