open-telemetry / open-telemetry/opentelemetry-python-contrib
Metric: gen_ai.server.time_to_first_token
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
What problem do you want to solve?
In Semantic Conventions 1.38.0, there is a standard definition for the TTFT (Time to First Transaction) metric in the metrics section. However, the current agent does not yet implement this metric. Is there any plan to implement this metric in the future? If not, what would be the approach to customizing the implementation of this metric?
Describe the solution you'd like
- Follow-up plan for achieving the TTFT metric.
- Developer's approach to customizing the TTFT metric.
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
None
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
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 reviewing Semantic Conventions 1.38.0 and the current agent support for gen_ai metrics. Clarify whether TTFT will be implemented and document the customization approach; done means the follow-up plan and developer guidance are agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100