What it checks

Telemetry linting runs on the data already in Loggerhead. It looks at the last window of logs, metrics, and spans and lists findings on the Improvements page. Each finding has an impact, a plain explanation, and an action.

The checks

Finding	Impact	What it means
Noisy log line	Medium	One log line dominates the volume. It costs money and hides the lines that matter.
Mostly low-signal logs	Low	Most records are DEBUG or TRACE with no fields. They add little in production.
Error logs missing trace context	High	Error records carry no trace ID, so they cannot link to the request that failed.
Possible sensitive data	High	A log field looks like an email address, a token, or a card number.
Flatlined metric	Medium	A metric is always zero. The instrument may be wired wrong.
Stale metric	Medium	A metric has no recent data points. The exporter may have stopped.
Duplicate metrics	Low	Two metric names carry the same series. Keep one.
High-cardinality label	High	A label has thousands of values, such as a raw URL path. It blows up storage on any platform.
Sustained error rate with no alert	High	A service has kept an error rate up with no alert rule on it.

When it runs

The engine evaluates the window on a schedule and when you open the Improvements page. Findings merge across runs, so a finding keeps its state while the problem persists and clears when the problem goes away.

AI insight

With an AI provider configured in Settings, Analyse with AI sends the rule findings and a summary of the window to the model and adds insight findings with a plain-language explanation. The API key stays in the macOS Keychain. See Settings.