Tracing

Page content

Distributed tracing is critical in microservice architectures to understand the lifecycle of a single request.

• The trace_id property: By attaching the same UUID or Hash as a trace_id to multiple events, Astralog links them together.

// Event from Frontend
{"service": "web-client", "message": "Checkout initiated", "trace_id": "txn-999"}
// Event from Backend
{"service": "api-server", "message": "Validating cart", "trace_id": "txn-999"}
// Event from Database Worker
{"service": "db-worker", "level": "error", "message": "Deadlock found", "trace_id": "txn-999"}

• Blast Radius & AI Context: When you trigger an Auto Root-Cause Analysis, Astralog queries the database for all preceding events that share the exact same trace_id. This allows the AI to understand the full journey and find the real culprit.