On the refresh value, this was an unintentionally broad change.
CSP sadly catches the META HTTP-EQUIV "Refresh" tag as well as something that is no longer honored, which requires moving it up into the actual HTTP headers. This updated version of the CSP patch (from the last email) does two things:
- separate out info and trends pages from "regular" svcstatus pages. The former won't be auto-refreshed
- adds a previously-referenced XYMWEBREFRESH variable, which can be used to configure this (default: 60s)
Going from 60s to 30s was an error on my part. I'd actually thought that was the value for some reason...
On info pages not allowing _targets, that's also something caught by CSP. The patch should fix this as well. Please verify if you can.
Regards, -jc
On Wed, February 10, 2016 2:02 pm, John Thurston wrote:
On 2/10/2016 12:44 PM, Matt Vander Werf wrote:
- snip -
I very much disagree with the idea of having to hit F5 every so often to see a refreshed Xymon page, rather then it refreshing automatically.
If I have a Xymon page up on a monitor and then I am working on something else on another monitor, I don't want to have to go over to the browser on the other monitor and hit F5 every so often to refresh the page. I'd much rather it refresh every so often automatically, so then I just have to look over at the monitor every so often to look for any changes.
Where exactly are you seeing this refresh change (just curious)?
This refresh has been moved from the _meta_ content of the svchosts page the HTTP _header_ . As such, "view source" will no longer reveal it.
Why wouldn't you want it to refresh automatically? Isn't the idea to get the most up-to-date info possible?
Not in all cases. I want the general pages of hosts (like xymon.html) to refresh periodically, but there is no need to have them auto-refresh faster than I am running xymongen.
The issue I see is specifically with the "info" page produced by svcstatus.sh. I have it open when I'm studying a host for a specific reason. I would prefer that page not auto-refresh while I'm studying it trying to figure out a problem. If I want new information, I can refresh it. I might even want to keep it frozen and open a new copy in a new tab so I could compare the past and the present.
Does anyone put a single host's "info" page on a screen and leave it there for general monitoring? If so, why? What problem does it solve that looking at the parent page of hosts does not?
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon