Job schedulers specification #2170
-
|
Hi there, my team is working on the transition from OpenTracing to OpenTelemetry standards within the company and we're in doubt about what should be the guidelines regarding span names and attributes for job schedulers (specifically, we're using Hangfire), That specification is something that is being worked on currently? If not, is there someone that wants to share their current customized implementation? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
As far as I know, there's nobody currently actively working on a specification for this. There's a group working on stabilizing messaging semantic conventions, however, job schedulers like Hangfire were defined as out-of-scope for that effort. This will likely be a separate semantic convention document. Some work on this was started, but was abandoned. If you want to start working on this, the abandoned PR might be a good starting point. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @pyohannes . I will take a look |
Beta Was this translation helpful? Give feedback.
As far as I know, there's nobody currently actively working on a specification for this.
There's a group working on stabilizing messaging semantic conventions, however, job schedulers like Hangfire were defined as out-of-scope for that effort.
This will likely be a separate semantic convention document. Some work on this was started, but was abandoned. If you want to start working on this, the abandoned PR might be a good starting point.