Keep SigNoz as the telemetry source of truth.

What Tracey reads

Tracey uses bounded queries to discover agent runs, inspect traces, correlate logs and exceptions, compare metrics, and collect recovery evidence.

• Traces and span attributes
• Logs and exception events
• Latency, error-rate, and resource metrics
• Before-and-after health comparisons

Connection checklist

Configure the SigNoz endpoint and a credential with the least read access required for the workspace and services Tracey should investigate.

• Confirm the endpoint is reachable from the Tracey deployment
• Test trace, log, and metric queries independently
• Verify the service and environment names match emitted telemetry
• Record connector readiness and missing permissions

Bounded investigation flow

Tracey does not hand an unrestricted query surface to the model. The investigator selects bounded tools, applies time and result limits, and attaches the returned evidence to the investigation.

Question
  → bounded query plan
  → SigNoz traces / logs / metrics
  → normalized evidence
  → answer with sources and limitations

When data is missing

A failed query, incomplete span, or absent semantic field is reported as a limitation. Tracey should narrow the answer or ask for more evidence rather than fabricate a diagnosis.

SigNoz remains the system of record. Tracey stores bounded semantic summaries, investigations, policies, and audit history—not a replacement copy of raw telemetry.