Synchronize Counters

[xcentric]

Synchronize Counters

I want to get a clearer picture of when or when not to use this option.

When is it a good or bad idea to punish dependent statistics if a master fails?

I would imagine remote network internal tests should not be synchronized while external tests into the network should be synchronized.

5 websites should synchronize if the router's ping fails.
But the internal tests should not. Or should they?

Since the internal tests cannot be checked because the master is down it would be logical that the dependent statistics reflect unknown?

If this is the case then I guess I should be using an expression to set unknown status of dependents if the master fails. Also, can I prevent 5 unknown dependents from firing their actions?

I am trying to understand but sometimes I get a headache with all the possibilities. Much like thinking about time travel paradoxes.

Oh word of the wise I summon thee.

Regards

[KS-Soft]

I think its up to your accountant
If you provide (or rent) some service and you do not want to collect (or pay) money when web site is not accessible, you don't care about the reason why exactly server is not accessible. You just know it does not work so you don't have to pay money. Then you may enable "Synchronize counters" option.
When you want to see statistics for the server itself excluding some general network problems, disable this option.

Also, can I prevent 5 unknown dependents from firing their actions?

Simply keep "Synchronize status&alerts" option disabled.

Regards
Alex

[xcentric]

Ok, thanks for putting it that way. It makes sense.

Now I want to combine "synchronize counters" and "treat unknown status as bad" in the following example but I cannot see how it can be done.

For "bad" AND "unknown" status I want to be alerted. However in order to do this I have to select "treat unknown status as bad". Ok, fine. But now my counters do not show the status as unknown. Instead the unknown status now affects the bad counter. Of course this behavior is by design. That is what the option if for.

The million dollar question.
How do I preserve a test's unknown counters "where the status is unknown" and receive alerts at the same time without treating unknown status as bad?
As far as I can tell only "bad" statuses can trigger actions.

[KS-Soft Europe]

How do I preserve a test's unknown counters "where the status is unknown" and receive alerts at the same time without treating unknown status as bad?
As far as I can tell only "bad" statuses can trigger actions.

You may use Advanced mode actions for such tests.
E.g. Expression for such action may look like the following:
('%SimpleStatus%'<>'UP') AND (%Recurrences%<2)

Please check the manual or visit our web site for more information at:
http://www.ks-soft.net/hostmon.eng/mfra ... ncedaction

[xcentric]

And we have a winner!!!

Thank you so much. I could not see the forest through all those trees.

Regards