hashicorp / hashicorp/vault-helm
helm value server.logLevel does not set the log level but just logs all entries using this value
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
Tried to make the Vault server less chatty by reducing the log level to warn, but instead of logging less entries, the very same entries are logged now with level warn instead of info. Tried the same with error with same result.
Example log entry
```json
{
"@level": "error",
"@message": "completed_request",
"@module": "core",
"@timestamp": "2024-01-23T08:59:05.550149Z",
"client_address": "172.16.14.48:60886",
"client_id": "",
"duration": "1ms",
"request_method": "GET",
"request_path": "/v1/brix/data/engine",
"start_time": "2024-01-23T08:59:05Z",
"status_code": 200
}
```
The helm value injector.logLevel works as expected though.
Vault version: 1.15.2
Chart version: 0.27.0
Contributor guide
Research direction
Start by comparing how the Helm chart handles the server.logLevel and injector.logLevel values, using the reported Vault 1.15.2 and chart 0.27.0 setup. Reproduce the configuration with warn or error and verify that server entries below the selected level are filtered rather than merely relabeled; done means server.logLevel behaves like injector.logLevel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100