Graylog2 / Graylog2/graylog2-server
When changing the value of the Override Sidecar configuration checkbox, sidecars may take up to 1 hour to consume this change
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
When changing the value of the Override Sidecar configuration checkbox, sidecars may take up to 1 hour to consume this change


Note the HTTP 202 once per hour. You can see towards the end of the graph that after i enabled "Override Sidecar configuration" and up to an hour elapsed, the new setting did apply and we have much more infrequent sidecar updates (once every 30s vs 10s).
## Expected Behavior
changing the value of the Override Sidecar configuration checkbox takes effect in near realtime. Not neccearily instantly, but not more than a minute or so.
## Current Behavior
changing the value of the Override Sidecar configuration checkbox takes up to 1 hour to have any effect.
## Possible Solution
My first thought here is this is a caching bug.
## Steps to Reproduce (for bugs)
1. Verify Override Sidecar configuration checkbox is unchecked
2. Setup/configure sidecar with all defaults. The sidecar will send an update once every 10s (default value)
3. Enable Override Sidecar configuration checkbox
4. Observe that sidecar will take up to 1 hour to apply this change
## Context
## Your Environment
* Graylog Version: Graylog 5.1.4+6fa2de3
* Java Version: Bundled
* OpenSearch Version: 2.9.0
* MongoDB Version: 6.9.0
* Operating System: Ubuntu Server 22.04 LTS
* Browser version: Google Chrome Version 116.0.5845.140 (Official Build) (arm64)
Please let me know if there are any questions.
Contributor guide
Assessment
This issue has not been assessed yet.