There are no products in your shopping cart.
Service check goes into UNKNOWN state immediately
I am trying to monitor a couple Panasonic Projectors that use the PJLink protocol. The projectors lose network connection a couple times a day for about 30 seconds (this isn't a network issue but an issue with the device itself). This hasn't been a problem until one of them has gone into Critical mode (needs a new bulb) and has sat in that mode for a few weeks (we are waiting for the new year to buy a new bulb). We acknowledged the Critical alert but that is where we started noticing the problem.
It seems that while it takes X number of times for a service check to go into "notified" critical mode, because the projectors lose connection randomly the service check occasionally goes into UNKNOWN state as soon as one check can't contact the projector. Then when it "recovers" (i.e. successfully contacts the projector and sees that it is still in CRITICAL state) I get another alert and the acknowledgment goes away.
I suppose technically this is correct, but is there a way for me to work around that for these devices that have poor network connectivity? Would I would love is for a "soft UNKNOWN" state so that it doesn't clear acknowledgements until it has been in that unknown state for X number of checks. Kind of like the way something can go CRITICAL but I don't hear about it until it has stayed critical for X number of checks.
I know the "correct" solution is to fix the device, but since it is an internal issue I don't think we can do anything about it. I have looked and can't find any firmware updates (or even a way to update the firmware) so I think we are stuck with them.
I can acknowledge the item as sticky, but that requires me to remember to "unsticky" it when we do change the bulb. I can also schedule downtime, but since we don't know when the bulb will actually be replaced just yet I don't have a definite period of time to use.
Any suggestions would be appreciated, thanks!