KS-Soft

Hi Alex, I wanted to implement HM at a site but your offers do not fit our needs. Today we do have 57 tests so HM Standard would fit (a bit huge, but space do grow, we could put up with that). But we need 1 (one) RMA, rather liked to have 2. To pay 250$ for 10 is simply too much. Is there really no ...

Thank you very much, and

Happy New Year

If test status changed like Bad->WaitForMaster->Good then this is correct behavior. That's a pity. It's like you describe and the mails do give a wrong impression (to the manager) that the device has been 'up' in between because 1st mail says "down since 01:05:22" and the next mail (6 hou...

KS-Soft wrote:Do you mean it would be more easy?
But you still make expression for advanced action

Sure it was easier. Not the 'bad' action itself, but the good action. I would not need to program that dummy 'bad' action(s) that the good actions depend on.

They showed a %StatusChangedTime% of the last "'Wait' 2 'Good' change, not the last '"bad' 2 'good'" or '"good' 2 'bad'"change), they were fired when status went from 'wait' to 'good' etc. What settings do you use for the action? Have you checked Recurrences counter for thi...

I was already be OK with just being able to choose triggered 'advanced' bad actions to be a cause for 'good actions.
OK with you too?

Dear Alex, I am SO sorry and all is my fault. I should be more expressive. On the other hand I linked the post and KS-Europe (which will 'only' be a reseller, not you) proposed the stuff. Anyway, the 'advanced' bad actions KS-Europe proposed are not eligble to be used as 'bad' actions to depend on t...

Dear Alex, unluckily I deleted the "good" messages as they were trash. They showed a %StatusChangedTime% of the last "'Wait' 2 'Good' change, not the last '"bad' 2 'good'" or '"good' 2 'bad'"change), they were fired when status went from 'wait' to 'good' etc. Pleas...

Hi, we were glad there was an option if a test turning to 'Waiting for Master' or turning from it to good was handeled as if nothing at all had happened. That means - no overwriting of %StatusChangedTime% and other related macro variales - no triggering of 'good' actions - no other stuff that is mea...

@all I find some workaround: I set up a bad action 'execute external program' and execute the command 'REM' after the 10th consecutive bad. I then can use that action as reference for 'action depends on "bad" one. Should be fixed though, IMHO. Especially that triggering good actions when a...

Hi Alex, sorry if this has already been asked.* When defining a bad status action with 'advanced mode' such as in repeated alerts the alert action is not choosable for "action depends on "bad" one" condition in good status action. Please add, it makes 'advanced mode' pretty usele...

Dear Alex, you're the boss, just move the post, please, if you feel it more appropriate to be a wish. For us it comes out like a bug falsifying the order of events (i.e. making us check the log file each time which is additional work). You would not need to change any schedule if you either a) provi...

Hi, this is not exactly a bug but has the same effect: When checking logfiles (NT Event log, even more *nix logs) and having the setting AlertMode = AllEvents the mails are sent in such a short frequency (actually immediately after each other) that they get mixed up at mail servers (the order of the...

my sympathy, Alex.
But now just imagine the amount of emails without this forum! At least we often first search here...

pretty late to reply, huh?
But you could just "set okay status manually". I guess that option came later that this tread was 'closed'

@Alex: You might want to reply threads if their topic is 'fixed' (treated) by an enhancement you made.