[FEATURE] Add disable_auto_refresh config - #212
Open
mixturesolutions wants to merge 1 commit into
Open
Conversation
6 tasks
…a server config (default false) Signed-off-by: Iris Ye <iris.ye.cs@gmail.com>
mixturesolutions
force-pushed
the
feat/4295-disable-auto-refresh
branch
from
August 4, 2026 14:22
2e9c4cb to
e7d4d0f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds an optional admin config flag to centrally disable dashboard auto-refresh, addressing perses/perses#4295
Default: false (no behavior change unless explicitly enabled)
When enabled:
Note this is linked with another PR in the main perses repo
Screenshots
To enable, change in the respective perses config yaml file like the following:

Once the changes are deployed, config page will reflect the changes and the dashboard ui will look like:

Checklist
[<catalog_entry>] <commit message>naming convention using one of thefollowing
catalog_entryvalues:FEATURE,ENHANCEMENT,BUGFIX,BREAKINGCHANGE,DOC,IGNORE.UI Changes
See e2e docs for more details. Common issues include: