Im not sure if there was an update to our system recently, but a behavior change has left me stumped as to what to do.
Im usign I have a JSON dashboard for a series of log4j style service logs to gain visualisations on critical data. This dashboard Is a pretty standard faire, with a Global Time Range token, and derived from that i also decided I wanted to add a manual control to the dasboard so i can adjust the automatic refresh rate of each visualisation. I called it the global refresh rate. its a simple input.number with a 0 minimum, high maximum, and a default value of 300
At the time i found i could implement it by putting this code in the JSON code for the data sources.
right after the queryParameters field in my data sources.
This worked well enough, however recently I found i could no longer do this.
All existing visualisations function as they should, but if i try to change any of the data sources, it will no longer let me save changes without first removing the $global_refresh$ token - treating it as invalid. I also have found i cannout add it back in after removing the token.
Is this a bug? Is there a way around this? what changed that now prevents this from being done?
Because it would be nice to be able to control the refresh interval from the dashboard outside of the data source so that i can lower it if i need more frequent updates during times of high monitoring, and raise it when i only need periodic updates.
Hi @Jaryed
Please could you let me know which version of Splunk you are running so I can test this out and compare?
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing