Zabbix Documentation 5.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:items:preprocessing

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:config:items:preprocessing [2020/02/13 09:45]
martins-v some rewording
manual:config:items:preprocessing [2020/02/21 11:16] (current)
martins-v better wording
Line 82: Line 82:
 |//Previous value// ​ |Enter a previous input value to compare to.\\ Only for //Change// and //​Throttling//​ preprocessing steps. ​ | |//Previous value// ​ |Enter a previous input value to compare to.\\ Only for //Change// and //​Throttling//​ preprocessing steps. ​ |
 |//Previous time// ​ |Enter the previous input value time to compare to.\\ Only for //Change// and //​Throttling//​ preprocessing steps.\\ The default value is based on the '​Update interval'​ field value of the item (if '​1m',​ then this field is filled with ''​now-1m''​). If nothing is specified or user has no access to host, the default is ''​now-30s''​. ​ | |//Previous time// ​ |Enter the previous input value time to compare to.\\ Only for //Change// and //​Throttling//​ preprocessing steps.\\ The default value is based on the '​Update interval'​ field value of the item (if '​1m',​ then this field is filled with ''​now-1m''​). If nothing is specified or user has no access to host, the default is ''​now-30s''​. ​ |
-|//​Macros// ​ |If any macros are used, they are listed along with their values. The values are editable for testing purposes, but the changes will only be saved within the testing context.\\ If non-existing or non-accessible (because of permissions) macro names are used, the macro values are editable within the testing context as well.  |+|//​Macros// ​ |If any macros are used, they are listed along with their values. The values are editable for testing purposes, but the changes will only be saved within the testing context. ​ |
 |//End of line sequence// ​ |Select the end of line sequence for multiline input values:\\ **LF** - LF (line feed) sequence\\ **CRLF** - CRLF (carriage-return line-feed) sequence. ​ | |//End of line sequence// ​ |Select the end of line sequence for multiline input values:\\ **LF** - LF (line feed) sequence\\ **CRLF** - CRLF (carriage-return line-feed) sequence. ​ |
 |//​Preprocessing steps// ​ |Preprocessing steps are listed; the testing result is displayed for each step after the //Test// button is clicked.\\ If the step failed in testing, an error icon is displayed. The error description is displayed on mouseover.\\ In case "​Custom on fail" is specified for the step and that action is performed, a new line appears right after the preprocessing test step row, showing what action was done and what outcome it produced (error or value). ​ | |//​Preprocessing steps// ​ |Preprocessing steps are listed; the testing result is displayed for each step after the //Test// button is clicked.\\ If the step failed in testing, an error icon is displayed. The error description is displayed on mouseover.\\ In case "​Custom on fail" is specified for the step and that action is performed, a new line appears right after the preprocessing test step row, showing what action was done and what outcome it produced (error or value). ​ |
Line 93: Line 93:
 The testing is done by Zabbix server. The frontend sends a corresponding request to the server and waits for the result. The request contains the input value and preprocessing steps (with expanded user macros). For //Change// and //​Throttling//​ steps, an optional previous value and time can be specified. The server responds with results for each preprocessing step.  The testing is done by Zabbix server. The frontend sends a corresponding request to the server and waits for the result. The request contains the input value and preprocessing steps (with expanded user macros). For //Change// and //​Throttling//​ steps, an optional previous value and time can be specified. The server responds with results for each preprocessing step. 
  
-Technical connection ​errors are displayed ​as error box at the top of the testing window.+All technical errors or input validations ​errors are displayed ​in the error box at the top of the testing window.
  
 == Testing real value == == Testing real value ==
Line 100: Line 100:
  
   * Mark the //Get value from host// checkbox   * Mark the //Get value from host// checkbox
-  * Make sure the host interface ​fields are correct (should be automatically ​filled) +  * Enter or verify ​host parameters (host address, port, proxy name/no proxy). These fields are context aware: 
-  Click on //Get value// ​to get a real value in the //​Value// ​field+    * The values are pre-filled ​when possible, i.e. for items requiring an agent, by taking the information from the selected agent interface of the host 
 +    The values have to be filled manually for template items 
 +    * The field are disabled when not needed ​in the context of the item type (e.g. the host address ​field is disabled for calculated and aggregate items, the proxy field is disabled for calculated items)
   * Click on //Get value and test// to test the preprocessing   * Click on //Get value and test// to test the preprocessing