After testing in a few environments I can say the monitors kick back the needed information. However, I can't find any possible way to throw an alert when the monitors haven't update in say, 10 minutes. In essence, a monitor (host) can go down completely and there's no alert. As long as the viewer sees the last update is in a good state it just keeps checking and getting that last update.
Is there a way to set an alert for when the host doesn't provide any updates at a scheduled interval?
In the setup on the web application you can set the "M.I.A." interval in the modify monitor page. This will cause the portal to tell the viewer when a monitor hasn't checked in after a certain amount of time.
Thanks Mike. After setting that in the web app and then creating a custom notification on each sensor that works.
Is there any way to set a default that when any sensors are M.I.A. an email is sent? Also, can the emails contain more information than just "# warning, # critical"?
The notifications are handled by the PortSensor viewer currently. Any sensors that report back as M.I.A. will cause a critical status and an email to be sent out like any other critical sensor would, unless you manually created custom notifications on the sensor to override this behavior.
As for more details in the emails, we did previously have more of a breakdown of the status of the sensors but we ended up simplifying it since oftentimes people use the notification emails for notifications to their phone and a small concise message is usually sufficient to get you to check the actual viewer, or status on the portal. Still, it's something we could consider bringing back in a simpler fashion.
Even if it would just send what the sensor name is that would be much more useful. Like you mentioned, I receive this on my phone and it's fair to say that most techs can receive a good amount of text in emails on their smart phones ;)
Is there anything I can adjust to at least get the sensor name? Or the monitor name?
