Return to Answer

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state, the trigger will generate alert.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].sum(#3)}>0 

This trigger will work with any step counts of your web scenario. It sends PROBLEM alert at first failed test and sends OK restore alert after three consecutive successful checks (180 secs after service was fully restored).

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state or value more than 0, the trigger will generate PROBLEM alert.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].sum(#3)}>0 

This trigger will work with any step counts of your web scenario. It sends PROBLEM alert at first failed test and sends OK restore alert after three consecutive successful checks (180 secs after service was fully restored).

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state, the trigger will not generate alert. To check reachability of the host use a ping check.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].last()}>0 and {hosts1:web.test.fail[test.example.com].last(#1)}>0 and {hosts1:web.test.fail[test.example.com].last(#2)}>0 

This trigger will work with any step counts of your web scenario.

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state, the trigger will generate alert.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].sum(#3)}>0 

This trigger will work with any step counts of your web scenario. It sends PROBLEM alert at first failed test and sends OK restore alert after three consecutive successful checks (180 secs after service was fully restored).

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable or web service is down.

If the trigger expression will return UNKNOWN state, the trigger will not generate alert. To check reachability of the host use a ping check.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].last()}>0 and {hosts1:web.test.fail[test.example.com].last(#1)}>0 and {hosts1:web.test.fail[test.example.com].last(#2)}>0 

This trigger will work with any step counts of your web scenario.

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

• 0 - OK. The web scenario test.example.com (all steps) was tested successfully;
• 1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
• UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state, the trigger will not generate alert. To check reachability of the host use a ping check.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].last()}>0 and {hosts1:web.test.fail[test.example.com].last(#1)}>0 and {hosts1:web.test.fail[test.example.com].last(#2)}>0 

This trigger will work with any step counts of your web scenario.