---
title: "When dashboards go quiet: observability needs cross-checks"
description: "How to tell that monitoring actually monitors, and why “green” is not proof."
canonical: "https://simosphereai.com/en/field-reports/observability-needs-cross-checks"
lang: en
---

# When dashboards go quiet: observability needs cross-checks

How to tell that monitoring actually monitors, and why “green” is not proof.

- Published: 2026-10-06
- Updated: 2026-10-06
- Status: praxis
- Publisher: SIMO GmbH

## Starting question

How do we know that our monitoring actually monitors?

## Result: works with conditions

Monitoring works only with a cross-check against the real data source. “Successful but empty” has to count as an error.

Only by cross-checking against the actual data source. A query can report success and still return nothing, for example because a metric was renamed. “Successful but empty” therefore has to count as an error, and when something fails, the upstream protection layer is the first thing to check.

## What we experienced

While building 56 charts across five dashboards, one central chart stayed empty. The metric had been renamed in the version in use, and the query reported success with zero results.

Elsewhere, the bot protection of the upstream network service injected challenge pages into data requests. It looked like a broken backend.

## What it means for business architecture

“Green” is not proof. Anyone using metrics for decisions needs a check against the actual data source, not against the documentation.

## Lessons learned

- “Successful but empty” is the most treacherous state. It has to count as an error.
- Check metric names against the live interface instead of copying them from examples.
- Several protective layers can get in each other’s way. When something fails, check the upstream layer first.

Rendered version: https://simosphereai.com/en/field-reports/observability-needs-cross-checks