Zabbix Documentation 4.2

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:config:macros:lld_macros

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:lld_macros [2018/08/22 05:31]
martins-v lld macros are supported in lld rule filter
manual:config:macros:lld_macros [2019/01/10 06:18] (current)
martins-v more precise wording
Line 7: Line 7:
   {#​MACRO} ​   {#​MACRO} ​
  
-It is a macro that is used in an LLD rule and returns real values of file system names, network interfaces ​and SNMP OIDs.+It is a macro that is used in an LLD rule and returns real values of file system names, network interfacesSNMP OIDs, etc.
  
 These macros can be used for creating item, trigger and graph //​prototypes//​. Then, when discovering real file systems, network interfaces etc., these macros are substituted with real values and are the basis for creating real items, triggers and graphs. These macros can be used for creating item, trigger and graph //​prototypes//​. Then, when discovering real file systems, network interfaces etc., these macros are substituted with real values and are the basis for creating real items, triggers and graphs.
Line 27: Line 27:
     * history storage periods     * history storage periods
     * trend storage periods     * trend storage periods
 +    * item value preprocessing steps
     * SNMP OIDs     * SNMP OIDs
     * IPMI sensor fields     * IPMI sensor fields
Line 34: Line 35:
     * JMX item endpoint fields     * JMX item endpoint fields
     * descriptions     * descriptions
-    ​* since Zabbix 4.0 also in: +    * HTTP agent URL field 
-      * item value preprocessing steps +    * HTTP agent HTTP query fields field 
-      ​* HTTP agent URL field +    * HTTP agent request body field 
-      * HTTP agent HTTP query fields field +    * HTTP agent required status codes field 
-      * HTTP agent request body field +    * HTTP agent headers field key and value 
-      * HTTP agent required status codes field +    * HTTP agent HTTP authentication username field 
-      * HTTP agent headers field key and value +    * HTTP agent HTTP authentication password field 
-      * HTTP agent HTTP authentication username field +    * HTTP agent HTTP proxy field 
-      * HTTP agent HTTP authentication password field +    * HTTP agent HTTP SSL certificate file field 
-      * HTTP agent HTTP proxy field +    * HTTP agent HTTP SSL key file field 
-      * HTTP agent HTTP SSL certificate file field +    * HTTP agent HTTP SSL key password field 
-      * HTTP agent HTTP SSL key file field +    * HTTP agent HTTP timeout field
-      * HTTP agent HTTP SSL key password field +
-      * HTTP agent HTTP timeout field+
   * for trigger prototypes in   * for trigger prototypes in
     * names     * names
-    * expressions+    * expression (only in constants and function parameters)
     * URLs     * URLs
     * descriptions     * descriptions
Line 66: Line 65:
 === Using macro functions === === Using macro functions ===
  
-Macro functions are supported with low-level discovery macros, allowing to extract a certain part of the macro value using a regular expression.+Macro functions are supported with low-level discovery macros ​(except in low-level discovery rule filter), allowing to extract a certain part of the macro value using a regular expression.
  
 For example, you may want to extract the customer name and interface number from the following LLD macro for the purposes of event tagging: For example, you may want to extract the customer name and interface number from the following LLD macro for the purposes of event tagging:
Line 79: Line 78:
  
 Macro functions are supported in low-level discovery macros since Zabbix 4.0. Macro functions are supported in low-level discovery macros since Zabbix 4.0.
-