-
Notifications
You must be signed in to change notification settings - Fork 2k
Add IDs to all observability signals #15223
Copy link
Copy link
Closed
Labels
Observability (AI Telemetry)Issues related to AI related Observability/Telemetry (Traces, Metrics, Logs)Issues related to AI related Observability/Telemetry (Traces, Metrics, Logs)TelemetryIssues surrounding observability via OTELIssues surrounding observability via OTELeffort:mediumimpact:hightrio-tracery
Metadata
Metadata
Assignees
Labels
Observability (AI Telemetry)Issues related to AI related Observability/Telemetry (Traces, Metrics, Logs)Issues related to AI related Observability/Telemetry (Traces, Metrics, Logs)TelemetryIssues surrounding observability via OTELIssues surrounding observability via OTELeffort:mediumimpact:hightrio-tracery
Add unique IDs to all observability signals, created at event emission time.
Spans already have unique IDs (traceId + spanId)
But we should create unique IDs for each log, metric, score, feedback, etc..
LogId would ideally use the same format as logId in otel...if a standard exists.
Others can be just uuids.
Primary use case today is use as a de-duplication key in our OLAP stores, but also can help with linking signals to other systems.