A problem about dead action.

[leo1631]

A test turns bad when its dead action is out of schedule, the dead action will not be started. when the dead action's schedule is time, the test remain bad, but the dead action will still not be started.
How to start the dead action when its schedule is time?

Thanks.

[KS-Soft Europe]

As I understand, you have specified certain value in "Repeat N times" and enable appropriate checkbox (Action Properties window > Condition to start action group). I suppose, you have to enable "Repeat until status changes" checkbox to figure it out.

Regards,
Max

[leo1631]

As I understand, you have specified certain value in "Repeat N times" and enable appropriate checkbox (Action Properties window > Condition to start action group).

yes.

I suppose, you have to enable "Repeat until status changes" checkbox to figure it out.

I don't want to do that, cause I hope the bad action start just 1 times.

Actually I hope the test works like this:
1.It should monitor at 7 days 24 hours, cause I need the all_time reply data. I means the test's schedule is 7 days 24 hours.
2.When the test is bad at the time from 9 AM to 5 PM(when I'm in office), the bad action start, just 1 times.
3.When the test is bad at other time (when I'm at home), the bad action do not start. But if the test remain bad when I come to office(9 AM), I hope the bad action start and alert me.

All above can be control by test's schedule and action's schedule, except this:if the test remain bad when I come to office(9 AM), I hope the bad action start and alert me.
That is my problem!
Can HM do that? Is there any suggestion if it can not?

Thanks again.

[KS-Soft Europe]

Sorry, such type of alert is not implemented yet. But we would suggets you another solution. You should create two actions in your action profile for such test. One action to alert you at day time, another to set some "alert" flag, e.g. you may use "Record HM log" action to create specific log file for this purpose. Also you should setup "File Availability" test method to check for that log file at 9am and start alert (e.g. send failure log by e-mail) if file exists. Then remove the file (using second action with "Start when 2 consecutive Bad results occur" option).

This approach is not so clear, but it works

Regards,
Max

[leo1631]

Understand, Thank Max.

I think this function maybe needed by someone else also, hope it be implemented in future version.

Sorry for my poor English.

[thomasschmeidl]

Hello Leo1631, hello Max,

we have a similar setting as Leo1631 has.

The idea of an action to set the alert flag works indeed but it is not very straightforward.

PROPOSAL/WISH: A checkbox in the Action Properties dialog like "Delayed start of actions that are triggered out of schedule" ...

Kind regards

Thomas

[KS-Soft]

Yes, we have such task in our "to do" list. Medium priority

Regards
Alex

[thomasschmeidl]

Hi Alex,

thanks a lot for your prompt reply.

Just a question: How long are your todo-lists?

Kind regards

Thomas

[KS-Soft]

Over 200 items

Regards
Alex

[leo1631]

Hi Alex, about how long should I wait for until this item is implemented?

[KS-Soft]

Sorry, I don't know. We have a lot of tasks with medium priority. Some of them will be implemeneted next month, some - next year, others in 2008, 2009, 2010...

Regards
Alex

[thomasschmeidl]

Hi Alex,

maybe I found a workaround for the problem with the 'dead alerts'

Setting:
- There is a test (e.g a ping) that runs once a minute 7x24 (important for the statistics).
- There is an action (e-mail) triggered once after 5 recurrent bad tests. The action is scheduled 5x8
- If the ping fails during the night there will be no e-mail as the 5th test will have passed by when the schedule for the alarm is on.

Possible solution - some more actions:
1. An hms-script triggered once after 5 recurrent bad tests writing a comment like "e-Mail sent" into the comment line
2. An hms-script triggered once after 1 recurrent good tests clearing the comment line
3. An e-mail scheduled 5x8 in advanced mode: (%Recurrences% >5) AND ('%SimpleStatus%'=='DOWN') AND ('%CommentLine1%'=='')
4. An hms-script writing into the comment line (like action 1) scheduled 5x8 in advanced mode: (%Recurrences% >5) AND ('%SimpleStatus%'=='DOWN') AND ('%CommentLine1%'=='')

This solution obviously works, but it is dependent on the order of checking the action conditions. If the checking and execution for Action 3 and 4 are performed in this order it's ok. If they are checked / executed in order 4 - 3 it will not work.

Is there a way to determine the order of checking and execution?

Regards

Thomas

[KS-Soft]

I think HostMonitor version 6.10+ offers simpler solution

1) change "Repeat" option of the action from "Repeat: 1 time" to "Repeat until status changes"
2) add second action (Execute HM Script) into profile using the same "Start when", "Repeat until status changes" and "Time restriction" parameters. Add single command into script: "AckTestStatus %TestName% StopAlerts".
If you use the same test names for different tests in different folders, then you need to add another command (before "AckTestStatsu"): "SetCurrentFolder %FullPath%"

Regards
Alex

[thomasschmeidl]

thanx a lot for your reply.

I already thoght about this possibility, but "acknowledged" means in our department: "the admin knows about the problem and will solve it". You yourself recently stated, that it doesn't make much sense to produce acks by HM itself.

Anyway - is there an answer to my question?

Regards

Thomas

[thomasschmeidl]

thanx a lot for your reply.

I already thoght about this possibility, but "acknowledged" means in our department: "the admin knows about the problem and will fix it". You yourself recently stated, that it doesn't make much sense to produce acks by HM itself.

Anyway - is there an answer to my question?

Regards

Thomas