influxdata / influxdata/influxdb
Zap-Trace-Span is probably not used anymore
Open
area/api
area/client
area/HTTP
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
If I remember well the `Zap-Trace-Span` is something added when we tried tracing via logs.
Are we sure this is still usual? It is a requirement we expose via API and via Swagger, so it means documentation and generated code as a consequence.
@nathanielc were you involved?
Contributor guide
Research direction
Start by searching the API and Swagger definitions for `Zap-Trace-Span`, then check whether the requirement is still used by the tracing or logging paths. Done means confirming its status and, if obsolete, removing the API requirement together with the affected documentation and generated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100