traceloop / traceloop/openllmetry
🚀 Feature: Provide more attributes for drill down to application
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this feature for?
All Packages
🔖 Feature description
The attributes of metrics and traces are able to provide the process name, hostname and etc., making it easy to identify the application and host where performance issues are occurring, that's helpful for monitoring multiple applications.
🎤 Why is this feature needed ?
If monitoring detects an issue, I need a clear view of the application, such as application name and hostname.
✌️ How do you aim to achieve this?
I can have the enough information from metrics or traces to easily drill down the detected issues to applications.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None
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
The issue names no files, tests, or entry points. Begin by mapping how metrics and traces currently expose attributes across All Packages, then identify where application name and hostname information would need to be available. Done means metrics or traces provide enough application-identifying information to drill down from a detected issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100