Then please read my previous answers and simply add 1 more action into profile
Regards
Alex
Time restricted test does not returns to regular work
Yes, that will work, but I didn't wanted to stop future notifications after the first alert.
If my profile set to notify some1 at the first time and, in case if after some time problem wasn't solved yet, it supposed to send "escalation" alert - that will not work in the way you proposed.
Btw, there are one more strange thing happens: when I use autoacknowledge - the good action of send mail, which is configured to be dependent on the "send mail" from the bad actions, sending mail always, even if no bad status mail was sent.
Regards,
Gluk.
If my profile set to notify some1 at the first time and, in case if after some time problem wasn't solved yet, it supposed to send "escalation" alert - that will not work in the way you proposed.
Btw, there are one more strange thing happens: when I use autoacknowledge - the good action of send mail, which is configured to be dependent on the "send mail" from the bad actions, sending mail always, even if no bad status mail was sent.
Regards,
Gluk.
Then "deffered action" option will not help you either. The only option that should work for you - Schedule assigned to the testIf my profile set to notify some1 at the first time and, in case if after some time problem wasn't solved yet, it supposed to send "escalation" alert - that will not work in the way you proposed
http://www.ks-soft.net/hostmon.eng/mfra ... ofiles.htm
Regards
Alex
Using schedule on the whole test will leave me without any info about what happened with that test during non-working hours.
Thats why I use schedule only on alerting action.
Unfortunately, in my view, it doesn't works according to action rules.
I think you need either fix that or, at least, explain me whats wrong in my understanding of the action rules and what is the logic behind its current behaviour.
And, what is about this issue that while I use autoacknowledge, action which supposed to send "good mail" and dependent on the "send bad mail", yes sending mail during time restriction interval, although no "bad mail" was sent?
Regards,
Gluk.
Thats why I use schedule only on alerting action.
Unfortunately, in my view, it doesn't works according to action rules.
I think you need either fix that or, at least, explain me whats wrong in my understanding of the action rules and what is the logic behind its current behaviour.
And, what is about this issue that while I use autoacknowledge, action which supposed to send "good mail" and dependent on the "send bad mail", yes sending mail during time restriction interval, although no "bad mail" was sent?
Regards,
Gluk.
Using schedule on the whole test will leave me without any info about what happened with that test during non-working hours
You need 2 test items - one for statistics, another for alerts. Yes, its not nice solution. So we will improve HostMonitor.
I told you 5 times, but you are not listening at all. Please read my previous posts.I think you need either fix that or, at least, explain me whats wrong in my understanding of the action rules and what is the logic behind its current behaviour
And, what is about this issue that while I use autoacknowledge, action which supposed to send "good mail" and dependent on the "send bad mail", yes sending mail during time restriction interval, although no "bad mail" was sent?
Here you probably right. This behaviour should be changed
Regards
Alex
From my point of view there are already 3 continuous failures done, therefore Mail should be send at 6am just when time schedule becomes active.Gluk wrote:3. On 6am, "Time Restriction" supposed to trigger "Send Mail" action ON and after it detected 3 continious failures - it supposed to send mail.
To the rest I agree. That is the way I'd like to have it too.
Thats true too but, action of sending alert was supposed to be stopped by "time restriction", so if each action dependent on the number of failed tests since it starts, it will only start counting failures at 6am.From my point of view there are already 3 continuous failures done, therefore Mail should be send at 6am just when time schedule becomes active.
Although for me it seems more logical to have all actions dependent on the single failures counter of the test and work according to it.
But the point is that according to any logic mail have to be sent and the fact is that it doesn't.
Maybe this feature may help:
Implemented since 7.00 Beta
Implemented since 7.00 Beta
JuergenNew feature: Deferred actions. "Time restriction" option allows you to suppress action execution depending on time of the day and/or day of the week. Additional "Deferred action" option tells HostMonitor to delay action execution if specified schedule does not allow immediate execution of the action. HostMonitor will execute action at the beginning of "allowed" time frame on condition that status of the test is identical to status that triggered alert.
Note1: If the same test triggers the same action several times within "restricted" time frame, HostMonitor will execute action just once at the beginning of "allowed" time frame.
Note2: When HostMonitor starts deferred (delayed) action, macro variables will be resolved with using of current (up to date) test status, current date and time, current status of HostMonitor, etc.
Note3: HostMonitor considers the following statuses as identical
- Bad = Bad contents = No answer
- Ok = Host is alive = Normal
- Unknown = Unknown host
Also "Warning" status can be considered as identical to "Bad" when "Treat Warning status as Bad" option of the test item is enabled. The same is true for "Unknown" and "Unknown host" statuses when "Treat Unknown status as Bad" option is enabled.