typelevel / typelevel/natchez-http4s
OpenTelemetry Semantic Conventions
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 50
- Forks
- 18
- Avg merge
- 15m
- Merged PRs (30d)
- 5
Description
Should the trace attributes added by this library follow OpenTelemetry semantic conventions? For example, https://github.com/typelevel/natchez-http4s/blob/659d412e0c7287dbb074ce49e58cec6599e40f83/modules/http4s/src/main/scala/natchez/http4s/NatchezMiddleware.scala#L176-L177 should be url.full and http.request.method, respectively, and https://github.com/typelevel/natchez-http4s/blob/659d412e0c7287dbb074ce49e58cec6599e40f83/modules/http4s/src/main/scala/natchez/http4s/NatchezMiddleware.scala#L183 should be http.response.status_code.
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 in modules/http4s/src/main/scala/natchez/http4s/NatchezMiddleware.scala at lines 176-177 and 183, and compare the emitted trace attributes with the linked OpenTelemetry semantic-convention pages. Determine whether the library's trace attributes should use the named URL and HTTP keys, then verify that the affected attributes consistently follow those conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100