ehhuang e58c7f6c37 fix(telemetry): root span not yet received (#1828) ... # What does this PR do? closes #1725 In https://github.com/meta-llama/llama-stack/pull/1759's attempt to make trace_id consistent in llama stack and otel exports, it incorrectly sets the span_id in context, which causes the root span to have a parent ID, leading to the issue in #1725. This PR reverts #1759's change to set the parent context. We will need to follow up with a proper way to do this. ## Test Plan <img width="1868" alt="image" src="https://github.com/user-attachments/assets/15e9ac18-8541-461d-b261-c4e124388cc3" />		2025-03-28 14:40:17 -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	chore: Revert "chore(telemetry): remove service_name entirely" (#1785)	2025-03-25 14:42:05 -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	feat: use same trace ids in stack and otel (#1759)	2025-03-21 15:41:26 -07:00
telemetry.py	fix(telemetry): root span not yet received (#1828)	2025-03-28 14:40:17 -07:00