llama-stack/llama_stack/providers/inline/telemetry/meta_reference
Dinesh Yeduguru 6104bd06a0
feat: add different sinks for otel traces and metrics (#1731)
# What does this PR do?
Since we now start recording and exporting metrics, we no longer can use
single OTEL endpoint to export both traces and metrics. This PR adds two
sinks: OTEL_TRACE and OTEL_METRIC to be able to selectively enable the
exporters.

## Test Plan
Start server with OTEL_TRACE as sink and verify traces show up in jaeger
![Screenshot 2025-03-20 at 3 12
25 PM](https://github.com/user-attachments/assets/51007f28-b5ed-4853-912a-965a5cfe83af)
2025-03-20 15:51:41 -07:00
..
__init__.py chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711) 2025-03-20 10:01:10 -07:00
config.py feat: add different sinks for otel traces and metrics (#1731) 2025-03-20 15:51:41 -07:00
console_span_processor.py chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711) 2025-03-20 10:01:10 -07:00
sqlite_span_processor.py refactor: move all datetime.now() calls to UTC (#1589) 2025-03-13 15:34:53 -07:00
telemetry.py feat: add different sinks for otel traces and metrics (#1731) 2025-03-20 15:51:41 -07:00