Hello KS,
My apologies if this is already submitted or even implemented.
How about some general Action to take in case:
- Any test in any folder status is 'failed' - HM icon becoming red -
- And /or any test in a given folder only.
This would allows to easily replicate the 'red' status to a network of users on duty.
Hope you'll find this useful.
Any failed test > action
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Actually, there is a "Change icon when a host dies" option, located in "Options" -> "Preferences" tab. With this option enabled, HostMonitor will change icon from blue to red when any host changes status to "bad", or change color to yellow if a test goes to "Unknown" status.
Beside that, each folder has its own "Test statuses should not affect tray icon color" option, located in "Folder Properties" window -> "Specials" tab. As you know HostMonitor changes color of the tray icon when a test fails. This option allows you to make exception for set of test items.
Regards,
Max
Beside that, each folder has its own "Test statuses should not affect tray icon color" option, located in "Folder Properties" window -> "Specials" tab. As you know HostMonitor changes color of the tray icon when a test fails. This option allows you to make exception for set of test items.
Regards,
Max
Max,
Good explanation of the icon options, but I think Tizou may be, like me, looking for a little more. The statements regarding looking for
The folder level variables will make this easier, but I would love to be able to, independently, assign an action to a folder.
In my case I have a series of 'managers' folders, each with subfolders assigned to that manager's reporting technicians. If a technician doesn't acknowledge an alarm in a four hour window I would like the manager to receive an email warning about this fact.
Any advice?
Good explanation of the icon options, but I think Tizou may be, like me, looking for a little more. The statements regarding looking for
hint at something I have been trying to figure out how to best implement."a general Action to take in case. . ."
and
". . . replicate the 'red' status to a network of users on duty."
The folder level variables will make this easier, but I would love to be able to, independently, assign an action to a folder.
Code: Select all
If any test in this folder, and subfolders, not acknowledged in (timeframe)
then email %fvar_manager%
Any advice?

Any chance of implementing this sort of 'executive' alert? It's really the beginning of an escalation model - something every large implementation will expect sooner or later.
One for "non-acknowledged alerts > timeframe-1" and another for "any alert > timeframe-2"
As a bonus, on a large tree it would also be nice to have an audit report with an alert 'tree', revealing where there might be a breakdown in the escalation process.
In order to work smoothly to acommodate different level managers it seems that this would beg for inheritable, appendable folder level variables, so that a variable could be added further down the branch (something requested in an earlier post).
One for "non-acknowledged alerts > timeframe-1" and another for "any alert > timeframe-2"
As a bonus, on a large tree it would also be nice to have an audit report with an alert 'tree', revealing where there might be a breakdown in the escalation process.
In order to work smoothly to acommodate different level managers it seems that this would beg for inheritable, appendable folder level variables, so that a variable could be added further down the branch (something requested in an earlier post).
I have added your request into "to do" list but I am not sure when and how this can be implemented.
We can implement some variable like %TimeOfOldestNonAcknowledgedNadItemInTheFolder% but its not very flexible solution.. may be we add some folder-level alert options.. or implemend some functions instead of just variable, e.g. GetNumberOfNonAcknowledgedItems(foldername, timinterval, recursive)
Regards
Alex
We can implement some variable like %TimeOfOldestNonAcknowledgedNadItemInTheFolder% but its not very flexible solution.. may be we add some folder-level alert options.. or implemend some functions instead of just variable, e.g. GetNumberOfNonAcknowledgedItems(foldername, timinterval, recursive)
Regards
Alex
Alex,
Thanks. You're thinking along the same lines as I - a folder level property tied to a function. This kind of query should be relatively easy to construct against a database log. I'm thinking I could, in the interim, produce a daily report. I'll let you know how that goes.
BTW - I was impressed how well you handled another post from a particular BIG PURPLE poster. I wouldn't have been so calm & collected. Good Job!
Thanks. You're thinking along the same lines as I - a folder level property tied to a function. This kind of query should be relatively easy to construct against a database log. I'm thinking I could, in the interim, produce a daily report. I'll let you know how that goes.
BTW - I was impressed how well you handled another post from a particular BIG PURPLE poster. I wouldn't have been so calm & collected. Good Job!