Zabbix Documentation 4.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:config:items:item

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:config:items:item [2019/07/17 07:53]
martins-v removing duplicated jsonpath examples
manual:config:items:item [2019/08/14 12:44] (current)
martins-v 'custom on fail' supported in 'check for error...' steps
Line 107: Line 107:
 |:::​|//​Matches regular expression// ​ |Specify a regular expression that a value must match.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message. ​ | |:::​|//​Matches regular expression// ​ |Specify a regular expression that a value must match.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message. ​ |
 |:::|//Does not match regular expression// ​ |Specify a regular expression that a value must not match.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message. ​ | |:::|//Does not match regular expression// ​ |Specify a regular expression that a value must not match.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message. ​ |
-|:::​|//​Check for error in JSON// ​ |Check for an application-level error message located at JSONpath. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ No error will be reported in case of failing to parse invalid JSON.  | +|:::​|//​Check for error in JSON// ​ |Check for an application-level error message located at JSONpath. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ No error will be reported in case of failing to parse invalid JSON.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.  | 
-|:::​|//​Check for error in XML//  |Check for an application-level error message located at xpath. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ No error will be reported in case of failing to parse invalid XML.  | +|:::​|//​Check for error in XML//  |Check for an application-level error message located at xpath. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ No error will be reported in case of failing to parse invalid XML.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.  | 
-|:::​|//​Check for error using a regular expression// ​ |Check for an application-level error message using a regular expression. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ Parameters:​\\ **pattern** - regular expression\\ **output** - output formatting template. An \N (where N=1…9) escape sequence is replaced with the Nth matched group. A \0 escape sequence is replaced with the matched text.  |+|:::​|//​Check for error using a regular expression// ​ |Check for an application-level error message using a regular expression. Stop processing if succeeded and message is not empty; otherwise continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to user as is, without adding preprocessing step information.\\ Parameters:​\\ **pattern** - regular expression\\ **output** - output formatting template. An \N (where N=1…9) escape sequence is replaced with the Nth matched group. A \0 escape sequence is replaced with the matched text.\\ If you mark the //Custom on fail// checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.  |
 ^Throttling ​ ^^^ ^Throttling ​ ^^^
 |   ​|//​Discard unchanged// ​ |Discard a value if it has not changed.\\ Only one throttling option can be specified for an item.  | |   ​|//​Discard unchanged// ​ |Discard a value if it has not changed.\\ Only one throttling option can be specified for an item.  |