open-telemetry / open-telemetry/opentelemetry-php
[opentelemetry-auto-symfony] missing console default root span creation
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 912
- Forks
- 232
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 4
Description
I am in the process of setting up open telemetry for a Symfony 6 project. Everything is working nicely so far. However I noticed that only for the HTTP kernel a default root span is being created. I have created a listener for the ConsoleCommandEvent, ConsoleErrorEvent, ... which handles the default root span myself for now.
Was this left out on purpose? I'm wondering if I should not be doing this.
For reference, the packages I'm currently depending on:
"open-telemetry/exporter-otlp": "^1.3",
"open-telemetry/opentelemetry-auto-doctrine": "^0.3.1",
"open-telemetry/opentelemetry-auto-symfony": "^1.1",
"open-telemetry/opentelemetry-logger-monolog": "^1.1",
"open-telemetry/sdk": "^1.9",
"open-telemetry/transport-grpc": "^1.1",
Thanks in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Symfony auto-instrumentation entry points for ConsoleCommandEvent and ConsoleErrorEvent, then compare their handling with the existing HTTP kernel root-span creation. Done means console commands create the expected default root span, with coverage for successful and error console events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, symfony
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100