influxdata / influxdata/influxdb
Log client information in HTTP requests
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
### Problem
The logs for incoming HTTP requests do not emit any information about the client making the request.
### Proposed solution
Determine where client information, e.g., `influxdb-client-python/1.36.1`, is included in incoming requests (headers?) and capture/emit that in the logs.
### Additional context
See [slack thread](https://influxdata.slack.com/archives/C084G9LR2HL/p1745536848493959).
Contributor guide
Research direction
Start by locating where incoming HTTP requests are logged and determine which request header contains client information such as `influxdb-client-python/1.36.1`. Done means the incoming-request logs emit that client information; the issue does not name a file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100