Skip to content

Observability FAQ

Answers to common questions about Observability measurements, charts, and the heatmap, grouped by topic. For questions about the checks themselves, see the FAQ of the Volumetric, Freshness, and Metric checks.

Tracking and Automation

Volume Tracking is on but no Volumetric checks appear. Why?

Volume Tracking records the measurements. Create AI Volumetric checks is what creates checks from them, and it needs enough history first: about a week for the 1 day check. Until then the card shows No observability checks. With the option off, no check appears however long you wait. Turn it on in the container's Observability Settings, or author a Volumetric check yourself.

When is the first daily measurement recorded?

The hourly cycle runs at minute 30 UTC, so the first one of a UTC day lands from 00:30 UTC on. A Scan or Profile that counts the container earlier in the day also records a row count, and the hourly cycle then skips it for volume that day.

What happens when I turn Volume Tracking off?

New hourly measurements stop, and Create AI Volumetric checks is turned off with it. Existing checks are kept. Scans and Profiles still record row counts, but days without one are missing from the history. The same applies to Freshness Tracking and Create AI Freshness checks.

Why does a measurement show on a different day than I expected?

The charts and the heatmap group measurements by calendar day in your browser's time zone, and show their times in that zone. The hourly cycle and the Volumetric check's history use UTC days. A measurement taken near midnight can therefore fall on one day on the chart and on the neighboring day in the check's history, or in an ETL log kept in another time zone.


Chart and Heatmap

Why is the heatmap grey for today but cyan for yesterday?

Grey means no measurement was recorded for that period yet. Today's square stays grey until the first successful measurement of the day lands.

What do the heatmap colors mean?

  • Cyan. A measurement was recorded, and the selected check raised no anomaly.
  • Orange. The selected check raised at least one anomaly in that period.
  • Grey. No measurement was recorded for that period.

The salmon color on the chart is separate: it marks a value outside the check's limits for which no anomaly was recorded.

Why is a point salmon when there is no anomaly?

Salmon means the value is outside the selected check's limits, but no anomaly was recorded for that period. Measurements never raise anomalies: only a Scan that evaluates the check does, so the usual cause is that no Scan ran. See Pair every chart with a scheduled Scan.

Why does a day have a row count but no freshness bar?

Each period shows its most recent measurement. When the last one of the day came from a Profile, or from a Scan that evaluated only Volumetric checks, it carries a row count but no last modification time. See How It Works.

My Metric chart shows "No measures" after two Scans. Why?

The chart needs two measurements for Absolute Value and three for Absolute Change or Percentage Change before it draws. Run another Scan, then reload the page.


Anomalies and Status

An anomaly appeared but the value on the chart looks fine. Why?

A change comparison judges the movement, not the value itself. For a Volumetric check, the baseline is the count one Measurement Period earlier, so a 7 day check compares with the same day last week, not with yesterday. For a Metric check, it is the previous Scan of the same read strategy. Hover the point to see the limits that applied to it.

My container's status changed to Inaccessible. What does that mean for Observability?

Three consecutive measurements failed, so the container was marked Inaccessible and the hourly cycle stopped measuring it. It does not retry on its own. Fix the access problem, then run a Sync on the datastore: a successful Sync that finds the container marks it Available, and the next hourly cycle measures it again. A Sync does not discover a Computed Table, Computed File, or Computed Join, so for those, open the container, click Edit, then Validate and Save its definition.


Explore and Navigation

Where do I see Observability across all my datastores at once?

The Explore section has an Observability page that lists containers and Metric checks across every datastore you can access.

Can I filter by Rule Type on the Metrics tab?

No. The Rule Type filter is only on the Measures tab, where Volumetric and Freshness checks share each card. The Metrics tab holds only Metric checks.

How do I keep a container or check at the top of the listing?

Click the Bookmark icon on its card. Favorites are per user, so yours do not affect anyone else. See Mark a Check as Favorite.