open-telemetry / open-telemetry/opentelemetry-php
SDK should collect OTel metrics by default
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 912
- Forks
- 232
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem?
Currently, tracing is the most mature signal we use in OTel-PHP. There are other use-cases where metrics are a desired outcome for users to use with analytics backends.
Describe the solution you'd like
Support the canonical metrics:
Describe alternatives you've considered
None
Additional context
Some of the metrics are not yet fully specified, but we should probably define first how they are best collected (for example SDK vs extension).
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 with the four linked OpenTelemetry semantic-conventions pages for HTTP, database, messaging, and RPC/gRPC metrics. Then investigate whether collection belongs in the SDK or a PHP extension, as the issue explicitly leaves that choice open. Done means the collection approach and scope are agreed, with support for the selected canonical metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100