elsa-workflows / elsa-workflows/elsa-core
Align open telemetry library with semantic conventions
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
## Enhancement Request
### Enhancement Overview
**Is your enhancement request related to a problem? Please describe.**
I want my elsa workflow to be generating telemetry based upon definitions in Open Telemetry Semantic conventions.
### Proposed Enhancement
**Describe the enhancement you'd like**
Attribute keys are updated to reflect semconv
### Alternative Solutions
**Describe alternatives you've considered**
Have you explored any workarounds or other features that provide similar functionality? Please share your findings, including why these alternatives do not meet your needs fully. This helps us understand the unique value of your proposed enhancement.
### Use Cases
**Identify potential use cases**
Anyone looking at telemetry.
### Impact of Enhancement
**Explain the potential impact**
It would help to provide guidance and alignment on minimum needs while also allowing ideas from other solutions to be leveraged over time.
### Additional Context
**Add any other context**
I am already working on the open telemetry definitions https://github.com/open-telemetry/semantic-conventions/pull/2387 and will be in a position to contribute the changes here.
https://github.com/elsa-workflows/elsa-core/issues/5988
Contributor guide
Assessment
This issue has not been assessed yet.