Zabbix Documentation 3.2

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

User Tools

Site Tools


manual:config:macros:usermacros

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:macros:usermacros [2016/01/11 10:28]
asaveljevs [Example 4] added a third example filesystem and better trigger practice
manual:config:macros:usermacros [2017/04/26 12:45] (current)
martins-v more precise wording
Line 1: Line 1:
-==== User macros ====+==== User macros ====
  
 === Overview === === Overview ===
  
-For greater flexibility, ​Zabbix supports user macros, which can be defined on global, template and host level. These macros have a special syntax: **{$MACRO}**. An optional context can be used in user macros, allowing ​to override default value with context specific one. User macros ​with context have similar syntax**{$MACRO:​context}**.+User macros are supported in Zabbix for greater flexibility,​ in addition ​to the macros ​[[:manual/​appendix/​macros/​supported_by_location|supported]] out-of-the-box
  
-The macros can be used in:+User macros can be defined on global, template and host level. These macros have a special syntax:  
 + 
 +  {$MACRO} 
 + 
 +User macros can be used in:
  
   * item names   * item names
   * item key parameters ​   * item key parameters ​
   * trigger names and descriptions   * trigger names and descriptions
-  * trigger expression parameters and constants (see examples) +  * trigger expression parameters and constants (see [[#examples|examples]]
-  * several ​other [[manual:appendix:macros:supported_by_location#​additional_support_for_user_macros|locations]]+  * many other locations (see [[:manual/appendix/macros/supported_by_location|Macros supported by location]])
  
 The following characters are allowed in the macro names: **A-Z** , **0-9** , **_** , **.** The following characters are allowed in the macro names: **A-Z** , **0-9** , **_** , **.**
Line 20: Line 24:
   - macros defined for first level templates of the host (i.e., templates linked directly to the host), sorted by template ID   - macros defined for first level templates of the host (i.e., templates linked directly to the host), sorted by template ID
   - macros defined for second level templates of the host, sorted by template ID   - macros defined for second level templates of the host, sorted by template ID
-  - macros defined for third level templates of the host, sorted by template ID +  - macros defined for third level templates of the host, sorted by template ID, etc.
-  - ...+
   - global macros (checked last)   - global macros (checked last)
  
Line 34: Line 37:
 <note tip>If a user macro is used in items or triggers in a template, it is suggested to add that macro to the template even if it is defined on a global level. That way, exporting the template to XML and importing it in another system will still allow it to work as expected.</​note>​ <note tip>If a user macro is used in items or triggers in a template, it is suggested to add that macro to the template even if it is defined on a global level. That way, exporting the template to XML and importing it in another system will still allow it to work as expected.</​note>​
  
-**Most common ​use cases of global and host macros:**+== Common ​use cases of global and host macros ​==
  
-  ​- taking ​advantage of templates with host specific attributes: passwords, port numbers, file names, regular expressions,​ etc +  ​* take advantage of templates with host-specific attributes: passwords, port numbers, file names, regular expressions,​ etc. 
-  ​global macros for global one-click configuration changes and fine tuning+  ​* apply global macros for global one-click configuration changes and fine tuning
  
-=== Macro context === 
- 
-Macro context is a simple text value. The common use case for macro contexts would be using LLD macro value as a user macro context. For example, a trigger prototype could be defined for mounted file system discovery to use different low space limit depending on mount points or file system types. 
- 
-Only discovery macros are supported in macro contexts. Any other macros are ignored and treated as plain text. 
- 
-Technically,​ macro context is specified using rules similar to [[manual:​config:​items:​item:​key|item key]] parameters, except macro context is not parsed as several parameters if there is a '',''​ character: 
- 
-  * Macro context is quoted with ''"''​ if context contains ''​}''​ character or starts with ''"''​ character. Quotes inside quoted macros must be escaped with ''​\''​ character. The ''​\''​ character itself is not escaped, which means it's impossible to have quoted macro ending with ''​\''​ character - the macro ''​{$MACRO:"​a:​\b\c\"​}''​ is invalid. 
-  * The leading spaces in context are ignored, the trailing spaces are not. For example ''​{$MACRO:​A}''​ is the same as ''​{$MACRO:​ A}'',​ but not ''​{$MACRO:​A }''​. 
-  * All spaces before leading quotes and after trailing quotes are ignored, but all spaces inside quotes are not. Macros ''​{$MACRO:"​A"​}'',​ ''​{$MACRO:​ "​A"​}'',​ ''​{$MACRO:"​A"​ }''​ and ''​{$MACRO:​ "​A"​ }''​ are the same, but macros ''​{$MACRO:"​A"​}''​ and ''​{$MACRO:"​ A "​}''​ are not. 
- 
-The following macros are all equivalent, because they have the same context: ''​{$MACRO:​A}'',​ ''​{$MACRO:​ A}''​ and ''​{$MACRO:"​A"​}''​. This is in contrast with item keys, where ''​key[a]'',​ ''​key[ a]''​ and ''​key["​a"​]''​ are the same semantically,​ but different for uniqueness purposes. 
- 
-When context macros are processed, Zabbix looks up the macro with its context. If a macro with this context is not defined by host or linked templates, and it is not a defined as global macro with context, then the macro without context is searched for. 
 === Examples === === Examples ===
  
Line 84: Line 72:
 <note important>​In trigger expressions user macros will resolve if referencing a parameter or constant. They will NOT resolve if referencing the host, item key, function, operator or another trigger expression.</​note>​ <note important>​In trigger expressions user macros will resolve if referencing a parameter or constant. They will NOT resolve if referencing the host, item key, function, operator or another trigger expression.</​note>​
  
-== Example 4 == +=== User macro context === 
-Set the free disk space trigger prototype for a host to:+ 
 +An optional context can be used in user macros, allowing to override ​the default value with context-specific one.  
 + 
 +User macros with context have a similar syntax:  
 + 
 +  {$MACRO:​context}  
 + 
 +Macro context is a simple text value. The common use case for macro contexts would be using a low-level discovery [[:​manual/​discovery/​low_level_discovery#​using_lld_macros_in_user_macro_contexts|macro value]] as a user macro context. For example, a trigger prototype ​could be defined ​for mounted file system discovery to use different low space limit depending on the mount points or file system types. 
 + 
 +Only low-level discovery macros are supported in macro contexts. Any other macros are ignored and treated as plain text. 
 + 
 +Technically,​ macro context is specified using rules similar ​to [[manual:​config:​items:​item:​key|item key]] parameters, except macro context is not parsed as several parameters if there is a '',''​ character:​ 
 + 
 +  * Macro context must be quoted with ''<​nowiki>"</​nowiki>''​ if the context contains a ''​}''​ character or starts with a ''<​nowiki>"</​nowiki>''​ character. Quotes inside quoted context must be escaped with the ''​\''​ character. The ''​\''​ character itself is not escaped, which means it's impossible to have a quoted context ending with the ''​\''​ character - the macro ''​{$MACRO:<​nowiki>"</​nowiki>​a:​\b\c\<​nowiki>"</​nowiki>​}''​ is invalid. 
 +  * The leading spaces in context are ignored, the trailing spaces are not. For example ''​{$MACRO:​A}''​ is the same as ''​{$MACRO:​ A}'',​ but not ''​{$MACRO:​A }''​. 
 +  * All spaces before leading quotes and after trailing quotes are ignored, but all spaces inside quotes are not. Macros ''​{$MACRO:<​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​}'',​ ''​{$MACRO:​ <​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​}'',​ ''​{$MACRO:<​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​ }''​ and ''​{$MACRO:​ <​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​ }''​ are the same, but macros ''​{$MACRO:<​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​}''​ and ''​{$MACRO:<​nowiki>"</​nowiki>​ A <​nowiki>"</​nowiki>​}''​ are not.
  
-''​{ca_001:vfs.fs.size[{#​FSNAME},pfree].last()}<{$LOW_SPACE_LIMIT:#FSNAME}''​+The following macros are all equivalent, because they have the same context: ​''​{$MACRO:A}''​''​{$MACRO:​ A}''​ and ''​{$MACRO:<​nowiki>"</​nowiki>​A<​nowiki>"</​nowiki>​}''​. This is in contrast with item keys, where ''​key[a]'',​ ''​key[ a]''​ and ''​key[<​nowiki>"</​nowiki>​a<​nowiki>"</​nowiki>​]''​ are the same semantically,​ but different for uniqueness purposes.
  
-Add macros+When context ​macros ​are processed, Zabbix looks up the macro with its context. If a macro with this context is not defined by host or linked templates, and it is not a defined as a global macro with context, then the macro without context is searched for.
-  * ''​{$LOW_SPACE_LIMIT}''​ **10** +
-  * ''​{$LOW_SPACE_LIMIT:/​tmp}''​ **50**+
  
-If, for example, the mounted file system discovery discovered filesystems ''/'',​ ''/​home''​ and ''/​tmp'',​ then events will be created when ''/''​ and ''/​home''​ filesystems have less than **10**% ​of free disk space or ''/​tmp''​ filesystem has less than **50**% of free disk space.+See [[manual:​discovery:​low_level_discovery#​using_lld_macros_in_user_macro_contexts|usage ​example]] of macro context in a disk space trigger prototype and take limitation clause into consideration