This appears to have been a bug ever since I plugged the setting into the prometheus codec.
It should be set directly from the querier engine config.
The frontend v2 config also sets it from the original source, the querier engine config. Since this codec module gets initialized before the frontend v2 config setting does, by referencing the uninitialized config value, it always ends up zero instead of the real value.
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
[ ] Tests updated.
[ ] Documentation added.
[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
What this PR does
This appears to have been a bug ever since I plugged the setting into the prometheus codec.
It should be set directly from the querier engine config. The frontend v2 config also sets it from the original source, the querier engine config. Since this codec module gets initialized before the frontend v2 config setting does, by referencing the uninitialized config value, it always ends up zero instead of the real value.
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX].about-versioning.mdupdated with experimental features.