Hi! The Autorefresh of every page every xx minutes is driving me crazy today. I'm researching some events by viewing the event log and I keep loosing my place because the autorefresh keeps taking me back to the beginning. Can we get a PAUSE button? Here are some suggestions. (I can see this rolling out in multiple phases.)
1) Add a standard <pause refresh> button that is available on every view & show the current refresh frequency for the page. If pressed, the pause would only be effective for the current user/session.
2) Add a miscellaneous resource for views that contains a <pause refresh> button that impacts the entire page. (This would be my 2nd choice, as I do not want to have to update all of our views.)
3) For each view design,allow an override to the default autorefresh (e.g., no refresh, a different frequency, or default autorefresh (show the default value-greyed out)). If no refresh is chosen, the user can use IE's refresh button.
Why? I would use this on several views that I've created in NPM or SAM that show historical information, plus the events page, reports, etc. that do not need to be refreshed very often (if at all). By refreshing them today, the user loses their place while viewing multiple page/scrolling data. Also, I have some historical node disk statistic data that times out a lot when it loads. And this thwart page is refreshing while I'm typing this idea. Urgh!! I'm typing in the tags and it scrolls up and places my cursor back in the text. So now I'm typing in the wrong area!
Phase 3 & beyond
4) Allow a refresh override for each resource on the page. Some may be historical information that needs updated less frequently than the entire page.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.