influxdata / influxdata/influxdb
INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS doesn't filter logs
Open
A pull request for this has already been merged.
- #27312 by @gwossum — merged
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Steps to reproduce:
- start influxdb by docker image 1.7.7 with ENVs:
- INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_0: "4xx"
- INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_1: "5xx"
- send there any data
- logs contains
rappahw [httpd] 10.0.0.13 - mydb [09/Oct/2019:08:07:57 +0000] "POST /write?db=mydb&p=%5BREDACTED%5D&precision=n&rp=&u=test HTTP/1.1" 204 0 "-" "-" e792484f-eb6b-11e9-820b-03420aff0011 2260
Expected behavior:
Logs should contains request with responses 4xx or 5xx.
Actual behavior:
Logs contains all https logs.
Environment info:
- System info: Influx is running in docker, Host OS: Linux 4.19.0-5-amd64 x86_64
- InfluxDB version: InfluxDB v1.7.7 (git: 1.7 f8fdf652f348fc9980997fe1c972e2b79ddd13b0)
- Other relevant environment details: Docker 19.03.1
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 by reproducing the behavior with the Docker image and the INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_0 and _1 environment variables. Check the HTTP access-log filtering entry point using a request that returns 204 and requests returning 4xx or 5xx. Done means only responses matching the configured status filters appear in the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100