Zabbix Documentation 2.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:web_monitoring:items

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:web_monitoring:items [2014/09/25 14:23]
sasha Page moved from 2.0:manual:web_monitoring:items to manual:web_monitoring:items
manual:web_monitoring:items [2018/09/06 06:26] (current)
martins-v using correct function in example
Line 12: Line 12:
 |//Download speed for scenario <​Scenario>// ​ |This item will collect information about the download speed (bytes per second) of the whole scenario, i.e. average for all steps.\\ Item key: web.test.in[Scenario,,​bps]\\ Type: //​Numeric(float)// ​ | |//Download speed for scenario <​Scenario>// ​ |This item will collect information about the download speed (bytes per second) of the whole scenario, i.e. average for all steps.\\ Item key: web.test.in[Scenario,,​bps]\\ Type: //​Numeric(float)// ​ |
 |//Failed step of scenario <​Scenario>// ​ |This item will display the number of the step that failed on the scenario. If all steps are executed successfully,​ 0 is returned.\\ Item key: web.test.fail[Scenario]\\ Type: //​Numeric(unsigned)// ​ | |//Failed step of scenario <​Scenario>// ​ |This item will display the number of the step that failed on the scenario. If all steps are executed successfully,​ 0 is returned.\\ Item key: web.test.fail[Scenario]\\ Type: //​Numeric(unsigned)// ​ |
-|//Last error message of scenario <​Scenario>// ​ |This item returns the last error message text of the scenario.\\ Item key: web.test.error[Scenario] ​ |+|//Last error message of scenario <​Scenario>// ​ |This item returns the last error message text of the scenario. A new value is stored only if the scenario has a failed step. If all steps are ok, no new value is collected.\\ Item key: web.test.error[Scenario]\\ Type: //​Character// ​ |
  
 The actual scenario name will be used instead of "​Scenario"​. The actual scenario name will be used instead of "​Scenario"​.
Line 29: Line 29:
  
 == Example 2 == == Example 2 ==
 +
 +To create a "Web scenario failed"​ trigger with a useful problem description in the trigger name, you can define a trigger with name:
 +
 +  Web scenario "​Scenario"​ failed: {ITEM.VALUE}
 +
 +and trigger expression:
 +
 +  {host:​web.test.error[Scenario].strlen()}>​0 and {host:​web.test.fail[Scenario].last()}>​0
 +
 +Make sure to replace '​Scenario'​ with the real name of your scenario.
 +
 +== Example 3 ==
  
 To create a "Web application is slow" trigger, you can define a trigger expression: To create a "Web application is slow" trigger, you can define a trigger expression:
Line 42: Line 54:
 ^Item^Description^ ^Item^Description^
 |//Download speed for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect information about the download speed (bytes per second) of the step.\\ ​ Item key: web.test.in[Scenario,​Step,​bps]\\ ​ Type: //​Numeric(float)// ​ | |//Download speed for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect information about the download speed (bytes per second) of the step.\\ ​ Item key: web.test.in[Scenario,​Step,​bps]\\ ​ Type: //​Numeric(float)// ​ |
-|//Response time for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect information about the response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred.\\ ​ Item key: web.test.time[Scenario,​Step]\\ ​ Type: //​Numeric(float)// ​ |+|//Response time for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect information about the response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred.\\ ​ Item key: web.test.time[Scenario,​Step,resp]\\  Type: //​Numeric(float)// ​ |
 |//Response code for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect response codes of the step.\\ ​ Item key: web.test.rspcode[Scenario,​Step]\\ ​ Type: //​Numeric(unsigned)// ​ | |//Response code for step <​Step>​ of scenario <​Scenario>// ​ |This item will collect response codes of the step.\\ ​ Item key: web.test.rspcode[Scenario,​Step]\\ ​ Type: //​Numeric(unsigned)// ​ |
  
Line 51: Line 63:
 These items can be used to create triggers and define notification conditions. For example, to create a "​Zabbix GUI login is too slow" trigger, you can define a trigger expression: These items can be used to create triggers and define notification conditions. For example, to create a "​Zabbix GUI login is too slow" trigger, you can define a trigger expression:
  
-  {zabbix:​web.test.time[ZABBIX GUI,​Login].last(0)}>​3+  {zabbix:​web.test.time[ZABBIX GUI,Login,resp].last(0)}>​3