What is the point of forcing an immediate check of a passive check? It's not going to know what to check. It just goes to an OK status with a message of "No data received yet." Is there something useful in there that I'm missing?
If not, is there an easy way to hide "Force an Immediate Check" for passive checks?
Passive Checks & Forcing Immediate Checks
Re: Passive Checks & Forcing Immediate Checks
No, you're not missing anything. I think we just never added logic to remove that particular button from service checks that are passive only. I'll drop in a feature request for this, and see if we can get it added at some point.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Passive Checks & Forcing Immediate Checks
Excellent, thanks!
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Passive Checks & Forcing Immediate Checks
Locking threadcstuart wrote:Excellent, thanks!