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 		2025-03-20 15:51:41 -07:00
..
agents	feat(agent): support multiple tool groups (#1556)	2025-03-17 22:13:09 -07:00
datasetio	fix: Call pandas.read_* in a seperate thread (#1698)	2025-03-19 10:46:37 -07:00
eval	feat(api): (1/n) datasets api clean up (#1573)	2025-03-17 16:55:45 -07:00
inference	fix: Updating ToolCall.arguments to allow for json strings that can be decoded on client side (#1685)	2025-03-19 10:36:19 -07:00
ios/inference	chore: removed executorch submodule (#1265)	2025-02-25 21:57:21 -08:00
post_training	chore: fix mypy violations in post_training modules (#1548)	2025-03-18 14:58:16 -07:00
safety	feat(agent): support multiple tool groups (#1556)	2025-03-17 22:13:09 -07:00
scoring	feat: [New Eval Benchamark] IfEval (#1708)	2025-03-19 16:39:59 -07:00
telemetry	feat: add different sinks for otel traces and metrics (#1731)	2025-03-20 15:51:41 -07:00
tool_runtime	chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711)	2025-03-20 10:01:10 -07:00
vector_io	chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711)	2025-03-20 10:01:10 -07:00
__init__.py	impls -> inline, adapters -> remote (#381)	2024-11-06 14:54:05 -08:00