# 10 Macros # 10 Macros #### 10 Map In the map element you can display a configured network map. To configure, select *Map* as resource:  You may set the following specific options: | | | |---|---| |*Map*|Select the map to display.| #### 10 Map In the map element you can display a configured network map. To configure, select *Map* as resource:  You may set the following specific options: | | | |---|---| |*Map*|Select the map to display.| # 10 Services # 10 Services # 11. Maintenance # 11. Maintenance #### 11 Plain text In the plain text element you can display latest item data in plain text. To configure, select *Plain text* as resource:  You may set the following specific options: | | | |---|---| |*Item*|Select the item.| |*Show lines*|Set how many latest data lines will be displayed in the screen cell.| |*Show text as HTML*|Set to display text as HTML.| |*Dynamic item*|Set to display different data depending on the selected host.| #### 11 Plain text In the plain text element you can display latest item data in plain text. To configure, select *Plain text* as resource:  You may set the following specific options: | | | |---|---| |*Item*|Select the item.| |*Show lines*|Set how many latest data lines will be displayed in the screen cell.| |*Show text as HTML*|Set to display text as HTML.| |*Dynamic item*|Set to display different data depending on the selected host.| #### 12 Screen In the screen element you can display another Zabbix screen. One screen may contain other screens inside. To configure, select *Screen* as resource:  You may set the following specific options: | | | |---|---| |*Screen*|Select the screen to display.| #### 12 Screen In the screen element you can display another Zabbix screen. One screen may contain other screens inside. To configure, select *Screen* as resource:  You may set the following specific options: | | | |---|---| |*Screen*|Select the screen to display.| #### 13 Simple graph In the simple graph element you can display a single simple graph. To configure, select *Simple graph* as resource:  You may set the following specific options: | | | |---|---| |*Item*|Select the item for the simple graph.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| #### 13 Simple graph In the simple graph element you can display a single simple graph. To configure, select *Simple graph* as resource:  You may set the following specific options: | | | |---|---| |*Item*|Select the item for the simple graph.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| # 13 Supported JSONPath functionality ::: noteimportant The full JSONPath functionality as described in this page is available starting with Zabbix 4.0.11. ::: # 13 Supported JSONPath functionality ::: noteimportant The full JSONPath functionality as described in this page is available starting with Zabbix 4.0.11. ::: # 14. Configuration export/import # 14. Configuration export/import #### 14 Simple graph prototype In the simple graph prototype element you can display a simple graph based on an item generated by low-level discovery. To configure, select *Simple graph prototype* as resource:  You may set the following specific options: | | | |---|---| |*Item prototype*|Select the item prototype for the simple graph.| |*Max columns*|In how many columns generated graphs should be displayed in the screen cell.<br>Useful when there are many LLD-generated graphs.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| #### 14 Simple graph prototype In the simple graph prototype element you can display a simple graph based on an item generated by low-level discovery. To configure, select *Simple graph prototype* as resource:  You may set the following specific options: | | | |---|---| |*Item prototype*|Select the item prototype for the simple graph.| |*Max columns*|In how many columns generated graphs should be displayed in the screen cell.<br>Useful when there are many LLD-generated graphs.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| #### 15 System information In the system information element you can display high-level Zabbix and Zabbix server information. To configure, select *System information* as resource:  #### 15 System information In the system information element you can display high-level Zabbix and Zabbix server information. To configure, select *System information* as resource:  # 15 What's new in Zabbix 4.0.10 # 15 What's new in Zabbix 4.0.10 #### 16 Problems by severity In this element you can display problems by severity similarly as in the Dashboard widget. To configure, select *Problems by severity* as resource:  #### 16 Problems by severity In this element you can display problems by severity similarly as in the Dashboard widget. To configure, select *Problems by severity* as resource:  # 16 What's new in Zabbix 4.0.11 # 16 What's new in Zabbix 4.0.11 #### 17 Trigger info In the trigger info element you can display high-level information about trigger states. To configure, select *Trigger info* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select the host group(s).| |*Style*|Select vertical or horizontal display.| #### 17 Trigger info In the trigger info element you can display high-level information about trigger states. To configure, select *Trigger info* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select the host group(s).| |*Style*|Select vertical or horizontal display.| # 17 What's new in Zabbix 4.0.12 # 17 What's new in Zabbix 4.0.12 #### 18 Trigger overview In the trigger overview element you can display the trigger states for a group of hosts. It replicates information from *Monitoring → Overview* (when *Triggers* is selected as Type there). To configure, select *Trigger overview* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select the host group(s).| |*Application*|Enter the application name.| |*Hosts location*|Select host location - left or top.| #### 18 Trigger overview In the trigger overview element you can display the trigger states for a group of hosts. It replicates information from *Monitoring → Overview* (when *Triggers* is selected as Type there). To configure, select *Trigger overview* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select the host group(s).| |*Application*|Enter the application name.| |*Hosts location*|Select host location - left or top.| # 18 Upgrade notes for 4.0.9 This minor version does not have any upgrade notes. # 18 Upgrade notes for 4.0.9 This minor version does not have any upgrade notes. # 18 What's new in Zabbix 4.0.13 # 18 What's new in Zabbix 4.0.13 # 19. API # 19. API # 19 Upgrade notes for 4.0.10 This minor version does not have any upgrade notes. # 19 Upgrade notes for 4.0.10 This minor version does not have any upgrade notes. #### 19 URL The URL element displays the content retrieved from the specified URL. To configure, select *URL* as resource:  You may set the following specific options: | | | |---|---| |*URL*|Enter the URL to display. Relative paths are allowed since Zabbix 4.0.20.| |*Width*|Select window width.| |*Height*|Select window width.| |*Dynamic item*|Set to display different URL content depending on the selected host.| ::: noteimportant Browsers might not load an HTTP page included in a screen (using URL element), if Zabbix frontend is accessed over HTTPS. ::: #### 19 URL The URL element displays the content retrieved from the specified URL. To configure, select *URL* as resource:  You may set the following specific options: | | | |---|---| |*URL*|Enter the URL to display. Relative paths are allowed since Zabbix 4.0.20.| |*Width*|Select window width.| |*Height*|Select window width.| |*Dynamic item*|Set to display different URL content depending on the selected host.| ::: noteimportant Browsers might not load an HTTP page included in a screen (using URL element), if Zabbix frontend is accessed over HTTPS. ::: # 19 What's new in Zabbix 4.0.14 # 19 What's new in Zabbix 4.0.14 #### 1 Action log In the action log element you can display details of action operations (notifications, remote commands). It replicates information from *Reports → Audit*. To configure, select *Action log* as resource:  All mandatory input fields are marked with a red asterisk. You may set the following specific options: | | | |---|---| |*Show lines*|Set how many action log lines will be displayed in the screen cell.| |*Sort entries by*|Sort entries by:<br>**Time** (descending or ascending)<br>**Type** (descending or ascending)<br>**Status** (descending or ascending)<br>**Recipient** (descending or ascending).| #### 1 Action log In the action log element you can display details of action operations (notifications, remote commands). It replicates information from *Reports → Audit*. To configure, select *Action log* as resource:  All mandatory input fields are marked with a red asterisk. You may set the following specific options: | | | |---|---| |*Show lines*|Set how many action log lines will be displayed in the screen cell.| |*Sort entries by*|Sort entries by:<br>**Time** (descending or ascending)<br>**Type** (descending or ascending)<br>**Status** (descending or ascending)<br>**Recipient** (descending or ascending).| # 1 Applications # 1 Applications # 1 Conditions # 1 Conditions # 1 Configuring a network map # 1 Configuring a network map # 1 Discovery of mounted filesystems # 1 Discovery of mounted filesystems # 1 E-mail # 1 E-mail # 1 Graphs # 1 Graphs # 1 Red Hat Enterprise Linux/CentOS # 1 Red Hat Enterprise Linux/CentOS # 1 Red Hat Enterprise Linux/CentOS # 1 Red Hat Enterprise Linux/CentOS # 1 Screen elements # 1 Screen elements # 1 Simple graphs # 1 Simple graphs # 1 VMware monitoring item keys # 1 VMware monitoring item keys # 20 Upgrade notes for 4.0.11 This minor version does not have any upgrade notes. # 20 Upgrade notes for 4.0.11 This minor version does not have any upgrade notes. # 20 What's new in Zabbix 4.0.15 # 20 What's new in Zabbix 4.0.15 # 21 Upgrade notes for 4.0.12 # 21 Upgrade notes for 4.0.12 # 21 What's new in Zabbix 4.0.16 # 21 What's new in Zabbix 4.0.16 # 22 Upgrade notes for 4.0.13 # 22 Upgrade notes for 4.0.13 # 22 What's new in Zabbix 4.0.17 # 22 What's new in Zabbix 4.0.17 # 23 Upgrade notes for 4.0.14 # 23 Upgrade notes for 4.0.14 # 23 What's new in Zabbix 4.0.18 # 23 What's new in Zabbix 4.0.18 # 24 Upgrade notes for 4.0.15 This minor version does not have any upgrade notes. # 24 Upgrade notes for 4.0.15 This minor version does not have any upgrade notes. # 24 What's new in Zabbix 4.0.19 # 24 What's new in Zabbix 4.0.19 # 25 Upgrade notes for 4.0.16 # 25 Upgrade notes for 4.0.16 # 25 What's new in Zabbix 4.0.20 # 25 What's new in Zabbix 4.0.20 # 26 Upgrade notes for 4.0.17 # 26 Upgrade notes for 4.0.17 # 26 What's new in Zabbix 4.0.21 # 26 What's new in Zabbix 4.0.21 # 27 Upgrade notes for 4.0.18 # 27 Upgrade notes for 4.0.18 # 27 What's new in Zabbix 4.0.22 # 27 What's new in Zabbix 4.0.22 # 28 Upgrade notes for 4.0.19 This minor version does not have any upgrade notes. # 28 Upgrade notes for 4.0.19 This minor version does not have any upgrade notes. # 28 What's new in Zabbix 4.0.23 # 28 What's new in Zabbix 4.0.23 # 29 Upgrade notes for 4.0.20 # 29 Upgrade notes for 4.0.20 # 29 What's new in Zabbix 4.0.24 This minor version contains no functional changes. # 29 What's new in Zabbix 4.0.24 This minor version contains no functional changes. # 2 Actions # 2 Actions # 2 Agent # 2 Agent #### 2 Clock In the clock element you may display local, server or specified host time. To configure, select *Clock* as resource:  You may set the following specific options: | | | |---|---| |*Time type*|Select local, server or specified host time.| |*Item*|Select the item for displaying time. To display host time, use the `system.localtime[local]` item. This item must exist on the host.<br>This field is available only when *Host time* is selected.| |*Width*|Select clock width.| |*Height*|Select clock height.| #### 2 Clock In the clock element you may display local, server or specified host time. To configure, select *Clock* as resource:  You may set the following specific options: | | | |---|---| |*Time type*|Select local, server or specified host time.| |*Item*|Select the item for displaying time. To display host time, use the `system.localtime[local]` item. This item must exist on the host.<br>This field is available only when *Host time* is selected.| |*Width*|Select clock width.| |*Height*|Select clock height.| # 2 Custom graphs # 2 Custom graphs # 2 Debian/Ubuntu # 2 Debian/Ubuntu # 2 Host group elements # 2 Host group elements # 2 Installation # 2 Installation # 2 Network maps # 2 Network maps # 2 Repairing Zabbix database character set and collation # 2 Repairing Zabbix database character set and collation # 2 SMS # 2 SMS # 30 Upgrade notes for 4.0.21 This minor version has no upgrade notes. # 30 Upgrade notes for 4.0.21 This minor version has no upgrade notes. # 30 What's new in Zabbix 4.0.25 # 30 What's new in Zabbix 4.0.25 # 31 Upgrade notes for 4.0.22 # 31 Upgrade notes for 4.0.22 # 31 What's new in Zabbix 4.0.26 This minor version contains no functional changes. # 31 What's new in Zabbix 4.0.26 This minor version contains no functional changes. # 32 Upgrade notes for 4.0.23 This minor version does not have any upgrade notes. # 32 Upgrade notes for 4.0.23 This minor version does not have any upgrade notes. # 32 What's new in Zabbix 4.0.27 # 32 What's new in Zabbix 4.0.27 # 33 Upgrade notes for 4.0.24 This minor version does not have any upgrade notes. # 33 Upgrade notes for 4.0.24 This minor version does not have any upgrade notes. # 33 What's new in Zabbix 4.0.28 # 33 What's new in Zabbix 4.0.28 # 34 Upgrade notes for 4.0.25 This minor version does not have any upgrade notes. # 34 Upgrade notes for 4.0.25 This minor version does not have any upgrade notes. # 34 What's new in Zabbix 4.0.29 This minor version does not have any functional changes. # 34 What's new in Zabbix 4.0.29 This minor version does not have any functional changes. # 35 Upgrade notes for 4.0.26 # 35 Upgrade notes for 4.0.26 # 35 What's new in Zabbix 4.0.30 This minor version does not have any functional changes. # 35 What's new in Zabbix 4.0.30 This minor version does not have any functional changes. # 36 Upgrade notes for 4.0.27 # 36 Upgrade notes for 4.0.27 # 36 What's new in Zabbix 4.0.31 This minor version does not have any functional changes. # 36 What's new in Zabbix 4.0.31 This minor version does not have any functional changes. # 37 Upgrade notes for 4.0.28 # 37 Upgrade notes for 4.0.28 # 37 What's new in Zabbix 4.0.32 # 37 What's new in Zabbix 4.0.32 # 38 What's new in Zabbix 4.0.33 This minor version does not have any functional changes. # 38 What's new in Zabbix 4.0.33 This minor version does not have any functional changes. # 39 What's new in Zabbix 4.0.34 # 39 What's new in Zabbix 4.0.34 # 3 Ad-hoc graphs # 3 Ad-hoc graphs #### 3 Data overview In the data overview element you can display the latest data for a group of hosts. It replicates information from *Monitoring → Overview* (when *Data* is selected as Type there). To configure, select *Data overview* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group.| |*Application*|Enter application name.| |*Hosts location*|Select host location - left or top.| #### 3 Data overview In the data overview element you can display the latest data for a group of hosts. It replicates information from *Monitoring → Overview* (when *Data* is selected as Type there). To configure, select *Data overview* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group.| |*Application*|Enter application name.| |*Hosts location*|Select host location - left or top.| # 3 Jabber # 3 Jabber # 3 Link indicators # 3 Link indicators # 3 Proxy # 3 Proxy # 3 Screens # 3 Screens ### 4.0.13 ### 4.0.13 ### 4.0.16 ### 4.0.16 ### 4.0.2 ### 4.0.2 ### 4.0.7 ### 4.0.7 ### 4.0.8 ### 4.0.8 # 4 Audit # 4 Audit # 4 Configuration # 4 Configuration # 4 Ez Texting # 4 Ez Texting #### 4 Graph In the graph element you can display a single custom graph. To configure, select *Graph* as resource:  You may set the following specific options: | | | |---|---| |*Graph*|Select the graph to display.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| #### 4 Graph In the graph element you can display a single custom graph. To configure, select *Graph* as resource:  You may set the following specific options: | | | |---|---| |*Graph*|Select the graph to display.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| # 4 Maintenance # 4 Maintenance # 4 Slide shows # 4 Slide shows # 4 Update operations # 4 Update operations # 4 Web # 4 Web # 5 Actions # 5 Actions # 5 Administration # 5 Administration #### 5 Graph prototype In the graph prototype element you can display a custom graph from a low-level discovery rule. To configure, select *Graph prototype* as resource:  You may set the following specific options: | | | |---|---| |*Graph prototype*|Select the graph prototype to display.| |*Max columns*|In how many columns generated graphs should be displayed in the screen cell.<br>Useful when there are many LLD-generated graphs.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| #### 5 Graph prototype In the graph prototype element you can display a custom graph from a low-level discovery rule. To configure, select *Graph prototype* as resource:  You may set the following specific options: | | | |---|---| |*Graph prototype*|Select the graph prototype to display.| |*Max columns*|In how many columns generated graphs should be displayed in the screen cell.<br>Useful when there are many LLD-generated graphs.| |*Width*|Select graph width.<br>Note that a line graph may actually take up more space due to legend text.| |*Height*|Select graph height.<br>Note that a line graph may actually take up more space due to legend text.| |*Dynamic item*|Set graph to display different data depending on the selected host.| # 5 Host screens # 5 Host screens # 5 Running Agent as root Starting with version **4.0.15** systemd service file for Zabbix agent in official packages (<https://www.zabbix.com/download>) was updated to explicitly include directives for `User` and `Group`. Both are set to `zabbix`. This means that old functionality of configuring which user Zabbix agent runs as via `zabbix_agentd.conf` file is bypassed and agent will always run as the user specified in the systemd service file. To override this new behavior create file `/etc/systemd/system/zabbix-agent.service.d/override.conf` with the following content. [Service] User=root Group=root Reload daemons and restart zabbix-agent service. systemctl daemon-reload systemctl restart zabbix-agent For **agent2** this completely determines the user that it runs as. For old **agent** this only re-enables the functionality of configuring user in `zabbix_agentd.conf` file. Therefore in order to run zabbix agent as root you still have to edit `zabbix_agentd.conf` and specify `User=root` as well as `AllowRoot=1` options. More on this here: <https://www.zabbix.com/documentation/4.0/manual/appendix/config/zabbix_agentd>. # 5 Running Agent as root Starting with version **4.0.15** systemd service file for Zabbix agent in official packages (<https://www.zabbix.com/download>) was updated to explicitly include directives for `User` and `Group`. Both are set to `zabbix`. This means that old functionality of configuring which user Zabbix agent runs as via `zabbix_agentd.conf` file is bypassed and agent will always run as the user specified in the systemd service file. To override this new behavior create file `/etc/systemd/system/zabbix-agent.service.d/override.conf` with the following content. [Service] User=root Group=root Reload daemons and restart zabbix-agent service. systemctl daemon-reload systemctl restart zabbix-agent For **agent2** this completely determines the user that it runs as. For old **agent** this only re-enables the functionality of configuring user in `zabbix_agentd.conf` file. Therefore in order to run zabbix agent as root you still have to edit `zabbix_agentd.conf` and specify `User=root` as well as `AllowRoot=1` options. More on this here: <https://www.zabbix.com/documentation/4.0/manual/appendix/config/zabbix_agentd>. # 5 Sender # 5 Sender # 6 Get # 6 Get #### 6 History of events In the history of events element you can display latest events. To configure, select *History of events* as resource:  You may set the following specific option: | | | |---|---| |*Show lines*|Set how many event lines will be displayed in the screen cell.| #### 6 History of events In the history of events element you can display latest events. To configure, select *History of events* as resource:  You may set the following specific option: | | | |---|---| |*Show lines*|Set how many event lines will be displayed in the screen cell.| # 6 Notifications # 6 Notifications # 6 Visualization # 6 Visualization # 7 Additional frontend languages # 7 Additional frontend languages #### 7 Host group issues In the host group issue element you can display problem details filtered by the selected host group. The problem severity color displayed is originally from the underlying trigger, but can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen. To configure, select *Host group issues* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group.| |*Show lines*|Set how many problem lines will be displayed in the screen cell.| |*Sort triggers by*|Select from the dropdown to sort problems by last change, severity (both descending) or host (ascending).| #### 7 Host group issues In the host group issue element you can display problem details filtered by the selected host group. The problem severity color displayed is originally from the underlying trigger, but can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen. To configure, select *Host group issues* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group.| |*Show lines*|Set how many problem lines will be displayed in the screen cell.| |*Sort triggers by*|Select from the dropdown to sort problems by last change, severity (both descending) or host (ascending).| # 7 Macros # 7 Macros # 7 Scripts # 7 Scripts #### 8 Host info In the host information element you can display high-level information about host availability. To configure, select *Host info* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group(s).| |*Style*|Select vertical or horizontal display.| #### 8 Host info In the host information element you can display high-level information about host availability. To configure, select *Host info* as resource:  You may set the following specific options: | | | |---|---| |*Group*|Select host group(s).| |*Style*|Select vertical or horizontal display.| # 8 Services # 8 Services # 9 Applications # 9 Applications # 9 Cookies used by Zabbix # 9 Cookies used by Zabbix #### 9 Host issues In the host issue element you can display problem details filtered by the selected host. The problem severity color displayed is originally from the underlying trigger, but can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen. To configure, select *Host issues* as resource:  You may set the following specific options: | | | |---|---| |*Host*|Select the host.| |*Show lines*|Set how many problem lines will be displayed in the screen cell.| |*Sort triggers by*|Select from the dropdown to sort problems by last change, severity (both descending) or host (ascending).| #### 9 Host issues In the host issue element you can display problem details filtered by the selected host. The problem severity color displayed is originally from the underlying trigger, but can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen. To configure, select *Host issues* as resource:  You may set the following specific options: | | | |---|---| |*Host*|Select the host.| |*Show lines*|Set how many problem lines will be displayed in the screen cell.| |*Sort triggers by*|Select from the dropdown to sort problems by last change, severity (both descending) or host (ascending).| #### Absence of data For items with a regular update interval, nothing is displayed in the graph if item data are not collected. However, for trapper items and items with a scheduled update interval (and regular update interval set to 0), a straight line is drawn leading up to the first collected value and from the last collected value to the end of graph; the line is on the level of the first/last value respectively. #### Absence of data For items with a regular update interval, nothing is displayed in the graph if item data are not collected. However, for trapper items and items with a scheduled update interval (and regular update interval set to 0), a straight line is drawn leading up to the first collected value and from the last collected value to the end of graph; the line is on the level of the first/last value respectively. #### Accessing host screens Access to host screens is provided: - From the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) that is available in many frontend locations: - click on the host name and then select *Host screens* from the drop-down menu  - When searching for a host name in [global search](/manual/web_interface/global_search): - click on the *Screens* link provided in search results ```{=html} <!-- --> ``` - When clicking on a host name in *Inventory* → *[Hosts](/manual/web_interface/frontend_sections/inventory/hosts)*: - click on the *Screens* link provided #### Accessing host screens Access to host screens is provided: - From the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) that is available in many frontend locations: - click on the host name and then select *Host screens* from the drop-down menu  - When searching for a host name in [global search](/manual/web_interface/global_search): - click on the *Screens* link provided in search results ```{=html} <!-- --> ``` - When clicking on a host name in *Inventory* → *[Hosts](/manual/web_interface/frontend_sections/inventory/hosts)*: - click on the *Screens* link provided #### Acknowledged problems in trigger overview The icon that indicates an acknowledged problem in Monitoring → Overview now is displayed only if all problems or resolved problems of the trigger are acknowledged. Previously it was enough for the last problem to be acknowledged. #### Acknowledged problems in trigger overview The icon that indicates an acknowledged problem in Monitoring → Overview now is displayed only if all problems or resolved problems of the trigger are acknowledged. Previously it was enough for the last problem to be acknowledged. # action.create # action.create # action.delete # action.delete # action.get # action.get #### Actions In [actions](/manual/config/notifications/action), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Trigger-based notifications and commands|<|yes| |Trigger-based internal notifications|<|yes| |Problem update notifications|<|yes| |Time period condition|<|no| |*Operations*|<|<| |<|Default operation step duration|no| |^|Step duration|no| #### Actions In [actions](/manual/config/notifications/action), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Trigger-based notifications and commands|<|yes| |Trigger-based internal notifications|<|yes| |Problem update notifications|<|yes| |Time period condition|<|no| |*Operations*|<|<| |<|Default operation step duration|no| |^|Step duration|no| # action.update # action.update #### Adding elements To add elements to the screen, click on *Constructor* next to the screen name in the list. On a new screen you probably only see links named *Change*. Clicking those links opens a form whereby you set what to display in each cell. On an existing screen you click on the existing elements to open the form whereby you set what to display. {width="600"} All mandatory input fields are marked with a red asterisk. Screen element attributes: |Parameter|Description| |---------|-----------| |*Resource*|Information displayed in the cell:<br>**Action log** - history of recent actions<br>**Clock** - digital or analog clock displaying current server or local time<br>**Data overview** - latest data for a group of hosts<br>**Graph** - single custom graph<br>**Graph prototype** - custom graph from low-level discovery rule<br>**History of events** - latest events<br>**Host group issues** - status of triggers filtered by the host group (includes triggers without events, since Zabbix 2.2)<br>**Host info** - high level host related information<br>**Host issues** - status of triggers filtered by the host (includes triggers without events, since Zabbix 2.2)<br>**Map** - single map<br>**Plain text** - plain text data<br>**Screen** - screen (one screen may contain other screens inside)<br>**Simple graph** - single simple graph<br>**Simple graph prototype** - simple graph based on item generated by low-level discovery<br>**System information** - high-level information about Zabbix server<br>**Problems by severity** - displays problems by severity (similar to the Dashboard)<br>**Trigger info** - high level trigger related information<br>**Trigger overview** - status of triggers for a host group<br>**URL** - include content from the specified resource<br>See also more information on configuring [each resource](/manual/config/visualization/screens/elements).| |*Horizontal align*|Possible values:<br>**Center**<br>**Left**<br>**Right**| |*Vertical align*|Possible values:<br>**Middle**<br>**Top**<br>**Bottom**| |*Column span*|Extend cell to a number of columns, same way as HTML column spanning works.| |*Row span*|Extend cell to a number of rows, same way as HTML row spanning works.| Take note of the '+' and '-' controls on each side of the table. Clicking on '+' above the table will add a column. Clicking on '-' beneath the table will remove a column. Clicking on '+' on the left side of the table will add a row. Clicking on '-' on the right side of the table will remove a row. ::: noteimportant If graph height is set as less than 120 pixels, no trigger will be displayed in the legend. ::: #### Adding elements To add elements to the screen, click on *Constructor* next to the screen name in the list. On a new screen you probably only see links named *Change*. Clicking those links opens a form whereby you set what to display in each cell. On an existing screen you click on the existing elements to open the form whereby you set what to display. {width="600"} All mandatory input fields are marked with a red asterisk. Screen element attributes: |Parameter|Description| |---------|-----------| |*Resource*|Information displayed in the cell:<br>**Action log** - history of recent actions<br>**Clock** - digital or analog clock displaying current server or local time<br>**Data overview** - latest data for a group of hosts<br>**Graph** - single custom graph<br>**Graph prototype** - custom graph from low-level discovery rule<br>**History of events** - latest events<br>**Host group issues** - status of triggers filtered by the host group (includes triggers without events, since Zabbix 2.2)<br>**Host info** - high level host related information<br>**Host issues** - status of triggers filtered by the host (includes triggers without events, since Zabbix 2.2)<br>**Map** - single map<br>**Plain text** - plain text data<br>**Screen** - screen (one screen may contain other screens inside)<br>**Simple graph** - single simple graph<br>**Simple graph prototype** - simple graph based on item generated by low-level discovery<br>**System information** - high-level information about Zabbix server<br>**Problems by severity** - displays problems by severity (similar to the Dashboard)<br>**Trigger info** - high level trigger related information<br>**Trigger overview** - status of triggers for a host group<br>**URL** - include content from the specified resource<br>See also more information on configuring [each resource](/manual/config/visualization/screens/elements).| |*Horizontal align*|Possible values:<br>**Center**<br>**Left**<br>**Right**| |*Vertical align*|Possible values:<br>**Middle**<br>**Top**<br>**Bottom**| |*Column span*|Extend cell to a number of columns, same way as HTML column spanning works.| |*Row span*|Extend cell to a number of rows, same way as HTML row spanning works.| Take note of the '+' and '-' controls on each side of the table. Clicking on '+' above the table will add a column. Clicking on '-' beneath the table will remove a column. Clicking on '+' on the left side of the table will add a row. Clicking on '-' on the right side of the table will remove a row. ::: noteimportant If graph height is set as less than 120 pixels, no trigger will be displayed in the legend. ::: #### Adding lines In addition to shapes, it is also possible to add some lines. Lines can be used to link elements or shapes in a map. To add a line, click on *Add* next to Shape. A new shape will appear at the top left corner of the map. Select it and click on *Line* in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, color, etc. {width="600"} #### Adding lines In addition to shapes, it is also possible to add some lines. Lines can be used to link elements or shapes in a map. To add a line, click on *Add* next to Shape. A new shape will appear at the top left corner of the map. Select it and click on *Line* in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, color, etc. {width="600"} #### Adding shapes In addition to map elements, it is also possible to add some shapes. Shapes are not map elements; they are just a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Rectangle and ellipse shapes can be added. To add a shape, click on *Add* next to Shape. The new shape will appear at the top left corner of the map. Drag and drop it wherever you like. A new shape is added with default colors. By clicking on the shape, a form is displayed and you can customize the way a shape looks, add text, etc. {width="600"} To select shapes, select one and then hold down *Ctrl* to select the others. With several shapes selected, common properties can be mass updated, similarly as with elements. Text can be added in the shapes. To display text only the shape can be made invisible by removing the shape border (select 'None' in the *Border* field). For example, take note of how the {MAP.NAME} macro, visible in the screenshot above, is actually a rectangle shape with text, which can be seen when clicking on the macro:  {MAP.NAME} resolves to the configured map name, when viewing the map. If hyperlinks are used in the text, they become clickable when viewing the map. Line wrapping for text is always "on" within shapes. However, within an ellipse the lines are wrapped as though the ellipse were a rectangle. Word wrapping is not implemented, so long words (words that do not fit the shape) are not wrapped, but are masked (constructor page) or clipped (other pages with maps). #### Adding shapes In addition to map elements, it is also possible to add some shapes. Shapes are not map elements; they are just a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Rectangle and ellipse shapes can be added. To add a shape, click on *Add* next to Shape. The new shape will appear at the top left corner of the map. Drag and drop it wherever you like. A new shape is added with default colors. By clicking on the shape, a form is displayed and you can customize the way a shape looks, add text, etc. {width="600"} To select shapes, select one and then hold down *Ctrl* to select the others. With several shapes selected, common properties can be mass updated, similarly as with elements. Text can be added in the shapes. To display text only the shape can be made invisible by removing the shape border (select 'None' in the *Border* field). For example, take note of how the {MAP.NAME} macro, visible in the screenshot above, is actually a rectangle shape with text, which can be seen when clicking on the macro:  {MAP.NAME} resolves to the configured map name, when viewing the map. If hyperlinks are used in the text, they become clickable when viewing the map. Line wrapping for text is always "on" within shapes. However, within an ellipse the lines are wrapped as though the ellipse were a rectangle. Word wrapping is not implemented, so long words (words that do not fit the shape) are not wrapped, but are masked (constructor page) or clipped (other pages with maps). #### Aggregate item helper The item key selector for [aggregate items](/manual/config/items/itemtypes/aggregate) in the frontend now lists all available aggregate keys (grpavg,grpmax,grpmin,grpsum) and their descriptions. #### Aggregate item helper The item key selector for [aggregate items](/manual/config/items/itemtypes/aggregate) in the frontend now lists all available aggregate keys (grpavg,grpmax,grpmin,grpsum) and their descriptions. #### alert Changes:\ [ZBX-11272](https://support.zabbix.com/browse/ZBX-11272) `alert.get`: added support of two new options `mediatypeid` and `sendto` in the `sortfield` parameter\ #### alert Changes:\ [ZBX-11272](https://support.zabbix.com/browse/ZBX-11272) `alert.get`: added support of two new options `mediatypeid` and `sendto` in the `sortfield` parameter\ # alert.get # alert.get # apiinfo.version # apiinfo.version # application.create # application.create # application.delete # application.delete # application.get # application.get # application.massadd # application.massadd # application.update # application.update ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} #### Building with libxml2 When building with libxml2, pkg-config is now used instead of xml2-config to detect and use libxml2, as xml2-config is to be removed from libxml2 in the future. #### Building with libxml2 When building with libxml2, pkg-config is now used instead of xml2-config to detect and use libxml2, as xml2-config is to be removed from libxml2 in the future. #### Cache size configuration parameter The maximum value of the CacheSize configuration parameter for Zabbix [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) has been increased from 8GB to 64GB. #### Cache size configuration parameter The maximum value of the CacheSize configuration parameter for Zabbix [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) has been increased from 8GB to 64GB. #### Cannot support audio notification notice “Cannot support notification audio for this device.” message will be displayed when [notification sounds](/manual/web_interface/user_profile/sound) on the device cannot be played. #### Cannot support audio notification notice “Cannot support notification audio for this device.” message will be displayed when [notification sounds](/manual/web_interface/user_profile/sound) on the device cannot be played. ### Changes in 4.0.13 ### Changes in 4.0.13 ### Changes in 4.0.14 ### Changes in 4.0.14 ### Changes in 4.0.15 Low-level **discovery rules** have been split from the parent template *Template Module HOST-RESOURCES-MIB SNMPv2* into separate linked templates: - Template Module HOST-RESOURCES-MIB storage SNMPv2 - Template Module HOST-RESOURCES-MIB memory SNMPv2 - Template Module HOST-RESOURCES-MIB CPU SNMPv2 Other changes: - A CPU utilization item has been added to *Template Module HOST-RESOURCES-MIB CPU SNMPv2*; - The filesystem discovery filter has been improved to exclude some unnecessary values in *Template Module HOST-RESOURCES-MIB storage SNMPv2* (linked to *Template OS Windows SNMPv2*, *Template Net Arista SNMPv2*); - The network interface discovery filter has been improved to exclude some unnecessary values in *Template Module Interfaces Windows SNMPv2* (linked to *Template OS Windows SNMPv2*); - Discovery filters in several templates are now defined by template-level user macros (for example {$VFS.FS.FSNAME.MATCHES} and {$VFS.FS.FSNAME.NOT\_MATCHES}) that can be overridden on host or linked-template level for flexibility: - *Template Module HOST-RESOURCES-MIB storage SNMPv2* - *Template Module HOST-RESOURCES-MIB memory SNMPv2* - *Template Module HOST-RESOURCES-MIB CPU SNMPv2* - *Template Module Interfaces Windows SNMPv2* ### Changes in 4.0.15 Low-level **discovery rules** have been split from the parent template *Template Module HOST-RESOURCES-MIB SNMPv2* into separate linked templates: - Template Module HOST-RESOURCES-MIB storage SNMPv2 - Template Module HOST-RESOURCES-MIB memory SNMPv2 - Template Module HOST-RESOURCES-MIB CPU SNMPv2 Other changes: - A CPU utilization item has been added to *Template Module HOST-RESOURCES-MIB CPU SNMPv2*; - The filesystem discovery filter has been improved to exclude some unnecessary values in *Template Module HOST-RESOURCES-MIB storage SNMPv2* (linked to *Template OS Windows SNMPv2*, *Template Net Arista SNMPv2*); - The network interface discovery filter has been improved to exclude some unnecessary values in *Template Module Interfaces Windows SNMPv2* (linked to *Template OS Windows SNMPv2*); - Discovery filters in several templates are now defined by template-level user macros (for example {$VFS.FS.FSNAME.MATCHES} and {$VFS.FS.FSNAME.NOT\_MATCHES}) that can be overridden on host or linked-template level for flexibility: - *Template Module HOST-RESOURCES-MIB storage SNMPv2* - *Template Module HOST-RESOURCES-MIB memory SNMPv2* - *Template Module HOST-RESOURCES-MIB CPU SNMPv2* - *Template Module Interfaces Windows SNMPv2* ### Changes in 4.0.25 ### Changes in 4.0.25 ### Changes in 4.0.5 ### Changes in 4.0.5 ### Changes in 4.0.6 ### Changes in 4.0.6 ### Changes in 4.0.7 ### Changes in 4.0.7 #### Cisco UCS server template A Cisco UCS server monitoring template - *Template Server Cisco UCS SNMPv2* has been added. It will be available in *Configuration* → *Templates* in new installations. If you are upgrading from previous versions, you can find this template in the `templates` directory of the downloaded latest Zabbix version. Then, while in *Configuration* → *Templates* you can import it manually into Zabbix. #### Cisco UCS server template A Cisco UCS server monitoring template - *Template Server Cisco UCS SNMPv2* has been added. It will be available in *Configuration* → *Templates* in new installations. If you are upgrading from previous versions, you can find this template in the `templates` directory of the downloaded latest Zabbix version. Then, while in *Configuration* → *Templates* you can import it manually into Zabbix. #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### configuration Changes:\ [ZBXNEXT-5271](https://support.zabbix.com/browse/ZBXNEXT-5271) `configuration.import`: implemented `deleteMissing` option for `templateLinkage`\ #### configuration Changes:\ [ZBXNEXT-5271](https://support.zabbix.com/browse/ZBXNEXT-5271) `configuration.import`: implemented `deleteMissing` option for `templateLinkage`\ # configuration.export # configuration.export # configuration.import # configuration.import #### Configuration parameters The [LoadModule](/manual/appendix/config/zabbix_server) server/proxy/agent parameter now supports specifying relative or absolute path to the module. #### Configuration parameters The [LoadModule](/manual/appendix/config/zabbix_server) server/proxy/agent parameter now supports specifying relative or absolute path to the module. #### Configuration To assign triggers as link indicators, do the following: - select a map element - click on *Edit* in the *Links* section for the appropriate link - click on *Add* in the *Link indicators* block and select one or more triggers {width="600"} All mandatory input fields are marked with a red asterisk. Added triggers can be seen in the *Link indicators* list. You can set the link type and color for each trigger directly from the list. When done, click on *Apply*, close the form and click on *Update* to save the map changes. #### Configuration To assign triggers as link indicators, do the following: - select a map element - click on *Edit* in the *Links* section for the appropriate link - click on *Add* in the *Link indicators* block and select one or more triggers {width="600"} All mandatory input fields are marked with a red asterisk. Added triggers can be seen in the *Link indicators* list. You can set the link type and color for each trigger directly from the list. When done, click on *Apply*, close the form and click on *Update* to save the map changes. #### Configuration To create an ad-hoc graph, do the following: - Go to *Monitoring* → *Latest data* - Use filter to display items that you want - Mark checkboxes of the items you want to graph - Click on *Display stacked graph* or *Display graph* buttons {width="600"} Your graph is created instantly: {width="600"} Note that to avoid displaying too many lines in the graph, only the average value for each item is displayed (min/max value lines are not displayed). Triggers and trigger information is not displayed in the graph. In the created graph window you have the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) available and the possibility to switch from the "normal" line graph to a stacked one (and back). {width="600"} #### Configuration To create an ad-hoc graph, do the following: - Go to *Monitoring* → *Latest data* - Use filter to display items that you want - Mark checkboxes of the items you want to graph - Click on *Display stacked graph* or *Display graph* buttons {width="600"} Your graph is created instantly: {width="600"} Note that to avoid displaying too many lines in the graph, only the average value for each item is displayed (min/max value lines are not displayed). Triggers and trigger information is not displayed in the graph. In the created graph window you have the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) available and the possibility to switch from the "normal" line graph to a stacked one (and back). {width="600"} #### Configuration To create a slide show, do the following: - Go to *Monitoring → Screens* - Select *Slide shows* in the dropdown - Go to the view with all slide shows - Click on *Create slide show* The **Slide** tab contains general slide show attributes: {width="600"} All mandatory input fields are marked with a red asterisk. |Parameter|Description| |---------|-----------| |*Owner*|Select the slide show owner. Specifying owner is mandatory.| |*Name*|Unique name of the slide show.| |*Default delay*|How long one screen is displayed by default, before rotating to the next.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 5m, 2h, 1d.| |*Slides*|List of screens to be rotated. Click on *Add* to select screens.<br>The *Up/Down* arrow before the screen allows to drag a screen up and down in the sort order of display.<br>If you want to display only, say, a single graph in the slide show, create a screen containing just that one graph.| |*Screen*|Screen name.| |*Delay*|A custom value for how long the screen will be displayed, in seconds.<br>If set to 0, the *Default delay* value will be used.| |*Action*|Click on *Remove* to remove a screen from the slide show.| The slide show in this example consists of two screens which will be displayed in the following order: Zabbix server ⇒ Displayed for 30 seconds ⇒ Zabbix server2 ⇒ Displayed for 15 seconds ⇒ Zabbix server ⇒ Displayed for 30 seconds ⇒ Zabbix server2 ⇒ … The **Sharing** tab contains the slide show type as well as sharing options (user groups, users) for private slide shows:  |Parameter|Description| |---------|-----------| |*Type*|Select slide show type:<br>**Private** - slide show is visible only to selected user groups and users<br>**Public** - slide show is visible to all| |*List of user group shares*|Select user groups that the slide show is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the slide show is accessible to.<br>You may allow read-only or read-write access.| Click on *Add* to save the slide show. #### Configuration To create a slide show, do the following: - Go to *Monitoring → Screens* - Select *Slide shows* in the dropdown - Go to the view with all slide shows - Click on *Create slide show* The **Slide** tab contains general slide show attributes: {width="600"} All mandatory input fields are marked with a red asterisk. |Parameter|Description| |---------|-----------| |*Owner*|Select the slide show owner. Specifying owner is mandatory.| |*Name*|Unique name of the slide show.| |*Default delay*|How long one screen is displayed by default, before rotating to the next.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 5m, 2h, 1d.| |*Slides*|List of screens to be rotated. Click on *Add* to select screens.<br>The *Up/Down* arrow before the screen allows to drag a screen up and down in the sort order of display.<br>If you want to display only, say, a single graph in the slide show, create a screen containing just that one graph.| |*Screen*|Screen name.| |*Delay*|A custom value for how long the screen will be displayed, in seconds.<br>If set to 0, the *Default delay* value will be used.| |*Action*|Click on *Remove* to remove a screen from the slide show.| The slide show in this example consists of two screens which will be displayed in the following order: Zabbix server ⇒ Displayed for 30 seconds ⇒ Zabbix server2 ⇒ Displayed for 15 seconds ⇒ Zabbix server ⇒ Displayed for 30 seconds ⇒ Zabbix server2 ⇒ … The **Sharing** tab contains the slide show type as well as sharing options (user groups, users) for private slide shows:  |Parameter|Description| |---------|-----------| |*Type*|Select slide show type:<br>**Private** - slide show is visible only to selected user groups and users<br>**Public** - slide show is visible to all| |*List of user group shares*|Select user groups that the slide show is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the slide show is accessible to.<br>You may allow read-only or read-write access.| Click on *Add* to save the slide show. #### Configuring an update operation To configure an update operation: - Go to the *Update operations* tab in action [configuration](/manual/config/notifications/action) - Click on *New* in the Operations block - Edit the operation details and click on *Add* Several operations can be added. Update operation attributes:  |Parameter|<|<|<|<|Description| |---------|-|-|-|-|-----------| |*Default subject*|<|<|<|<|Default message subject for update notifications. The subject may contain [macros](/manual/config/notifications/action/operation/macros).| |*Default message*|<|<|<|<|Default message for update notifications. The message may contain [macros](/manual/config/notifications/action/operation/macros).| |*Operations*|<|<|<|<|Update operation details are displayed.<br>To configure a new update operation, click on *New*.<br>| |*Operation details*|<|<|<|<|This block is used to configure the details of an update operation.| |<|*Operation type*|<|<|<|Three operation types are available for update operations:<br>**Send message** - send update message to specified user when event is updated, for example, acknowledged<br>**Remote command** - execute a remote command when event is updated, for example, acknowledged<br>**Notify all involved** - send notification message to all users who received notification about the problem appearing and/or have updated the problem event.<br>If the same recipient with unchanged default subject/message is defined in several operation types, duplicate notifications are not sent.<br>The person who updates a problem does not receive notification about their own update.| |^|<|Operation type: [send message](/manual/config/notifications/action/operation/message)|<|<|<| |^|^|*Send to user groups*|<|<|Click on *Add* to select user groups to send the update message to.<br>The user group must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|^|*Send to users*|<|<|Click on *Add* to select users to send the update message to.<br>The user must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|^|*Send only to*|<|<|Send update message to all defined media types or a selected one only.| |^|^|*Default message*|<|<|If selected, the default message will be used (see above).| |^|^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|^|*Message*|<|<|The custom message. The message may contain macros.| |^|^|Operation type: [remote command](/manual/config/notifications/action/operation/remote_command)|<|<|<| |^|^|*Target list*|<|<|Select targets to execute the command on:<br>**Current host** - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.<br>**Host** - select host(s) to execute the command on.<br>**Host group** - select host group(s) to execute the command on. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups.<br>A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).<br>The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.<br>Note that for global scripts, the target selection also depends on the *Host group* setting in global script [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script).| |^|^|*Type*|<|<|Select the command type:<br>**IPMI** - execute an [IPMI command](/manual/config/notifications/action/operation/remote_command#ipmi_remote_commands)<br>**Custom script** - execute a custom set of commands<br>**SSH** - execute an SSH command<br>**Telnet** - execute a Telnet command<br>**Global script** - execute one of the global scripts defined in *Administration→Scripts*.| |^|^|*Execute on*|<|<|Execute a custom script on:<br>**Zabbix agent** - the script will be executed by Zabbix agent on the host<br>**Zabbix server (proxy)** - the script will be executed by Zabbix server or proxy - depending on whether the host is monitored by server or proxy<br>**Zabbix server** - the script will be executed by Zabbix server only<br>To execute scripts on the agent, it must be [configured](/manual/appendix/config/zabbix_agentd) to allow remote commands from the server.<br>This field is available if 'Custom script' is selected as *Type*.| |^|^|*Commands*|<|<|Enter the command(s).<br>Supported macros will be resolved based on the trigger expression that caused the event. For example, host macros will resolve to the hosts of the trigger expression (and not of the target list).| |^|<|Operation type: notify all involved|<|<|<| |^|^|*Default media type*|<|<|Users who update a problem but have not received notifications about the problem appearing will receive notifications about further updates on the selected default media type - Email, Jabber or SMS.<br>This field is available since Zabbix 3.4.2.| |^|^|*Default message*|<|<|If selected, the default message will be used (see above).| |^|^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|^|*Message*|<|<|The custom message. The message may contain macros.| #### Configuring an update operation To configure an update operation: - Go to the *Update operations* tab in action [configuration](/manual/config/notifications/action) - Click on *New* in the Operations block - Edit the operation details and click on *Add* Several operations can be added. Update operation attributes:  |Parameter|<|<|<|<|Description| |---------|-|-|-|-|-----------| |*Default subject*|<|<|<|<|Default message subject for update notifications. The subject may contain [macros](/manual/config/notifications/action/operation/macros).| |*Default message*|<|<|<|<|Default message for update notifications. The message may contain [macros](/manual/config/notifications/action/operation/macros).| |*Operations*|<|<|<|<|Update operation details are displayed.<br>To configure a new update operation, click on *New*.<br>| |*Operation details*|<|<|<|<|This block is used to configure the details of an update operation.| |<|*Operation type*|<|<|<|Three operation types are available for update operations:<br>**Send message** - send update message to specified user when event is updated, for example, acknowledged<br>**Remote command** - execute a remote command when event is updated, for example, acknowledged<br>**Notify all involved** - send notification message to all users who received notification about the problem appearing and/or have updated the problem event.<br>If the same recipient with unchanged default subject/message is defined in several operation types, duplicate notifications are not sent.<br>The person who updates a problem does not receive notification about their own update.| |^|<|Operation type: [send message](/manual/config/notifications/action/operation/message)|<|<|<| |^|^|*Send to user groups*|<|<|Click on *Add* to select user groups to send the update message to.<br>The user group must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|^|*Send to users*|<|<|Click on *Add* to select users to send the update message to.<br>The user must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|^|*Send only to*|<|<|Send update message to all defined media types or a selected one only.| |^|^|*Default message*|<|<|If selected, the default message will be used (see above).| |^|^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|^|*Message*|<|<|The custom message. The message may contain macros.| |^|^|Operation type: [remote command](/manual/config/notifications/action/operation/remote_command)|<|<|<| |^|^|*Target list*|<|<|Select targets to execute the command on:<br>**Current host** - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.<br>**Host** - select host(s) to execute the command on.<br>**Host group** - select host group(s) to execute the command on. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups.<br>A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).<br>The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.<br>Note that for global scripts, the target selection also depends on the *Host group* setting in global script [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script).| |^|^|*Type*|<|<|Select the command type:<br>**IPMI** - execute an [IPMI command](/manual/config/notifications/action/operation/remote_command#ipmi_remote_commands)<br>**Custom script** - execute a custom set of commands<br>**SSH** - execute an SSH command<br>**Telnet** - execute a Telnet command<br>**Global script** - execute one of the global scripts defined in *Administration→Scripts*.| |^|^|*Execute on*|<|<|Execute a custom script on:<br>**Zabbix agent** - the script will be executed by Zabbix agent on the host<br>**Zabbix server (proxy)** - the script will be executed by Zabbix server or proxy - depending on whether the host is monitored by server or proxy<br>**Zabbix server** - the script will be executed by Zabbix server only<br>To execute scripts on the agent, it must be [configured](/manual/appendix/config/zabbix_agentd) to allow remote commands from the server.<br>This field is available if 'Custom script' is selected as *Type*.| |^|^|*Commands*|<|<|Enter the command(s).<br>Supported macros will be resolved based on the trigger expression that caused the event. For example, host macros will resolve to the hosts of the trigger expression (and not of the target list).| |^|<|Operation type: notify all involved|<|<|<| |^|^|*Default media type*|<|<|Users who update a problem but have not received notifications about the problem appearing will receive notifications about further updates on the selected default media type - Email, Jabber or SMS.<br>This field is available since Zabbix 3.4.2.| |^|^|*Default message*|<|<|If selected, the default message will be used (see above).| |^|^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|^|*Message*|<|<|The custom message. The message may contain macros.| #### Configuring custom graphs To create a custom graph, do the following: - Go to *Configuration → Hosts (or Templates)* - Click on *Graphs* in the row next to the desired host or template - In the Graphs screen click on *Create graph* - Edit graph attributes {width="600"} All mandatory input fields are marked with a red asterisk. Graph attributes: |Parameter|<|Description| |---------|-|-----------| |*Name*|<|Unique graph name.<br>Starting with Zabbix 2.2, item values can be referenced in the name by using simple macros with the standard `{host:key.func(param)}` syntax. Only **avg**, **last**, **max** and **min** as functions with seconds as parameter are supported within this macro. {HOST.HOST<1-9>} macros are supported for the use within this macro, referencing the first, second, third, etc. host in the graph, for example `{{HOST.HOST1}:key.func(param)}`.| |*Width*|<|Graph width in pixels (for preview and pie/exploded graphs only).| |*Height*|<|Graph height in pixels.| |*Graph type*|<|Graph type:<br>**Normal** - normal graph, values displayed as lines<br>**Stacked** - stacked graph, filled areas displayed<br>**Pie** - pie graph<br>**Exploded** - "exploded" pie graph, portions displayed as "cut out" of the pie| |*Show legend*|<|Checking this box will set to display the graph legend.| |*Show working time*|<|If selected, non-working hours will be shown with gray background. Not available for pie and exploded pie graphs.| |*Show triggers*|<|If selected, simple triggers will be displayed as lines with black dashes over trigger severity color. Not available for pie and exploded pie graphs.| |*Percentile line (left)*|<|Display percentile for left Y axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 per cent of the values fall under. Displayed as a bright green line. Only available for normal graphs.| |*Percentile line (right)*|<|Display percentile for right Y axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 per cent of the values fall under. Displayed as a bright red line. Only available for normal graphs.| |*Y axis MIN value*|<|Minimum value of Y axis:<br>**Calculated** - Y axis minimum value will be automatically calculated<br>**Fixed** - fixed minimum value for Y axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the minimum value| |*Y axis MAX value*|<|Maximum value of Y axis:<br>**Calculated** - Y axis maximum value will be automatically calculated<br>**Fixed** - fixed maximum value for Y axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the maximum value| |*3D view*|<|Enable 3D style. For pie and exploded pie graphs only.| |*Items*|<|Items, data of which are to be displayed in this graph. Click on *Add* to select items. You can also select various displaying options (function, draw style, left/right axis display, color).| |<|*Sort order (0→100)*|Draw order. 0 will be processed first. Can be used to draw lines or regions behind (or in front of) another.<br>You can drag and drop items by the arrow in the beginning of line to set the sort order or which item is displayed in front of the other.| |^|*Name*|Name of the selected item is displayed as a link. Clicking on the link opens the list of other available items.| |^|*Type*|Type (only available for pie and exploded pie graphs):<br>**Simple** - value of the item is represented proportionally on the pie<br>**Graph sum** - value of the item represents the whole pie<br>Note that colouring of the "graph sum" item will only be visible to the extent that it is not taken up by "proportional" items.| |^|*Function*|Select what values will be displayed when more than one value exists per vertical graph pixel for an item:<br>**all** - display all possible values (minimum, maximum, average) in the graph. Note that for shorter periods this setting has no effect; only for longer periods, when data congestion in a vertical graph pixel increases, 'all' starts displaying minimum, maximum and average values. This function is only available for *Normal* graph type. See also: Generating graphs [from history/trends](/manual/config/visualization/graphs/simple#generating_from_historytrends).<br>**avg** - display the average values<br>**last** - display the latest values. This function is only available if either *Pie/Exploded pie* is selected as graph type.<br>**max** - display the maximum values<br>**min** - display the minimum values| |^|*Draw style*|Select the draw style (only available for normal graphs; for stacked graphs filled region is always used) to apply to the item data - *Line*, *Bold line*, *Filled region*, *Dot*, *Dashed line*, *Gradient line*.| |^|*Y axis side*|Select the Y axis side to show the item data - *Left*, *Right*.| |^|*Color*|Select the color to apply to the item data.| #### Configuring custom graphs To create a custom graph, do the following: - Go to *Configuration → Hosts (or Templates)* - Click on *Graphs* in the row next to the desired host or template - In the Graphs screen click on *Create graph* - Edit graph attributes {width="600"} All mandatory input fields are marked with a red asterisk. Graph attributes: |Parameter|<|Description| |---------|-|-----------| |*Name*|<|Unique graph name.<br>Starting with Zabbix 2.2, item values can be referenced in the name by using simple macros with the standard `{host:key.func(param)}` syntax. Only **avg**, **last**, **max** and **min** as functions with seconds as parameter are supported within this macro. {HOST.HOST<1-9>} macros are supported for the use within this macro, referencing the first, second, third, etc. host in the graph, for example `{{HOST.HOST1}:key.func(param)}`.| |*Width*|<|Graph width in pixels (for preview and pie/exploded graphs only).| |*Height*|<|Graph height in pixels.| |*Graph type*|<|Graph type:<br>**Normal** - normal graph, values displayed as lines<br>**Stacked** - stacked graph, filled areas displayed<br>**Pie** - pie graph<br>**Exploded** - "exploded" pie graph, portions displayed as "cut out" of the pie| |*Show legend*|<|Checking this box will set to display the graph legend.| |*Show working time*|<|If selected, non-working hours will be shown with gray background. Not available for pie and exploded pie graphs.| |*Show triggers*|<|If selected, simple triggers will be displayed as lines with black dashes over trigger severity color. Not available for pie and exploded pie graphs.| |*Percentile line (left)*|<|Display percentile for left Y axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 per cent of the values fall under. Displayed as a bright green line. Only available for normal graphs.| |*Percentile line (right)*|<|Display percentile for right Y axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 per cent of the values fall under. Displayed as a bright red line. Only available for normal graphs.| |*Y axis MIN value*|<|Minimum value of Y axis:<br>**Calculated** - Y axis minimum value will be automatically calculated<br>**Fixed** - fixed minimum value for Y axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the minimum value| |*Y axis MAX value*|<|Maximum value of Y axis:<br>**Calculated** - Y axis maximum value will be automatically calculated<br>**Fixed** - fixed maximum value for Y axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the maximum value| |*3D view*|<|Enable 3D style. For pie and exploded pie graphs only.| |*Items*|<|Items, data of which are to be displayed in this graph. Click on *Add* to select items. You can also select various displaying options (function, draw style, left/right axis display, color).| |<|*Sort order (0→100)*|Draw order. 0 will be processed first. Can be used to draw lines or regions behind (or in front of) another.<br>You can drag and drop items by the arrow in the beginning of line to set the sort order or which item is displayed in front of the other.| |^|*Name*|Name of the selected item is displayed as a link. Clicking on the link opens the list of other available items.| |^|*Type*|Type (only available for pie and exploded pie graphs):<br>**Simple** - value of the item is represented proportionally on the pie<br>**Graph sum** - value of the item represents the whole pie<br>Note that colouring of the "graph sum" item will only be visible to the extent that it is not taken up by "proportional" items.| |^|*Function*|Select what values will be displayed when more than one value exists per vertical graph pixel for an item:<br>**all** - display all possible values (minimum, maximum, average) in the graph. Note that for shorter periods this setting has no effect; only for longer periods, when data congestion in a vertical graph pixel increases, 'all' starts displaying minimum, maximum and average values. This function is only available for *Normal* graph type. See also: Generating graphs [from history/trends](/manual/config/visualization/graphs/simple#generating_from_historytrends).<br>**avg** - display the average values<br>**last** - display the latest values. This function is only available if either *Pie/Exploded pie* is selected as graph type.<br>**max** - display the maximum values<br>**min** - display the minimum values| |^|*Draw style*|Select the draw style (only available for normal graphs; for stacked graphs filled region is always used) to apply to the item data - *Line*, *Bold line*, *Filled region*, *Dot*, *Dashed line*, *Gradient line*.| |^|*Y axis side*|Select the Y axis side to show the item data - *Left*, *Right*.| |^|*Color*|Select the color to apply to the item data.| # correlation.create # correlation.create # correlation.delete # correlation.delete # correlation.get # correlation.get # correlation.update # correlation.update #### Creating a map To create a map, do the following: - Go to *Monitoring → Maps* - Go to the view with all maps - Click on *Create map* You can also use the *Clone* and *Full clone* buttons in the configuration form of an existing map to create a new map. Clicking on *Clone* will retain general layout attributes of the original map, but no elements. *Full clone* will retain both the general layout attributes and all elements of the original map. The **Map** tab contains general map attributes: {width="600"} All mandatory input fields are marked with a red asterisk. General map attributes: |Parameter|Description| |---------|-----------| |*Owner*|Name of map owner.| |*Name*|Unique map name.| |*Width*|Map width in pixels.| |*Height*|Map height in pixels.| |*Background image*|Use background image:<br>**No image** - no background image (white background)<br>**Image** - selected image to be used as a background image. No scaling is performed. You may use a geographical map or any other image to enhance your map.| |*Automatic icon mapping*|You can set to use an automatic icon mapping, configured in *Administration → General → Icon mapping*. Icon mapping allows to map certain icons against certain host inventory fields.| |*Icon highlighting*|If you check this box, map elements will receive highlighting.<br>Elements with an active trigger will receive a round background, in the same color as the highest severity trigger. Moreover, a thick green line will be displayed around the circle, if all problems are acknowledged.<br>Elements with "disabled" or "in maintenance" status will get a square background, gray and orange respectively.<br>See also: [Viewing maps](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)| |*Mark elements on trigger status change*|A recent change of trigger status (recent problem or resolution) will be highlighted with markers (inward-pointing red triangles) on the three sides of the element icon that are free of the label. Markers are displayed for 30 minutes.| |*Display problems*|Select how problems are displayed with a map element:<br>**Expand single problem** - name of the most critical problem is displayed<br>**Number of problems** - the total number of problems is displayed<br>**Number of problems and expand most critical one** - name of the most critical problem and the total number of problems is displayed.<br>'Most critical' is determined based on problem severity and, if equal, problem event ID (higher ID or later problem displayed first). (Note that trigger ID instead of problem event ID was evaluated before 4.0.7.)<br>*For trigger map element* it is based on problem severity and, if equal, trigger position in the trigger list. In case of multiple problems of the same trigger, the most recent one will be displayed.| |*Advanced labels*|If you check this box you will be able to define separate label types for separate element types.| |*Map element label type*|Label type used for map elements:<br>**Label** - map element label<br>**IP address** - IP address<br>**Element name** - element name (for example, host name)<br>**Status only** - status only (OK or PROBLEM)<br>**Nothing** - no labels are displayed| |*Map element label location*|Label location in relation to the map element:<br>**Bottom** - beneath the map element<br>**Left** - to the left<br>**Right** - to the right<br>**Top** - above the map element| |*Problem display*|Display problem count as:<br>**All** - full problem count will be displayed<br>**Separated** - unacknowledged problem count will be displayed separated as a number of the total problem count<br>**Unacknowledged only** - only the unacknowledged problem count will be displayed| |*Minimum trigger severity*|Problems below the selected minimum severity level will not be displayed in the map.<br>For example, with *Warning* selected, changes with *Information* and *Not classified* level triggers will not be reflected in the map.<br>This parameter is supported starting with Zabbix 2.2.| |*Show suppressed problems*|Mark the checkbox to display problems which would otherwise be suppressed (not shown) because of host maintenance.| |*URLs*|URLs for each element type can be defined (with a label). These will be displayed as links when a user clicks on the element in the map viewing mode.<br>[Macros](/manual/config/macros) that can be used in map URLs: {MAP.ID}, {HOSTGROUP.ID}, {HOST.ID}, {TRIGGER.ID}| #### Creating a map To create a map, do the following: - Go to *Monitoring → Maps* - Go to the view with all maps - Click on *Create map* You can also use the *Clone* and *Full clone* buttons in the configuration form of an existing map to create a new map. Clicking on *Clone* will retain general layout attributes of the original map, but no elements. *Full clone* will retain both the general layout attributes and all elements of the original map. The **Map** tab contains general map attributes: {width="600"} All mandatory input fields are marked with a red asterisk. General map attributes: |Parameter|Description| |---------|-----------| |*Owner*|Name of map owner.| |*Name*|Unique map name.| |*Width*|Map width in pixels.| |*Height*|Map height in pixels.| |*Background image*|Use background image:<br>**No image** - no background image (white background)<br>**Image** - selected image to be used as a background image. No scaling is performed. You may use a geographical map or any other image to enhance your map.| |*Automatic icon mapping*|You can set to use an automatic icon mapping, configured in *Administration → General → Icon mapping*. Icon mapping allows to map certain icons against certain host inventory fields.| |*Icon highlighting*|If you check this box, map elements will receive highlighting.<br>Elements with an active trigger will receive a round background, in the same color as the highest severity trigger. Moreover, a thick green line will be displayed around the circle, if all problems are acknowledged.<br>Elements with "disabled" or "in maintenance" status will get a square background, gray and orange respectively.<br>See also: [Viewing maps](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)| |*Mark elements on trigger status change*|A recent change of trigger status (recent problem or resolution) will be highlighted with markers (inward-pointing red triangles) on the three sides of the element icon that are free of the label. Markers are displayed for 30 minutes.| |*Display problems*|Select how problems are displayed with a map element:<br>**Expand single problem** - name of the most critical problem is displayed<br>**Number of problems** - the total number of problems is displayed<br>**Number of problems and expand most critical one** - name of the most critical problem and the total number of problems is displayed.<br>'Most critical' is determined based on problem severity and, if equal, problem event ID (higher ID or later problem displayed first). (Note that trigger ID instead of problem event ID was evaluated before 4.0.7.)<br>*For trigger map element* it is based on problem severity and, if equal, trigger position in the trigger list. In case of multiple problems of the same trigger, the most recent one will be displayed.| |*Advanced labels*|If you check this box you will be able to define separate label types for separate element types.| |*Map element label type*|Label type used for map elements:<br>**Label** - map element label<br>**IP address** - IP address<br>**Element name** - element name (for example, host name)<br>**Status only** - status only (OK or PROBLEM)<br>**Nothing** - no labels are displayed| |*Map element label location*|Label location in relation to the map element:<br>**Bottom** - beneath the map element<br>**Left** - to the left<br>**Right** - to the right<br>**Top** - above the map element| |*Problem display*|Display problem count as:<br>**All** - full problem count will be displayed<br>**Separated** - unacknowledged problem count will be displayed separated as a number of the total problem count<br>**Unacknowledged only** - only the unacknowledged problem count will be displayed| |*Minimum trigger severity*|Problems below the selected minimum severity level will not be displayed in the map.<br>For example, with *Warning* selected, changes with *Information* and *Not classified* level triggers will not be reflected in the map.<br>This parameter is supported starting with Zabbix 2.2.| |*Show suppressed problems*|Mark the checkbox to display problems which would otherwise be suppressed (not shown) because of host maintenance.| |*URLs*|URLs for each element type can be defined (with a label). These will be displayed as links when a user clicks on the element in the map viewing mode.<br>[Macros](/manual/config/macros) that can be used in map URLs: {MAP.ID}, {HOSTGROUP.ID}, {HOST.ID}, {TRIGGER.ID}| #### Creating a screen To create a screen, do the following: - Go to *Monitoring → Screens* - Go to the view with all screens - Click on *Create Screen* The **Screen** tab contains general screen attributes:  All mandatory input fields are marked with a red asterisk. Give your screen a unique name and set the number of columns (vertical cells) and rows (horizontal cells). The **Sharing** tab contains the screen type as well as sharing options (user groups, users) for private screens:  |Parameter|Description| |---------|-----------| |*Owner*|Select the screen owner.| |*Type*|Select screen type:<br>**Private** - screen is visible only to selected user groups and users<br>**Public** - screen is visible to all| |*List of user group shares*|Select user groups that the screen is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the screen is accessible to.<br>You may allow read-only or read-write access.| Click on *Add* to save the screen. #### Creating a screen To create a screen, do the following: - Go to *Monitoring → Screens* - Go to the view with all screens - Click on *Create Screen* The **Screen** tab contains general screen attributes:  All mandatory input fields are marked with a red asterisk. Give your screen a unique name and set the number of columns (vertical cells) and rows (horizontal cells). The **Sharing** tab contains the screen type as well as sharing options (user groups, users) for private screens:  |Parameter|Description| |---------|-----------| |*Owner*|Select the screen owner.| |*Type*|Select screen type:<br>**Private** - screen is visible only to selected user groups and users<br>**Public** - screen is visible to all| |*List of user group shares*|Select user groups that the screen is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the screen is accessible to.<br>You may allow read-only or read-write access.| Click on *Add* to save the screen. #### Custom multiplier preprocessing step Custom multiplier [preprocessing step](/manual/config/items/item#item_value_preprocessing) now accepts strings with macros (a macro must resolve as an integer or a floating-point number). #### Custom multiplier preprocessing step Custom multiplier [preprocessing step](/manual/config/items/item#item_value_preprocessing) now accepts strings with macros (a macro must resolve as an integer or a floating-point number). # dashboard.create # dashboard.create # dashboard.delete # dashboard.delete # dashboard.get # dashboard.get # dashboard.update # dashboard.update #### DB character set and collation check A check for the correct character set and collation is now performed on the database, database tables and table fields during the initial frontend installation. If the check fails a warning message is displayed. A warning message is also displayed in *Reports* → *System information*. #### DB character set and collation check A check for the correct character set and collation is now performed on the database, database tables and table fields during the initial frontend installation. If the check fails a warning message is displayed. A warning message is also displayed in *Reports* → *System information*. #### DB character set and collation check A check for the correct character set and collation is now performed on the database, database tables and table fields during the initial frontend installation. If the check fails a warning message is displayed. A warning message is also displayed in *Reports* → *System information*. See also instructions for [changing database character set and collation](/manual/appendix/install/db_scripts?rev=1582206793#mysql) in MySQL. #### DB character set and collation check A check for the correct character set and collation is now performed on the database, database tables and table fields during the initial frontend installation. If the check fails a warning message is displayed. A warning message is also displayed in *Reports* → *System information*. See also instructions for [changing database character set and collation](/manual/appendix/install/db_scripts?rev=1582206793#mysql) in MySQL. # dcheck.get # dcheck.get ##### Dependent item prototype Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `vfs.fs.get` item we created.  Note the use of macros in the item prototype name and key: - *Name*: Free disk space on {\#FSNAME}, type: {\#FSTYPE} - *Key*: Free\[{\#FSNAME}\] As type of information, use: - *Numeric (unsigned)* for metrics like 'free', 'total', 'used' - *Numeric (float)* for metrics like 'pfree', 'pused' (percentage) In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter: $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  When discovery starts, one item per each mountpoint will be created. This item will return the number of free bytes for the given mountpoint. ##### Dependent item prototype Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `vfs.fs.get` item we created.  Note the use of macros in the item prototype name and key: - *Name*: Free disk space on {\#FSNAME}, type: {\#FSTYPE} - *Key*: Free\[{\#FSNAME}\] As type of information, use: - *Numeric (unsigned)* for metrics like 'free', 'total', 'used' - *Numeric (float)* for metrics like 'pfree', 'pused' (percentage) In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter: $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  When discovery starts, one item per each mountpoint will be created. This item will return the number of free bytes for the given mountpoint. ## DESCRIPTION **zabbix\_agentd** is a daemon for monitoring of various server parameters. [ ]{#lbAE} ## DESCRIPTION **zabbix\_agentd** is a daemon for monitoring of various server parameters. [ ]{#lbAE} ## DESCRIPTION **zabbix\_get** is a command line utility for getting data from Zabbix agent. [ ]{#lbAE} ## DESCRIPTION **zabbix\_get** is a command line utility for getting data from Zabbix agent. [ ]{#lbAE} ## DESCRIPTION **zabbix\_proxy** is a daemon that collects monitoring data from devices and sends it to Zabbix server. [ ]{#lbAE} ## DESCRIPTION **zabbix\_proxy** is a daemon that collects monitoring data from devices and sends it to Zabbix server. [ ]{#lbAE} ## DESCRIPTION **zabbix\_sender** is a command line utility for sending monitoring data to Zabbix server or proxy. On the Zabbix server an item of type **Zabbix trapper** should be created with corresponding key. Note that incoming values will only be accepted from hosts specified in **Allowed hosts** field for this item. [ ]{#lbAE} ## DESCRIPTION **zabbix\_sender** is a command line utility for sending monitoring data to Zabbix server or proxy. On the Zabbix server an item of type **Zabbix trapper** should be created with corresponding key. Note that incoming values will only be accepted from hosts specified in **Allowed hosts** field for this item. [ ]{#lbAE} ## DESCRIPTION **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE} ## DESCRIPTION **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE} # dhost.get # dhost.get #### Disabled autocomplete attribute for sensitive fields To avoid potential exposure of data, the autocomplete attribute is now turned off for many fields containing sensitive information, such as a user's password for logging into Zabbix, pre-shared keys (PSK), macro values, usernames and passwords used for data collection by various items and hosts, SNMPv3 authentication and privacy passphrases, passwords for media types; SSL key password and HTTP proxy fields used in web scenarios and HTTP items; usernames, passwords and key passphrases in remote commands. This setting shall prevent most browsers from using autocompletion in the affected fields. #### Disabled autocomplete attribute for sensitive fields To avoid potential exposure of data, the autocomplete attribute is now turned off for many fields containing sensitive information, such as a user's password for logging into Zabbix, pre-shared keys (PSK), macro values, usernames and passwords used for data collection by various items and hosts, SNMPv3 authentication and privacy passphrases, passwords for media types; SSL key password and HTTP proxy fields used in web scenarios and HTTP items; usernames, passwords and key passphrases in remote commands. This setting shall prevent most browsers from using autocompletion in the affected fields. #### discoveryrule Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `discoveryrule.create`, `discoveryrule.update`: changed "username" and "password" fields to optional for HTTP agent type discovery rules and using authentication\ #### discoveryrule Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `discoveryrule.create`, `discoveryrule.update`: changed "username" and "password" fields to optional for HTTP agent type discovery rules and using authentication\ # discoveryrule.copy # discoveryrule.copy # discoveryrule.create # discoveryrule.create # discoveryrule.delete # discoveryrule.delete # discoveryrule.get # discoveryrule.get # discoveryrule.update # discoveryrule.update #### Displaying URL content in the sandbox Since version 4.0.22, some Zabbix frontend elements (for example, the [URL widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)) are preconfigured to sandbox content retrieved from the URL. It is recommended to keep all sandboxing restrictions enabled to ensure protection against XSS attacks. #### Displaying URL content in the sandbox Since version 4.0.22, some Zabbix frontend elements (for example, the [URL widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)) are preconfigured to sandbox content retrieved from the URL. It is recommended to keep all sandboxing restrictions enabled to ensure protection against XSS attacks. #### Display In *Monitoring → Maps* the respective color will be displayed on the link if the trigger goes into a problem state.  ::: noteclassic If multiple triggers go into a problem state, the problem with the highest severity will determine the link style and color. If multiple triggers with the same severity are assigned to the same map link, the one with the lowest ID takes precedence. Note also that:\ \ 1. *Minimimum trigger severity* and *Show suppressed problem* settings from map configuration affect which problems are taken into account.\ 2. In case with triggers with multiple problems (multiple problem generation), each problem may have severity that differs from trigger severity (changed manually), may have different tags (due to macros) and may be suppressed. ::: #### Display In *Monitoring → Maps* the respective color will be displayed on the link if the trigger goes into a problem state.  ::: noteclassic If multiple triggers go into a problem state, the problem with the highest severity will determine the link style and color. If multiple triggers with the same severity are assigned to the same map link, the one with the lowest ID takes precedence. Note also that:\ \ 1. *Minimimum trigger severity* and *Show suppressed problem* settings from map configuration affect which problems are taken into account.\ 2. In case with triggers with multiple problems (multiple problem generation), each problem may have severity that differs from trigger severity (changed manually), may have different tags (due to macros) and may be suppressed. ::: #### Display Slide shows that are ready can be viewed in *Monitoring → Screens*, then choosing *Slide shows* from the dropdown and clicking on the slide show name. With the Menu option next to the dropdown, you can accelerate or slow down the display by choosing a slide delay multiplier:  ::: noteimportant If a delay ends up as being less than 5 seconds (either by having entered a delay less than 5 seconds or by using the slide delay multiplier), a 5-second minimum delay will be used. ::: #### Display Slide shows that are ready can be viewed in *Monitoring → Screens*, then choosing *Slide shows* from the dropdown and clicking on the slide show name. With the Menu option next to the dropdown, you can accelerate or slow down the display by choosing a slide delay multiplier:  ::: noteimportant If a delay ends up as being less than 5 seconds (either by having entered a delay less than 5 seconds or by using the slide delay multiplier), a 5-second minimum delay will be used. ::: #### Docker appliance support dropped Zabbix Docker Appliance image has been decommissioned and will not be available for 4.0.20 and newer releases. Please use a separate Docker image for each component instead of the all-in-one solution. #### Docker appliance support dropped Zabbix Docker Appliance image has been decommissioned and will not be available for 4.0.20 and newer releases. Please use a separate Docker image for each component instead of the all-in-one solution. #### Dropping values outside history/trend periods From now on values older than the configured history and trend storage period will be rejected, even if the internal housekeeping is disabled. You may want to adjust history/trend storage periods after the upgrade. #### Dropping values outside history/trend periods From now on values older than the configured history and trend storage period will be rejected, even if the internal housekeeping is disabled. You may want to adjust history/trend storage periods after the upgrade. # drule.create # drule.create # drule.delete # drule.delete # drule.get # drule.get # drule.update # drule.update #### dservice Bug fixes:\ [ZBX-14833](https://support.zabbix.com/browse/ZBX-14833) `dservice.get`: fixed "selectHosts" option to return correct hosts that are monitored by current proxy or server\ #### dservice Bug fixes:\ [ZBX-14833](https://support.zabbix.com/browse/ZBX-14833) `dservice.get`: fixed "selectHosts" option to return correct hosts that are monitored by current proxy or server\ # dservice.get # dservice.get #### Dynamic elements For some of the elements there is an extra option called *Dynamic item*. Checking this box at first does not to seem to change anything. However, once you go to *Monitoring → Screens*, you may realize that now you have extra dropdowns there for selecting the host. Thus you have a screen where some elements display the same information while others display information depending on the currently selected host. The benefit of this is that you do not need to create extra screens just because you want to see the same graphs containing data from various hosts. *Dynamic item* option is available for several screen elements: - Graphs (custom graphs) - Graph prototypes - Simple graphs - Simple graph prototypes - Plain text - URL ::: noteclassic Clicking on a dynamic graph opens it in full view; although with custom graphs and graph prototypes that is currently supported with the default host only (i.e. with host 'not selected' in the dropdown). When selecting another host in the dropdown, the dynamic graph is created using item data of that host and the resulting graph is not clickable. ::: ::: noteclassic Dynamic URL elements will not be displayed in *Monitoring* → *Screens*, unless a host is selected. Without a selected host the "No host selected" message will be visible only. ::: #### Dynamic elements For some of the elements there is an extra option called *Dynamic item*. Checking this box at first does not to seem to change anything. However, once you go to *Monitoring → Screens*, you may realize that now you have extra dropdowns there for selecting the host. Thus you have a screen where some elements display the same information while others display information depending on the currently selected host. The benefit of this is that you do not need to create extra screens just because you want to see the same graphs containing data from various hosts. *Dynamic item* option is available for several screen elements: - Graphs (custom graphs) - Graph prototypes - Simple graphs - Simple graph prototypes - Plain text - URL ::: noteclassic Clicking on a dynamic graph opens it in full view; although with custom graphs and graph prototypes that is currently supported with the default host only (i.e. with host 'not selected' in the dropdown). When selecting another host in the dropdown, the dynamic graph is created using item data of that host and the resulting graph is not clickable. ::: ::: noteclassic Dynamic URL elements will not be displayed in *Monitoring* → *Screens*, unless a host is selected. Without a selected host the "No host selected" message will be visible only. ::: #### Encryption User-configured [ciphersuites](/manual/encryption#ciphersuites) are now supported for GnuTLS and OpenSSL. #### Encryption User-configured [ciphersuites](/manual/encryption#ciphersuites) are now supported for GnuTLS and OpenSSL. #### Enhanced URL widget security The URL dashboard widget and the URL screen element now put retrieved URL content into the sandbox. By default, all sandbox restrictions are enabled. It is possible to modify `sandbox` attribute settings in the *defines.inc.php* file, however turning sandboxing off is not recommended for security reasons. To learn more about the sandbox attribute, please see the [sandbox](https://www.w3.org/TR/2010/WD-html5-20100624/the-iframe-element.html#attr-iframe-sandbox) section of the iframe HTML element description. #### Enhanced URL widget security The URL dashboard widget and the URL screen element now put retrieved URL content into the sandbox. By default, all sandbox restrictions are enabled. It is possible to modify `sandbox` attribute settings in the *defines.inc.php* file, however turning sandboxing off is not recommended for security reasons. To learn more about the sandbox attribute, please see the [sandbox](https://www.w3.org/TR/2010/WD-html5-20100624/the-iframe-element.html#attr-iframe-sandbox) section of the iframe HTML element description. #### Enhanced URL widget security The URL dashboard widget and the URL screen element now put retrieved URL content into the sandbox. By default, all sandbox restrictions are enabled. It is possible to modify `sandbox` attribute settings in the *defines.inc.php* file, however turning sandboxing off is not recommended for security reasons. To learn more about the sandbox attribute, please see the [sandbox](https://www.w3.org/TR/2010/WD-html5-20100624/the-iframe-element.html#attr-iframe-sandbox) section of the iframe HTML element description. #### Enhanced URL widget security The URL dashboard widget and the URL screen element now put retrieved URL content into the sandbox. By default, all sandbox restrictions are enabled. It is possible to modify `sandbox` attribute settings in the *defines.inc.php* file, however turning sandboxing off is not recommended for security reasons. To learn more about the sandbox attribute, please see the [sandbox](https://www.w3.org/TR/2010/WD-html5-20100624/the-iframe-element.html#attr-iframe-sandbox) section of the iframe HTML element description. # event.acknowledge # event.acknowledge # event.get # event.get ##### Example configuration for Apache # .. ProxyPass "/" http://host/zabbix/ ProxyPassReverse "/" http://host/zabbix/ ProxyPassReverseCookiePath /zabbix / ProxyPassReverseCookieDomain host zabbix.example.com # .. ##### Example configuration for Apache # .. ProxyPass "/" http://host/zabbix/ ProxyPassReverse "/" http://host/zabbix/ ProxyPassReverseCookiePath /zabbix / ProxyPassReverseCookieDomain host zabbix.example.com # .. ##### Example configuration for nginx # .. location / { # .. proxy_cookie_path /zabbix /; proxy_pass http://192.168.0.94/zabbix/; # .. ##### Example configuration for nginx # .. location / { # .. proxy_cookie_path /zabbix /; proxy_pass http://192.168.0.94/zabbix/; # .. #### Examples #### Examples ## EXAMPLES **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH} ## EXAMPLES **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH} ## EXAMPLES **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of monitored host. Use monitored host and Zabbix server defined in agent configuration file. **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of **Monitored Host** host using Zabbix server defined in agent configuration file. \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt** \ Send values from file **data\_values.txt** to Zabbix server with IP **192.168.1.113**. Host names and keys are defined in the file. \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\ Send a timestamped value from the commandline to Zabbix server, specified in the agent configuration file. Dash in the input data indicates that hostname also should be used from the same configuration file. \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\ Send empty value of an item to the Zabbix server with IP address **192.168.1.113** on port **10000** from the commandline. Empty values must be indicated by empty double quotes. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with certificate. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with pre-shared key (PSK). [ ]{#lbAI} ## EXAMPLES **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of monitored host. Use monitored host and Zabbix server defined in agent configuration file. **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of **Monitored Host** host using Zabbix server defined in agent configuration file. \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt** \ Send values from file **data\_values.txt** to Zabbix server with IP **192.168.1.113**. Host names and keys are defined in the file. \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\ Send a timestamped value from the commandline to Zabbix server, specified in the agent configuration file. Dash in the input data indicates that hostname also should be used from the same configuration file. \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\ Send empty value of an item to the Zabbix server with IP address **192.168.1.113** on port **10000** from the commandline. Empty values must be indicated by empty double quotes. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with certificate. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with pre-shared key (PSK). [ ]{#lbAI} ## EXIT STATUS The exit status is 0 if the values were sent and all of them were successfully processed by server. If data was sent, but processing of at least one of the values failed, the exit status is 2. If data sending failed, the exit status is 1. [ ]{#lbAH} ## EXIT STATUS The exit status is 0 if the values were sent and all of them were successfully processed by server. If data was sent, but processing of at least one of the values failed, the exit status is 2. If data sending failed, the exit status is 1. [ ]{#lbAH} ## FILES */usr/local/etc/zabbix\_agentd.conf* Default location of Zabbix agent configuration file (if not modified during compile time). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_agentd.conf* Default location of Zabbix agent configuration file (if not modified during compile time). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_proxy.conf* Default location of Zabbix proxy configuration file (if not modified during compile time). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_proxy.conf* Default location of Zabbix proxy configuration file (if not modified during compile time). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_server.conf* Default location of Zabbix server configuration file (if not modified during compile time). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_server.conf* Default location of Zabbix server configuration file (if not modified during compile time). [ ]{#lbAI} #### Filter expression Filter expression is a arithmetical expression in infix notation. Supported operands: |Operand|Description|Example| |-------|-----------|-------| |`"<text>"`<br>`'<text>'`|Text constant.|'value: \\'1\\''<br>"value: '1'"| |`<number>`|Numeric constant supporting scientific notation.|123| |`<jsonpath starting with $>`|Value referred to by the JSONPath from the input document root node; only definite paths are supported.|$.object.name| |`<jsonpath starting with @>`|Value referred to by the JSONPath from the current object/element; only definite paths are supported.|@.name| Supported operators: |Operator|Type|Description|Result| |--------|----|-----------|------| |`-`|binary|Subtraction.|Number.| |`+`|binary|Addition.|Number.| |`/`|binary|Division.|Number.| |`*`|binary|Multiplication.|Number.| |`==`|binary|Is equal to.|Boolean (1 or 0).| |`!=`|binary|Is not equal to.|Boolean (1 or 0).| |`<`|binary|Is less than.|Boolean (1 or 0).| |`<=`|binary|Is less than or equal to.|Boolean (1 or 0).| |`>`|binary|Is greater than.|Boolean (1 or 0).| |`>=`|binary|Is greater than or equal to.|Boolean (1 or 0).| |`=~`|binary|Matches regular expression.|Boolean (1 or 0).| |`!`|unary|Boolean not.|Boolean (1 or 0).| |`\|\|`|binary|Boolean or.|Boolean (1 or 0).| |`&&`|binary|Boolean and.|Boolean (1 or 0).| #### Filter expression Filter expression is a arithmetical expression in infix notation. Supported operands: |Operand|Description|Example| |-------|-----------|-------| |`"<text>"`<br>`'<text>'`|Text constant.|'value: \\'1\\''<br>"value: '1'"| |`<number>`|Numeric constant supporting scientific notation.|123| |`<jsonpath starting with $>`|Value referred to by the JSONPath from the input document root node; only definite paths are supported.|$.object.name| |`<jsonpath starting with @>`|Value referred to by the JSONPath from the current object/element; only definite paths are supported.|@.name| Supported operators: |Operator|Type|Description|Result| |--------|----|-----------|------| |`-`|binary|Subtraction.|Number.| |`+`|binary|Addition.|Number.| |`/`|binary|Division.|Number.| |`*`|binary|Multiplication.|Number.| |`==`|binary|Is equal to.|Boolean (1 or 0).| |`!=`|binary|Is not equal to.|Boolean (1 or 0).| |`<`|binary|Is less than.|Boolean (1 or 0).| |`<=`|binary|Is less than or equal to.|Boolean (1 or 0).| |`>`|binary|Is greater than.|Boolean (1 or 0).| |`>=`|binary|Is greater than or equal to.|Boolean (1 or 0).| |`=~`|binary|Matches regular expression.|Boolean (1 or 0).| |`!`|unary|Boolean not.|Boolean (1 or 0).| |`\|\|`|binary|Boolean or.|Boolean (1 or 0).| |`&&`|binary|Boolean and.|Boolean (1 or 0).| ##### Filtering by host In the *by host* mode results can be filtered by host or by host group. Specifying a parent host group implicitly selects all nested host groups. ##### Filtering by host In the *by host* mode results can be filtered by host or by host group. Specifying a parent host group implicitly selects all nested host groups. ##### Filtering by trigger template In the *by trigger template* mode results can be filtered by one or several parameters listed below. |Parameter|Description| |---------|-----------| |*Template group*|Select all hosts with triggers from templates belonging to that group. Any host group that includes at least one template can be selected.| |*Template*|Select hosts with triggers from chosen template and all nested templates. Only triggers inherited from the selected template will be displayed. If a nested template has additional own triggers, those triggers will not be displayed.| |//Template trigger //|Select hosts with chosen trigger. Other triggers of the selected hosts will not be displayed.| |*Host group*|Select hosts belonging to the group.| ##### Filtering by trigger template In the *by trigger template* mode results can be filtered by one or several parameters listed below. |Parameter|Description| |---------|-----------| |*Template group*|Select all hosts with triggers from templates belonging to that group. Any host group that includes at least one template can be selected.| |*Template*|Select hosts with triggers from chosen template and all nested templates. Only triggers inherited from the selected template will be displayed. If a nested template has additional own triggers, those triggers will not be displayed.| |//Template trigger //|Select hosts with chosen trigger. Other triggers of the selected hosts will not be displayed.| |*Host group*|Select hosts belonging to the group.| ##### Footnotes ^**1**^ Default value. ##### Footnotes ^**1**^ Default value. ##### Footnotes ^**1**^ If multiple macros in a field or macros mixed with text are not supported for the location, a single macro has to fill the whole field. ##### Footnotes ^**1**^ If multiple macros in a field or macros mixed with text are not supported for the location, a single macro has to fill the whole field. ##### Footnotes ^**1**^ In the fields marked with ^[1](lld_macros#footnotes)^ a single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported. ##### Footnotes ^**1**^ In the fields marked with ^[1](lld_macros#footnotes)^ a single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported. ##### Footnotes ^**1**^ Note that too many data gathering processes (pollers, unreachable pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers) together with IPMI manager, SNMP trapper and preprocessing workers can **exhaust** the per-process file descriptor limit for the preprocessing manager. ::: notewarning This will cause Zabbix server to stop (usually shortly after the start, but sometimes it can take more time). The configuration file should be revised or the limit should be raised to avoid this situation. ::: ^**2**^ When a lot of items are deleted it increases the load to the database, because the housekeeper will need to remove all the history data that these items had. For example, if we only have to remove 1 item prototype, but this prototype is linked to 50 hosts and for every host the prototype is expanded to 100 real items, 5000 items in total have to be removed (1\*50\*100). If 500 is set for MaxHousekeeperDelete (MaxHousekeeperDelete=500), the housekeeper process will have to remove up to 2500000 values (5000\*500) for the deleted items from history and trends tables in one cycle. ##### Footnotes ^**1**^ Note that too many data gathering processes (pollers, unreachable pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers) together with IPMI manager, SNMP trapper and preprocessing workers can **exhaust** the per-process file descriptor limit for the preprocessing manager. ::: notewarning This will cause Zabbix server to stop (usually shortly after the start, but sometimes it can take more time). The configuration file should be revised or the limit should be raised to avoid this situation. ::: ^**2**^ When a lot of items are deleted it increases the load to the database, because the housekeeper will need to remove all the history data that these items had. For example, if we only have to remove 1 item prototype, but this prototype is linked to 50 hosts and for every host the prototype is expanded to 100 real items, 5000 items in total have to be removed (1\*50\*100). If 500 is set for MaxHousekeeperDelete (MaxHousekeeperDelete=500), the housekeeper process will have to remove up to 2500000 values (5000\*500) for the deleted items from history and trends tables in one cycle. ##### Footnotes ^**1**^ The VMware performance counter path has the `group/counter[rollup]` format where: - `group` - the performance counter group, for example *cpu* - `counter` - the performance counter name, for example *usagemhz* - `rollup` - the performance counter rollup type, for example *average* So the above example would give the following counter path: `cpu/usagemhz[average]` The performance counter group descriptions, counter names and rollup types can be found in [VMware documentation](https://www.vmware.com/support/developer/converter-sdk/conv60_apireference/vim.PerformanceManager.html). ^**2**^ The value of these items is obtained from VMware performance counters and the VMwarePerfFrequency [parameter](/manual/appendix/config/zabbix_server) is used to refresh their data in Zabbix VMware cache: - vmware.hv.datastore.read - vmware.hv.datastore.write - vmware.hv.network.in - vmware.hv.network.out - vmware.hv.perfcounter - vmware.vm.cpu.ready - vmware.vm.net.if.in - vmware.vm.net.if.out - vmware.vm.perfcounter - vmware.vm.vfs.dev.read - vmware.vm.vfs.dev.write ##### Footnotes ^**1**^ The VMware performance counter path has the `group/counter[rollup]` format where: - `group` - the performance counter group, for example *cpu* - `counter` - the performance counter name, for example *usagemhz* - `rollup` - the performance counter rollup type, for example *average* So the above example would give the following counter path: `cpu/usagemhz[average]` The performance counter group descriptions, counter names and rollup types can be found in [VMware documentation](https://www.vmware.com/support/developer/converter-sdk/conv60_apireference/vim.PerformanceManager.html). ^**2**^ The value of these items is obtained from VMware performance counters and the VMwarePerfFrequency [parameter](/manual/appendix/config/zabbix_server) is used to refresh their data in Zabbix VMware cache: - vmware.hv.datastore.read - vmware.hv.datastore.write - vmware.hv.network.in - vmware.hv.network.out - vmware.hv.perfcounter - vmware.vm.cpu.ready - vmware.vm.net.if.in - vmware.vm.net.if.out - vmware.vm.perfcounter - vmware.vm.vfs.dev.read - vmware.vm.vfs.dev.write #### Form buttons Buttons at the bottom of the form allow to perform several operations. | | | |---|---| ||Add an item. This button is only available for new items.| ||Update the properties of an item.| ||Create another item based on the properties of the current item.| ||Execute a check for a new item value immediately. Supported for **passive** checks only (see [more details](/manual/config/items/check_now)).<br>*Note* that when checking for a value immediately, configuration cache is not updated, thus the value will not reflect very recent changes to item configuration.| ||Delete the item history and trends.| ||Delete the item.| ||Cancel the editing of item properties.| #### Form buttons Buttons at the bottom of the form allow to perform several operations. | | | |---|---| ||Add an item. This button is only available for new items.| ||Update the properties of an item.| ||Create another item based on the properties of the current item.| ||Execute a check for a new item value immediately. Supported for **passive** checks only (see [more details](/manual/config/items/check_now)).<br>*Note* that when checking for a value immediately, configuration cache is not updated, thus the value will not reflect very recent changes to item configuration.| ||Delete the item history and trends.| ||Delete the item.| ||Cancel the editing of item properties.| #### Frontend If Zabbix web interface is opened in one of the languages available on the Zabbix website, clicking the Support link will open the Support page in the appropriate language. For all other languages, including English, the Support page will be opened in English. #### Frontend If Zabbix web interface is opened in one of the languages available on the Zabbix website, clicking the Support link will open the Support page in the appropriate language. For all other languages, including English, the Support page will be opened in English. #### Full JSONPath functionality supported Full support of [JSONPath functionality](/manual/appendix/items/jsonpath) has been added in item value preprocessing. #### Full JSONPath functionality supported Full support of [JSONPath functionality](/manual/appendix/items/jsonpath) has been added in item value preprocessing. #### Functions and unsupported items Since Zabbix 3.2, **nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **now()** and **time()** functions are calculated for unsupported items, too. Other functions require that the referenced item is in a supported state. #### Functions and unsupported items Since Zabbix 3.2, **nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **now()** and **time()** functions are calculated for unsupported items, too. Other functions require that the referenced item is in a supported state. #### Functions Functions can be used at the end of JSONPath. Multiple functions can be chained if the preceding function returns value that is accepted by the following function. Supported functions: |Function|Description|Input|Output| |--------|-----------|-----|------| |`avg`|Average value of numbers in input array.|Array of numbers.|Number.| |`min`|Minimum value of numbers in input array.|Array of numbers.|Number.| |`max`|Maximum value of numbers in input array.|Array of numbers.|Number.| |`sum`|Sum of numbers in input array.|Array of numbers.|Number.| |`length`|Number of elements in input array.|Array.|Number.| |`first`|The first array element.|Array.|A JSON construct (object, array, value) depending on input array contents.| Quoted numeric values are accepted by the JSONPath aggregate functions since Zabbix 4.0.14. It means that the values are converted from string type to numeric if aggregation is required. Incompatible input will cause the function to generate error. #### Functions Functions can be used at the end of JSONPath. Multiple functions can be chained if the preceding function returns value that is accepted by the following function. Supported functions: |Function|Description|Input|Output| |--------|-----------|-----|------| |`avg`|Average value of numbers in input array.|Array of numbers.|Number.| |`min`|Minimum value of numbers in input array.|Array of numbers.|Number.| |`max`|Maximum value of numbers in input array.|Array of numbers.|Number.| |`sum`|Sum of numbers in input array.|Array of numbers.|Number.| |`length`|Number of elements in input array.|Array.|Number.| |`first`|The first array element.|Array.|A JSON construct (object, array, value) depending on input array contents.| Quoted numeric values are accepted by the JSONPath aggregate functions since Zabbix 4.0.14. It means that the values are converted from string type to numeric if aggregation is required. Incompatible input will cause the function to generate error. ##### Generating from history/trends Graphs can be drawn based on either item [history or trends](/manual/config/items/history_and_trends). For the users who have frontend [debug mode](/manual/web_interface/debug_mode) activated, a gray, vertical caption is displayed at the bottom right of a graph indicating where the data come from. Several factors influence whether history of trends is used: - longevity of item history. For example, item history can be kept for 14 days. In that case, any data older than the fourteen days will be coming from trends. ```{=html} <!-- --> ``` - data congestion in the graph. If the amount of seconds to display in a horizontal graph pixel exceeds 3600/16, trend data are displayed (even if item history is still available for the same period). ```{=html} <!-- --> ``` - if trends are disabled, item history is used for graph building - if available for that period. This is supported starting with Zabbix 2.2.1 (before, disabled trends would mean an empty graph for the period even if item history was available). ##### Generating from history/trends Graphs can be drawn based on either item [history or trends](/manual/config/items/history_and_trends). For the users who have frontend [debug mode](/manual/web_interface/debug_mode) activated, a gray, vertical caption is displayed at the bottom right of a graph indicating where the data come from. Several factors influence whether history of trends is used: - longevity of item history. For example, item history can be kept for 14 days. In that case, any data older than the fourteen days will be coming from trends. ```{=html} <!-- --> ``` - data congestion in the graph. If the amount of seconds to display in a horizontal graph pixel exceeds 3600/16, trend data are displayed (even if item history is still available for the same period). ```{=html} <!-- --> ``` - if trends are disabled, item history is used for graph building - if available for that period. This is supported starting with Zabbix 2.2.1 (before, disabled trends would mean an empty graph for the period even if item history was available). #### Global notifications Default audio clips are now in MP3 (it used to be wave files). An embedded media player is not used any more (it was used for Internet Explorer only), so now, in case of custom audio files, you must be sure that your browser can play them (or just use the MP3 format). #### Global notifications Default audio clips are now in MP3 (it used to be wave files). An embedded media player is not used any more (it was used for Internet Explorer only), so now, in case of custom audio files, you must be sure that your browser can play them (or just use the MP3 format). #### Global notifications Several improvements have been made to [global notification](/manual/web_interface/user_profile/global_notifications) messages and sounds: - Notifications are synchronized across tabs and windows. Any changes to the list of notifications are immediately rendered into other tabs. - Notification timeout is calculated since the first rendering time of the notification. - The *Display OK triggers for* [setting](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options) is now applied to recovery type notifications. That becomes relevant if it is shorter than the regular problem notification message timeout thus the notification disappears sooner. - Default audio clips are now in MP3 (it used to be wave files). An embedded media player is not used any more (it was used for Internet Explorer only), so now, in case of custom audio files, you must be sure that your browser can play them (or just use the MP3 format). - The sound tends to follow the focused tab/window, except when *Play sound* is set to 'Once'. - When *Play sound* is set to 'Once' it will not replay the sound on page reload. - In case of several notifications, the sound of the most severe or the most recent notification is played. - There is now an icon next to each snoozed notification. - It is possible to snooze a whole list of notifications of *High* severity and be assured to receive an alarm when an *Average* severity notification arrives, meanwhile keeping the notification list with all event links open. - If you snooze a notification in problem state, it will not play audio when the particular problem becomes resolved. - Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title in response, if the client receives the same notification ID. - Recovery of a crashed tab is implemented. Any tab that is still able to execute JavaStript will detect a crashed tab and would continue to be the one who polls server. In case of a slow connection and heavy page load during the request, any other tab would continue to poll for notifications. Thus with a notification timeout (30 seconds) and a performed request (40 seconds) one can be assured that no notifications will miss the eye if there is another tab.. - Slide animations are improved. Fade out will happen when all remaining notifications reach the message timeout at once, else the consecutive slide-up transition is applied. - Updated user settings, such as the timeout and audiofile, are applied to the list of notifications dynamically. #### Global notifications Several improvements have been made to [global notification](/manual/web_interface/user_profile/global_notifications) messages and sounds: - Notifications are synchronized across tabs and windows. Any changes to the list of notifications are immediately rendered into other tabs. - Notification timeout is calculated since the first rendering time of the notification. - The *Display OK triggers for* [setting](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options) is now applied to recovery type notifications. That becomes relevant if it is shorter than the regular problem notification message timeout thus the notification disappears sooner. - Default audio clips are now in MP3 (it used to be wave files). An embedded media player is not used any more (it was used for Internet Explorer only), so now, in case of custom audio files, you must be sure that your browser can play them (or just use the MP3 format). - The sound tends to follow the focused tab/window, except when *Play sound* is set to 'Once'. - When *Play sound* is set to 'Once' it will not replay the sound on page reload. - In case of several notifications, the sound of the most severe or the most recent notification is played. - There is now an icon next to each snoozed notification. - It is possible to snooze a whole list of notifications of *High* severity and be assured to receive an alarm when an *Average* severity notification arrives, meanwhile keeping the notification list with all event links open. - If you snooze a notification in problem state, it will not play audio when the particular problem becomes resolved. - Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title in response, if the client receives the same notification ID. - Recovery of a crashed tab is implemented. Any tab that is still able to execute JavaStript will detect a crashed tab and would continue to be the one who polls server. In case of a slow connection and heavy page load during the request, any other tab would continue to poll for notifications. Thus with a notification timeout (30 seconds) and a performed request (40 seconds) one can be assured that no notifications will miss the eye if there is another tab.. - Slide animations are improved. Fade out will happen when all remaining notifications reach the message timeout at once, else the consecutive slide-up transition is applied. - Updated user settings, such as the timeout and audiofile, are applied to the list of notifications dynamically. # graph.create # graph.create # graph.delete # graph.delete # graph.get # graph.get # graphitem.get # graphitem.get ##### Graph preview In the *Preview* tab, a preview of the graph is displayed so you can immediately see what you are creating. {width="600"} Note that the preview will not show any data for template items. {width="600"} In this example, pay attention to the dashed bold line displaying the trigger level and the trigger information displayed in the legend. ::: noteclassic No more than 3 trigger lines can be displayed. If there are more triggers then the triggers with lower severity are prioritized for display.\ \ If graph height is set as less than 120 pixels, no trigger will be displayed in the legend. ::: ##### Graph preview In the *Preview* tab, a preview of the graph is displayed so you can immediately see what you are creating. {width="600"} Note that the preview will not show any data for template items. {width="600"} In this example, pay attention to the dashed bold line displaying the trigger level and the trigger information displayed in the legend. ::: noteclassic No more than 3 trigger lines can be displayed. If there are more triggers then the triggers with lower severity are prioritized for display.\ \ If graph height is set as less than 120 pixels, no trigger will be displayed in the legend. ::: # graphprototype.create # graphprototype.create # graphprototype.delete # graphprototype.delete # graphprototype.get # graphprototype.get # graphprototype.update # graphprototype.update # graph.update # graph.update #### Guest user disabled The "guest" user is now disabled by default in new installations. #### Guest user disabled The "guest" user is now disabled by default in new installations. #### Guest user info In previous versions, when logged in as guest, there was no way to tell what user you were logged in as, because the profile icon was hidden for the guest user. In the new version a slightly different version of the profile icon is displayed when you are logged in as guest - . This icon is not clickable and does not lead to the user profile. When the mouse is positioned over it, info is displayed with the name 'guest' to suggest the currently logged in user. #### Guest user info In previous versions, when logged in as guest, there was no way to tell what user you were logged in as, because the profile icon was hidden for the guest user. In the new version a slightly different version of the profile icon is displayed when you are logged in as guest - . This icon is not clickable and does not lead to the user profile. When the mouse is positioned over it, info is displayed with the name 'guest' to suggest the currently logged in user. # history.get # history.get #### Host column always displayed The host column is now always displayed even if only one host is selected in: - *Monitoring* → *Latest data* - *Monitoring* → *Web* - *Reports* → *Availability* This results in a wider page than previously with one host data. For more information, see the [What's new](/manual/introduction/whatsnew400#host_column_always_displayed) section. #### Host column always displayed The host column is now always displayed even if only one host is selected in: - *Monitoring* → *Latest data* - *Monitoring* → *Web* - *Reports* → *Availability* This results in a wider page than previously with one host data. For more information, see the [What's new](/manual/introduction/whatsnew400#host_column_always_displayed) section. # host.create # host.create # host.delete # host.delete # host.get # host.get # hostgroup.create # hostgroup.create # hostgroup.delete # hostgroup.delete # hostgroup.get # hostgroup.get # hostgroup.massadd # hostgroup.massadd # hostgroup.massremove # hostgroup.massremove # hostgroup.massupdate # hostgroup.massupdate # hostgroup.update # hostgroup.update #### Host information in VMware event log The information returned by the `vmware.eventlog[<url>,<mode>]` item now contains information about the source host, if such information is detected in the log. #### Host information in VMware event log The information returned by the `vmware.eventlog[<url>,<mode>]` item now contains information about the source host, if such information is detected in the log. # hostinterface.create # hostinterface.create # hostinterface.delete # hostinterface.delete # hostinterface.get # hostinterface.get # hostinterface.massadd # hostinterface.massadd # hostinterface.massremove # hostinterface.massremove # hostinterface.replacehostinterfaces # hostinterface.replacehostinterfaces # hostinterface.update # hostinterface.update # host.massadd # host.massadd # host.massremove # host.massremove # host.massupdate # host.massupdate # hostprototype.create # hostprototype.create # hostprototype.delete # hostprototype.delete # hostprototype.get # hostprototype.get # hostprototype.update # hostprototype.update #### Hosts In a [host](/manual/config/hosts/host) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Interface IP/DNS|<|DNS only| |Interface port|<|no| |*SNMP v1, v2*|<|<| |<|Interface community|yes| |*SNMP v3*|<|<| |<|Interface context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |*IPMI*|<|<| |<|Username|yes| |^|Password|yes| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| #### Hosts In a [host](/manual/config/hosts/host) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Interface IP/DNS|<|DNS only| |Interface port|<|no| |*SNMP v1, v2*|<|<| |<|Interface community|yes| |*SNMP v3*|<|<| |<|Interface context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |*IPMI*|<|<| |<|Username|yes| |^|Password|yes| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| #### Host/template cloning Long lists of objects to be cloned (items, triggers, graphs, etc) have been removed from host and template full clone forms. #### Host/template cloning Long lists of objects to be cloned (items, triggers, graphs, etc) have been removed from host and template full clone forms. # host.update # host.update #### HP Comware template The *Template Net HP Comware HH3C SNMPv2* now contains the correct value mapping. #### HP Comware template The *Template Net HP Comware HH3C SNMPv2* now contains the correct value mapping. #### HP iLO template The counter for overall server health check has been fixed in the *Template Server HP iLO SNMPv2* template. #### HP iLO template The counter for overall server health check has been fixed in the *Template Server HP iLO SNMPv2* template. #### httptest Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `httptest.create`, `httptest.update`: changed "http\_user" and "http\_password" fields to optional when using authentication\ #### httptest Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `httptest.create`, `httptest.update`: changed "http\_user" and "http\_password" fields to optional when using authentication\ # httptest.create # httptest.create # httptest.delete # httptest.delete # httptest.get # httptest.get # httptest.update # httptest.update # iconmap.create # iconmap.create # iconmap.delete # iconmap.delete # iconmap.get # iconmap.get # iconmap.update # iconmap.update # image.create # image.create # image.delete # image.delete # image.get # image.get # image.update # image.update #### Import option to remove existing template linkage During host or template import it is now possible to update template linkage using the *Delete missing* option. If using this option any template linkage that does not also exist in the import file will be deleted from the existing host/template along with **all** entities inherited from these unlinked templates (items, triggers, etc).  By default this option is unchecked and before it is possible to mark this checkbox a warning message is displayed that all inherited entities may be lost as a result. #### Import option to remove existing template linkage During host or template import it is now possible to update template linkage using the *Delete missing* option. If using this option any template linkage that does not also exist in the import file will be deleted from the existing host/template along with **all** entities inherited from these unlinked templates (items, triggers, etc).  By default this option is unchecked and before it is possible to mark this checkbox a warning message is displayed that all inherited entities may be lost as a result. #### Increased proxy-server limit per connection Limit per connection has been increased from 128MB to 1GB packet size (ZBX\_MAX\_RECV\_DATA\_SIZE constant). #### Increased proxy-server limit per connection Limit per connection has been increased from 128MB to 1GB packet size (ZBX\_MAX\_RECV\_DATA\_SIZE constant). ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created by [man2html](/documentation/4.0/manpages), using the manual pages.\ Time: 15:28:13 GMT, October 18, 2018 ### Installing debuginfo packages ::: noteclassic Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5. ::: To enable debuginfo repository edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository. [zabbix-debuginfo] name=Zabbix Official Repository debuginfo - $basearch baseurl=http://repo.zabbix.com/zabbix/4.0/rhel/7/$basearch/debuginfo/ enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 gpgcheck=1 This will allow you to install the zabbix-debuginfo package. # yum install zabbix-debuginfo This single package contains debug information for all binary Zabbix components. ### Installing debuginfo packages ::: noteclassic Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5. ::: To enable debuginfo repository edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository. [zabbix-debuginfo] name=Zabbix Official Repository debuginfo - $basearch baseurl=http://repo.zabbix.com/zabbix/4.0/rhel/7/$basearch/debuginfo/ enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 gpgcheck=1 This will allow you to install the zabbix-debuginfo package. # yum install zabbix-debuginfo This single package contains debug information for all binary Zabbix components. #### Installing locales To list all installed languages, run: locale -a If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset. Now, run: locale-gen Restart the web server. The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear. #### Installing locales To list all installed languages, run: locale -a If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset. Now, run: locale-gen Restart the web server. The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear. #### Installing Zabbix If installing Zabbix directly from [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), translation files should be generated manually. To generate translation files, run: make gettext locale/make_mo.sh This step is not needed when installing Zabbix from packages or source tar.gz files. #### Installing Zabbix If installing Zabbix directly from [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), translation files should be generated manually. To generate translation files, run: make gettext locale/make_mo.sh This step is not needed when installing Zabbix from packages or source tar.gz files. #### Internal events can be disabled Internal events will not be created, if all internal actions for them are disabled --- this can be useful for reducing the amount of event records and controlling the size of the event tables. See [more information](/manual/config/events/sources#internal_events). #### Internal events can be disabled Internal events will not be created, if all internal actions for them are disabled --- this can be useful for reducing the amount of event records and controlling the size of the event tables. See [more information](/manual/config/events/sources#internal_events). #### item Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `item.create`, `item.update`: changed "username" and "password" fields to optional for HTTP agent type items and using authentication\ #### item Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `item.create`, `item.update`: changed "username" and "password" fields to optional for HTTP agent type items and using authentication\ #### Item changes The Timeout [configuration parameter](/manual/appendix/config/zabbix_server) is now used for web.page.get, web.page.regexp and web.page.perf items. #### Item changes The Timeout [configuration parameter](/manual/appendix/config/zabbix_server) is now used for web.page.get, web.page.regexp and web.page.perf items. #### Item changes **web.page.get**, **web.page.perf**, **web.page.regexp** agent [items](/manual/config/items/itemtypes/zabbix_agent) now along with hostname also support URL as the first parameter, allowing to specify both HTTP and HTTPS protocols. As a prerequisite of SSL (HTTPS) functionality, the agent should be compiled with cURL support. Previously, only domain name or IP address was allowed in the first parameter and there was no support for HTTPS protocol. Additionally, Unicode is now supported in the hostnames of these items (Punycode support was added). #### Item changes **web.page.get**, **web.page.perf**, **web.page.regexp** agent [items](/manual/config/items/itemtypes/zabbix_agent) now along with hostname also support URL as the first parameter, allowing to specify both HTTP and HTTPS protocols. As a prerequisite of SSL (HTTPS) functionality, the agent should be compiled with cURL support. Previously, only domain name or IP address was allowed in the first parameter and there was no support for HTTPS protocol. Additionally, Unicode is now supported in the hostnames of these items (Punycode support was added). # item.create # item.create # item.delete # item.delete # item.get # item.get #### Item history Global housekeeper settings no longer override item-level history/trends settings in the case when keeping history/trends is entirely disabled on the item level. In addition, if previously disabling item history/trends had to be specified by entering '0' as the storage period value, now the same can be done using a dedicated radio button.  #### Item history Global housekeeper settings no longer override item-level history/trends settings in the case when keeping history/trends is entirely disabled on the item level. In addition, if previously disabling item history/trends had to be specified by entering '0' as the storage period value, now the same can be done using a dedicated radio button.  #### itemprototype Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `itemprototype.create`, `itemprototype.update`: changed "username" and "password" fields to optional for HTTP agent type item prototypes and using authentication\ #### itemprototype Bug fixes:\ [ZBX-10861](https://support.zabbix.com/browse/ZBX-10861) `itemprototype.create`, `itemprototype.update`: changed "username" and "password" fields to optional for HTTP agent type item prototypes and using authentication\ # itemprototype.create # itemprototype.create # itemprototype.delete # itemprototype.delete # itemprototype.get # itemprototype.get # itemprototype.update # itemprototype.update #### Items / item prototypes In an [item](/manual/config/items/item) or an [item prototype](/manual/discovery/low_level_discovery#item_prototypes) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name (deprecated)|<|yes| |Item key parameters|<|yes| |Update interval|<|no| |Custom intervals|<|no| |History storage period|<|no| |Trend storage period|<|no| |//Calculated item //|<|<| |<|Formula|yes| |*Database monitor*|<|<| |<|Username|yes| |^|Password|yes| |^|SQL query|yes| |//HTTP agent //|<|<| |<|URL|yes| |^|Query fields|yes| |^|Timeout|no| |^|Request body|yes| |^|Headers (names and values)|yes| |^|Required status codes|yes| |^|HTTP proxy|yes| |^|HTTP authentication username|yes| |^|HTTP authentication password|yes| |^|SSl certificate file|yes| |^|SSl key file|yes| |^|SSl key password|yes| |^|Allowed hosts|yes| |*JMX agent*|<|<| |<|JMX endpoint|yes| |//SNMP agent //|<|<| |<|SNMP OID|yes| |//SSH agent //|<|<| |<|Username|yes| |^|Public key file|yes| |^|Private key file|yes| |^|Password|yes| |^|Script|yes| |//TELNET agent //|<|<| |<|Username|yes| |^|Password|yes| |^|Script|yes| |//Zabbix trapper //|<|<| |<|Allowed hosts|yes| |*Preprocessing*|<|<| |<|Step parameters|yes| #### Items / item prototypes In an [item](/manual/config/items/item) or an [item prototype](/manual/discovery/low_level_discovery#item_prototypes) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name (deprecated)|<|yes| |Item key parameters|<|yes| |Update interval|<|no| |Custom intervals|<|no| |History storage period|<|no| |Trend storage period|<|no| |//Calculated item //|<|<| |<|Formula|yes| |*Database monitor*|<|<| |<|Username|yes| |^|Password|yes| |^|SQL query|yes| |//HTTP agent //|<|<| |<|URL|yes| |^|Query fields|yes| |^|Timeout|no| |^|Request body|yes| |^|Headers (names and values)|yes| |^|Required status codes|yes| |^|HTTP proxy|yes| |^|HTTP authentication username|yes| |^|HTTP authentication password|yes| |^|SSl certificate file|yes| |^|SSl key file|yes| |^|SSl key password|yes| |^|Allowed hosts|yes| |*JMX agent*|<|<| |<|JMX endpoint|yes| |//SNMP agent //|<|<| |<|SNMP OID|yes| |//SSH agent //|<|<| |<|Username|yes| |^|Public key file|yes| |^|Private key file|yes| |^|Password|yes| |^|Script|yes| |//TELNET agent //|<|<| |<|Username|yes| |^|Password|yes| |^|Script|yes| |//Zabbix trapper //|<|<| |<|Allowed hosts|yes| |*Preprocessing*|<|<| |<|Step parameters|yes| #### Items The **vmware.eventlog\[\]** item for [VMware monitoring](/manual/config/items/itemtypes/simple_checks/vmware_keys), when used with the 'skip' option, e. g. **vmware.eventlog\[<url>,skip\]** now behaves differently after being recreated (i.e. previous item removed, new one created with a different internal ID) - now the internal events cache is reset and only new events are read. Previously, the skip option would not be enforced in this scenario. #### Items The **vmware.eventlog\[\]** item for [VMware monitoring](/manual/config/items/itemtypes/simple_checks/vmware_keys), when used with the 'skip' option, e. g. **vmware.eventlog\[<url>,skip\]** now behaves differently after being recreated (i.e. previous item removed, new one created with a different internal ID) - now the internal events cache is reset and only new events are read. Previously, the skip option would not be enforced in this scenario. # item.update # item.update #### Item update interval for unreachable hosts A bug related to item check time on unreachable hosts has been fixed. This bug was introduced in Zabbix version 3.4.9 or 4.0.0. Now the item check period is recalculated based on the UnavailableDelay value, not on the item update period. This can potentially change unreachable poller performance. For example, if item previously had a delay of 1h then now it will be checked based on the UnavailableDelay value, not every 1h as it was (due to bug). Therefore it is recommended to increase UnavailableDelay value to avoid possible unreachable poller overload. #### Item update interval for unreachable hosts A bug related to item check time on unreachable hosts has been fixed. This bug was introduced in Zabbix version 3.4.9 or 4.0.0. Now the item check period is recalculated based on the UnavailableDelay value, not on the item update period. This can potentially change unreachable poller performance. For example, if item previously had a delay of 1h then now it will be checked based on the UnavailableDelay value, not every 1h as it was (due to bug). Therefore it is recommended to increase UnavailableDelay value to avoid possible unreachable poller overload. #### Java gateway property file A new `zabbix.propertiesFile` configuration [parameter](/manual/appendix/config/zabbix_java) allows to specify a property file, which can be used to set additional properties in such a way that they are not visible on a command line or to overwrite existing ones. #### Java gateway property file A new `zabbix.propertiesFile` configuration [parameter](/manual/appendix/config/zabbix_java) allows to specify a property file, which can be used to set additional properties in such a way that they are not visible on a command line or to overwrite existing ones. #### JMX monitoring error message As Zabbix Java gateway now supports working with custom MBeans returning non-primitive data types, which override the **toString()** method, the possible error message has been changed the following way: | | | |---|---| |*Previously:*|`data object type is not primitive: xxx`| |*In Zabbix 4.0:*|`Data object type cannot be converted to string.`| #### JMX monitoring error message As Zabbix Java gateway now supports working with custom MBeans returning non-primitive data types, which override the **toString()** method, the possible error message has been changed the following way: | | | |---|---| |*Previously:*|`data object type is not primitive: xxx`| |*In Zabbix 4.0:*|`Data object type cannot be converted to string.`| #### JSONPath preprocessing Quoted numeric values are now accepted by the JSONPath [aggregate functions](/manual/appendix/items/jsonpath#functions) (sum, min, max, etc.) in item value preprocessing. It means that the values are converted from string type to numeric if aggregation is required. #### JSONPath preprocessing Quoted numeric values are now accepted by the JSONPath [aggregate functions](/manual/appendix/items/jsonpath#functions) (sum, min, max, etc.) in item value preprocessing. It means that the values are converted from string type to numeric if aggregation is required. #### JSONPath Zabbix implementation of [JSONPath](/manual/appendix/items/jsonpath) now supports the extraction of matching element names with a `~` suffix. It returns the name of the matched object or an index in string format of the matched array item. #### JSONPath Zabbix implementation of [JSONPath](/manual/appendix/items/jsonpath) now supports the extraction of matching element names with a `~` suffix. It returns the name of the matched object or an index in string format of the matched array item. #### Juniper template The more correct OID of 'jnxOperatingCPU' (1.3.6.1.4.1.2636.3.1.13.1.8) is now used instead of 'jnxOperating5MinLoadAvg' (1.3.6.1.4.1.2636.3.1.13.1.21) in these LLD item and trigger prototypes: - `{#SNMPVALUE}: CPU utilization` - `{#SNMPVALUE}: High CPU utilization` in: - *Template Net Juniper SNMPv2* #### Juniper template The more correct OID of 'jnxOperatingCPU' (1.3.6.1.4.1.2636.3.1.13.1.8) is now used instead of 'jnxOperating5MinLoadAvg' (1.3.6.1.4.1.2636.3.1.13.1.21) in these LLD item and trigger prototypes: - `{#SNMPVALUE}: CPU utilization` - `{#SNMPVALUE}: High CPU utilization` in: - *Template Net Juniper SNMPv2* #### Known issues in 4.0.0 - 4.0.15 - High memory usage has been observed during process startup with SQLite 3.7.17 on Centos/RHEL 7. The startup process has been improved in 4.0.16 to avoid similar issues with other databases as well. See [ZBX-9084](https://support.zabbix.com/browse/ZBX-9084) for more details. #### Known issues in 4.0.0 - 4.0.15 - High memory usage has been observed during process startup with SQLite 3.7.17 on Centos/RHEL 7. The startup process has been improved in 4.0.16 to avoid similar issues with other databases as well. See [ZBX-9084](https://support.zabbix.com/browse/ZBX-9084) for more details. #### Known issues in 4.0.0, 4.0.1 - Upgrade to 4.0.0 and 4.0.1 from Zabbix 3.0 does not replace {TRIGGER.NAME} macros to {EVENT.NAME} macros like it should. Fixed for 4.0.2. #### Known issues in 4.0.0, 4.0.1 - Upgrade to 4.0.0 and 4.0.1 from Zabbix 3.0 does not replace {TRIGGER.NAME} macros to {EVENT.NAME} macros like it should. Fixed for 4.0.2. #### Known issues in 4.0.0 - 4.0.2 - If the *[Check now](/manual/config/items/check_now)* request is performed from the item list for items that do not support it (template items, active agent items, etc.), a 'Request sent successfully' message is displayed even though the functionality does not work for these items. Fixed in 4.0.3, by displaying a corresponding error message. #### Known issues in 4.0.0 - 4.0.2 - If the *[Check now](/manual/config/items/check_now)* request is performed from the item list for items that do not support it (template items, active agent items, etc.), a 'Request sent successfully' message is displayed even though the functionality does not work for these items. Fixed in 4.0.3, by displaying a corresponding error message. #### Known issues in 4.0.0 - 4.0.3 - Time suffixes do not work in constants of calculated item formulas. Fixed in 4.0.4. - [Negative problem duration](/manual/web_interface/frontend_sections/monitoring/problems#negative_problem_duration) affects the total result in [SLA calculation](/manual/it_services) or [Availability report](/manual/web_interface/frontend_sections/reports/availability), making it incorrect. Fixed in 4.0.4. #### Known issues in 4.0.0 - 4.0.3 - Time suffixes do not work in constants of calculated item formulas. Fixed in 4.0.4. - [Negative problem duration](/manual/web_interface/frontend_sections/monitoring/problems#negative_problem_duration) affects the total result in [SLA calculation](/manual/it_services) or [Availability report](/manual/web_interface/frontend_sections/reports/availability), making it incorrect. Fixed in 4.0.4. #### Known issues in 4.0.0 - 4.0.5 - `net.dns[]` Zabbix agent [item](/manual/config/items/itemtypes/zabbix_agent) does not support IPv6 addresses in its first parameter. Fixed in 4.0.6. #### Known issues in 4.0.0 - 4.0.5 - `net.dns[]` Zabbix agent [item](/manual/config/items/itemtypes/zabbix_agent) does not support IPv6 addresses in its first parameter. Fixed in 4.0.6. #### Known issues in 4.0.0 - Fullscreen mode for the dashboards cannot be accessed with the respective URL parameter: `/zabbix.php?action=dashboard.view&fullscreen=1`. Fixed in 4.0.1. - When filtering triggers in *Monitoring* → *Overview* (Triggers), trigger severity instead of problem severity is taken into account. #### Known issues in 4.0.0 - Fullscreen mode for the dashboards cannot be accessed with the respective URL parameter: `/zabbix.php?action=dashboard.view&fullscreen=1`. Fixed in 4.0.1. - When filtering triggers in *Monitoring* → *Overview* (Triggers), trigger severity instead of problem severity is taken into account. #### Known issues in 4.0.2 - Parent host group selection does not work in the following locations: - *Monitoring* → *Problems* filter - *Monitoring* → *Dashboard* widgets with host group selection: - *Reports* → *Triggers top 100* filter #### Known issues in 4.0.2 - Parent host group selection does not work in the following locations: - *Monitoring* → *Problems* filter - *Monitoring* → *Dashboard* widgets with host group selection: - *Reports* → *Triggers top 100* filter #### Known issues in 4.0.3 - If an item is deleted that has a low-level discovery created trigger, the trigger is not deleted. This leads to "orphaned" problems (with no item/host) being displayed in the problem view. Similarly, if an item is deleted that has low-level discovery created dependent item, the dependent item is not deleted. Fixed in 4.0.4. #### Known issues in 4.0.3 - If an item is deleted that has a low-level discovery created trigger, the trigger is not deleted. This leads to "orphaned" problems (with no item/host) being displayed in the problem view. Similarly, if an item is deleted that has low-level discovery created dependent item, the dependent item is not deleted. Fixed in 4.0.4. #### Known issues in 4.0.6, 4.0.7 - IPMI pollers are unable to process more than 60 items per minute. Fixed in 4.0.8. - You may encounter the issue of 100% CPU usage by IPMI pollers if using OpenIPMI version 2.0.26 and above. Fixed in 4.0.8. #### Known issues in 4.0.6, 4.0.7 - IPMI pollers are unable to process more than 60 items per minute. Fixed in 4.0.8. - You may encounter the issue of 100% CPU usage by IPMI pollers if using OpenIPMI version 2.0.26 and above. Fixed in 4.0.8. #### Known issues in 4.0.8 - This version requires *write* permissions to the `assets` directory for the web server user. This requirement, however, would break those installations of the frontend where the web server has no write permissions to the document root (see [ZBX-16180](https://support.zabbix.com/browse/ZBX-16180) for details). As a result, this requirement is rolled back in 4.0.9. #### Known issues in 4.0.8 - This version requires *write* permissions to the `assets` directory for the web server user. This requirement, however, would break those installations of the frontend where the web server has no write permissions to the document root (see [ZBX-16180](https://support.zabbix.com/browse/ZBX-16180) for details). As a result, this requirement is rolled back in 4.0.9. #### Known issues See [known issues](/manual/installation/known_issues#graphs) for graphs. #### Known issues See [known issues](/manual/installation/known_issues#graphs) for graphs. #### Known issues starting with 4.0.3 - Failed login attempt message has been changed to display only the first 39 characters of a stored IP address as that's the character limit in the database field. That means that IPv6 IP addresses longer than 39 characters will be shown incompletely. #### Known issues starting with 4.0.3 - Failed login attempt message has been changed to display only the first 39 characters of a stored IP address as that's the character limit in the database field. That means that IPv6 IP addresses longer than 39 characters will be shown incompletely. #### LDAP authentication with anonymous bind Anonymous bind is now supported in LDAP authentication. #### LDAP authentication with anonymous bind Anonymous bind is now supported in LDAP authentication. #### Leading and trailing spaces disallowed in host names Leading and trailing spaces are no longer allowed in host and template names. #### Leading and trailing spaces disallowed in host names Leading and trailing spaces are no longer allowed in host and template names. #### libssh support Support of the libssh library (starting from version 0.6.0) has been added. Previously only libssh2 was supported for SSH checks. #### libssh support Support of the libssh library (starting from version 0.6.0) has been added. Previously only libssh2 was supported for SSH checks. #### Linking elements Once you have put some elements on the map, it is time to start linking them. To link two elements you must first select them. With the elements selected, click on *Add* next to Link. With a link created, the single element form now contains an additional *Links* section. Click on *Edit* to edit link attributes. {width="600"} Link attributes: |Parameter|Description| |---------|-----------| |*Label*|Label that will be rendered on top of the link.<br>The [{host:key.func(param)}](/manual/appendix/macros/supported_by_location) macro is supported in this field, but only with `avg`, `last`, `min` and `max` trigger functions, with seconds as parameter.| |*Connect to*|The element that the link connects to.| |*Type (OK)*|Default link style:<br>**Line** - single line<br>**Bold line** - bold line<br>**Dot** - dots<br>**Dashed line** - dashed line| |*Color (OK)*|Default link color.| |*[Link indicators](links)*|List of triggers linked to the link. In case a trigger has status PROBLEM, its style is applied to the link.| #### Linking elements Once you have put some elements on the map, it is time to start linking them. To link two elements you must first select them. With the elements selected, click on *Add* next to Link. With a link created, the single element form now contains an additional *Links* section. Click on *Edit* to edit link attributes. {width="600"} Link attributes: |Parameter|Description| |---------|-----------| |*Label*|Label that will be rendered on top of the link.<br>The [{host:key.func(param)}](/manual/appendix/macros/supported_by_location) macro is supported in this field, but only with `avg`, `last`, `min` and `max` trigger functions, with seconds as parameter.| |*Connect to*|The element that the link connects to.| |*Type (OK)*|Default link style:<br>**Line** - single line<br>**Bold line** - bold line<br>**Dot** - dots<br>**Dashed line** - dashed line| |*Color (OK)*|Default link color.| |*[Link indicators](links)*|List of triggers linked to the link. In case a trigger has status PROBLEM, its style is applied to the link.| #### LLD rule filter condition The LLD rule filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression.| ::: notetip To better understand how to use filters with various types of expressions, see examples on the [discoveryrule.get](get#retrieving_filter_conditions) and [discoveryrule.create](create#using_a_custom_expression_filter) method pages. ::: #### LLD rule filter condition The LLD rule filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression.| ::: notetip To better understand how to use filters with various types of expressions, see examples on the [discoveryrule.get](get#retrieving_filter_conditions) and [discoveryrule.create](create#using_a_custom_expression_filter) method pages. ::: ### LLD rule filter The LLD rule filter object defines a set of conditions that can be used to filter discovered objects. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.| ### LLD rule filter The LLD rule filter object defines a set of conditions that can be used to filter discovered objects. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.| # > LLD rule object The following objects are directly related to the `discoveryrule` API. # > LLD rule object The following objects are directly related to the `discoveryrule` API. #### Logging changes The message printed to the log files about a full history cache has been changed the following way: | | | |---|---| |*Previously:*|`History buffer is full. Sleeping for 1 second.`| |*In Zabbix 4.0:*|`History cache is full. Sleeping for 1 second.`| #### Logging changes The message printed to the log files about a full history cache has been changed the following way: | | | |---|---| |*Previously:*|`History buffer is full. Sleeping for 1 second.`| |*In Zabbix 4.0:*|`History cache is full. Sleeping for 1 second.`| #### Login and systemd We recommend [creating](/manual/installation/install#create_user_account) a *zabbix* user as system user, that is, without ability to log in. Some users ignore this recommendation and use the same account to log in (e. g. using SSH) to host running Zabbix. This might crash Zabbix daemon on log out. In this case you will get something like the following in Zabbix server log: zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument and in Zabbix agent log: zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument This happens because of default systemd setting `RemoveIPC=yes` configured in `/etc/systemd/logind.conf`. When you log out of the system the semaphores created by Zabbix previously are removed which causes the crash. A quote from systemd documentation: RemoveIPC= Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources after the last of the user's sessions terminated. This covers System V semaphores, shared memory and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the root user and other system users are excluded from the effect of this setting. Defaults to "yes". There are 2 solutions to this problem: 1. (recommended) Stop using *zabbix* account for anything else than Zabbix processes, create a dedicated account for other things. 2. (not recommended) Set `RemoveIPC=no` in `/etc/systemd/logind.conf` and reboot the system. Note that `RemoveIPC` is a system-wide parameter, changing it will affect the whole system. #### Login and systemd We recommend [creating](/manual/installation/install#create_user_account) a *zabbix* user as system user, that is, without ability to log in. Some users ignore this recommendation and use the same account to log in (e. g. using SSH) to host running Zabbix. This might crash Zabbix daemon on log out. In this case you will get something like the following in Zabbix server log: zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument and in Zabbix agent log: zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument This happens because of default systemd setting `RemoveIPC=yes` configured in `/etc/systemd/logind.conf`. When you log out of the system the semaphores created by Zabbix previously are removed which causes the crash. A quote from systemd documentation: RemoveIPC= Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources after the last of the user's sessions terminated. This covers System V semaphores, shared memory and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the root user and other system users are excluded from the effect of this setting. Defaults to "yes". There are 2 solutions to this problem: 1. (recommended) Stop using *zabbix* account for anything else than Zabbix processes, create a dedicated account for other things. 2. (not recommended) Set `RemoveIPC=no` in `/etc/systemd/logind.conf` and reboot the system. Note that `RemoveIPC` is a system-wide parameter, changing it will affect the whole system. #### Log items Two new options have been added to the `log`, `log.count`, `logrt` and `logrt.count` [items](/manual/config/items/itemtypes/zabbix_agent): - *mtime-reread* - non-unique records, reread file if its modification time changes but size does not - *mtime-noreread* - non-unique records, do not reread file if its modification time changes but size does not For `log` and `log.count` items these options have been added as a new <options> parameter, e.g. log[file,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>] For `logrt` and `logrt.count` these options have been added to the already existing <options> parameter. #### Log items Two new options have been added to the `log`, `log.count`, `logrt` and `logrt.count` [items](/manual/config/items/itemtypes/zabbix_agent): - *mtime-reread* - non-unique records, reread file if its modification time changes but size does not - *mtime-noreread* - non-unique records, do not reread file if its modification time changes but size does not For `log` and `log.count` items these options have been added as a new <options> parameter, e.g. log[file,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>] For `logrt` and `logrt.count` these options have been added to the already existing <options> parameter. ### Log level control targets *process-type* All processes of specified type (active checks, collector, listener) *process-type,N* Process type and number (e.g., listener,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-p**, **--print** Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are: d Number with a decimal part. m Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state. s Text. Maximum length not limited. t Text. Same as **s**. u Unsigned integer. **-t**, **--test** *item-key* Test single item and exit. See **--print** for output description. **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Log level control targets *process-type* All processes of specified type (active checks, collector, listener) *process-type,N* Process type and number (e.g., listener,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-p**, **--print** Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are: d Number with a decimal part. m Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state. s Text. Maximum length not limited. t Text. Same as **s**. u Unsigned integer. **-t**, **--test** *item-key* Test single item and exit. See **--print** for output description. **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Log level control targets *process-type* All processes of specified type (alerter, alert manager, configuration syncer, discoverer, escalator, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, preprocessing manager, preprocessing worker, proxy poller, self-monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector) *process-type,N* Process type and number (e.g., poller,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Log level control targets *process-type* All processes of specified type (alerter, alert manager, configuration syncer, discoverer, escalator, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, preprocessing manager, preprocessing worker, proxy poller, self-monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector) *process-type,N* Process type and number (e.g., poller,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Log level control targets *process-type* All processes of specified type (configuration syncer, data sender, discoverer, heartbeat sender, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, self-monitoring, snmp trapper, task manager, trapper, unreachable poller, vmware collector) *process-type,N* Process type and number (e.g., poller,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Log level control targets *process-type* All processes of specified type (configuration syncer, data sender, discoverer, heartbeat sender, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, self-monitoring, snmp trapper, task manager, trapper, unreachable poller, vmware collector) *process-type,N* Process type and number (e.g., poller,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ##### Low-level discovery rule Create a low-level discovery rule using the in-built discovery key: vfs.fs.discovery  This discovery rule will return discovery macros such as {\#FSNAME}, {\#FSTYPE} that can be used in creating item prototypes. ##### Low-level discovery rule Create a low-level discovery rule using the in-built discovery key: vfs.fs.discovery  This discovery rule will return discovery macros such as {\#FSNAME}, {\#FSTYPE} that can be used in creating item prototypes. #### Macros A new {EVENT.RECOVERY.NAME} macro is supported, returning the recovery event name. {TRIGGER.ID} macro is now supported in trigger tag values. It may be useful for identifying triggers created from trigger prototypes and, for example, suppressing problems from these triggers during maintenance. #### Macros A new {EVENT.RECOVERY.NAME} macro is supported, returning the recovery event name. {TRIGGER.ID} macro is now supported in trigger tag values. It may be useful for identifying triggers created from trigger prototypes and, for example, suppressing problems from these triggers during maintenance. #### Maintenance and Daylight Saving Time In previous Zabbix versions, maintenance period calculation was unaware of the possible effects caused by Daylight Saving Time change resulting in unpredictable behaviours. In the new version Daylight Saving Time (DST) change is cared for and should not unpredictably affect how long the maintenance will be. Let's say we have a two-hour maintenance that usually starts at 1am and finishes at 3am. If after one hour of maintenance (at 2am) a DST change happens and current time changes from 2:00 to 3:00, the maintenance will continue for one more hour till 4:00. #### Maintenance and Daylight Saving Time In previous Zabbix versions, maintenance period calculation was unaware of the possible effects caused by Daylight Saving Time change resulting in unpredictable behaviours. In the new version Daylight Saving Time (DST) change is cared for and should not unpredictably affect how long the maintenance will be. Let's say we have a two-hour maintenance that usually starts at 1am and finishes at 3am. If after one hour of maintenance (at 2am) a DST change happens and current time changes from 2:00 to 3:00, the maintenance will continue for one more hour till 4:00. # maintenance.create # maintenance.create # maintenance.delete # maintenance.delete # maintenance.get # maintenance.get #### Maintenance icon in host list An orange wrench icon  next to the host status now indicates that this host is in maintenance in *Configuration → Hosts*. Maintenance details are displayed when the mouse pointer is positioned over the icon:  Previously, an orange *In maintenance* string was displayed as status instead of the icon. #### Maintenance icon in host list An orange wrench icon  next to the host status now indicates that this host is in maintenance in *Configuration → Hosts*. Maintenance details are displayed when the mouse pointer is positioned over the icon:  Previously, an orange *In maintenance* string was displayed as status instead of the icon. # maintenance.update # maintenance.update #### Manual closing of problems When [updating a problem](/manual/acknowledges#updating_problems), the checkbox for closing a problem is now available if the *Allow manual close* option is checked in [trigger configuration](/manual/config/triggers/trigger) for at least one of the selected problems. Only those problems will be closed that are allowed to be closed when clicking on *Update*. Already closed problems will not be closed repeatedly. If no problem is manually closeable, the checkbox is disabled. Previously, closing a problem in this way was only possible if the *Allow manual close* option was checked in [trigger configuration](/manual/config/triggers/trigger) for each selected problem. If at least one problem was not manually closeable, the checkbox was disabled. Similarly, when changing problem severity the relevant checkbox is now available if at least one selected problem is read-writable. Previously each selected problem had to be read-writable, otherwise the checkbox was disabled. #### Manual closing of problems When [updating a problem](/manual/acknowledges#updating_problems), the checkbox for closing a problem is now available if the *Allow manual close* option is checked in [trigger configuration](/manual/config/triggers/trigger) for at least one of the selected problems. Only those problems will be closed that are allowed to be closed when clicking on *Update*. Already closed problems will not be closed repeatedly. If no problem is manually closeable, the checkbox is disabled. Previously, closing a problem in this way was only possible if the *Allow manual close* option was checked in [trigger configuration](/manual/config/triggers/trigger) for each selected problem. If at least one problem was not manually closeable, the checkbox was disabled. Similarly, when changing problem severity the relevant checkbox is now available if at least one selected problem is read-writable. Previously each selected problem had to be read-writable, otherwise the checkbox was disabled. # map.create # map.create # map.delete # map.delete # map.get # map.get # map.update # map.update ##### Master item Create a Zabbix agent item using the following key: vfs.fs.get  Set the type of information to "Text" for possibly big JSON data. The data returned by this item will contain something like the following for a mounted filesystem: ``` {.java} { "fsname": "/", "fstype": "rootfs", "bytes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 }, "inodes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 } } ``` ##### Master item Create a Zabbix agent item using the following key: vfs.fs.get  Set the type of information to "Text" for possibly big JSON data. The data returned by this item will contain something like the following for a mounted filesystem: ``` {.java} { "fsname": "/", "fstype": "rootfs", "bytes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 }, "inodes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 } } ``` # mediatype.create # mediatype.create # mediatype.delete # mediatype.delete # mediatype.get # mediatype.get # mediatype.update # mediatype.update #### Modification time ignored in log, log.count items File modification time is now ignored in log and log.count [items](/manual/config/items/itemtypes/zabbix_agent). #### Modification time ignored in log, log.count items File modification time is now ignored in log and log.count [items](/manual/config/items/itemtypes/zabbix_agent). #### More info See [Virtual machine monitoring](/manual/vm_monitoring) for detailed information how to configure Zabbix to monitor VMware environments. #### More info See [Virtual machine monitoring](/manual/vm_monitoring) for detailed information how to configure Zabbix to monitor VMware environments. #### Moving and copy-pasting elements Several selected elements can be **moved** to another place in the map by clicking on one of the selected elements, holding down the mouse button and moving the cursor to the desired location. One or more elements can be **copied** by selecting the elements, then clicking on a selected element with the right mouse button and selecting *Copy* from the menu. {width="600"} To paste the elements, click on a map area with the right mouse button and select *Paste* from the menu. The *Paste without external links* option will paste the elements retaining only the links that are between the selected elements. Copy-pasting works within the same browser window. Keyboard shortcuts are not supported. #### Moving and copy-pasting elements Several selected elements can be **moved** to another place in the map by clicking on one of the selected elements, holding down the mouse button and moving the cursor to the desired location. One or more elements can be **copied** by selecting the elements, then clicking on a selected element with the right mouse button and selecting *Copy* from the menu. {width="600"} To paste the elements, click on a map area with the right mouse button and select *Paste* from the menu. The *Paste without external links* option will paste the elements retaining only the links that are between the selected elements. Copy-pasting works within the same browser window. Keyboard shortcuts are not supported. #### MySQL - CR\_CONN\_HOST\_ERROR - CR\_SERVER\_GONE\_ERROR - CR\_CONNECTION\_ERROR - CR\_SERVER\_LOST - CR\_UNKNOWN\_HOST - ER\_SERVER\_SHUTDOWN - ER\_ACCESS\_DENIED\_ERROR - ER\_ILLEGAL\_GRANT\_FOR\_TABLE - ER\_TABLEACCESS\_DENIED\_ERROR - ER\_UNKNOWN\_ERROR #### MySQL - CR\_CONN\_HOST\_ERROR - CR\_SERVER\_GONE\_ERROR - CR\_CONNECTION\_ERROR - CR\_SERVER\_LOST - CR\_UNKNOWN\_HOST - ER\_SERVER\_SHUTDOWN - ER\_ACCESS\_DENIED\_ERROR - ER\_ILLEGAL\_GRANT\_FOR\_TABLE - ER\_TABLEACCESS\_DENIED\_ERROR - ER\_UNKNOWN\_ERROR #### MySQL custom error codes If Zabbix is used with MySQL installation on Azure, an unclear error message *\[9002\] Some errors occurred* may appear in Zabbix logs. This generic error text is sent to Zabbix server or proxy by the database. To get more information about the cause of the error, check Azure logs. #### MySQL custom error codes If Zabbix is used with MySQL installation on Azure, an unclear error message *\[9002\] Some errors occurred* may appear in Zabbix logs. This generic error text is sent to Zabbix server or proxy by the database. To get more information about the cause of the error, check Azure logs. #### MySQL/MariaDB **1.** Check the database character set and collation. For example: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_general_ci | +--------------------------+----------------------+ As we see, the character set here is not 'utf8' and collation is not 'utf8\_bin', so we need to fix them. **2.** Stop Zabbix. **3.** Create a backup copy of the database! **4.** Fix the character set and collation on database level: alter database <your DB name> character set utf8 collate utf8_bin; Fixed values: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8 | utf8_bin | +--------------------------+----------------------+ **5.** Load the [script](https://support.zabbix.com/secure/attachment/113858/113858_utf8_convert.sql) to fix character set and collation on table and column level: mysql <your DB name> < utf8_convert.sql **6.** Execute the script: SET @ZABBIX_DATABASE = '<your DB name>'; If MariaDB → set innodb_strict_mode = OFF; CALL zbx_convert_utf8(); If MariaDB → set innodb_strict_mode = ON; drop procedure zbx_convert_utf8; Note that data encoding will be changed on disk. For example, when converting characters like Æ, Ñ, Ö from 'latin1' to 'utf8' they will go from 1 byte to 2 bytes. Thus the repaired database may require more space than before. **7.** If no errors - you may want to create a database backup copy with the fixed database. **8.** Start Zabbix. #### MySQL/MariaDB **1.** Check the database character set and collation. For example: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_general_ci | +--------------------------+----------------------+ As we see, the character set here is not 'utf8' and collation is not 'utf8\_bin', so we need to fix them. **2.** Stop Zabbix. **3.** Create a backup copy of the database! **4.** Fix the character set and collation on database level: alter database <your DB name> character set utf8 collate utf8_bin; Fixed values: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8 | utf8_bin | +--------------------------+----------------------+ **5.** Load the [script](https://support.zabbix.com/secure/attachment/113858/113858_utf8_convert.sql) to fix character set and collation on table and column level: mysql <your DB name> < utf8_convert.sql **6.** Execute the script: SET @ZABBIX_DATABASE = '<your DB name>'; If MariaDB → set innodb_strict_mode = OFF; CALL zbx_convert_utf8(); If MariaDB → set innodb_strict_mode = ON; drop procedure zbx_convert_utf8; Note that data encoding will be changed on disk. For example, when converting characters like Æ, Ñ, Ö from 'latin1' to 'utf8' they will go from 1 byte to 2 bytes. Thus the repaired database may require more space than before. **7.** If no errors - you may want to create a database backup copy with the fixed database. **8.** Start Zabbix. ## NAME zabbix\_agentd - Zabbix agent daemon [ ]{#lbAC} ## NAME zabbix\_agentd - Zabbix agent daemon [ ]{#lbAC} ## NAME zabbix\_get - Zabbix get utility [ ]{#lbAC} ## NAME zabbix\_get - Zabbix get utility [ ]{#lbAC} ## NAME zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC} ## NAME zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC} ## NAME zabbix\_sender - Zabbix sender utility [ ]{#lbAC} ## NAME zabbix\_sender - Zabbix sender utility [ ]{#lbAC} ## NAME zabbix\_server - Zabbix server daemon [ ]{#lbAC} ## NAME zabbix\_server - Zabbix server daemon [ ]{#lbAC} #### Network discovery In a [network discovery rule](/manual/discovery/network_discovery/rule), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Update interval|<|no| |*SNMP v1, v2*|<|<| |<|SNMP community|yes| |^|SNMP OID|yes| |*SNMP v3*|<|<| |<|Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |^|SNMP OID|yes| #### Network discovery In a [network discovery rule](/manual/discovery/network_discovery/rule), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Update interval|<|no| |*SNMP v1, v2*|<|<| |<|SNMP community|yes| |^|SNMP OID|yes| |*SNMP v3*|<|<| |<|Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |^|SNMP OID|yes| #### New Cisco UCS server template A Cisco UCS server monitoring template - *Template Server Cisco UCS SNMPv2* has been added. It will be available in *Configuration* → *Templates* in new installations. If you are upgrading from previous versions, you can find this template in the `templates` directory of the downloaded latest Zabbix version. Then, while in *Configuration* → *Templates* you can import it manually into Zabbix. #### New Cisco UCS server template A Cisco UCS server monitoring template - *Template Server Cisco UCS SNMPv2* has been added. It will be available in *Configuration* → *Templates* in new installations. If you are upgrading from previous versions, you can find this template in the `templates` directory of the downloaded latest Zabbix version. Then, while in *Configuration* → *Templates* you can import it manually into Zabbix. #### New items A new `vfs.fs.get` agent item has been added that returns a JSON with filesystem data including such details as the mountpoint name, mountpoint type, filesystem size and inode metrics. See a [working example](/manual/discovery/low_level_discovery/mounted_filesystems) of how this item can be used in discovery. #### New items A new `vfs.fs.get` agent item has been added that returns a JSON with filesystem data including such details as the mountpoint name, mountpoint type, filesystem size and inode metrics. See a [working example](/manual/discovery/low_level_discovery/mounted_filesystems) of how this item can be used in discovery. #### New templates New templates are available for [remote monitoring](/manual/appendix/items/remote_stats) of Zabbix server or proxy internal metrics from an external instance: - Template App Remote Zabbix server - Template App Remote Zabbix proxy Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring. #### New templates New templates are available for [remote monitoring](/manual/appendix/items/remote_stats) of Zabbix server or proxy internal metrics from an external instance: - Template App Remote Zabbix server - Template App Remote Zabbix proxy Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring. #### Non-root permissions implemented for Docker images Zabbix Docker images have been updated to implement non-root container best practices. Due to the change: - All directories have been restricted for the container user, except directories which are required for the container. For example, /etc/zabbix/ with Zabbix component configuration files. - Ports 80 and 443 have been changed to 8080 and 8443, because usage of all ports <1024 is restricted for non-privileged users. Zabbix web interface images have been updated to use non-privileged ports 8080, 8443; Zabbix snmptrap images port 1162. - All Zabbix images are updated to use a non-privileged user. By default, 'zabbix' with UID 1997. A known issue: Nginx based images do not run under root. Will be fixed soon. #### Non-root permissions implemented for Docker images Zabbix Docker images have been updated to implement non-root container best practices. Due to the change: - All directories have been restricted for the container user, except directories which are required for the container. For example, /etc/zabbix/ with Zabbix component configuration files. - Ports 80 and 443 have been changed to 8080 and 8443, because usage of all ports <1024 is restricted for non-privileged users. Zabbix web interface images have been updated to use non-privileged ports 8080, 8443; Zabbix snmptrap images port 1162. - All Zabbix images are updated to use a non-privileged user. By default, 'zabbix' with UID 1997. A known issue: Nginx based images do not run under root. Will be fixed soon. ### Notation ### Notation ::: noteclassic This blank page is needed for the parent page to be displayed as folder. ::: ::: noteclassic This blank page is needed for the parent page to be displayed as folder. ::: ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix agent in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix agent in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix proxy in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix proxy in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix server in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix server in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-s**, **--host** *host-name-or-IP* Specify host name or IP address of a host. **-p**, **--port** *port-number* Specify port number of agent running on the host. Default is 10050. **-I**, **--source-address** *IP-address* Specify source IP address. **-k**, **--key** *item-key* Specify key of item to retrieve value for. **--tls-connect** *value* How to connect to agent. Values: [ ]{#lbAF} ## OPTIONS **-s**, **--host** *host-name-or-IP* Specify host name or IP address of a host. **-p**, **--port** *port-number* Specify port number of agent running on the host. Default is 10050. **-I**, **--source-address** *IP-address* Specify source IP address. **-k**, **--key** *item-key* Specify key of item to retrieve value for. **--tls-connect** *value* How to connect to agent. Values: [ ]{#lbAF} #### Ordering shapes and lines To bring one shape in front of the other (or vice versa) click on the shape with the right mouse button bringing up the map shape menu.  #### Ordering shapes and lines To bring one shape in front of the other (or vice versa) click on the shape with the right mouse button bringing up the map shape menu.  #### Other locations In addition to the locations listed here, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Global scripts (including confirmation text)|<|yes| |*Monitoring → Screens*|<|<| |<|URL field of *dynamic URL* screen element|yes| |*Administration → Users → Media*|<|<| |<|When active|no| |*Administration → General → Working time*|<|<| |<|Working time|no| For a complete list of all macros supported in Zabbix, see [supported macros](/manual/appendix/macros/supported_by_location). #### Other locations In addition to the locations listed here, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Global scripts (including confirmation text)|<|yes| |*Monitoring → Screens*|<|<| |<|URL field of *dynamic URL* screen element|yes| |*Administration → Users → Media*|<|<| |<|When active|no| |*Administration → General → Working time*|<|<| |<|Working time|no| For a complete list of all macros supported in Zabbix, see [supported macros](/manual/appendix/macros/supported_by_location). ##### Outgoing connections The simplest case is outgoing connections: - For outgoing connections with certificate - use TLSCipherCert13 or TLSCipherCert - For outgoing connections with PSK - use TLSCipherPSK13 and TLSCipherPSK - In case of zabbix\_get and zabbix\_sender utilities the command-line parameters `--tls-cipher13` and `--tls-cipher` can be used (encryption is unambiguously specified with a `--tls-connect` parameter) ##### Outgoing connections The simplest case is outgoing connections: - For outgoing connections with certificate - use TLSCipherCert13 or TLSCipherCert - For outgoing connections with PSK - use TLSCipherPSK13 and TLSCipherPSK - In case of zabbix\_get and zabbix\_sender utilities the command-line parameters `--tls-cipher13` and `--tls-cipher` can be used (encryption is unambiguously specified with a `--tls-connect` parameter) #### Output value JSONPaths can be divided in definite and indefinite paths. A definite path can return only null or a single match. An indefinite path can return multiple matches, basically JSONPaths with detached, multiple name/index list, array slice or expression segments. However, when a function is used the JSONPath becomes definite, as functions always output single value. A definite path returns the object/array/value it's referencing, while indefinite path returns an array of the matched objects/arrays/values. #### Output value JSONPaths can be divided in definite and indefinite paths. A definite path can return only null or a single match. An indefinite path can return multiple matches, basically JSONPaths with detached, multiple name/index list, array slice or expression segments. However, when a function is used the JSONPath becomes definite, as functions always output single value. A definite path returns the object/array/value it's referencing, while indefinite path returns an array of the matched objects/arrays/values. #### Overview Configuring a map in Zabbix requires that you first create a map by defining its general parameters and then you start filling the actual map with elements and their links. You can populate the map with elements that are a host, a host group, a trigger, an image or another map. Icons are used to represent map elements. You can define the information that will be displayed with the icons and set that recent problems are displayed in a special way. You can link the icons and define information to be displayed on the links. You can add custom URLs to be accessible by clicking on the icons. Thus you may link a host icon to host properties or a map icon to another map. Maps are managed in *Monitoring* → *[Maps](/manual/web_interface/frontend_sections/monitoring/maps)*, where they can be configured, managed and viewed. In the monitoring view you can click on the icons and take advantage of the links to some scripts and URLs. Network maps are based on vector graphics (SVG) since Zabbix 3.4. #### Overview Configuring a map in Zabbix requires that you first create a map by defining its general parameters and then you start filling the actual map with elements and their links. You can populate the map with elements that are a host, a host group, a trigger, an image or another map. Icons are used to represent map elements. You can define the information that will be displayed with the icons and set that recent problems are displayed in a special way. You can link the icons and define information to be displayed on the links. You can add custom URLs to be accessible by clicking on the icons. Thus you may link a host icon to host properties or a map icon to another map. Maps are managed in *Monitoring* → *[Maps](/manual/web_interface/frontend_sections/monitoring/maps)*, where they can be configured, managed and viewed. In the monitoring view you can click on the icons and take advantage of the links to some scripts and URLs. Network maps are based on vector graphics (SVG) since Zabbix 3.4. #### Overview Custom graphs, as the name suggests, offer customisation capabilities. While simple graphs are good for viewing data of a single item, they do not offer configuration capabilities. Thus, if you want to change graph style or the way lines are displayed or compare several items, for example incoming and outgoing traffic in a single graph, you need a custom graph. Custom graphs are configured manually. They can be created for a host or several hosts or for a single template. #### Overview Custom graphs, as the name suggests, offer customisation capabilities. While simple graphs are good for viewing data of a single item, they do not offer configuration capabilities. Thus, if you want to change graph style or the way lines are displayed or compare several items, for example incoming and outgoing traffic in a single graph, you need a custom graph. Custom graphs are configured manually. They can be created for a host or several hosts or for a single template. #### Overview Host screens look similar to [global screens](/manual/config/visualization/screens), however, host screens display data about the host only. Host screens are configured on the [template](/manual/config/templates/template#adding_screens) level and then are generated for a host, once the template is linked to the host. Host screens *cannot* be configured or directly accessed in the *Monitoring* → *[Screens](/manual/web_interface/frontend_sections/monitoring/screens)* section, which is reserved for global screens. The ways to access host screens are listed below in this section. {width="600"} #### Overview Host screens look similar to [global screens](/manual/config/visualization/screens), however, host screens display data about the host only. Host screens are configured on the [template](/manual/config/templates/template#adding_screens) level and then are generated for a host, once the template is linked to the host. Host screens *cannot* be configured or directly accessed in the *Monitoring* → *[Screens](/manual/web_interface/frontend_sections/monitoring/screens)* section, which is reserved for global screens. The ways to access host screens are listed below in this section. {width="600"} #### Overview If you have a network to look after, you may want to have an overview of your infrastructure somewhere. For that purpose you can create maps in Zabbix - of networks and of anything you like. All users can create network maps. The maps can be public (available to all users) or private (available to selected users). Proceed to [configuring a network map](/manual/config/visualization/maps/map). #### Overview If you have a network to look after, you may want to have an overview of your infrastructure somewhere. For that purpose you can create maps in Zabbix - of networks and of anything you like. All users can create network maps. The maps can be public (available to all users) or private (available to selected users). Proceed to [configuring a network map](/manual/config/visualization/maps/map). #### Overview In a slide show you can configure that a number of [screens](screens) are displayed one after another at set intervals. Sometimes you might want to switch between some configured screens. While that can be done manually, doing that more than once or twice may become very tedious. This is where the slide show function comes to rescue. All users in Zabbix (including non-admin users) can create slide shows. Slide shows have an owner - the user who created them. Slide shows can be made public or private. Public slide shows are visible to all users, however, they must have at least read permissions to all slide show elements (screens) to see it. To add a screen to the slide show the user must also have at least read permission to it. Private slide shows are visible only to their owner. Private slide shows can be shared by the owner to other users and user groups. Regular (non-Super admin) users can only share with the groups and users they are member of. Private slide shows will be visible to their owner and the users the slide show is shared with as long as they have read permissions to all included screens. Admin level users, as long as they have read permissions to all included screens, can see and edit private slide shows regardless of being the owner or belonging to the shared user list. #### Overview In a slide show you can configure that a number of [screens](screens) are displayed one after another at set intervals. Sometimes you might want to switch between some configured screens. While that can be done manually, doing that more than once or twice may become very tedious. This is where the slide show function comes to rescue. All users in Zabbix (including non-admin users) can create slide shows. Slide shows have an owner - the user who created them. Slide shows can be made public or private. Public slide shows are visible to all users, however, they must have at least read permissions to all slide show elements (screens) to see it. To add a screen to the slide show the user must also have at least read permission to it. Private slide shows are visible only to their owner. Private slide shows can be shared by the owner to other users and user groups. Regular (non-Super admin) users can only share with the groups and users they are member of. Private slide shows will be visible to their owner and the users the slide show is shared with as long as they have read permissions to all included screens. Admin level users, as long as they have read permissions to all included screens, can see and edit private slide shows regardless of being the owner or belonging to the shared user list. #### Overview In order to use any other language than English in Zabbix web interface, its locale should be installed on the web server. Additionally, the PHP gettext extension is required for the translations to work. If a locale is installed, a language becomes available in the [language selector](/manual/web_interface/user_profile#user_profile) in Zabbix web interface. Languages for which locales are not installed are greyed out and cannot be selected. #### Overview In order to use any other language than English in Zabbix web interface, its locale should be installed on the web server. Additionally, the PHP gettext extension is required for the translations to work. If a locale is installed, a language becomes available in the [language selector](/manual/web_interface/user_profile#user_profile) in Zabbix web interface. Languages for which locales are not installed are greyed out and cannot be selected. #### Overview It is possible to discover mounted filesystems and their properties (mountpoint name, mountpoint type, filesystem size and inode statistics). To do that, you may use a combination of: - the `vfs.fs.get` agent item (supported since Zabbix **4.0.17**) as the master item - a low-level discovery rule and dependent item prototypes #### Overview It is possible to discover mounted filesystems and their properties (mountpoint name, mountpoint type, filesystem size and inode statistics). To do that, you may use a combination of: - the `vfs.fs.get` agent item (supported since Zabbix **4.0.17**) as the master item - a low-level discovery rule and dependent item prototypes #### Overview JSONPath consists of segments separated with dots. A segment can be either a simple word like a JSON value name, `*` or a more complex construct enclosed within square brackets `[` `]`. The separating dot before bracket segment is optional and can be omitted. For example: |Path|Description| |----|-----------| |`$.object.name`|Return the object.name contents.| |`$.object['name']`|Return the object.name contents.| |`$.object.['name']`|Return the object.name contents.| |`$["object"]['name']`|Return the object.name contents.| |`$.['object'].["name"]`|Return the object.name contents.| |`$.object.history.length()`|Return the number of object.history array elements.| |`$[?(@.name == 'Object')].price.first()`|Return the price field of the first object with name 'Object'.| |`$[?(@.name == 'Object')].history.first().length()`|Return the number of history array elements of the first object with name 'Object'.| |`$[?(@.price > 10)].length()`|Return the number of objects with price being greater than 10.| #### Overview JSONPath consists of segments separated with dots. A segment can be either a simple word like a JSON value name, `*` or a more complex construct enclosed within square brackets `[` `]`. The separating dot before bracket segment is optional and can be omitted. For example: |Path|Description| |----|-----------| |`$.object.name`|Return the object.name contents.| |`$.object['name']`|Return the object.name contents.| |`$.object.['name']`|Return the object.name contents.| |`$["object"]['name']`|Return the object.name contents.| |`$.['object'].["name"]`|Return the object.name contents.| |`$.object.history.length()`|Return the number of object.history array elements.| |`$[?(@.name == 'Object')].price.first()`|Return the price field of the first object with name 'Object'.| |`$[?(@.name == 'Object')].history.first().length()`|Return the number of history array elements of the first object with name 'Object'.| |`$[?(@.price > 10)].length()`|Return the number of objects with price being greater than 10.| #### Overview On Zabbix screens you can group information from various sources for a quick overview on a single screen. Building the screens is quite easy and intuitive. Essentially a screen is a table. You choose how many cells per table and what elements to display in the cells. The following elements can be displayed: - simple graphs - simple graph prototypes - user-defined custom graphs - custom graph prototypes - maps - other screens - plain text information - server information (overview) - host information (overview) - trigger information (overview) - host/host group issues (status of problems) - problems by severity - data overview - clock - history of events - history of recent actions - URL (data taken from another location) Global screens are managed in *Monitoring* → *[Screens](/manual/web_interface/frontend_sections/monitoring/screens)*, where they can be configured, managed and viewed. They can also be added to the favorites section of *Monitoring* → *[Dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard)*. [Host-level screens](/manual/config/visualization/host_screens) are configured on template level and then generated for hosts once the template is linked to the hosts. To configure a screen you must first create it by defining its general properties and then add individual elements in the cells. All users in Zabbix (including non-admin users) can create screens. Screens have an owner - the user who created them. Screens can be made public or private. Public screens are visible to all users. Private screens are visible only to their owner. Private screens can be shared by the owner to other users and user groups. Regular (non-Super admin) users can only share with the groups and users they are member of. Private screens will be visible to their owner and the users the screen is shared with as long as they have read permissions to all screen elements. Admin level users, as long as they have read permissions to all screen elements, can see and edit private screens regardless of being the owner or belonging to the shared user list. ::: notewarning For both public and private screens a user must have at least read permissions to all screen elements in order to see the screen. To add an element to a screen a user must also have at least read permission to it. ::: #### Overview On Zabbix screens you can group information from various sources for a quick overview on a single screen. Building the screens is quite easy and intuitive. Essentially a screen is a table. You choose how many cells per table and what elements to display in the cells. The following elements can be displayed: - simple graphs - simple graph prototypes - user-defined custom graphs - custom graph prototypes - maps - other screens - plain text information - server information (overview) - host information (overview) - trigger information (overview) - host/host group issues (status of problems) - problems by severity - data overview - clock - history of events - history of recent actions - URL (data taken from another location) Global screens are managed in *Monitoring* → *[Screens](/manual/web_interface/frontend_sections/monitoring/screens)*, where they can be configured, managed and viewed. They can also be added to the favorites section of *Monitoring* → *[Dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard)*. [Host-level screens](/manual/config/visualization/host_screens) are configured on template level and then generated for hosts once the template is linked to the hosts. To configure a screen you must first create it by defining its general properties and then add individual elements in the cells. All users in Zabbix (including non-admin users) can create screens. Screens have an owner - the user who created them. Screens can be made public or private. Public screens are visible to all users. Private screens are visible only to their owner. Private screens can be shared by the owner to other users and user groups. Regular (non-Super admin) users can only share with the groups and users they are member of. Private screens will be visible to their owner and the users the screen is shared with as long as they have read permissions to all screen elements. Admin level users, as long as they have read permissions to all screen elements, can see and edit private screens regardless of being the owner or belonging to the shared user list. ::: notewarning For both public and private screens a user must have at least read permissions to all screen elements in order to see the screen. To add an element to a screen a user must also have at least read permission to it. ::: #### Overview Simple graphs are provided for the visualization of data gathered by items. No configuration effort is required on the user part to view simple graphs. They are freely made available by Zabbix. Just go to *Monitoring → Latest data* and click on the Graph link for the respective item and a graph will be displayed. {width="600"} ::: noteclassic Simple graphs are provided for all numeric items. For textual items, a link to History is available in *Monitoring → Latest data*. ::: #### Overview Simple graphs are provided for the visualization of data gathered by items. No configuration effort is required on the user part to view simple graphs. They are freely made available by Zabbix. Just go to *Monitoring → Latest data* and click on the Graph link for the respective item and a graph will be displayed. {width="600"} ::: noteclassic Simple graphs are provided for all numeric items. For textual items, a link to History is available in *Monitoring → Latest data*. ::: #### Overview This page provides a list of cookies used by Zabbix. |Name|Description|Values|Expires/Max-Age|HttpOnly[^1]|Secure[^2]| |----|-----------|------|---------------|------------|----------| |PHPSESSID|Unique PHP session ID.<br><br>The length can be set in *php.ini - session.sid\_length*.|Example: kvlp5pu2ru1a2ccvff0g52m87a|Session (expires when the browsing session ends)|\+|\+ (only if HTTPS is enabled on a web server)| |ZBX\_SESSION\_NAME<br>(available since 4.0.0).<br>String used as the name of the Zabbix frontend session cookie.<br><br>Default: zbx\_sessionid|Unique session cookie ID - a 32 character string.|Example: 004bc0213e7e8bca87fcc3919eca5270|Current date and time +1 month (31 days)|\+|\+ (only if HTTPS is enabled on a web server)| |tab|Active tab number; this cookie is only used on pages with multiple tabs (e.g. *Host*, *Trigger* or *Action* configuration page) and is created, when a user navigates from a primary tab to another tab (such as *Tags* or *Dependencies* tab).<br><br>0 is used for the primary tab.|Example: 1|Session (expires when the browsing session ends)|\-|\-| |browserwarning\_ignore|Whether a warning about using an outdated browser should be ignored.|yes|Session (expires when the browsing session ends)|\-|\-| ::: noteclassic Forcing 'HttpOnly' flag on Zabbix cookies by a webserver directive is not supported. ::: [^1]: When `HttpOnly` is 'true' the cookie will be made accessible only through the HTTP protocol. This means that the cookie won't be accessible by scripting languages, such as JavaScript. This setting can effectively help to reduce identity theft through XSS attacks (although it is not supported by all browsers). [^2]: `Secure` indicates that the cookie should only be transmitted over a secure HTTPS connection from the client. When set to 'true', the cookie will only be set if a secure connection exists. #### Overview This page provides a list of cookies used by Zabbix. |Name|Description|Values|Expires/Max-Age|HttpOnly[^1]|Secure[^2]| |----|-----------|------|---------------|------------|----------| |PHPSESSID|Unique PHP session ID.<br><br>The length can be set in *php.ini - session.sid\_length*.|Example: kvlp5pu2ru1a2ccvff0g52m87a|Session (expires when the browsing session ends)|\+|\+ (only if HTTPS is enabled on a web server)| |ZBX\_SESSION\_NAME<br>(available since 4.0.0).<br>String used as the name of the Zabbix frontend session cookie.<br><br>Default: zbx\_sessionid|Unique session cookie ID - a 32 character string.|Example: 004bc0213e7e8bca87fcc3919eca5270|Current date and time +1 month (31 days)|\+|\+ (only if HTTPS is enabled on a web server)| |tab|Active tab number; this cookie is only used on pages with multiple tabs (e.g. *Host*, *Trigger* or *Action* configuration page) and is created, when a user navigates from a primary tab to another tab (such as *Tags* or *Dependencies* tab).<br><br>0 is used for the primary tab.|Example: 1|Session (expires when the browsing session ends)|\-|\-| |browserwarning\_ignore|Whether a warning about using an outdated browser should be ignored.|yes|Session (expires when the browsing session ends)|\-|\-| ::: noteclassic Forcing 'HttpOnly' flag on Zabbix cookies by a webserver directive is not supported. ::: [^1]: When `HttpOnly` is 'true' the cookie will be made accessible only through the HTTP protocol. This means that the cookie won't be accessible by scripting languages, such as JavaScript. This setting can effectively help to reduce identity theft through XSS attacks (although it is not supported by all browsers). [^2]: `Secure` indicates that the cookie should only be transmitted over a secure HTTPS connection from the client. When set to 'true', the cookie will only be set if a secure connection exists. #### Overview This section explains how to add a “Host group” type element when configuring a [network map](/manual/config/visualization/maps/map). #### Overview This section explains how to add a “Host group” type element when configuring a [network map](/manual/config/visualization/maps/map). #### Overview This section lists available [screen](/manual/config/visualization/screens) elements and provides details for screen element configuration. #### Overview This section lists available [screen](/manual/config/visualization/screens) elements and provides details for screen element configuration. #### Overview This section lists parameters supported in a Zabbix proxy configuration file (zabbix\_proxy.conf). Note that: - The default values reflect daemon defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Overview This section lists parameters supported in a Zabbix proxy configuration file (zabbix\_proxy.conf). Note that: - The default values reflect daemon defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Overview Update operations allow you to be notified when problems are [updated](/manual/acknowledges#updating_problems) by other users, i.e.: - commented upon - acknowledged - severity changed - closed (manually) Update operations are available in actions with the event source as *Triggers*. Both messages and remote commands are supported in update operations. Update operations do not support escalating - all operations are assigned to a single step. #### Overview Update operations allow you to be notified when problems are [updated](/manual/acknowledges#updating_problems) by other users, i.e.: - commented upon - acknowledged - severity changed - closed (manually) Update operations are available in actions with the event source as *Triggers*. Both messages and remote commands are supported in update operations. Update operations do not support escalating - all operations are assigned to a single step. #### Overview While a [simple graph](simple) is great for accessing data of one item and [custom graphs](custom) offer customisation options, none of the two allow to quickly create a comparison graph for multiple items with little effort and no maintenance. To address this issue, since Zabbix 2.4 it is possible to create ad-hoc graphs for several items in a very quick way. #### Overview While a [simple graph](simple) is great for accessing data of one item and [custom graphs](custom) offer customisation options, none of the two allow to quickly create a comparison graph for multiple items with little effort and no maintenance. To address this issue, since Zabbix 2.4 it is possible to create ad-hoc graphs for several items in a very quick way. #### Overview With lots of data flowing into Zabbix, it becomes much easier for the users if they can look at a visual representation of what is going on rather than only numbers. This is where graphs come in. Graphs allow to grasp the data flow at a glance, correlate problems, discover when something started or make a presentation of when something might turn into a problem. Zabbix provides users with: - built-in [simple graphs](/manual/config/visualization/graphs/simple) of one item data - the possibility to create more complex [customized graphs](/manual/config/visualization/graphs/custom) - access to a comparison of several items quickly in [ad-hoc graphs](/manual/config/visualization/graphs/adhoc) - modern customisable [vector graphs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph) #### Overview With lots of data flowing into Zabbix, it becomes much easier for the users if they can look at a visual representation of what is going on rather than only numbers. This is where graphs come in. Graphs allow to grasp the data flow at a glance, correlate problems, discover when something started or make a presentation of when something might turn into a problem. Zabbix provides users with: - built-in [simple graphs](/manual/config/visualization/graphs/simple) of one item data - the possibility to create more complex [customized graphs](/manual/config/visualization/graphs/custom) - access to a comparison of several items quickly in [ad-hoc graphs](/manual/config/visualization/graphs/adhoc) - modern customisable [vector graphs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph) #### Overview You can assign some triggers to a [link](/manual/config/visualization/maps/map#linking_elements) between elements in a network map. When these triggers go into a problem state, the link can reflect that. When you configure a link, you set the default link type and color. When you assign triggers to a link, you can assign different link types and colors with these triggers. Should any of these triggers go into a problem state, their link style and color will be displayed on the link. So maybe your default link was a green line. Now, with the trigger in problem state, your link may become bold red (if you have defined it so). #### Overview You can assign some triggers to a [link](/manual/config/visualization/maps/map#linking_elements) between elements in a network map. When these triggers go into a problem state, the link can reflect that. When you configure a link, you set the default link type and color. When you assign triggers to a link, you can assign different link types and colors with these triggers. Should any of these triggers go into a problem state, their link style and color will be displayed on the link. So maybe your default link was a green line. Now, with the trigger in problem state, your link may become bold red (if you have defined it so). #### Parameters |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AlertScriptsPath|no|<|/usr/local/share/zabbix/alertscripts|Location of custom alert scripts (depends on compile-time installation variable *datadir*).| |AllowRoot|no|<|0|Allow the server to run as 'root'. If disabled and the server is started by 'root', the server will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow<br>This parameter is supported since Zabbix 2.2.0.| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size for storing host, item and trigger data.<br>The maximum value of this parameter was increased from 8GB to 64GB in Zabbix 4.0.21.| |CacheUpdateFrequency|no|1-3600|60|How often Zabbix will perform update of configuration cache, in seconds.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.| |DBName|yes|<|<|Database name.| |DBPassword|no|<|<|Database password.<br>Comment this line if no password is used.| |DBPort|no|1024-65535|<|Database port when not using local socket.| |DBSchema|no|<|<|Schema name. Used for IBM DB2 and PostgreSQL.| |DBSocket|no|<|<|Path to MySQL socket file.| |DBUser|no|<|<|Database user.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)<br>See also [runtime control](/manual/concepts/server#server_process) options.| |ExportDir|no|<|<|Directory for [real-time export](/manual/appendix/install/real_time_export) of events, history and trends in newline-delimited JSON format. If set, enables real-time export.<br>This parameter is supported since Zabbix 4.0.0.| |ExportFileSize|no|1M-1G|1G|Maximum size per export file in bytes. Only used for rotation if ExportDir is set.<br>This parameter is supported since Zabbix 4.0.0.| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |HistoryStorageDateIndex|no|<|0|Enable preprocessing of history values in history storage to store values in different indices based on date:<br>0 - disable<br>1 - enable| |HistoryStorageURL|no|<|<|History storage HTTP\[S\] URL.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HistoryStorageTypes|no|<|uint,dbl,str,log,text|Comma separated list of value types to be sent to the history storage.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter. This postponing behavior is in place since Zabbix 2.4.0.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`. Pattern matching is supported since Zabbix 2.4.0.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.<br>This parameter is supported since Zabbix 2.0.0.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.<br>This parameter is supported since Zabbix 2.0.0.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.<br>Multiple IP addresses are supported since Zabbix 1.8.3.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at server startup. Modules are used to extend functionality of the server.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>(since 4.0.9) LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or (since 4.0.9) the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of server modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.<br>This parameter is supported since Zabbix 1.8.2.| |MaxHousekeeperDelete|no|0-1000000|5000|No more than 'MaxHousekeeperDelete' rows (corresponding to \[tablename\], \[field\], \[value\]) will be deleted per one task in one housekeeping cycle.<br>If set to 0 then no limit is used at all. In this case you must know what you are doing, so as not to [overload the database!](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items.| |PidFile|no|<|/tmp/zabbix\_server.pid|Name of PID file.| |ProxyConfigFrequency|no|1-604800|3600|How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.<br>This parameter is supported since Zabbix 1.8.3.| |ProxyDataFrequency|no|1-3600|1|How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.<br>This parameter is supported since Zabbix 1.8.3.| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the server.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.<br>This parameter is supported since Zabbix 2.0.0.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix proxy and Zabbix agent;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- sending notification emails (connections to SMTP server)| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.| |SSLCALocation|no|<|<|Override the location of certificate authority (CA) files for SSL server certificate verification. If not set, system-wide directory will be used.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of DB Syncers.<br>The upper limit used to be 64 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartAlerters|no|1-100|3|Number of pre-forked instances of alerters.<br>This parameter is supported since Zabbix 3.4.0.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of discoverers.<br>The upper limit used to be 255 before version 1.8.5.| |StartEscalators|no|1-100|1|Number of pre-forked instances of escalators.<br>This parameter is supported since Zabbix 3.0.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of HTTP pollers**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of IPMI pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of Java pollers**^[1](zabbix_server#footnotes)^**.<br>This parameter is supported since Zabbix 2.0.0.| |StartPingers|no|0-1000|1|Number of pre-forked instances of ICMP pingers**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java)**^[1](zabbix_server#footnotes)^**.<br>Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.<br>The upper limit used to be 255 before version 1.8.5.<br>This option is missing in version 1.8.3.| |StartPollers|no|0-1000|5|Number of pre-forked instances of pollers**^[1](zabbix_server#footnotes)^**.<br>*Note* that a non-zero value is required for internal, aggregated and calculated items to work.| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing workers**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 3.4.0.| |StartProxyPollers|no|0-250|1|Number of pre-forked instances of pollers for passive proxies**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartSNMPTrapper|no|0-1|0|If set to 1, SNMP trapper process will be started.<br>This parameter is supported since Zabbix 2.0.0.| |StartTimers|no|1-1000|1|Number of pre-forked instances of timers.<br>Timers process maintenance periods.<br>This parameter is supported since Zabbix 2.2.0.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of trappers**^[1](zabbix_server#footnotes)^**.<br>Trappers accept incoming connections from Zabbix sender, active agents and active proxies.<br>At least one trapper process must be running to display server availability and view queue in the frontend.<br>The upper limit used to be 255 before version 1.8.5.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked vmware collector instances.<br>This parameter is supported since Zabbix 2.2.0.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.0.5.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |TrendCacheSize|no|128K-2G|4M|Size of trend cache, in bytes.<br>Shared memory size for storing trends data.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.<br>This parameter is supported since Zabbix 2.4.0.| |ValueCacheSize|no|0,128K-64G|8M|Size of history value cache, in bytes.<br>Shared memory size for caching item history data requests.<br>Setting to 0 disables value cache (not recommended).<br>When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.<br>This parameter is supported since Zabbix 2.2.0.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| #### Parameters |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AlertScriptsPath|no|<|/usr/local/share/zabbix/alertscripts|Location of custom alert scripts (depends on compile-time installation variable *datadir*).| |AllowRoot|no|<|0|Allow the server to run as 'root'. If disabled and the server is started by 'root', the server will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow<br>This parameter is supported since Zabbix 2.2.0.| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size for storing host, item and trigger data.<br>The maximum value of this parameter was increased from 8GB to 64GB in Zabbix 4.0.21.| |CacheUpdateFrequency|no|1-3600|60|How often Zabbix will perform update of configuration cache, in seconds.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.| |DBName|yes|<|<|Database name.| |DBPassword|no|<|<|Database password.<br>Comment this line if no password is used.| |DBPort|no|1024-65535|<|Database port when not using local socket.| |DBSchema|no|<|<|Schema name. Used for IBM DB2 and PostgreSQL.| |DBSocket|no|<|<|Path to MySQL socket file.| |DBUser|no|<|<|Database user.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)<br>See also [runtime control](/manual/concepts/server#server_process) options.| |ExportDir|no|<|<|Directory for [real-time export](/manual/appendix/install/real_time_export) of events, history and trends in newline-delimited JSON format. If set, enables real-time export.<br>This parameter is supported since Zabbix 4.0.0.| |ExportFileSize|no|1M-1G|1G|Maximum size per export file in bytes. Only used for rotation if ExportDir is set.<br>This parameter is supported since Zabbix 4.0.0.| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |HistoryStorageDateIndex|no|<|0|Enable preprocessing of history values in history storage to store values in different indices based on date:<br>0 - disable<br>1 - enable| |HistoryStorageURL|no|<|<|History storage HTTP\[S\] URL.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HistoryStorageTypes|no|<|uint,dbl,str,log,text|Comma separated list of value types to be sent to the history storage.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter. This postponing behavior is in place since Zabbix 2.4.0.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`. Pattern matching is supported since Zabbix 2.4.0.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.<br>This parameter is supported since Zabbix 2.0.0.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.<br>This parameter is supported since Zabbix 2.0.0.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.<br>Multiple IP addresses are supported since Zabbix 1.8.3.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at server startup. Modules are used to extend functionality of the server.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>(since 4.0.9) LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or (since 4.0.9) the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of server modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.<br>This parameter is supported since Zabbix 1.8.2.| |MaxHousekeeperDelete|no|0-1000000|5000|No more than 'MaxHousekeeperDelete' rows (corresponding to \[tablename\], \[field\], \[value\]) will be deleted per one task in one housekeeping cycle.<br>If set to 0 then no limit is used at all. In this case you must know what you are doing, so as not to [overload the database!](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items.| |PidFile|no|<|/tmp/zabbix\_server.pid|Name of PID file.| |ProxyConfigFrequency|no|1-604800|3600|How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.<br>This parameter is supported since Zabbix 1.8.3.| |ProxyDataFrequency|no|1-3600|1|How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.<br>This parameter is supported since Zabbix 1.8.3.| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the server.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.<br>This parameter is supported since Zabbix 2.0.0.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix proxy and Zabbix agent;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- sending notification emails (connections to SMTP server)| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.| |SSLCALocation|no|<|<|Override the location of certificate authority (CA) files for SSL server certificate verification. If not set, system-wide directory will be used.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of DB Syncers.<br>The upper limit used to be 64 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartAlerters|no|1-100|3|Number of pre-forked instances of alerters.<br>This parameter is supported since Zabbix 3.4.0.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of discoverers.<br>The upper limit used to be 255 before version 1.8.5.| |StartEscalators|no|1-100|1|Number of pre-forked instances of escalators.<br>This parameter is supported since Zabbix 3.0.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of HTTP pollers**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of IPMI pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of Java pollers**^[1](zabbix_server#footnotes)^**.<br>This parameter is supported since Zabbix 2.0.0.| |StartPingers|no|0-1000|1|Number of pre-forked instances of ICMP pingers**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java)**^[1](zabbix_server#footnotes)^**.<br>Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.<br>The upper limit used to be 255 before version 1.8.5.<br>This option is missing in version 1.8.3.| |StartPollers|no|0-1000|5|Number of pre-forked instances of pollers**^[1](zabbix_server#footnotes)^**.<br>*Note* that a non-zero value is required for internal, aggregated and calculated items to work.| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing workers**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 3.4.0.| |StartProxyPollers|no|0-250|1|Number of pre-forked instances of pollers for passive proxies**^[1](zabbix_server#footnotes)^**.<br>The upper limit used to be 255 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartSNMPTrapper|no|0-1|0|If set to 1, SNMP trapper process will be started.<br>This parameter is supported since Zabbix 2.0.0.| |StartTimers|no|1-1000|1|Number of pre-forked instances of timers.<br>Timers process maintenance periods.<br>This parameter is supported since Zabbix 2.2.0.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of trappers**^[1](zabbix_server#footnotes)^**.<br>Trappers accept incoming connections from Zabbix sender, active agents and active proxies.<br>At least one trapper process must be running to display server availability and view queue in the frontend.<br>The upper limit used to be 255 before version 1.8.5.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked vmware collector instances.<br>This parameter is supported since Zabbix 2.2.0.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.0.5.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |TrendCacheSize|no|128K-2G|4M|Size of trend cache, in bytes.<br>Shared memory size for storing trends data.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.<br>This parameter is supported since Zabbix 2.4.0.| |ValueCacheSize|no|0,128K-64G|8M|Size of history value cache, in bytes.<br>Shared memory size for caching item history data requests.<br>Setting to 0 disables value cache (not recommended).<br>When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.<br>This parameter is supported since Zabbix 2.2.0.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| #### Parameters |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AllowRoot|no|<|0|Allow the proxy to run as 'root'. If disabled and the proxy is started by 'root', the proxy will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow<br>This parameter is supported since Zabbix 2.2.0.| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size, for storing host and item data.<br>The maximum value of this parameter was increased from 8GB to 64GB in Zabbix 4.0.21.| |ConfigFrequency|no|1-604800|3600|How often proxy retrieves configuration data from Zabbix server in seconds.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.| |DBName|yes|<|<|Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use [in-memory database](https://www.sqlite.org/inmemorydb.html), e.g. `:memory:`, `file::memory:?cache=shared` or `file:memdb1?mode=memory&cache=shared`).<br><br>Warning: Do not attempt to use the same database Zabbix server is using.| |DBPassword|no|<|<|Database password. Ignored for SQLite.<br>Comment this line if no password is used.| |DBSchema|no|<|<|Schema name. Used for IBM DB2 and PostgreSQL.| |DBSocket|no|<|3306|Path to MySQL socket.<br>Database port when not using local socket. Ignored for SQLite.| |DBUser|<|<|<|Database user. Ignored for SQLite.| |DataSenderFrequency|no|1-3600|1|Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |EnableRemoteCommands|no|<|0|Whether remote commands from Zabbix server are allowed.<br>0 - not allowed<br>1 - allowed<br>This parameter is supported since Zabbix 3.4.0.| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HeartbeatFrequency|no|0-3600|60|Frequency of heartbeat messages in seconds.<br>Used for monitoring availability of proxy on server side.<br>0 - heartbeat messages disabled.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |Hostname|no|<|Set by HostnameItem|Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 64| |HostnameItem|no|<|system.hostname|Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).<br>Does not support UserParameters, performance counters or aliases, but does support system.run\[\].<br><br>Ignored if Hostname is set.<br><br>This parameter is supported since Zabbix 1.8.6.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. This postponing behavior is in place since Zabbix 2.4.0.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`. Pattern matching is supported since Zabbix 2.4.0.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.<br>This parameter is supported since Zabbix 2.0.0.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.<br>This parameter is supported since Zabbix 2.0.0.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.<br>Multiple IP addresses are supported since Zabbix 1.8.3.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at proxy startup. Modules are used to extend functionality of the proxy.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>(since 4.0.9) LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or (since 4.0.9) the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of proxy modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogRemoteCommands|no|<|0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>This parameter is supported since Zabbix 3.4.0.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.<br>This parameter is supported since Zabbix 1.8.2.| |PidFile|no|<|/tmp/zabbix\_proxy.pid|Name of PID file.| |ProxyLocalBuffer|no|0-720|0|Proxy will keep data locally for N hours, even if the data have already been synced with the server.<br>This parameter may be used if local data will be used by third party applications.| |ProxyMode|no|0-1|0|Proxy operating mode.<br>0 - proxy in the active mode<br>1 - proxy in the passive mode<br>This parameter is supported since Zabbix 1.8.3.<br>*Note* that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place.| |ProxyOfflineBuffer|no|1-720|1|Proxy will keep data for N hours in case of no connectivity with Zabbix server.<br>Older data will be lost.| |ServerPort|no|1024-32767|10051|Port of Zabbix trapper on Zabbix server.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |Server|yes|<|<|If ProxyMode is set to *active mode*:<br>IP address or DNS name of Zabbix server to get configuration data from and send data to.<br><br>If ProxyMode is set to *passive mode*:<br>List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>*Example*: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the proxy.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.<br>This parameter is supported since Zabbix 2.0.0.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix server;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.0.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.0.| |SSLCALocation|no|<|<|Location of certificate authority (CA) files for SSL server certificate verification.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of DB Syncers.<br>The upper limit used to be 64 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of discoverers.<br>The upper limit used to be 255 before version 1.8.5.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of HTTP pollers.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of IPMI pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of Java pollers.<br>This parameter is supported since Zabbix 2.0.0.| |StartPingers|no|0-1000|1|Number of pre-forked instances of ICMP pingers.<br>The upper limit used to be 255 before version 1.8.5.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).<br>Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.<br>The upper limit used to be 255 before version 1.8.5.<br>This option is missing in version 1.8.3.| |StartPollers|no|0-1000|5|Number of pre-forked instances of pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartSNMPTrapper|no|0-1|0|If set to 1, SNMP trapper process will be started.<br>This parameter is supported since Zabbix 2.0.0.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of trappers.<br>Trappers accept incoming connections from Zabbix sender and active agents.<br>The upper limit used to be 255 before version 1.8.5.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked vmware collector instances.<br>This parameter is supported since Zabbix 2.2.0.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.0.5.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSAccept|yes for passive proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSConnect|yes for active proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no|<|<|Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no|<|<|Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no|<|<|Allowed server certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no|<|<|Allowed server certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.<br>This parameter is supported since Zabbix 2.4.0.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.<br>This parameter is supported since Zabbix 2.2.0.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| #### Parameters |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AllowRoot|no|<|0|Allow the proxy to run as 'root'. If disabled and the proxy is started by 'root', the proxy will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow<br>This parameter is supported since Zabbix 2.2.0.| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size, for storing host and item data.<br>The maximum value of this parameter was increased from 8GB to 64GB in Zabbix 4.0.21.| |ConfigFrequency|no|1-604800|3600|How often proxy retrieves configuration data from Zabbix server in seconds.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.| |DBName|yes|<|<|Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use [in-memory database](https://www.sqlite.org/inmemorydb.html), e.g. `:memory:`, `file::memory:?cache=shared` or `file:memdb1?mode=memory&cache=shared`).<br><br>Warning: Do not attempt to use the same database Zabbix server is using.| |DBPassword|no|<|<|Database password. Ignored for SQLite.<br>Comment this line if no password is used.| |DBSchema|no|<|<|Schema name. Used for IBM DB2 and PostgreSQL.| |DBSocket|no|<|3306|Path to MySQL socket.<br>Database port when not using local socket. Ignored for SQLite.| |DBUser|<|<|<|Database user. Ignored for SQLite.| |DataSenderFrequency|no|1-3600|1|Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |EnableRemoteCommands|no|<|0|Whether remote commands from Zabbix server are allowed.<br>0 - not allowed<br>1 - allowed<br>This parameter is supported since Zabbix 3.4.0.| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HeartbeatFrequency|no|0-3600|60|Frequency of heartbeat messages in seconds.<br>Used for monitoring availability of proxy on server side.<br>0 - heartbeat messages disabled.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |Hostname|no|<|Set by HostnameItem|Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 64| |HostnameItem|no|<|system.hostname|Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).<br>Does not support UserParameters, performance counters or aliases, but does support system.run\[\].<br><br>Ignored if Hostname is set.<br><br>This parameter is supported since Zabbix 1.8.6.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. This postponing behavior is in place since Zabbix 2.4.0.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`. Pattern matching is supported since Zabbix 2.4.0.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.<br>This parameter is supported since Zabbix 2.0.0.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.<br>This parameter is supported since Zabbix 2.0.0.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.<br>Multiple IP addresses are supported since Zabbix 1.8.3.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at proxy startup. Modules are used to extend functionality of the proxy.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>(since 4.0.9) LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or (since 4.0.9) the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of proxy modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogRemoteCommands|no|<|0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>This parameter is supported since Zabbix 3.4.0.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.<br>This parameter is supported since Zabbix 1.8.2.| |PidFile|no|<|/tmp/zabbix\_proxy.pid|Name of PID file.| |ProxyLocalBuffer|no|0-720|0|Proxy will keep data locally for N hours, even if the data have already been synced with the server.<br>This parameter may be used if local data will be used by third party applications.| |ProxyMode|no|0-1|0|Proxy operating mode.<br>0 - proxy in the active mode<br>1 - proxy in the passive mode<br>This parameter is supported since Zabbix 1.8.3.<br>*Note* that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place.| |ProxyOfflineBuffer|no|1-720|1|Proxy will keep data for N hours in case of no connectivity with Zabbix server.<br>Older data will be lost.| |ServerPort|no|1024-32767|10051|Port of Zabbix trapper on Zabbix server.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |Server|yes|<|<|If ProxyMode is set to *active mode*:<br>IP address or DNS name of Zabbix server to get configuration data from and send data to.<br><br>If ProxyMode is set to *passive mode*:<br>List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>*Example*: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the proxy.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.<br>This parameter is supported since Zabbix 2.0.0.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix server;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.0.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only and is supported since Zabbix 2.4.0.| |SSLCALocation|no|<|<|Location of certificate authority (CA) files for SSL server certificate verification.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of DB Syncers.<br>The upper limit used to be 64 before version 1.8.5.<br>This parameter is supported since Zabbix 1.8.3.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of discoverers.<br>The upper limit used to be 255 before version 1.8.5.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of HTTP pollers.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of IPMI pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of Java pollers.<br>This parameter is supported since Zabbix 2.0.0.| |StartPingers|no|0-1000|1|Number of pre-forked instances of ICMP pingers.<br>The upper limit used to be 255 before version 1.8.5.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).<br>Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.<br>The upper limit used to be 255 before version 1.8.5.<br>This option is missing in version 1.8.3.| |StartPollers|no|0-1000|5|Number of pre-forked instances of pollers.<br>The upper limit used to be 255 before version 1.8.5.| |StartSNMPTrapper|no|0-1|0|If set to 1, SNMP trapper process will be started.<br>This parameter is supported since Zabbix 2.0.0.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of trappers.<br>Trappers accept incoming connections from Zabbix sender and active agents.<br>The upper limit used to be 255 before version 1.8.5.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked vmware collector instances.<br>This parameter is supported since Zabbix 2.2.0.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.0.5.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSAccept|yes for passive proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.0.19.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.0.19.| |TLSConnect|yes for active proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no|<|<|Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no|<|<|Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no|<|<|Allowed server certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no|<|<|Allowed server certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.<br>This parameter is supported since Zabbix 2.4.0.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.<br>This parameter is supported since Zabbix 2.2.0.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.<br>This parameter is supported since Zabbix 2.2.0.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).<br>This parameter is supported since Zabbix 2.2.9, 2.4.4| #### Positional macros in web monitoring items [Deprecated positional macros](/manual/installation/upgrade_notes_400#deprecated_macros_in_item_names) ($1, $2, ...) are no longer used in the item names when creating web monitoring [items](/manual/web_monitoring/items). In those cases where positional macros are used in existing web monitoring items, the item names will be updated in the database not to use positional macros as soon as the web scenario is updated. #### Positional macros in web monitoring items [Deprecated positional macros](/manual/installation/upgrade_notes_400#deprecated_macros_in_item_names) ($1, $2, ...) are no longer used in the item names when creating web monitoring [items](/manual/web_monitoring/items). In those cases where positional macros are used in existing web monitoring items, the item names will be updated in the database not to use positional macros as soon as the web scenario is updated. #### Problem export to CSV Export to CSV in *Monitoring* → *Problems* now exports problems from all pages, not just the selected page. Filter settings are still obeyed. #### Problem export to CSV Export to CSV in *Monitoring* → *Problems* now exports problems from all pages, not just the selected page. Filter settings are still obeyed. # problem.get # problem.get #### Protection against user enumeration attacks To make sure an attacker may not guess valid user names because temporary account blocking after consecutive failed login attempts is only applied to existing user names, the account blocking is now also enforced if non-existing user names are used. To further obscure the possibility of such attacks, a unified generic message is now displayed for all problems related to incorrect login: Incorrect user name or password or account is temporarily blocked. #### Protection against user enumeration attacks To make sure an attacker may not guess valid user names because temporary account blocking after consecutive failed login attempts is only applied to existing user names, the account blocking is now also enforced if non-existing user names are used. To further obscure the possibility of such attacks, a unified generic message is now displayed for all problems related to incorrect login: Incorrect user name or password or account is temporarily blocked. #### Proxies In a [proxy](/manual/distributed_monitoring/proxies#configuration) configuration, user macros can be used in the following field: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Interface port (for passive proxy)|<|no| #### Proxies In a [proxy](/manual/distributed_monitoring/proxies#configuration) configuration, user macros can be used in the following field: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Interface port (for passive proxy)|<|no| # proxy.create # proxy.create # proxy.delete # proxy.delete # proxy.get # proxy.get # proxy.update # proxy.update #### Real-time export of events, items, trends In case of a write error during the export (data cannot be written to the export file or the export file cannot be renamed or a new one cannot be created after renaming it), the data item is now dropped and never written to the export file. It is written only in the Zabbix database. Writing data to the export file is resumed when the writing problem is resolved. Previously, in case of a write error, Zabbix would retry with a 10 second interval until success. The previous behavior, while ensuring history data equivalence between database and the export files resulted in actually stopping monitoring until the problem with the export file was fixed. Now the priority is given to continued monitoring rather than keeping the export file in sync with database at all cost. See also: [Real-time export of events, items, trends](/manual/appendix/install/real_time_export) #### Real-time export of events, items, trends In case of a write error during the export (data cannot be written to the export file or the export file cannot be renamed or a new one cannot be created after renaming it), the data item is now dropped and never written to the export file. It is written only in the Zabbix database. Writing data to the export file is resumed when the writing problem is resolved. Previously, in case of a write error, Zabbix would retry with a 10 second interval until success. The previous behavior, while ensuring history data equivalence between database and the export files resulted in actually stopping monitoring until the problem with the export file was fixed. Now the priority is given to continued monitoring rather than keeping the export file in sync with database at all cost. See also: [Real-time export of events, items, trends](/manual/appendix/install/real_time_export) #### Recent data vs longer periods For very recent data a **single** line is drawn connecting each received value. The single line is drawn as long as there is at least one horizontal pixel available for one value. For data that show a longer period **three lines** are drawn - a dark green one shows the average, while a light pink and a light green line shows the maximum and minimum values at that point in time. The space between the highs and the lows is filled with yellow background. Working time (working days) is displayed in graphs as a white background, while non-working time is displayed in gray (with the *Original blue* default frontend theme). {width="550"} Working time is always displayed in simple graphs, whereas displaying it in [custom graphs](custom#configuring_custom_graphs) is a user preference. Working time is not displayed if the graph shows more than 3 months. #### Recent data vs longer periods For very recent data a **single** line is drawn connecting each received value. The single line is drawn as long as there is at least one horizontal pixel available for one value. For data that show a longer period **three lines** are drawn - a dark green one shows the average, while a light pink and a light green line shows the maximum and minimum values at that point in time. The space between the highs and the lows is filled with yellow background. Working time (working days) is displayed in graphs as a white background, while non-working time is displayed in gray (with the *Original blue* default frontend theme). {width="550"} Working time is always displayed in simple graphs, whereas displaying it in [custom graphs](custom#configuring_custom_graphs) is a user preference. Working time is not displayed if the graph shows more than 3 months. #### Regular expressions The *File systems for discovery* global [regular expression](/manual/regular_expressions#explanation_of_global_regular_expressions) has been updated to include "apfs". #### Regular expressions The *File systems for discovery* global [regular expression](/manual/regular_expressions#explanation_of_global_regular_expressions) has been updated to include "apfs". ### Runtime control options **config\_cache\_reload** Reload configuration cache. Ignored if cache is being currently loaded. Active Zabbix proxy will connect to the Zabbix server and request configuration data. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file. **housekeeper\_execute** Execute the housekeeper. Ignored if housekeeper is being currently executed. **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Runtime control options **config\_cache\_reload** Reload configuration cache. Ignored if cache is being currently loaded. Active Zabbix proxy will connect to the Zabbix server and request configuration data. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file. **housekeeper\_execute** Execute the housekeeper. Ignored if housekeeper is being currently executed. **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Runtime control options **config\_cache\_reload** Reload configuration cache. Ignored if cache is being currently loaded. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file. **housekeeper\_execute** Execute the housekeeper. Ignored if housekeeper is being currently executed. **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Runtime control options **config\_cache\_reload** Reload configuration cache. Ignored if cache is being currently loaded. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file. **housekeeper\_execute** Execute the housekeeper. Ignored if housekeeper is being currently executed. **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Runtime control options **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Runtime control options **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} # screen.create # screen.create # screen.delete # screen.delete # screen.get # screen.get # screenitem.create # screenitem.create # screenitem.delete # screenitem.delete # screenitem.get # screenitem.get # screenitem.update # screenitem.update # screenitem.updatebyposition # screenitem.updatebyposition # screen.update # screen.update # script.create # script.create # script.delete # script.delete # script.execute # script.execute # script.get # script.get # script.getscriptsbyhosts # script.getscriptsbyhosts # script.update # script.update #### Second precision for age/duration macros Several built-in [macros](/manual/appendix/macros/supported_by_location) returning age/duration now return the value with down-to-a-second precision: - {DISCOVERY.DEVICE.UPTIME} - {DISCOVERY.SERVICE.UPTIME} - {EVENT.AGE} Previously these macros returned values with down-to-a-minute precision. #### Second precision for age/duration macros Several built-in [macros](/manual/appendix/macros/supported_by_location) returning age/duration now return the value with down-to-a-second precision: - {DISCOVERY.DEVICE.UPTIME} - {DISCOVERY.SERVICE.UPTIME} - {EVENT.AGE} Previously these macros returned values with down-to-a-minute precision. ### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858). ### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858). #### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858) #### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858) ### See also - [Template changes](/manual/installation/template_changes) ### See also - [Template changes](/manual/installation/template_changes) ### See also - [Template changes](/manual/installation/template_changes) ### See also - [Template changes](/manual/installation/template_changes) #### Selecting elements To select elements, select one and then hold down *Ctrl* to select the others. You can also select multiple elements by dragging a rectangle in the editable area and selecting all elements in it (option available since Zabbix 2.0). Once you select more than one element, the element property form shifts to the mass-update mode so you can change attributes of selected elements in one go. To do so, mark the attribute using the checkbox and enter a new value for it. You may use macros here (such as, say, {HOST.NAME} for the element label). {width="600"} #### Selecting elements To select elements, select one and then hold down *Ctrl* to select the others. You can also select multiple elements by dragging a rectangle in the editable area and selecting all elements in it (option available since Zabbix 2.0). Once you select more than one element, the element property form shifts to the mass-update mode so you can change attributes of selected elements in one go. To do so, mark the attribute using the checkbox and enter a new value for it. You may use macros here (such as, say, {HOST.NAME} for the element label). {width="600"} # service.adddependencies # service.adddependencies # service.addtimes # service.addtimes # service.create # service.create # service.delete # service.delete # service.deletedependencies # service.deletedependencies # service.deletetimes # service.deletetimes # service.get # service.get # service.getsla # service.getsla # service.update # service.update #### Sharing The **Sharing** tab contains the map type as well as sharing options (user groups, users) for private maps: {width="600"} |Parameter|Description| |---------|-----------| |*Type*|Select map type:<br>**Private** - map is visible only to selected user groups and users<br>**Public** - map is visible to all| |*List of user group shares*|Select user groups that the map is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the map is accessible to.<br>You may allow read-only or read-write access.| When you click on *Add* to save this map, you have created an empty map with a name, dimensions and certain preferences. Now you need to add some elements. For that, click on *Constructor* in the map list to open the editable area. #### Sharing The **Sharing** tab contains the map type as well as sharing options (user groups, users) for private maps: {width="600"} |Parameter|Description| |---------|-----------| |*Type*|Select map type:<br>**Private** - map is visible only to selected user groups and users<br>**Public** - map is visible to all| |*List of user group shares*|Select user groups that the map is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the map is accessible to.<br>You may allow read-only or read-write access.| When you click on *Add* to save this map, you have created an empty map with a name, dimensions and certain preferences. Now you need to add some elements. For that, click on *Constructor* in the map list to open the editable area. #### SNMP interface templates Update intervals have been changed from 5m to 3m for these LLD item prototypes: - `Interface {#IFNAME}({#IFALIAS}): Inbound packets with errors` - `Interface {#IFNAME}({#IFALIAS}): Outbound packets with errors` in: - *Template Module Interfaces Simple SNMPv1* - *Template Module Interfaces Simple SNMPv2* - *Template Module Interfaces SNMPv1* - *Template Module Interfaces SNMPv2* - *Template Module Interfaces Windows SNMPv2* These update intervals have been changed to avoid creation of excess internal events caused by trigger state flapping. #### SNMP interface templates Update intervals have been changed from 5m to 3m for these LLD item prototypes: - `Interface {#IFNAME}({#IFALIAS}): Inbound packets with errors` - `Interface {#IFNAME}({#IFALIAS}): Outbound packets with errors` in: - *Template Module Interfaces Simple SNMPv1* - *Template Module Interfaces Simple SNMPv2* - *Template Module Interfaces SNMPv1* - *Template Module Interfaces SNMPv2* - *Template Module Interfaces Windows SNMPv2* These update intervals have been changed to avoid creation of excess internal events caused by trigger state flapping. #### Sound in browsers Sounds are now supported in MP3 format only. #### Sound in browsers Sounds are now supported in MP3 format only. ### Source CGraphItem::get() in *frontends/php/include/classes/api/services/CGraphItem.php*. ### Source CGraphItem::get() in *frontends/php/include/classes/api/services/CGraphItem.php*. ### Source CItemPrototype::get() in *frontends/php/include/classes/api/services/CItemPrototype.php*. ### Source CItemPrototype::get() in *frontends/php/include/classes/api/services/CItemPrototype.php*. ### Source CScreen::get() in *frontends/php/include/classes/api/services/CScreen.php*. ### Source CScreen::get() in *frontends/php/include/classes/api/services/CScreen.php*. #### Strings Strings should be enclosed with single ' or double " quotes. Inside the strings, single or double quotes (depending on which are used to enclose it) and backslashes `\` are escaped with the backslash `\` character. #### Strings Strings should be enclosed with single ' or double " quotes. Inside the strings, single or double quotes (depending on which are used to enclose it) and backslashes `\` are escaped with the backslash `\` character. #### Supported segments |Segment|Description| |-------|-----------| |`<name>`|Match object property by name.| |`*`|Match all object properties.| |`['<name>']`|Match object property by name.| |`['<name>', '<name>', ...]`|Match object property by any of the listed names.| |`[<index>]`|Match array element by the index.| |`[<number>, <number>, ...]`|Match array element by any of the listed indexes.| |`[*]`|Match all object properties or array elements.| |`[<start>:<end>]`|Match array elements by the defined range:<br>**<start>** - the first index to match (including). If not specified matches all array elements from the beginning. If negative specifies starting offset from the end of array.<br>**<end>** - the last index to match (excluding). If not specified matches all array elements to the end. If negative specifies starting offset from the end of array.| |`[?(<expression>)]`|Match objects/array elements by applying filter expression.| To find a matching segment ignoring its ancestry (detached segment) it must be prefixed with '..' , for example `$..name` or `$..['name']` return values of all 'name' properties. Since Zabbix 4.0.19 matched element names can be extracted by adding a `~` suffix to the JSONPath. It returns the name of the matched object or an index in string format of the matched array item. The output format follows the same rules as other JSONPath queries - definite path results are returned 'as is' and indefinite path results are returned in array. However there is not much point of extracting the name of an element matching a definite path - it's already known. #### Supported segments |Segment|Description| |-------|-----------| |`<name>`|Match object property by name.| |`*`|Match all object properties.| |`['<name>']`|Match object property by name.| |`['<name>', '<name>', ...]`|Match object property by any of the listed names.| |`[<index>]`|Match array element by the index.| |`[<number>, <number>, ...]`|Match array element by any of the listed indexes.| |`[*]`|Match all object properties or array elements.| |`[<start>:<end>]`|Match array elements by the defined range:<br>**<start>** - the first index to match (including). If not specified matches all array elements from the beginning. If negative specifies starting offset from the end of array.<br>**<end>** - the last index to match (excluding). If not specified matches all array elements to the end. If negative specifies starting offset from the end of array.| |`[?(<expression>)]`|Match objects/array elements by applying filter expression.| To find a matching segment ignoring its ancestry (detached segment) it must be prefixed with '..' , for example `$..name` or `$..['name']` return values of all 'name' properties. Since Zabbix 4.0.19 matched element names can be extracted by adding a `~` suffix to the JSONPath. It returns the name of the matched object or an index in string format of the matched array item. The output format follows the same rules as other JSONPath queries - definite path results are returned 'as is' and indefinite path results are returned in array. However there is not much point of extracting the name of an element matching a definite path - it's already known. ##### Switching from AES128 to AES256 Zabbix uses AES128 as the built-in default for data. Let's assume you are using certificates and want to switch to AES256, on OpenSSL 1.1.1. This can be achieved by adding the respective parameters in `zabbix_server.conf`: TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/server.crt TLSKeyFile=/home/zabbix/server.key TLSCipherCert13=TLS_AES_256_GCM_SHA384 TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384 TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256 TLSCipherPSK=kECDHEPSK+AES256:-SHA1 TLSCipherAll13=TLS_AES_256_GCM_SHA384 TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384 ::: noteimportant Although only certificate-related ciphersuites will be used, `TLSCipherPSK*` parameters are defined as well to avoid their default values which include less secure ciphers for wider interoperability. PSK ciphersuites cannot be completely disabled on server/proxy. ::: And in `zabbix_agentd.conf`: TLSConnect=cert TLSAccept=cert TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/agent.crt TLSKeyFile=/home/zabbix/agent.key TLSCipherCert13=TLS_AES_256_GCM_SHA384 TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384 ##### Switching from AES128 to AES256 Zabbix uses AES128 as the built-in default for data. Let's assume you are using certificates and want to switch to AES256, on OpenSSL 1.1.1. This can be achieved by adding the respective parameters in `zabbix_server.conf`: TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/server.crt TLSKeyFile=/home/zabbix/server.key TLSCipherCert13=TLS_AES_256_GCM_SHA384 TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384 TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256 TLSCipherPSK=kECDHEPSK+AES256:-SHA1 TLSCipherAll13=TLS_AES_256_GCM_SHA384 TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384 ::: noteimportant Although only certificate-related ciphersuites will be used, `TLSCipherPSK*` parameters are defined as well to avoid their default values which include less secure ciphers for wider interoperability. PSK ciphersuites cannot be completely disabled on server/proxy. ::: And in `zabbix_agentd.conf`: TLSConnect=cert TLSAccept=cert TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/agent.crt TLSKeyFile=/home/zabbix/agent.key TLSCipherCert13=TLS_AES_256_GCM_SHA384 TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384 #### Switching to raw values A dropdown on the upper right allows to switch from the simple graph to the *Values/500 latest values* listings. This can be useful for viewing the numeric values making up the graph. The values represented here are raw, i.e. no units or postprocessing of values is used. Value mapping, however, is applied. #### Switching to raw values A dropdown on the upper right allows to switch from the simple graph to the *Values/500 latest values* listings. This can be useful for viewing the numeric values making up the graph. The values represented here are raw, i.e. no units or postprocessing of values is used. Value mapping, however, is applied. ## SYNOPSIS **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD} ## SYNOPSIS **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD} ## SYNOPSIS **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD} ## SYNOPSIS **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD} ## SYNOPSIS **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD} ## SYNOPSIS **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD} # task.create # task.create # template.create # template.create # template.delete # template.delete # template.get # template.get # template.massadd # template.massadd # template.massremove # template.massremove # template.massupdate # template.massupdate # templatescreen.copy # templatescreen.copy # templatescreen.create # templatescreen.create # templatescreen.delete # templatescreen.delete # templatescreen.get # templatescreen.get # templatescreenitem.get # templatescreenitem.get # templatescreen.update # templatescreen.update #### Templates In a [template](/manual/config/templates/template) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| #### Templates In a [template](/manual/config/templates/template) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| # template.update # template.update ##### Testing cipher strings and allowing only PFS ciphersuites To see which ciphersuites have been selected you need to set 'DebugLevel=4' in the configuration file, or use the `-vv` option for zabbix\_sender. Some experimenting with `TLSCipher*` parameters might be necessary before you get the desired ciphersuites. It is inconvenient to restart Zabbix server, proxy or agent multiple times just to tweak `TLSCipher*` parameters. More convenient options are using zabbix\_sender or the `openssl` command. Let's show both. **1.** Using zabbix\_sender. Let's make a test configuration file, for example /home/zabbix/test.conf, with the syntax of a zabbix\_agentd.conf file: Hostname=nonexisting ServerActive=nonexisting TLSConnect=cert TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/agent.crt TLSKeyFile=/home/zabbix/agent.key TLSPSKIdentity=nonexisting TLSPSKFile=/home/zabbix/agent.psk You need valid CA and agent certificates and PSK for this example. Adjust certificate and PSK file paths and names for your environment. If you are not using certificates, but only PSK, you can make a simpler test file: Hostname=nonexisting ServerActive=nonexisting TLSConnect=psk TLSPSKIdentity=nonexisting TLSPSKFile=/home/zabbix/agentd.psk The selected ciphersuites can be seen by running zabbix\_sender (example compiled with OpenSSL 1.1.d): $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA zabbix_sender [41271]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA Here you see the ciphersuites selected by default. These default values are chosen to ensure interoperability with Zabbix agents running on systems with older OpenSSL versions (from 1.0.1). With newer systems you can choose to tighten security by allowing only a few ciphersuites, e.g. only ciphersuites with PFS (Perfect Forward Secrecy). Let's try to allow only ciphersuites with PFS using `TLSCipher*` parameters. ::: noteimportant The result will not be interoperable with systems using OpenSSL 1.0.1 and 1.0.2, if PSK is used. Certificate-based encryption should work. ::: Add two lines to the `test.conf` configuration file: TLSCipherCert=EECDH+aRSA+AES128 TLSCipherPSK=kECDHEPSK+AES128 and test again: $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA zabbix_sender [42892]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA The "certificate ciphersuites" and "PSK ciphersuites" lists have changed - they are shorter than before, only containing TLS 1.3 ciphersuites and TLS 1.2 ECDHE-\* ciphersuites as expected. **2.** TLSCipherAll and TLSCipherAll13 cannot be tested with zabbix\_sender; they do not affect "certificate and PSK ciphersuites" value shown in the example above. To tweak TLSCipherAll and TLSCipherAll13 you need to experiment with the agent, proxy or server. So, to allow only PFS ciphersuites you may need to add up to three parameters TLSCipherCert=EECDH+aRSA+AES128 TLSCipherPSK=kECDHEPSK+AES128 TLSCipherAll=EECDH+aRSA+AES128:kECDHEPSK+AES128 to zabbix\_agentd.conf, zabbix\_proxy.conf and zabbix\_server\_conf if each of them has a configured certificate and agent has also PSK. If your Zabbix environment uses only PSK-based encryption and no certificates, then only one: TLSCipherPSK=kECDHEPSK+AES128 Now that you understand how it works you can test the ciphersuite selection even outside of Zabbix, with the `openssl` command. Let's test all three `TLSCipher*` parameter values: $ openssl ciphers EECDH+aRSA+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA $ openssl ciphers kECDHEPSK+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA $ openssl ciphers EECDH+aRSA+AES128:kECDHEPSK+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA You may prefer `openssl ciphers` with option `-V` for a more verbose output: $ openssl ciphers -V EECDH+aRSA+AES128:kECDHEPSK+AES128 0x13,0x02 - TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD 0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any Au=any Enc=CHACHA20/POLY1305(256) Mac=AEAD 0x13,0x01 - TLS_AES_128_GCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESGCM(128) Mac=AEAD 0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(128) Mac=AEAD 0xC0,0x27 - ECDHE-RSA-AES128-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA256 0xC0,0x13 - ECDHE-RSA-AES128-SHA TLSv1 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA1 0xC0,0x37 - ECDHE-PSK-AES128-CBC-SHA256 TLSv1 Kx=ECDHEPSK Au=PSK Enc=AES(128) Mac=SHA256 0xC0,0x35 - ECDHE-PSK-AES128-CBC-SHA TLSv1 Kx=ECDHEPSK Au=PSK Enc=AES(128) Mac=SHA1 Similarly, you can test the priority strings for GnuTLS: $ gnutls-cli -l --priority=NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509 Cipher suites for NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509 TLS_ECDHE_RSA_AES_128_GCM_SHA256 0xc0, 0x2f TLS1.2 TLS_ECDHE_RSA_AES_128_CBC_SHA256 0xc0, 0x27 TLS1.2 Protocols: VERS-TLS1.2 Ciphers: AES-128-GCM, AES-128-CBC MACs: AEAD, SHA256 Key Exchange Algorithms: ECDHE-RSA Groups: GROUP-SECP256R1, GROUP-SECP384R1, GROUP-SECP521R1, GROUP-X25519, GROUP-X448, GROUP-FFDHE2048, GROUP-FFDHE3072, GROUP-FFDHE4096, GROUP-FFDHE6144, GROUP-FFDHE8192 PK-signatures: SIGN-RSA-SHA256, SIGN-RSA-PSS-SHA256, SIGN-RSA-PSS-RSAE-SHA256, SIGN-ECDSA-SHA256, SIGN-ECDSA-SECP256R1-SHA256, SIGN-EdDSA-Ed25519, SIGN-RSA-SHA384, SIGN-RSA-PSS-SHA384, SIGN-RSA-PSS-RSAE-SHA384, SIGN-ECDSA-SHA384, SIGN-ECDSA-SECP384R1-SHA384, SIGN-EdDSA-Ed448, SIGN-RSA-SHA512, SIGN-RSA-PSS-SHA512, SIGN-RSA-PSS-RSAE-SHA512, SIGN-ECDSA-SHA512, SIGN-ECDSA-SECP521R1-SHA512, SIGN-RSA-SHA1, SIGN-ECDSA-SHA1 ##### Testing cipher strings and allowing only PFS ciphersuites To see which ciphersuites have been selected you need to set 'DebugLevel=4' in the configuration file, or use the `-vv` option for zabbix\_sender. Some experimenting with `TLSCipher*` parameters might be necessary before you get the desired ciphersuites. It is inconvenient to restart Zabbix server, proxy or agent multiple times just to tweak `TLSCipher*` parameters. More convenient options are using zabbix\_sender or the `openssl` command. Let's show both. **1.** Using zabbix\_sender. Let's make a test configuration file, for example /home/zabbix/test.conf, with the syntax of a zabbix\_agentd.conf file: Hostname=nonexisting ServerActive=nonexisting TLSConnect=cert TLSCAFile=/home/zabbix/ca.crt TLSCertFile=/home/zabbix/agent.crt TLSKeyFile=/home/zabbix/agent.key TLSPSKIdentity=nonexisting TLSPSKFile=/home/zabbix/agent.psk You need valid CA and agent certificates and PSK for this example. Adjust certificate and PSK file paths and names for your environment. If you are not using certificates, but only PSK, you can make a simpler test file: Hostname=nonexisting ServerActive=nonexisting TLSConnect=psk TLSPSKIdentity=nonexisting TLSPSKFile=/home/zabbix/agentd.psk The selected ciphersuites can be seen by running zabbix\_sender (example compiled with OpenSSL 1.1.d): $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA zabbix_sender [41271]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA Here you see the ciphersuites selected by default. These default values are chosen to ensure interoperability with Zabbix agents running on systems with older OpenSSL versions (from 1.0.1). With newer systems you can choose to tighten security by allowing only a few ciphersuites, e.g. only ciphersuites with PFS (Perfect Forward Secrecy). Let's try to allow only ciphersuites with PFS using `TLSCipher*` parameters. ::: noteimportant The result will not be interoperable with systems using OpenSSL 1.0.1 and 1.0.2, if PSK is used. Certificate-based encryption should work. ::: Add two lines to the `test.conf` configuration file: TLSCipherCert=EECDH+aRSA+AES128 TLSCipherPSK=kECDHEPSK+AES128 and test again: $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA zabbix_sender [42892]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA The "certificate ciphersuites" and "PSK ciphersuites" lists have changed - they are shorter than before, only containing TLS 1.3 ciphersuites and TLS 1.2 ECDHE-\* ciphersuites as expected. **2.** TLSCipherAll and TLSCipherAll13 cannot be tested with zabbix\_sender; they do not affect "certificate and PSK ciphersuites" value shown in the example above. To tweak TLSCipherAll and TLSCipherAll13 you need to experiment with the agent, proxy or server. So, to allow only PFS ciphersuites you may need to add up to three parameters TLSCipherCert=EECDH+aRSA+AES128 TLSCipherPSK=kECDHEPSK+AES128 TLSCipherAll=EECDH+aRSA+AES128:kECDHEPSK+AES128 to zabbix\_agentd.conf, zabbix\_proxy.conf and zabbix\_server\_conf if each of them has a configured certificate and agent has also PSK. If your Zabbix environment uses only PSK-based encryption and no certificates, then only one: TLSCipherPSK=kECDHEPSK+AES128 Now that you understand how it works you can test the ciphersuite selection even outside of Zabbix, with the `openssl` command. Let's test all three `TLSCipher*` parameter values: $ openssl ciphers EECDH+aRSA+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA $ openssl ciphers kECDHEPSK+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA $ openssl ciphers EECDH+aRSA+AES128:kECDHEPSK+AES128 | sed 's/:/ /g' TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA You may prefer `openssl ciphers` with option `-V` for a more verbose output: $ openssl ciphers -V EECDH+aRSA+AES128:kECDHEPSK+AES128 0x13,0x02 - TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD 0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any Au=any Enc=CHACHA20/POLY1305(256) Mac=AEAD 0x13,0x01 - TLS_AES_128_GCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESGCM(128) Mac=AEAD 0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(128) Mac=AEAD 0xC0,0x27 - ECDHE-RSA-AES128-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA256 0xC0,0x13 - ECDHE-RSA-AES128-SHA TLSv1 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA1 0xC0,0x37 - ECDHE-PSK-AES128-CBC-SHA256 TLSv1 Kx=ECDHEPSK Au=PSK Enc=AES(128) Mac=SHA256 0xC0,0x35 - ECDHE-PSK-AES128-CBC-SHA TLSv1 Kx=ECDHEPSK Au=PSK Enc=AES(128) Mac=SHA1 Similarly, you can test the priority strings for GnuTLS: $ gnutls-cli -l --priority=NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509 Cipher suites for NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509 TLS_ECDHE_RSA_AES_128_GCM_SHA256 0xc0, 0x2f TLS1.2 TLS_ECDHE_RSA_AES_128_CBC_SHA256 0xc0, 0x27 TLS1.2 Protocols: VERS-TLS1.2 Ciphers: AES-128-GCM, AES-128-CBC MACs: AEAD, SHA256 Key Exchange Algorithms: ECDHE-RSA Groups: GROUP-SECP256R1, GROUP-SECP384R1, GROUP-SECP521R1, GROUP-X25519, GROUP-X448, GROUP-FFDHE2048, GROUP-FFDHE3072, GROUP-FFDHE4096, GROUP-FFDHE6144, GROUP-FFDHE8192 PK-signatures: SIGN-RSA-SHA256, SIGN-RSA-PSS-SHA256, SIGN-RSA-PSS-RSAE-SHA256, SIGN-ECDSA-SHA256, SIGN-ECDSA-SECP256R1-SHA256, SIGN-EdDSA-Ed25519, SIGN-RSA-SHA384, SIGN-RSA-PSS-SHA384, SIGN-RSA-PSS-RSAE-SHA384, SIGN-ECDSA-SHA384, SIGN-ECDSA-SECP384R1-SHA384, SIGN-EdDSA-Ed448, SIGN-RSA-SHA512, SIGN-RSA-PSS-SHA512, SIGN-RSA-PSS-RSAE-SHA512, SIGN-ECDSA-SHA512, SIGN-ECDSA-SECP521R1-SHA512, SIGN-RSA-SHA1, SIGN-ECDSA-SHA1 This is a blank page to display the parent page as a folder. This is a blank page to display the parent page as a folder. #### Timeout value in web scenario steps The timeout value in a web scenario step can no longer be '0'. Similarly, any user macros used in this field must not resolve to '0'. #### Timeout value in web scenario steps The timeout value in a web scenario step can no longer be '0'. Similarly, any user macros used in this field must not resolve to '0'. #### Time period selector The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter. Clicking on *Show* in the Graph column displays a bar graph where availability information is displayed in bar format each bar representing a past week of the current year. {width="600"} The green part of a bar stands for OK time and red for problem time. #### Time period selector The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter. Clicking on *Show* in the Graph column displays a bar graph where availability information is displayed in bar format each bar representing a past week of the current year. {width="600"} The green part of a bar stands for OK time and red for problem time. #### Time synchronization It is very important to have precise system time on server with Zabbix running. [ntpd](http://www.ntp.org/) is the most popular daemon that synchronizes the host's time with the time of other machines. It's strongly recommended to maintain synchronized system time on all systems Zabbix components are running on. #### Time synchronization It is very important to have precise system time on server with Zabbix running. [ntpd](http://www.ntp.org/) is the most popular daemon that synchronizes the host's time with the time of other machines. It's strongly recommended to maintain synchronized system time on all systems Zabbix components are running on. #### Tomcat template *Template App Apache Tomcat JMX* has been updated: - support for recent Tomcat versions has been added - the following macros have been defined: {$PROTOCOL\_HANDLER\_HTTP}, {$PROTOCOL\_HANDLER\_HTTPS}, {$PROTOCOL\_HANDLER\_AJP} #### Tomcat template *Template App Apache Tomcat JMX* has been updated: - support for recent Tomcat versions has been added - the following macros have been defined: {$PROTOCOL\_HANDLER\_HTTP}, {$PROTOCOL\_HANDLER\_HTTPS}, {$PROTOCOL\_HANDLER\_AJP} # trend.get # trend.get # trigger.adddependencies # trigger.adddependencies # trigger.create # trigger.create # trigger.delete # trigger.delete # trigger.deletedependencies # trigger.deletedependencies # trigger.get # trigger.get ##### Trigger lines Simple triggers are displayed as lines with black dashes over trigger severity color -- take note of the blue line on the graph and the trigger information displayed in the legend. Up to 3 trigger lines can be displayed on the graph; if there are more triggers then the triggers with lower severity are prioritized. Triggers are always displayed in simple graphs, whereas displaying them in [custom graphs](custom#configuring_custom_graphs) is a user preference.  ##### Trigger lines Simple triggers are displayed as lines with black dashes over trigger severity color -- take note of the blue line on the graph and the trigger information displayed in the legend. Up to 3 trigger lines can be displayed on the graph; if there are more triggers then the triggers with lower severity are prioritized. Triggers are always displayed in simple graphs, whereas displaying them in [custom graphs](custom#configuring_custom_graphs) is a user preference.  # triggerprototype.create # triggerprototype.create # triggerprototype.delete # triggerprototype.delete # triggerprototype.get # triggerprototype.get # triggerprototype.update # triggerprototype.update #### Triggers In a [trigger](/manual/config/triggers/trigger) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name|<|yes| |Operational data|<|yes| |Expression (only in constants and function parameters; secret macros are not supported)|<|yes| |Description|<|yes| |URL|<|yes| |Tag for matching|<|yes| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| #### Triggers In a [trigger](/manual/config/triggers/trigger) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name|<|yes| |Operational data|<|yes| |Expression (only in constants and function parameters; secret macros are not supported).|<|yes| |Description|<|yes| |URL|<|yes| |Tag for matching|<|yes| |//Tags //|<|<| |<|Tag names|yes| |^|Tag values|yes| # trigger.update # trigger.update #### Troubleshooting and removing agent This section lists some useful commands that can be used for troubleshooting and removing Zabbix agent installation. See if Zabbix agent is running: ps aux | grep zabbix_agentd See if Zabbix agent has been installed from packages: $ pkgutil --pkgs | grep zabbix com.zabbix.pkg.ZabbixAgent See the files that were installed from the installer package (note that the initial `/` is not displayed in this view): $ pkgutil --only-files --files com.zabbix.pkg.ZabbixAgent Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist usr/local/bin/zabbix_get usr/local/bin/zabbix_sender usr/local/etc/zabbix/zabbix_agentd/userparameter_examples.conf.NEW usr/local/etc/zabbix/zabbix_agentd/userparameter_mysql.conf.NEW usr/local/etc/zabbix/zabbix_agentd.conf.NEW usr/local/sbin/zabbix_agentd Stop Zabbix agent if it was launched with `launchctl`: sudo launchctl unload /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist Remove files (including configuration and logs) that were installed with installer package: sudo rm -f /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist sudo rm -f /usr/local/sbin/zabbix_agentd sudo rm -f /usr/local/bin/zabbix_get sudo rm -f /usr/local/bin/zabbix_sender sudo rm -rf /usr/local/etc/zabbix sudo rm -rf /var/logs/zabbix Forget that Zabbix agent has been installed: sudo pkgutil --forget com.zabbix.pkg.ZabbixAgent #### Troubleshooting and removing agent This section lists some useful commands that can be used for troubleshooting and removing Zabbix agent installation. See if Zabbix agent is running: ps aux | grep zabbix_agentd See if Zabbix agent has been installed from packages: $ pkgutil --pkgs | grep zabbix com.zabbix.pkg.ZabbixAgent See the files that were installed from the installer package (note that the initial `/` is not displayed in this view): $ pkgutil --only-files --files com.zabbix.pkg.ZabbixAgent Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist usr/local/bin/zabbix_get usr/local/bin/zabbix_sender usr/local/etc/zabbix/zabbix_agentd/userparameter_examples.conf.NEW usr/local/etc/zabbix/zabbix_agentd/userparameter_mysql.conf.NEW usr/local/etc/zabbix/zabbix_agentd.conf.NEW usr/local/sbin/zabbix_agentd Stop Zabbix agent if it was launched with `launchctl`: sudo launchctl unload /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist Remove files (including configuration and logs) that were installed with installer package: sudo rm -f /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist sudo rm -f /usr/local/sbin/zabbix_agentd sudo rm -f /usr/local/bin/zabbix_get sudo rm -f /usr/local/bin/zabbix_sender sudo rm -rf /usr/local/etc/zabbix sudo rm -rf /var/logs/zabbix Forget that Zabbix agent has been installed: sudo pkgutil --forget com.zabbix.pkg.ZabbixAgent #### Unavailable host After the UnreachablePeriod ends and the host has not reappeared, the host is treated as unavailable. In the server log it is indicated by messages like these: temporarily disabling Zabbix agent checks on host "New host": host unavailable and in the [frontend](/manual/web_interface/frontend_sections/configuration/hosts) the host availability icon for the respective interface goes from green (or gray) to red (note that on mouseover a tooltip with the error description is displayed):  The **UnavailableDelay** parameter defines how often a host is checked during host unavailability. By default it is 60 seconds (so in this case "temporarily disabling", from the log message above, will mean disabling checks for one minute). When the connection to the host is restored, the monitoring returns to normal automatically, too: enabling Zabbix agent checks on host "New host": host became available #### Unavailable host After the UnreachablePeriod ends and the host has not reappeared, the host is treated as unavailable. In the server log it is indicated by messages like these: temporarily disabling Zabbix agent checks on host "New host": host unavailable and in the [frontend](/manual/web_interface/frontend_sections/configuration/hosts) the host availability icon for the respective interface goes from green (or gray) to red (note that on mouseover a tooltip with the error description is displayed):  The **UnavailableDelay** parameter defines how often a host is checked during host unavailability. By default it is 60 seconds (so in this case "temporarily disabling", from the log message above, will mean disabling checks for one minute). When the connection to the host is restored, the monitoring returns to normal automatically, too: enabling Zabbix agent checks on host "New host": host became available #### Unsupported items An item can become unsupported if its value cannot be retrieved for some reason. Such items are still rechecked at a fixed interval, configurable in [Administration section](/manual/web_interface/frontend_sections/administration/general?&#other_parameters). Unsupported items are reported as having a NOT SUPPORTED state. #### Unsupported items An item can become unsupported if its value cannot be retrieved for some reason. Such items are still rechecked at a fixed interval, configurable in [Administration section](/manual/web_interface/frontend_sections/administration/general?&#other_parameters). Unsupported items are reported as having a NOT SUPPORTED state. #### Use of relative URLs Relative paths are now allowed in a URL field. #### Use of relative URLs Relative paths are now allowed in a URL field. # user.checkAuthentication # user.checkAuthentication #### User-configured ciphersuites The built-in ciphersuite selection criteria can be overridden with user-configured ciphersuites (since Zabbix 4.0.19). ::: noteimportant User-configured ciphersuites is a feature intended for advanced users who understand TLS ciphersuites, their security and consequences of mistakes, and who are comfortable with TLS troubleshooting. ::: The built-in ciphersuite selection criteria can be overridden using the following parameters: |Override scope|Parameter|Value|Description| |--------------|---------|-----|-----------| |Ciphersuite selection for certificates|TLSCipherCert13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Certificate-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherCert|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Certificate-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Ciphersuite selection for PSK|TLSCipherPSK13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|PSK-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherPSK|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|PSK-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Combined ciphersuite list for certificate and PSK|TLSCipherAll13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherAll|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| To override the ciphersuite selection in [zabbix\_get](/manpages/zabbix_get) and [zabbix\_sender](/manpages/zabbix_sender) utilities - use the command-line parameters: - `--tls-cipher13` - `--tls-cipher` The new parameters are optional. If a parameter is not specified, the internal default value is used. If a parameter is defined it cannot be empty. If the setting of a TLSCipher\* value in the crypto library fails then the server, proxy or agent will not start and an error is logged. It is important to understand when each parameter is applicable. #### User-configured ciphersuites The built-in ciphersuite selection criteria can be overridden with user-configured ciphersuites (since Zabbix 4.0.19). ::: noteimportant User-configured ciphersuites is a feature intended for advanced users who understand TLS ciphersuites, their security and consequences of mistakes, and who are comfortable with TLS troubleshooting. ::: The built-in ciphersuite selection criteria can be overridden using the following parameters: |Override scope|Parameter|Value|Description| |--------------|---------|-----|-----------| |Ciphersuite selection for certificates|TLSCipherCert13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Certificate-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherCert|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Certificate-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Ciphersuite selection for PSK|TLSCipherPSK13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|PSK-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherPSK|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|PSK-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Combined ciphersuite list for certificate and PSK|TLSCipherAll13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherAll|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| To override the ciphersuite selection in [zabbix\_get](/manpages/zabbix_get) and [zabbix\_sender](/manpages/zabbix_sender) utilities - use the command-line parameters: - `--tls-cipher13` - `--tls-cipher` The new parameters are optional. If a parameter is not specified, the internal default value is used. If a parameter is defined it cannot be empty. If the setting of a TLSCipher\* value in the crypto library fails then the server, proxy or agent will not start and an error is logged. It is important to understand when each parameter is applicable. # user.create # user.create # user.delete # user.delete # user.get # user.get # usergroup.create # usergroup.create # usergroup.delete # usergroup.delete # usergroup.get # usergroup.get # usergroup.update # usergroup.update # user.login # user.login # user.logout # user.logout # usermacro.create # usermacro.create # usermacro.createglobal # usermacro.createglobal # usermacro.delete # usermacro.delete # usermacro.deleteglobal # usermacro.deleteglobal # usermacro.get # usermacro.get # usermacro.update # usermacro.update # usermacro.updateglobal # usermacro.updateglobal # user.update # user.update #### Using filter Filter can help narrow down the number of hosts and/or triggers displayed. The filter is located below the *Availability report* bar. It can be opened and collapsed by clicking on the *Filter* tab on the left. #### Using filter Filter can help narrow down the number of hosts and/or triggers displayed. The filter is located below the *Availability report* bar. It can be opened and collapsed by clicking on the *Filter* tab on the left. #### Using Zabbix frontend behind proxy If Zabbix frontend runs behind proxy server, the cookie path in the proxy configuration file needs to be rewritten in order to match the reverse-proxied path. See examples below. If the cookie path is not rewritten, users may experience authorization issues, when trying to login to Zabbix frontend. #### Using Zabbix frontend behind proxy If Zabbix frontend runs behind proxy server, the cookie path in the proxy configuration file needs to be rewritten in order to match the reverse-proxied path. See examples below. If the cookie path is not rewritten, users may experience authorization issues, when trying to login to Zabbix frontend. #### valuemap Changes:\ [ZBX-3783](https://support.zabbix.com/browse/ZBX-3783) `valuemap.get`: added strict validation of input parameters\ #### valuemap Changes:\ [ZBX-3783](https://support.zabbix.com/browse/ZBX-3783) `valuemap.get`: added strict validation of input parameters\ # valuemap.create # valuemap.create # valuemap.delete # valuemap.delete # valuemap.get # valuemap.get # valuemap.update # valuemap.update #### Viewing host group elements This option is available if "Host group elements" show option is chosen. When selecting "Host group elements" as the *show* option, you will at first see only one icon for the host group. However, when you save the map and then go to the map view, you will see that the map includes all the elements (hosts) of the certain host group: |Map editing view|Map view| |----------------|--------| |*{width="450"}*|{width="450"}| Notice how the {HOST.NAME} macro is used. In map editing the macro name in unresolved, while in map view all the unique names of the hosts are displayed. #### Viewing host group elements This option is available if "Host group elements" show option is chosen. When selecting "Host group elements" as the *show* option, you will at first see only one icon for the host group. However, when you save the map and then go to the map view, you will see that the map includes all the elements (hosts) of the certain host group: |Map editing view|Map view| |----------------|--------| |*{width="450"}*|{width="450"}| Notice how the {HOST.NAME} macro is used. In map editing the macro name in unresolved, while in map view all the unique names of the hosts are displayed. #### VMware datacenter discovery A new `vmware.dc.discovery[url]` [item](/manual/config/items/itemtypes/simple_checks/vmware_keys) returns a JSON containing {\#DATACENTER} and {\#DATACENTERID} properties. #### VMware datacenter discovery A new `vmware.dc.discovery[url]` [item](/manual/config/items/itemtypes/simple_checks/vmware_keys) returns a JSON containing {\#DATACENTER} and {\#DATACENTERID} properties. #### VMware datastore discovery VMware datastore discovery has been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of one time per each hypervisor. Within this development the following new items have been added: - vmware.datastore.discovery\[<url>\] - vmware.datastore.hv.list\[<url>,<datastore>\] - vmware.datastore.read\[<url>,<datastore>,<mode>\] - vmware.datastore.write\[<url>,<datastore>,<mode>\] - vmware.datastore.size\[<url>,<datastore>,<mode>\] - vmware.hv.datastore.list\[<url>,<uuid>\] For more information on the added items, see: [VMware monitoring item keys](/manual/config/items/itemtypes/simple_checks/vmware_keys) #### VMware datastore discovery VMware datastore discovery has been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of one time per each hypervisor. Within this development the following new items have been added: - vmware.datastore.discovery\[<url>\] - vmware.datastore.hv.list\[<url>,<datastore>\] - vmware.datastore.read\[<url>,<datastore>,<mode>\] - vmware.datastore.write\[<url>,<datastore>,<mode>\] - vmware.datastore.size\[<url>,<datastore>,<mode>\] - vmware.hv.datastore.list\[<url>,<uuid>\] For more information on the added items, see: [VMware monitoring item keys](/manual/config/items/itemtypes/simple_checks/vmware_keys) #### VMware template *Template VM VMware* has been updated: - the key of the "Event log" item has been changed to `vmware.eventlog[{$URL},skip]` - now skipping old data #### VMware template *Template VM VMware* has been updated: - the key of the "Event log" item has been changed to `vmware.eventlog[{$URL},skip]` - now skipping old data #### VMware template *Template VM VMware* has been updated: - the type of information for the "VMware: Free space on datastore (percentage)" item has been corrected and is now set to Numeric (float). - The following template macros now have more specific names: - {$URL} renamed to {$VMWARE.URL} - {$USERNAME} renamed to {$VMWARE.USERNAME} - {$PASSWORD} renamed to {$VMWARE.PASSWORD} #### VMware template *Template VM VMware* has been updated: - the type of information for the "VMware: Free space on datastore (percentage)" item has been corrected and is now set to Numeric (float). - The following template macros now have more specific names: - {$URL} renamed to {$VMWARE.URL} - {$USERNAME} renamed to {$VMWARE.USERNAME} - {$PASSWORD} renamed to {$VMWARE.PASSWORD} #### Web monitoring items Removed support of `{HOST.*}` macro in name property of web scenario and web scenario step. #### Web monitoring items Removed support of `{HOST.*}` macro in name property of web scenario and web scenario step. #### Web scenario fields The maximum field size has been increased from 255 to 2000 characters in the web scenario variables and web scenario step variables and post fields. #### Web scenario fields The maximum field size has been increased from 255 to 2000 characters in the web scenario variables and web scenario step variables and post fields. #### Web scenario In a [web scenario](/manual/web_monitoring) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name|<|yes| |Update interval|<|no| |Agent|<|yes| |HTTP proxy|<|yes| |Variables (values only)|<|yes| |Headers (names and values)|<|yes| |//Steps //|<|<| |<|Name|yes| |^|URL|yes| |^|Variables (values only)|yes| |^|Headers (names and values)|yes| |^|Timeout|no| |^|Required string|yes| |^|Required status codes|no| |//Authentication //|<|<| |<|User|yes| |^|Password|yes| |^|SSL certificate|yes| |^|SSL key file|yes| |^|SSL key password|yes| #### Web scenario In a [web scenario](/manual/web_monitoring) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |Name|<|yes| |Update interval|<|no| |Agent|<|yes| |HTTP proxy|<|yes| |Variables (values only)|<|yes| |Headers (names and values)|<|yes| |//Steps //|<|<| |<|Name|yes| |^|URL|yes| |^|Variables (values only)|yes| |^|Headers (names and values)|yes| |^|Timeout|no| |^|Required string|yes| |^|Required status codes|no| |//Authentication //|<|<| |<|User|yes| |^|Password|yes| |^|SSL certificate|yes| |^|SSL key file|yes| |^|SSL key password|yes| #### Whitespace Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`. #### Whitespace Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`. ##### Windows agent compilation revision Generating a Windows file properties revision number has been added for agent compilation on MS Windows. It follows a `{b}{t}{nn}` format where: - `{b}` - source (1 - feature or release, 2 - tag) - `{t}` - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) - `{nn}` - sequence number for the 'type' For example: |Tag|Branch|Version|Result| |---|------|-------|------| |4.0.8|<|Zabbix 4.0.8|4.0.8.2400| |<|release/4.0|Zabbix 4.0.8rc3|4.0.8.1303| |<|feature/ZBX-16074|Zabbix 4.0.8rc1|4.0.8.1301| ##### Windows agent compilation revision Generating a Windows file properties revision number has been added for agent compilation on MS Windows. It follows a `{b}{t}{nn}` format where: - `{b}` - source (1 - feature or release, 2 - tag) - `{t}` - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) - `{nn}` - sequence number for the 'type' For example: |Tag|Branch|Version|Result| |---|------|-------|------| |4.0.8|<|Zabbix 4.0.8|4.0.8.2400| |<|release/4.0|Zabbix 4.0.8rc3|4.0.8.1303| |<|feature/ZBX-16074|Zabbix 4.0.8rc1|4.0.8.1301| #### Working with English perfcounters on Windows It is now possible to work with exclusively English names of Windows performance counters, regardless of the locale, using the new items/parameters: - `perf_counter_en` Windows agent [item](/manual/config/items/itemtypes/zabbix_agent/win_keys) - `PerfCounterEn` Windows agent [parameter](/manual/appendix/config/zabbix_agentd_win) Note that these items will only work on **Windows Server 2008/Vista** and above. #### Working with English perfcounters on Windows It is now possible to work with exclusively English names of Windows performance counters, regardless of the locale, using the new items/parameters: - `perf_counter_en` Windows agent [item](/manual/config/items/itemtypes/zabbix_agent/win_keys) - `PerfCounterEn` Windows agent [parameter](/manual/appendix/config/zabbix_agentd_win) Note that these items will only work on **Windows Server 2008/Vista** and above. #### Zabbix agent checks on Windows Non-existing DNS entries in a `Server` parameter of Zabbix agent configuration file (zabbix\_agentd.conf) may increase Zabbix agent response time on Windows. This happens because Windows DNS caching daemon doesn't cache negative responses for IPv4 addresses. However, for IPv6 addresses negative responses are cached, so a possible workaround to this is disabling IPv4 on the host. #### Zabbix agent checks on Windows Non-existing DNS entries in a `Server` parameter of Zabbix agent configuration file (zabbix\_agentd.conf) may increase Zabbix agent response time on Windows. This happens because Windows DNS caching daemon doesn't cache negative responses for IPv4 addresses. However, for IPv6 addresses negative responses are cached, so a possible workaround to this is disabling IPv4 on the host. # zabbix\_agentd Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} # zabbix\_agentd Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} #### Zabbix frontend sets own cookie path If Zabbix frontend runs behind proxy, cookie path set by Zabbix now needs to be specified in the proxy configuration. See [using Zabbix frontend behind proxy](/manual/appendix/other_issues#using Zabbix frontend behind proxy) for details. #### Zabbix frontend sets own cookie path If Zabbix frontend runs behind proxy, cookie path set by Zabbix now needs to be specified in the proxy configuration. See [using Zabbix frontend behind proxy](/manual/appendix/other_issues#using Zabbix frontend behind proxy) for details. # Zabbix manpages These are Zabbix manpages for Zabbix processes. # Zabbix manpages These are Zabbix manpages for Zabbix processes. ##### Zabbix packages from OS repositories Often, OS distributions (in particular, Debian-based distributions) provide their own Zabbix packages.\ Note, that these packages are not supported by Zabbix, they are typically out of date and lack the latest features and bug fixes. Only the packages from [repo.zabbix.com](https://repo.zabbix.com/) are officially supported. If you are upgrading from packages provided by OS distributions (or had them installed at some point), follow this procedure to switch to official Zabbix packages: 1. Always uninstall the old packages first. 2. Check for residual files that may have been left after deinstallation. 3. Install official packages following [installation instructions](https://www.zabbix.com/download?zabbix=4.0) provided by Zabbix. Never do a direct update, as this may result in a broken installation. ##### Zabbix packages from OS repositories Often, OS distributions (in particular, Debian-based distributions) provide their own Zabbix packages.\ Note, that these packages are not supported by Zabbix, they are typically out of date and lack the latest features and bug fixes. Only the packages from [repo.zabbix.com](https://repo.zabbix.com/) are officially supported. If you are upgrading from packages provided by OS distributions (or had them installed at some point), follow this procedure to switch to official Zabbix packages: 1. Always uninstall the old packages first. 2. Check for residual files that may have been left after deinstallation. 3. Install official packages following [installation instructions](https://www.zabbix.com/download?zabbix=4.0) provided by Zabbix. Never do a direct update, as this may result in a broken installation. # zabbix\_proxy Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} # zabbix\_proxy Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} # zabbix\_server Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} # zabbix\_server Section: Maintenance Commands (8)\ Updated: 2018-10-11\ [Index](#index) [Return to Main Contents](/documentation/4.0/manpages) ------------------------------------------------------------------------ [ ]{#lbAB} ### ### # 10 Cookies used by Zabbix # 10 Cookies utilisés par Zabbix # 10 Discovery using WMI queries # 10 Découverte à l'aide de requêtes WMI # 10 Graph prototype # 10 Prototype de graphique # 10 Inclusion # 10 Inclusion # 10 Notes on selecting processes in proc.mem and proc.num items # 10 Remarques sur la sélection des processus dans les éléments proc.mem et proc.num # 10 Notifications upon events # 10 Notifications sur les événements # 10 Queue # 10 File d'attente # 10 Telnet checks # 10 Vérifications Telnet # 10 Upgrade notes for 6.0.0 These notes are for upgrading from Zabbix 5.4.x to Zabbix 6.0.0. All notes are grouped into: - `Critical` - the most critical information related to the upgrade process and the changes in Zabbix functionality - `Informational` - all remaining information describing the changes in Zabbix functionality It is possible to upgrade to Zabbix 6.0.0 from versions before Zabbix 5.4.0. See the [upgrade procedure](/manual/installation/upgrade) section for all relevant information about upgrading from previous Zabbix versions. # 10 Notes de mise à jour pour 6.0.0 Ces notes concernent la mise à niveau de Zabbix 5.4.x vers Zabbix 6.0.0. Toutes les notes sont regroupées en : - `Critique` - les informations les plus critiques liées au processus de mise à niveau et aux modifications des fonctionnalités de Zabbix - `Informel` - toutes les informations restantes décrivant les modifications apportées aux fonctionnalités de Zabbix Il est possible de mettre à niveau vers Zabbix 6.0.0 à partir de versions antérieures à Zabbix 5.4.0. Consultez la section [procédure de mise à niveau](/manual/installation/upgrade) pour toutes les informations pertinentes sur la mise à niveau depuis les versions précédentes de Zabbix. # 10. Virtual machine monitoring # 10. Supervision des machines virtuelles # 10 What's new in Zabbix 6.0.5 # 10 Quoi de neuf dans Zabbix 6.0.5 # 10 Zabbix agent on Microsoft Windows # 10 Agent Zabbix pour Microsoft Windows # 11 Discovery using ODBC SQL queries # 11 Découverte à l'aide de requêtes SQL ODBC # 11 External checks # 11 Vérifications externes # 11 Host availability # 11 Disponibilité de l'hôte # 11 Implementation details of net.tcp.service and net.udp.service checks Implementation of net.tcp.service and net.udp.service checks is detailed on this page for various services specified in the service parameter. # 11 Détails d'implémentation des vérifications net.tcp.service et net.udp.service La mise en œuvre des vérifications net.tcp.service et net.udp.service est détaillée sur cette page pour les différents services spécifiés dans le paramètre service. # 11 Macros # 11 Macros # 11. Maintenance # 11. Maintenance # 11 Time zones # 11 Fuseaux horaires # 11 Upgrade notes for 6.0.1 # 11 Notes de mise à jour pour 6.0.1 # 11 Value cache # 11 Cache de valeur # 11 What's new in Zabbix 6.0.6 # 11 Quoi de neuf dans Zabbix 6.0.6 # 12 Discovery using Prometheus data # 12 Découverte à l'aide des données Prometheus # 12 Execute now # 12 Exécuter maintenant # 12 Item value # 12 Valeur d'élément # 12. Regular expressions # 12. Expressions régulières # 12 Trapper items # 12 Elément trapper # 12 Unreachable/unavailable host interface settings # 12 Paramètres de l'interface hôte inaccessibles/indisponibles # 12 Upgrade notes for 6.0.2 This minor version doesn't have any upgrade notes. # 12 Notes de mise à jour pour 6.0.2 Cette version mineure n'a pas de notes de mise à jour. # 12 Users and user groups # 12 Utilisateurs et groupes d'utilisateurs # 12 What's new in Zabbix 6.0.7 # 12 Quoi de neuf dans Zabbix 6.0.7 # 13 Discovery of block devices In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover block devices and their type. # 13 Découverte des périphériques de bloc De la même manière que les [systèmes de fichiers](/manual/discovery/low_level_discovery#configuring_low-level_discovery) sont découverts, il est également possible de découvrir les périphériques de bloc et leur type. # 13 JMX monitoring # 13 Surveillance JMX # 13 Map # 13 Carte # 13 Map # 13 Carte # 13. Problem acknowledgment # 13. Acquittement des problèmes # 13 Remote monitoring of Zabbix stats # 13 Surveillance à distance des statistiques Zabbix # 13 Restricting agent checks # 13 Restreindre les vérifications des agents # 13 Storage of secrets # 13 Stockage des secrets # 13 Upgrade notes for 6.0.3 This minor version doesn't have any upgrade notes. # 13 Notes de mise à jour pour 6.0.3 Cette version mineure n'a pas de notes de mise à jour. # 13 What's new in Zabbix 6.0.8 # 13 Quoi de neuf dans Zabbix 6.0.8 # 14. Configuration export/import # 14. Exportation/importation de la configuration # 14 Configuring Kerberos with Zabbix # 14 Configurer Kerberos avec Zabbix # 14 Discovery of host interfaces in Zabbix # 14 Découverte des interfaces d'hôtes dans Zabbix # 14 Map navigation tree # 14 Arborescence de navigation de la carte # 14 ODBC monitoring # 14 Surveillance ODBC # 14 Plugins # 14 Plugins # 14 Scheduled reports # 14 Rapports planifiés # 14 Service monitoring upgrade # 14 Mise à niveau de la surveillance des services # 14 Upgrade notes for 6.0.4 This minor version doesn't have any upgrade notes. # 14 Notes de mise à jour pour 6.0.4 Cette version mineure n'a pas de notes de mise à jour. # 14 What's new in Zabbix 6.0.9 # 14 Quoi de neuf dans Zabbix 6.0.9 # 15 Dependent items # 15 Éléments dépendants # 15. Discovery Please use the sidebar to access content in the Discovery section. # 15. Découverte Veuillez utiliser la barre latérale pour accéder au contenu de la section Introduction. # 15 modbus.get parameters # 15 Paramètres de modbus.get # 15 Other issues # 15 Autres problèmes # 15 Plain text # 15 Texte brut # 15 Plain text # 15 Texte brut # 15 What's new in Zabbix 6.0.10 # 15 Quoi de neuf dans 6.0.10 # 16 Creating custom performance counter names for VMware # 16 Création de noms de compteurs de performances personnalisés pour VMware # 16. Distributed monitoring # 16. Supervision distribuée # 16 HTTP agent # 16 Agent HTTP # 16 Issues with SELinux Socket-based inter-process communication has been added since Zabbix 3.4. On systems where SELinux is enabled it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the `SocketDir` directory. Currently socket files are used by server (alerter, preprocessing, IPMI) and proxy (IPMI). Socket files are persistent, meaning are present while the process is running. # 16 Problèmes avec SELinux La communication inter-processus basée sur les sockets a été ajoutée depuis Zabbix 3.4. Sur les systèmes où SELinux est activé, il peut être nécessaire d'ajouter des règles SELinux pour permettre à Zabbix de créer/utiliser des sockets de domaine UNIX dans le répertoire "SocketDir". Actuellement, les fichiers de socket sont utilisés par le serveur (alerteur, prétraitement, IPMI) et le proxy (IPMI). Les fichiers de socket sont persistants, ce qui signifie qu'ils sont présents pendant l'exécution du processus. # 16 Problem hosts # 16 Hôtes problématiques # 16 Problem hosts # 16 Hôtes problématiques # 16 Upgrade notes for 6.0.6 # 16 Notes de mise à jour pour 6.0.6 # 16 What's new in Zabbix 6.0.11 # 16 Quoi de neuf dans Zabbix 6.0.11 # 17. Encryption # 17. Chiffrement # 17 Problems # 17 Problèmes # 17 Problems # 17 Problèmes # 17 Prometheus checks # 17 Vérifications Prometheus # 17 Upgrade notes for 6.0.7 # 17 Notes de mise à jour pour 6.0.7 # 17 What's new in Zabbix 6.0.12 # 17 Quoi de neuf dans Zabbix 6.0.12 # 18 Problems by severity # 18 Problèmes par gravité # 18 Problems by severity # 18 Problèmes par sévérité # 18 Script items # 18 Éléments de script # 18 Upgrade notes for 6.0.8 This minor version doesn't have any upgrade notes. # 18 Notes de mise à jour pour 6.0.8 Cette version mineure n'a pas de notes de mise à jour. # 18. Web interface # 18. Interface Web # 18 What's new in Zabbix 6.0.13 # 18 Quoi de neuf dans Zabbix 6.0.13 # 19. API # 19. API # 19 SLA report # 19 Rapport SLA # 19 Upgrade notes for 6.0.9 This minor version doesn't have any upgrade notes. # 19 Notes de mise à jour pour 6.0.9 Cette version mineure n'a pas de notes de mise à jour. # 19 What's new in Zabbix 6.0.14 # 19 Quoi de neuf dans Zabbix 6.0.14 # 1 Action log # 1 Journal des actions # 1 Building loadable plugins # 1 Construire des plugins chargeables # 1 Ceph plugin # 1 Plugin Ceph # 1 Conditions # 1 Conditions # 1 Configuring a host # 1 Configuration d'un hôte # 1 Configuring a network discovery rule # 1 Configuration d'une règle de découverte réseau # 1 Configuring a network map # 1 Configuration d'une carte réseau # 1 Configuring a template # 1 Configuration d'un modèle # 1 Configuring a trigger # 1 Configuration d'un déclencheur # 1 Configuring a user # 1 Configuration d'un utilisateur # 1 Connection type or permission problems # 1 Problèmes de type de connexion ou d'autorisation # 1 Creating an item # 1 Création d'un élément # 1 Dashboard # 1 Tableau de bord # 1 Database creation # 1 Création de la base de données # 1 Discovery of mounted filesystems # 1 Découverte des systèmes de fichiers montés # 1 Dynamic indexes # 1 Index dynamiques # 1 E-mail # 1 E-mail # 1 Extending Zabbix agents This tutorial provides step-by-step instructions on how to extend the functionality of Zabbix agent with the use of a [user parameter](/manual/config/items/userparameters). # 1 Extension des agents Zabbix Ce tutoriel fournit des instructions pas à pas sur l'extension des fonctionnalités de l'agent Zabbix à l'aide d'un [paramètre utilisateur](/manual/config/items/userparameters). # 1 Foreach functions # 1 Fonctions Foreach # 1 General # 1 Général # 1 Getting Zabbix # 1 Obtenir Zabbix # 1 Global notifications # 1 Notifications globales # 1 Graphs # 1 Graphiques # 1 Graphs # 1 Graphiques # 1 High availability # 1 Cluster haute disponibilité # 1 Host groups # 1 Groupes d'hôtes # 1 Hosts and host groups # 1 Hôtes et groupes d’hôtes # 1. Introduction Please use the sidebar to access content in the Introduction section. # 1. Introduction Veuillez utiliser la barre latérale pour accéder au contenu de la section Introduction. # 1 Item key format Item key format, including key parameters, must follow syntax rules. The following illustrations depict the supported syntax. Allowed elements and characters at each point can be determined by following the arrows - if some block can be reached through the line, it is allowed, if not - it is not allowed. {width="600"} To construct a valid item key, one starts with specifying the key name, then there's a choice to either have parameters or not - as depicted by the two lines that could be followed. # 1 Format de clé d’élément Le format de la clé d’élément, y compris les paramètres clés, doit suivre les règles de syntaxe. Les illustrations suivantes illustrent la syntaxe prise en charge. Les éléments et caractères autorisés à chaque point peuvent être déterminés en suivant les flèches - si un bloc peut être atteint par la ligne, il est autorisé, sinon - il n'est pas autorisé. {width="600"} Pour construire une clé d'élément valide, on commence par spécifier le nom de la clé, puis on a le choix d'avoir des paramètres ou non - comme l'illustrent les deux lignes qui peuvent être suivies. # 1 Item prototypes # 1 Prototypes d'élément # 1 Item prototypes # 1 Prototypes d'élément # 1 Items # 1 Eléments # 1 Items # 1 Eléments # 1 Login and configuring user # 1 Connexion et configuration de l'utilisateur # 1 Macro functions # 1 Fonctions de macro # 1 Media types # 1 Types de Media # 1 Menu # 1 Menu # 1 Monitoring # 1 Surveillance # 1 MySQL encryption configuration [comment]: # (tags: ssl) # 1 Configuration du chiffrement MySQL # 1 Network discovery # 1 Découverte du réseau # 1 Overview # 1 Aperçu # 1 Proxies # 1 Proxys # 1 Recommended UnixODBC settings for MySQL # 1 Paramètres UnixODBC recommandés pour MySQL # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux # 1 Red Hat Enterprise Linux/CentOS # 1 Red Hat Enterprise Linux/CentOS # 1 Sending message # 1 Envoi d'un message # 1 Server # 1 Serveur # 1 Server-proxy data exchange protocol # 1 Protocole d'échange de données serveur-proxy # 1 Services # 1 Services # 1 Service tree Service tree is configured in the *Services->Services* menu section. In the upper right corner, switch from [View](/manual/web_interface/frontend_sections/services/service) to the Edit mode. {width=600} To [configure](#service_configuration) a new service, click on the *Create service* button in the top right-hand corner. To quickly add a child service, you can alternatively press a plus icon next to the parent service. This will open the same service configuration form, but the Parent services parameter will be pre-filled. # 1 Arborescence des services L'arborescence des services est configurée dans la section de menu *Services->Services*. Dans le coin supérieur droit, passez de [Affichage](/manual/web_interface/frontend_sections/services/service) au mode Édition. {width=600} Pour [configurer](#service_configuration) un nouveau service, cliquez sur le bouton *Créer un service* en haut à droite. Pour ajouter rapidement un service enfant, vous pouvez également appuyer sur une icône plus à côté du service parent. Cela ouvrira le même formulaire de configuration de service, mais le paramètre Services parents sera pré-rempli. # 1 Simple graphs # 1 Graphiques simples ##### 1 Stop agent Stop Zabbix agent. ##### 1 Arrêt de l’agent Zabbix Arrêtez l’agent Zabbix. ##### 1 Stop proxy Stop Zabbix proxy. ##### 1 Arrêt du proxy Zabbix Arrêtez le proxy Zabbix. ##### 1 Stop server Stop Zabbix server to make sure that no new data is inserted into database. ##### 1 Arrêt du serveur Zabbix Arrêter le serveur Zabbix pour être sûr qu’aucune nouvelle donnée ne soit insérée en base de données. ##### 1 Stop Zabbix processes Stop Zabbix server to make sure that no new data is inserted into database. # systemctl stop zabbix-server If upgrading the proxy, stop proxy too. # systemctl stop zabbix-proxy ::: noteimportant It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. ::: ##### 1 Arrêt des processus Zabbix Arrêtez le serveur Zabbix pour vous assurer qu'aucune nouvelle donnée n'est insérée dans la base de données. # systemctl stop zabbix-server Si vous mettez à niveau le proxy Zabbix, arrêtez également le proxy. # systemctl start zabbix-server ::: noteimportant Il n'est plus possible de démarrer le serveur mis à niveau et de faire en sorte que des proxys plus anciens, mais non mis à niveau, transmettent des données à un serveur plus récent. Cette approche, qui n'a jamais été recommandée ni prise en charge par Zabbix, est désormais officiellement désactivée, car le serveur ignorera les données des proxys non mis à niveau. ::: # 1 System information # 1 Information système # 1 Trigger-based event correlation # 1 Corrélation d'événements basée sur les déclencheurs # 1 Trigger event generation # 1 Génération d'événement déclencheur # 1 Usage examples # 1 Exemples d'utilisation # 1 Using certificates # 1 Par certificat # 1 Virtual machine discovery key fields The following table lists fields returned by virtual machine related discovery keys. |**Item key**|<|<| |--|--|----| |**Description**|**Field**|**Retrieved content**| |vmware.cluster.discovery|<|<| |Performs cluster discovery.|{\#CLUSTER.ID}|Cluster identifier.| |^|{\#CLUSTER.NAME}|Cluster name.| |vmware.datastore.discovery|<|<| |Performs datastore discovery.|{\#DATASTORE}|Datastore name.| |^|{\#DATASTORE.EXTENT}|JSON object with an array of {instanceName:partitionId}.| |vmware.dc.discovery|<|<| |Performs datacenter discovery.|{\#DATACENTER}|Datacenter name.| |^|{\#DATACENTERID}|Datacenter ID.| |vmware.hv.discovery|<|<| |Performs hypervisor discovery.|{\#HV.UUID}|Unique hypervisor identifier.| |^|{\#HV.ID}|Hypervisor identifier (HostSystem managed object name).| |^|{\#HV.NAME}|Hypervisor name.| |^|{\#HV.NETNAME}|Hypervisor network host name.| |^|{\#HV.IP}|Hypervisor IP address, might be empty.<br>In case of an HA configuration with multiple net interfaces, the following selection priority for interface is observed:<br>- prefer the IP which shares the IP-subnet with the vCenter IP<br>- prefer the IP from IP-subnet with default gateway<br>- prefer the IP from interface with the lowest ID<br>This field is supported since Zabbix 5.2.2.| |^|{\#CLUSTER.NAME}|Cluster name, might be empty.| |^|{\#DATACENTER.NAME}|Datacenter name.| |^|{\#PARENT.NAME}|Name of container that stores the hypervisor.<br>Supported since Zabbix 4.0.3.| |^|{\#PARENT.TYPE}|Type of container in which the hypervisor is stored. The values could be `Datacenter`, `Folder`, `ClusterComputeResource`, `VMware`, where 'VMware' stands for unknown container type.<br>Supported since Zabbix 4.0.3.| |vmware.hv.datastore.discovery|<|<| |Performs hypervisor datastore discovery. Note that multiple hypervisors can use the same datastore.|{\#DATASTORE}|Datastore name.| |^|{\#MULTIPATH.COUNT}|Registered number of datastore paths.| |^|{\#MULTIPATH.PARTITION.COUNT}|Number of available disk partitions.| |vmware.vm.discovery|<|<| |Performs virtual machine discovery.|{\#VM.UUID}|Unique virtual machine identifier.| |^|{\#VM.ID}|Virtual machine identifier (VirtualMachine managed object name).| |^|{\#VM.NAME}|Virtual machine name.| |^|{\#HV.NAME}|Hypervisor name.| |^|{\#DATACENTER.NAME}|Datacenter name.| |^|{\#CLUSTER.NAME}|Cluster name, might be empty.| |^|{\#VM.IP}|Virtual machine IP address, might be empty.<br>Supported since Zabbix 5.2.2.| |^|{\#VM.DNS}|Virtual machine DNS name, might be empty.<br>Supported since Zabbix 5.2.2.| |^|{\#VM.GUESTFAMILY}|Guest virtual machine OS family, might be empty.<br>Supported since Zabbix 5.2.2.| |^|{\#VM.GUESTFULLNAME}|Full guest virtual machine OS name, might be empty.<br>Supported since Zabbix 5.2.2.| |^|{\#VM.FOLDER}|The chain of virtual machine parent folders, can be used as value for nested groups; folder names are combined with "/". Might be empty.<br>Supported since Zabbix 5.4.2.| |vmware.vm.net.if.discovery|<|<| |Performs virtual machine network interface discovery.|{\#IFNAME}|Network interface name.| |vmware.vm.vfs.dev.discovery|<|<| |Performs virtual machine disk device discovery.|{\#DISKNAME}|Disk device name.| |vmware.vm.vfs.fs.discovery|<|<| |Performs virtual machine file system discovery.|{\#FSNAME}|File system name.| # 1 Champs clés de découverte de machine virtuelle Le tableau suivant répertorie les champs renvoyés par les clés de découverte liées aux machines virtuelles. |**Clé de l'élément**|<|<| |--|--|----| |**Description**|**Champ**|**Contenu récupéré**| |vmware.cluster.discovery|<|<| |Effectue la découverte du cluster.|{\#CLUSTER.ID}|Identifiant du cluster.| |^|{\#CLUSTER.NAME}|Nom du cluster.| |vmware.datastore.discovery|<|<| |Effectue la découverte du magasin de données.|{\#DATASTORE}|Nom du magasin de données.| |^|{\#DATASTORE.EXTENT}|Objet JSON avec un tableau de {instanceName:partitionId}.| |vmware.dc.discovery|<|<| |Effectue la découverte du centre de données.|{\#DATACENTER}|Nom du centre de données.| |^|{\# DATACENTERID}|Identifiant du centre de données.| |vmware.hv.discovery|<|<| |Effectue la découverte de l'hyperviseur.|{\#HV.UUID}|Identifiant unique de l'hyperviseur.| |^|{\#HV.ID}|Identifiant de l'hyperviseur (nom de l'objet géré HostSystem).| |^|{\#HV.NAME}|Nom de l'hyperviseur.| |^|{\#HV.NETNAME}|Nom d'hôte du réseau de l'hyperviseur.| |^|{\#HV.IP}|L'adresse IP de l'hyperviseur peut être vide.<br>Dans le cas d'une configuration HA avec plusieurs interfaces réseau, la priorité de sélection suivante pour l'interface est observée :<br>- préférez l'IP qui partage le sous-réseau IP avec l'IP de vCenter<br>- préférez l'IP du sous-réseau IP avec la passerelle par défaut<br>- préférez l'IP de l'interface avec l'ID le plus bas<br>Ce champ est pris en charge depuis Zabbix 5.2.2.| |^|{\#CLUSTER.NAME}|Nom du cluster, peut être vide.| |^|{\#DATACENTRE.NAME}|Nom du centre de données.| |^|{\#PARENT.NAME}|Nom du conteneur qui stocke l'hyperviseur.<br>Pris en charge depuis Zabbix 4.0.3.| |^|{\#PARENT.TYPE}|Type de conteneur dans lequel l'hyperviseur est stocké. Les valeurs peuvent être `Datacenter`, `Folder`, `ClusterComputeResource`, `VMware`, où 'VMware' représente un type de conteneur inconnu.<br>Pris en charge depuis Zabbix 4.0.3.| |vmware.hv.datastore.discovery|<|<| |Effectue la découverte du magasin de données de l'hyperviseur. Notez que plusieurs hyperviseurs peuvent utiliser le même magasin de données.|{\#DATASTORE}|Nom du magasin de données.| |^|{\#MULTIPATH.COUNT}|Nombre enregistré de chemins de datastore.| |^|{\#MULTIPATH.PARTITION.COUNT}|Nombre de partitions de disque disponibles.| |vmware.vm.discovery|<|<| |Effectue la découverte de la machine virtuelle.|{\#VM.UUID}|Identifiant unique de la machine virtuelle.| |^|{\#VM.ID}|Identifiant de la machine virtuelle (nom de l'objet géré VirtualMachine).| |^|{\#VM.NAME}|Nom de la machine virtuelle.| |^|{\#HV.NAME}|Nom de l'hyperviseur.| |^|{\#DATACENTRE.NAME}|Nom du centre de données.| |^|{\#CLUSTER.NAME}|Nom du cluster, peut être vide.| |^|{\#VM.IP}|Adresse IP de la machine virtuelle, peut être vide.<br>Pris en charge depuis Zabbix 5.2.2.| |^|{\#VM.DNS}|Nom DNS de la machine virtuelle, peut être vide.<br>Pris en charge depuis Zabbix 5.2.2.| |^|{\#VM.GUESTFAMILY}|Famille d'OS de machine virtuelle invitée, peut être vide.<br>Pris en charge depuis Zabbix 5.2.2.| |^|{\#VM.GUESTFULLNAME}|Nom complet du système d'exploitation de la machine virtuelle invitée, peut être vide.<br>Pris en charge depuis Zabbix 5.2.2.| |^|{\#VM.FOLDER}|La chaîne de dossiers parents de la machine virtuelle, peut être utilisée comme valeur pour les groupes imbriqués ; les noms de dossier sont combinés avec "/". Peut être vide.<br>Pris en charge depuis Zabbix 5.4.2.| |vmware.vm.net.if.discovery|<|<| |Effectue la découverte de l'interface réseau de la machine virtuelle.|{\#IFNAME}|Nom de l'interface réseau.| |vmware.vm.vfs.dev.discovery|<|<| |Effectue la découverte du périphérique de disque de la machine virtuelle.|{\#DISKNAME}|Nom du périphérique de disque.| |vmware.vm.vfs.fs.discovery|<|<| |Effectue la découverte du système de fichiers de la machine virtuelle.|{\#FSNAME}|Nom du système de fichiers.| # 1 Web monitoring items # 1 Éléments de supervision Web # 1 Zabbix agent # 1 Agent Zabbix # 1 Zabbix server # 1 Serveur Zabbix # 20. Modules # 20. Modules # 20 System information # 20 Information système # 20 Top hosts # 20 Top hôtes # 20 Upgrade notes for 6.0.10 # 20 Notes de mise à jour pour 6.0.10 # 20 What's new in Zabbix 6.0.15 # 20 Quoi de neuf dans Zabbix 6.0.15 # 21 Upgrade notes for 6.0.11 # 21 Notes de mise à jour pour 6.0.11 # 22 Trigger overview # 22 Aperçu de déclencheur # 22 Upgrade notes for 6.0.12 # 22 Notes de mise à jour pour 6.0.12 # 22 URL # 22 URL # 23 Upgrade notes for 6.0.13 # 23 Notes de mise à jour pour 6.0.13 # 24 Upgrade notes for 6.0.14 # 24 Notes de mise à jour pour 6.0.14 # 24 Web monitoring # 24 Surveillance Web # 2 Actions [comment]: # (tags: action) # 2 Actions # 2 Active agent autoregistration # 2 Enregistrement automatique d'agent actif # 2 Agent # 2 Agent ##### 2 Back up configuration files and Zabbix agent binaries Make a backup copy of the Zabbix agent binary and configuration file. ##### 2 Sauvegarde des fichiers de configuration et des binaires de l’agent Zabbix Faites une copie de sauvegarde des binaires de l’agent Zabbix et des fichiers de configuration. ##### 2 Back up configuration files and Zabbix proxy binaries Make a backup copy of the Zabbix proxy binary and configuration file. ##### 2 Sauvegarde des fichiers de configuration et des binaires du proxy Zabbix Faites une copie de sauvegarde des binaires du proxy Zabbix et des fichiers de configuration. ##### 2 Back up the existing Zabbix database This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem). ##### 2 Sauvegarde de la base de données Zabbix existante Il s’agit d’une étape très importante. Vérifiez que vous disposez d’une sauvegarde de votre base de données. Cela aidera si la procédure de mise à jour échoue (manque d’espace disque, arrêt inopiné ou tout autre problème imprévu). ##### 2 Back up the existing Zabbix database This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem). ##### 2 Sauvegarde de la base de données Zabbix existante Ceci est une étape très importante. Assurez-vous d'avoir une sauvegarde de votre base de données. Cela aidera si la procédure de mise à niveau échoue (manque d'espace disque, mise hors tension, tout problème inattendu). ##### 2 Back up the existing Zabbix database This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem). ##### 2 Sauvegarde de la base de données Zabbix existante Ceci est une étape très importante. Assurez-vous d'avoir une sauvegarde de votre base de données. Cela aidera si la procédure de mise à niveau échoue (manque d'espace disque, mise hors tension, tout problème inattendu). ##### 2 Back up the existing Zabbix database This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem). ##### 2 Sauvegarder la base de données Zabbix existante Ceci est une étape très importante. Assurez-vous d'avoir une sauvegarde de votre base de données. Cela aidera si la procédure de mise à niveau échoue (manque d'espace disque, mise hors tension, tout problème inattendu). # 2 Bitwise functions All functions listed here are supported in: - [Trigger expressions](/manual/config/triggers/expression) - [Calculated items](/manual/config/items/itemtypes/calculated) Some general notes on function parameters: - Function parameters are separated by a comma - Expressions are accepted as parameters - Optional function parameters (or parameter parts) are indicated by `<` `>` |FUNCTION|<|<| |--|--|--| |**Description**|**Function-specific parameters**|**Comments**| |**bitand** (value,mask)|<|<| |Value of "bitwise AND" of an item value and mask.|**value** - value to check<br>**mask** (mandatory) - 64-bit unsigned integer (0 - 18446744073709551615)|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.<br><br>Examples:<br>=> **bitand**(last(/host/key),**12**)=8 or **bitand**(last(/host/key),**12**)=4 → 3rd or 4th bit set, but not both at the same time<br>=> **bitand**(last(/host/key),**20**)=16 → 3rd bit not set and 5th bit set.| |**bitlshift** (value,bits to shift)|<|<| |Bitwise shift left of an item value.|**value** - value to check<br>**bits to shift** (mandatory) - number of bits to shift|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.| |**bitnot** (value)|<|<| |Value of "bitwise NOT" of an item value.|**value** - value to check<br>|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.| |**bitor** (value,mask)|<|<| |Value of "bitwise OR" of an item value and mask.|**value** - value to check<br>**mask** (mandatory) - 64-bit unsigned integer (0 - 18446744073709551615)|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.| |**bitrshift** (value,bits to shift)|<|<| |Bitwise shift right of an item value.|**value** - value to check<br>**bits to shift** (mandatory) - number of bits to shift|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.| |**bitxor** (value,mask)|<|<| |Value of "bitwise exclusive OR" of an item value and mask.|**value** - value to check<br>**mask** (mandatory) - 64-bit unsigned integer (0 - 18446744073709551615)|Supported value types: int<br><br>Although the comparison is done in a bitwise manner, all the values must be supplied and are returned in decimal. For example, checking for the 3rd bit is done by comparing to 4, not 100.| # 2 Fonctions binaires Toutes les fonctions répertoriées ici sont prises en charge dans : - [Expressions de déclenchement](/manual/config/triggers/expression) - [Éléments calculés](/manual/config/items/itemtypes/calculated) Quelques notes générales sur les paramètres de fonction : - Les paramètres de fonction sont séparés par une virgule - Les expressions sont acceptées comme paramètres - Les paramètres de fonction optionnels (ou parties de paramètres) sont indiqués par `<` `>` |FONCTION|<|<| |--|--|--| |**Description**|**Paramètres spécifiques à la fonction**|**Commentaires**| |**bitand** (valeur,masque)|<|<| |Valeur de "ET binaire" d'une valeur d'élément et d'un masque.|**valeur** : valeur à vérifier<br>**masque** (obligatoire) : entier non signé 64 bits (0 - 18446744073709551615)|Types de valeur pris en charge : int<br><br>Bien que la comparaison se fasse au niveau du bit, toutes les valeurs doivent être fournies et sont renvoyées en décimal. Par exemple, la vérification du 3e bit est effectuée en comparant à 4, et non à 100.<br><br>Exemples :<br>=> **bitand**(last(/host/key),**12** )=8 ou **bitand**(last(/host/key),**12**)=4 → 3ème ou 4ème bit défini, mais pas les deux en même temps<br>=> **bitand** (last(/host/key),**20**)=16 → 3e bit non défini et 5e bit défini.| |**bitlshift** (valeur,bits à décaler)|<|<| |Décalage au niveau du bit à gauche d'une valeur d'élément.|**valeur** : valeur à vérifier<br>**bits à décaler** (obligatoire) : nombre de bits à décaler|Types de valeurs pris en charge : int<br><br> Bien que la comparaison se fasse au niveau du bit, toutes les valeurs doivent être fournies et sont renvoyées en décimal. Par exemple, la vérification du 3e bit se fait en comparant à 4, et non à 100.| |**bitnot** (valeur)|<|<| |Valeur de "NON binaire" d'une valeur d'élément.|**valeur** - valeur à vérifier<br>|Types de valeur pris en charge : int<br><br>Bien que la comparaison soit effectuée au niveau du bit, toutes les valeurs doivent être fournis et sont retournés en décimal. Par exemple, la vérification du 3e bit se fait en comparant à 4, et non à 100.| |**bitor** (valeur,masque)|<|<| |Valeur de "OU binaire" d'une valeur d'élément et d'un masque.|**valeur** : valeur à vérifier<br>**masque** (obligatoire) : entier non signé 64 bits (0 - 18446744073709551615)|Types de valeur pris en charge : int<br><br>Bien que la comparaison se fasse au niveau du bit, toutes les valeurs doivent être fournies et sont renvoyées en décimal. Par exemple, la vérification du 3e bit se fait en comparant à 4, et non à 100.| |**bitrshift** (valeur,bits à décaler)|<|<| |Décalage au niveau du bit vers la droite d'une valeur d'élément.|**valeur** : valeur à vérifier<br>**bits à décaler** (obligatoire) : nombre de bits à décaler|Types de valeurs pris en charge : int<br><br> Bien que la comparaison se fasse au niveau du bit, toutes les valeurs doivent être fournies et sont renvoyées en décimal. Par exemple, la vérification du 3e bit se fait en comparant à 4, et non à 100.| |**bitxor** (valeur,masque)|<|<| |Valeur du "OU exclusif binaire" d'une valeur d'élément et d'un masque.|**valeur** : valeur à vérifier<br>**masque** (obligatoire) : entier non signé 64 bits (0 - 18446744073709551615)|Valeur prise en charge types : int<br><br>Bien que la comparaison se fasse au niveau du bit, toutes les valeurs doivent être fournies et sont renvoyées en décimal. Par exemple, la vérification du 3e bit se fait en comparant à 4, et non à 100.| # 2 Certificate problems # 2 Problèmes de certificat # 2 Clock # 2 Horloge # 2 Custom graphs # 2 Graphiques personnalisés # 2 Custom intervals # 2 Intervalles personnalisés # 2 Debian/Ubuntu # 2 Debian/Ubuntu # 2 Debian/Ubuntu/Raspbian # 2 Debian/Ubuntu/Raspbian # 2. Definitions # 2. Définitions # 2 Discovery of network interfaces In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover network interfaces. # 2 Découverte des interfaces réseau De la même manière que les [systèmes de fichiers](/manual/discovery/low_level_discovery#configuring_low-level_discovery) sont découverts, il est également possible de découvrir les interfaces réseau. # 2 Docker plugin # 2 Plugin Docker # 2 Global event correlation # 2 Corrélation globale des événements # 2 Host group elements # 2 Éléments du groupe d'hôtes # 2 Hosts # 2 Hôtes # 2 Items # 2 Éléments # 2 Item value preprocessing # 2 Prétraitement de la valeur de l'élément # 2 Linking/unlinking # 2 Lier/Délier # 2 Network maps [comment]: # (tags: map) # 2 Cartes du réseau # 2 New host # 2 Nouvel hôte # 2 Operations # 2 Opérations # 2 Other event sources # 2 Autres sources d'événements # 2 Permissions # 2 Permissions # 2 PostgreSQL encryption configuration [comment]: # (tags: ssl) # 2 Configuration du chiffrement PostgreSQL [comment]: # (tags: ssl) # 2 Preprocessing details # 2 Détails du prétraitement # 2 Problems # 2 Problèmes # 2 Proxies # 2 Proxys # 2 Real life scenario # 2 Scénario concret # 2 Recommended UnixODBC settings for PostgreSQL # 2 Paramètres UnixODBC recommandés pour PostgreSQL # 2 Remote commands # 2 Commandes à distance # 2 Repairing Zabbix database character set and collation # 2 Réparation du jeu de caractères et de la collation de la base de données Zabbix # 2 Requirements # 2 Pré-requis # 2 Scheduled reports # 2 Rapports planifiés # 2 Service actions # 2 Actions de service # 2 Service actions # 2 Actions de service # 2 Services # 2 Services # 2 Setup from RHEL packages # 2 Installation à partir des paquets RHEL # 2 Setup from RHEL packages # 2 Configuration à partir des packages RHEL # 2 SMS # 2 SMS # 2 SNMP agent [comment]: # (tags: snmp) # 2 Agent SNMP # 2 Sound in browsers # 2 Son dans les navigateurs # 2 Special OIDs Some of the most used SNMP OIDs are translated automatically to a numeric representation by Zabbix. For example, **ifIndex** is translated to **1.3.6.1.2.1.2.2.1.1**, **ifIndex.0** is translated to **1.3.6.1.2.1.2.2.1.1.0**. The table contains list of the special OIDs. |Special OID|Identifier|Description| |-----------|----------|-----------| |ifIndex|1.3.6.1.2.1.2.2.1.1|A unique value for each interface.| |ifDescr|1.3.6.1.2.1.2.2.1.2|A textual string containing information about the interface.This string should include the name of the manufacturer, the product name and the version of the hardware interface.| |ifType|1.3.6.1.2.1.2.2.1.3|The type of interface, distinguished according to the physical/link protocol(s) immediately 'below' the network layer in the protocol stack.| |ifMtu|1.3.6.1.2.1.2.2.1.4|The size of the largest datagram which can be sent / received on the interface, specified in octets.| |ifSpeed|1.3.6.1.2.1.2.2.1.5|An estimate of the interface's current bandwidth in bits per second.| |ifPhysAddress|1.3.6.1.2.1.2.2.1.6|The interface's address at the protocol layer immediately \`below' the network layer in the protocol stack.| |ifAdminStatus|1.3.6.1.2.1.2.2.1.7|The current administrative state of the interface.| |ifOperStatus|1.3.6.1.2.1.2.2.1.8|The current operational state of the interface.| |ifInOctets|1.3.6.1.2.1.2.2.1.10|The total number of octets received on the interface, including framing characters.| |ifInUcastPkts|1.3.6.1.2.1.2.2.1.11|The number of subnetwork-unicast packets delivered to a higher-layer protocol.| |ifInNUcastPkts|1.3.6.1.2.1.2.2.1.12|The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.| |ifInDiscards|1.3.6.1.2.1.2.2.1.13|The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.| |ifInErrors|1.3.6.1.2.1.2.2.1.14|The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.| |ifInUnknownProtos|1.3.6.1.2.1.2.2.1.15|The number of packets received via the interface which were discarded because of an unknown or unsupported protocol.| |ifOutOctets|1.3.6.1.2.1.2.2.1.16|The total number of octets transmitted out of the interface, including framing characters.| |ifOutUcastPkts|1.3.6.1.2.1.2.2.1.17|The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.| |ifOutNUcastPkts|1.3.6.1.2.1.2.2.1.18|The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.| |ifOutDiscards|1.3.6.1.2.1.2.2.1.19|The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.| |ifOutErrors|1.3.6.1.2.1.2.2.1.20|The number of outbound packets that could not be transmitted because of errors.| |ifOutQLen|1.3.6.1.2.1.2.2.1.21|The length of the output packet queue (in packets).| # 2 OID spéciaux Certains des OID SNMP les plus utilisés sont traduits automatiquement en une représentation numérique par Zabbix. Par exemple, **ifIndex** est traduit en 1.3.6.1.2.1.2.2.1.1, **ifIndex.0** est traduit en **1.3.6.1.2.1.2.2.1.1.0**. Le tableau suivant contient la liste des OID spéciaux. |OID Spéciaux|Identificateur|Description| |-----------|----------|-----------| |ifIndex|1.3.6.1.2.1.2.2.1.1|Une valeur unique pour chaque interface.| |ifDescr|1.3.6.1.2.1.2.2.1.2|Une chaîne textuelle contenant des informations sur l'interface. Cette chaîne doit inclure le nom du fabricant, le nom du produit et la version de l'interface matérielle.| |ifType|1.3.6.1.2.1.2.2.1.3|Le type d'interface, distingué en fonction du (des) protocole(s) physique(s) / de liaison immédiatement "en dessous" de la couche réseau dans la pile de protocole.| |ifMtu|1.3.6.1.2.1.2.2.1.4|La taille du plus grand datagramme pouvant être envoyé/reçu sur l'interface, spécifié en octets.| |ifSpeed|1.3.6.1.2.1.2.2.1.5|Une estimation de la bande passante actuelle de l'interface en bits par seconde.| |ifPhysAddress|1.3.6.1.2.1.2.2.1.6|L'adresse de l'interface au niveau de la couche de protocole est immédiatement inférieure à la couche réseau dans la pile de protocoles.| |ifAdminStatus|1.3.6.1.2.1.2.2.1.7|L'état administratif actuel de l'interface.| |ifOperStatus|1.3.6.1.2.1.2.2.1.8|L'état opérationnel actuel de l'interface.| |ifInOctets|1.3.6.1.2.1.2.2.1.10|Nombre total d'octets reçus sur l'interface, y compris les caractères de cadre.| |ifInUcastPkts|1.3.6.1.2.1.2.2.1.11|Le nombre de paquets sub-network-unicast livrés à un protocole de couche supérieure.| |ifInNUcastPkts|1.3.6.1.2.1.2.2.1.12|Nombre de paquets non monodiffusion (c.-à-d., Sous-réseau diffusé ou sous-réseau-multidiffusion) transmis à un protocole de couche supérieure.| |ifInDiscards|1.3.6.1.2.1.2.2.1.13|Le nombre de paquets entrants qui ont été choisis pour être rejetés même si aucune erreur n'a été détectée pour empêcher leur transmission à un protocole de couche supérieure. Une raison possible pour éliminer un tel paquet pourrait être de libérer de l'espace buffer.| |ifInErrors|1.3.6.1.2.1.2.2.1.14|Nombre de paquets entrants contenant des erreurs empêchant leur transmission à un protocole de couche supérieure.| |ifInUnknownProtos|1.3.6.1.2.1.2.2.1.15|Nombre de paquets reçus via l'interface qui ont été rejetés en raison d'un protocole inconnu ou non supporté.| |ifOutOctets|1.3.6.1.2.1.2.2.1.16|Nombre total d'octets transmis hors de l'interface, y compris les caractères de cadre.| |ifOutUcastPkts|1.3.6.1.2.1.2.2.1.17|Nombre total de paquets que les protocoles de niveau supérieur requis ont transmis et qui n'ont pas été adressés à une adresse de multidiffusion ou de diffusion de cette sous-couche, y compris ceux qui ont été rejetés ou non envoyés.| |ifOutNUcastPkts|1.3.6.1.2.1.2.2.1.18|Nombre total de paquets que les protocoles de niveau supérieur requis ont transmis et qui ont été adressés à une adresse de multidiffusion ou de diffusion de cette sous-couche, y compris ceux qui ont été rejetés ou non envoyés.| |ifOutDiscards|1.3.6.1.2.1.2.2.1.19|Le nombre de paquets sortants qui ont été choisis pour être rejetés même si aucune erreur n'a été détectée pour empêcher leur transmission. Une raison possible pour éliminer un tel paquet pourrait être de libérer de l'espace buffer.| |ifOutErrors|1.3.6.1.2.1.2.2.1.20|Le nombre de paquets sortants qui n'ont pas pu être transmis en raison d'erreurs.| |ifOutQLen|1.3.6.1.2.1.2.2.1.21|La longueur de la file d'attente de paquets de sortie (en paquets).| # 2 Templates # 2 Modèles # 2 Trigger expression # 2 Expression de déclenchement # 2 Trigger prototypes # 2 Prototypes de déclencheur # 2 Trigger prototypes # 2 Prototypes de déclencheur # 2 Triggers # 2 Déclencheurs # 2 Triggers # 2 Déclencheurs # 2 User macros # 2 Macros utilisateur # 2 User macros supported by location # 2 Macros utilisateurs supportées par emplacement # 2 Using pre-shared keys # 2 Par clés pré-partagées (PSK) # 2 vm.memory.size parameters # 2 Paramètres vm.memory.size # 2 Web scenarios # 2 Scenarios Web # 2 Zabbix agent protocol Please refer to [Passive and active agent checks](/manual/appendix/items/activepassive) page for more information. # 2 Protocole de l'agent Zabbix Veuillez vous référer à la page [Vérifications de l'agent actif et passif](/fr/manual/appendix/items/activepassive) pour plus d'informations. # 2 Zabbix proxy # 2 Proxy Zabbix ##### 32 bit Open MinGW environment (Windows command prompt) and navigate to *build/mingw* directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make ARCH=x86 PCRE=c:\dev\pcre32 OPENSSL=c:\dev\openssl32 ##### 32 bit Ouvrir l'environnement MinGW (invite de commande Windows) et accéder au répertoire *build/mingw* dans l'arborescence des sources Zabbix. Exécuter : mingw32-make clean mingw32-make ARCH=x86 PCRE=c:\dev\pcre32 OPENSSL=c:\dev\openssl32 # 3 Additional operations # 3 Opérations supplémentaires # 3 Ad-hoc graphs # 3 Graphiques ad-hoc # 3 Agent 2 # 3 Agent 2 # 3 Authentication [comment]: # (tags: ldap, saml) # 3 Authentification # 3 Availability report # 3 Rapport de disponibilité ##### 3 Back up configuration files, PHP files and Zabbix binaries Make a backup copy of Zabbix binaries, configuration files and the PHP file directory. ##### 3 Sauvegarde des fichiers de configuration, des fichiers PHP et des binaires Zabbix Faites une copie de sauvegarde des binaires Zabbix, des fichiers de configuration et du répertoire des fichiers PHP. ##### 3 Back up configuration files, PHP files and Zabbix binaries Make a backup copy of Zabbix binaries, configuration files and the PHP file directory. Configuration files: # mkdir /opt/zabbix-backup/ # cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/ # cp /etc/httpd/conf.d/zabbix.conf /opt/zabbix-backup/ PHP files and Zabbix binaries: # cp -R /usr/share/zabbix/ /opt/zabbix-backup/ # cp -R /usr/share/zabbix-* /opt/zabbix-backup/ ##### 3 Sauvegarde des fichiers de configuration, des fichiers PHP et des binaires Zabbix Faites une copie de sauvegarde des fichiers binaires Zabbix, des fichiers de configuration et du répertoire de fichiers PHP. Fichiers de configuration : # mkdir /opt/zabbix-backup/ # cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/ # cp /etc/httpd/conf.d/zabbix.conf /opt/zabbix-backup/ Fichiers PHP et binaires Zabbix : # cp -R /usr/share/zabbix/ /opt/zabbix-backup/ # cp -R /usr/share/zabbix-* /opt/zabbix-backup/ ##### 3 Create Zabbix database For Zabbix [server](/manual/concepts/server) and [proxy](/manual/concepts/proxy) daemons, as well as Zabbix frontend, a database is required. It is not needed to run Zabbix [agent](/manual/concepts/agent). SQL [scripts are provided](/manual/appendix/install/db_scripts) for creating database schema and inserting the dataset. Zabbix proxy database needs only the schema while Zabbix server database requires also the dataset on top of the schema. Having created a Zabbix database, proceed to the following steps of compiling Zabbix. ##### 3 Créer la base de données Zabbix Pour les démons [serveur](/manual/concepts/server) et [proxy](/manual/concepts/proxy), tout comme pour l'interface Web, une base de données est nécessaire. Cela n’est pas nécessaire pour l'[agent](/manual/concepts/agent) Zabbix. Des [scripts SQL sont fournis](/manual/appendix/install/db_scripts) pour créer le schéma de base de données et insérer l'ensemble de données. La base de données du proxy Zabbix n'a besoin que du schéma tandis que la base de données du serveur Zabbix requiert également l'ensemble de données au-dessus du schéma. Après avoir créé la base de données Zabbix, passez aux étapes suivantes de la compilation de Zabbix. # 3 Dashboards [Dashboards](/manual/web_interface/frontend_sections/monitoring/dashboard) and their widgets provide a strong visualization platform with such tools as modern graphs, maps, slideshows, and many more. {width="600"} # 3 Tableaux de bord Les [tableaux de bord](/manual/web_interface/frontend_sections/monitoring/dashboard) et leurs widgets fournissent une plate-forme de visualisation puissante avec des outils tels que des graphiques modernes, des cartes, des diaporamas et bien d'autres. {width="600"} # 3 Database upgrade to primary keys # 3 Mise à niveau de la base de données vers les clés primaires # 3 Data overview # 3 Aperçu des données # 3 Discovery of CPUs and CPU cores In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover CPUs and CPU cores. # 3 Découverte des processeurs et des cœurs De la même manière que les [systèmes de fichiers](/manual/discovery/low_level_discovery#configuring_low-level_discovery) sont découverts, il est également possible de découvrir des CPU et des cœurs de CPU. # 3 Graph prototypes # 3 Prototypes de graphique # 3 Graph prototypes # 3 Prototypes de graphique # 3 Graph prototypes We can create graph prototypes, too:  Attributes that are specific for graph prototypes: |Parameter|Description| |--|--------| |*Discover*|If checked (default) the graph will be added to a discovered entity.<br>If unchecked, the graph will not be added to a discovered entity, unless this setting is [overridden](/manual/discovery/low_level_discovery#override) in the discovery rule.|  Finally, we have created a discovery rule that looks as shown below. It has five item prototypes, two trigger prototypes, and one graph prototype.  *Note*: For configuring host prototypes, see the section about [host prototype](/manual/vm_monitoring#host_prototypes) configuration in virtual machine monitoring. # 3 Prototypes de graphique Nous pouvons également créer des prototypes de graphique :  Attributs spécifiques aux prototypes de graphique : |Paramètre|Description| |--|--------| |*Discover*|Si coché (par défaut), le graphique sera ajouté à une entité découverte.<br>Si décoché, le graphique ne sera pas ajouté à une entité découverte, sauf si ce paramètre est [surchargé](/manual/discovery/low_level_discovery#override) dans la règle de découverte.|  Enfin, nous avons créé une règle de découverte qui ressemble à celle illustrée ci-dessous. Elle a cinq prototypes d'éléments, deux prototypes de déclencheurs et un prototype de graphique.  *Remarque* : Pour configurer les prototypes d'hôte, consultez la section sur la configuration des [prototypes d'hôte](/manual/vm_monitoring#host_prototypes) pour la surveillance des machines virtuelles. # 3 Graphs # 3 Graphiques # 3 Graphs # 3 Graphiques # 3 Hosts # 3 Hötes # 3 Hosts # 3 hötes # 3 Hosts # 3 Hôtes # 3 Installation from sources You can get the very latest version of Zabbix by compiling it from the sources. A step-by-step tutorial for installing Zabbix from the sources is provided here. # 3 Installation à partir des sources Vous pouvez obtenir la toute dernière version de Zabbix en la compilant à partir des sources. Un tutoriel étape par étape pour installer Zabbix à partir des sources est fourni ici. #### 3 Installing Java gateway It is required to install Java gateway only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database. To install from sources, first [download](/manual/installation/install#download_the_source_archive) and extract the source archive. To compile Java gateway, run the `./configure` script with `--enable-java` option. It is advisable that you specify the `--prefix` option to request installation path other than the default /usr/local, because installing Java gateway will create a whole directory tree, not just a single executable. $ ./configure --enable-java --prefix=$PREFIX To compile and package Java gateway into a JAR file, run `make`. Note that for this step you will need `javac` and `jar` executables in your path. $ make Now you have a zabbix-java-gateway-$VERSION.jar file in src/zabbix\_java/bin. If you are comfortable with running Java gateway from src/zabbix\_java in the distribution directory, then you can proceed to instructions for configuring and running [Java gateway](/manual/concepts/java#overview_of_files_in_java_gateway_distribution). Otherwise, make sure you have enough privileges and run `make install`. $ make install Proceed to [setup](/manual/concepts/java/from_sources) for more details on configuring and running Java gateway. #### 3 Installation de la passerelle Java Il est nécessaire d’installer la passerelle Java uniquement si vous souhaitez superviser les applications JMX. La passerelle Java est légère et ne nécessite pas de base de données. Pour installer depuis les sources, [téléchargez](/manual/installation/install#download_the_source_archive) d'abord l'archive contenant les sources et décompresser là. Pour compiler la passerelle Java, exécutez le script `./configure` avec l'option `--enable-java`. Il est recommandé de spécifier l'option `--prefix` pour positionner un chemin d'installation autre que celui par défaut /usr/local, car l’installation de la passerelle Java créera une arborescence de répertoires complète et non pas un seul exécutable. $ ./configure --enable-java --prefix=$PREFIX Pour compiler et packager la passerelle Java dans un fichier JAR, exécutez `make`. Notez que pour cette étape, vous aurez besoin des exécutables `javac` et `jar` dans votre Path. $ make Vous avez maintenant un fichier zabbix-java-gateway-$VERSION.jar dans src/zabbix\_java/bin. Si vous êtes à l'aise avec l'exécution de la passerelle Java à partir de src/zabbix\_java dans le répertoire de distribution, vous pouvez alors consulter les instructions pour configurer et exécuter la [passerelle Java](/manual/concepts/java#overview_of_files_in_java_gateway_distribution). Sinon, assurez-vous d'avoir suffisamment de privilèges et lancez `make install`. $ make install Procédez à la [configuration](/manual/concepts/java#from_sources) pour plus de détails sur comment configurer et démarrer la passerelle Java et sur comment configurer le serveur Zabbix pour fonctionner avec celle-ci. ##### 3 Install new agent binaries Use these [instructions](/manual/installation/install#installing_zabbix_daemons) to compile Zabbix agent from sources. Alternatively, you may download pre-compiled Zabbix agents from the [Zabbix download page](http://www.zabbix.com/download.php). ##### 3 Installation des nouveaux binaires d’agent Utilisez les [instructions](/manual/installation/install#installing_zabbix_daemons) pour compiler l’agent Zabbix depuis les sources. Sinon, vous pouvez télécharger un agent pré-compilé depuis la [page de téléchargement Zabbix](http://www.zabbix.com/download.php). ##### 3 Install new proxy binaries Use these [instructions](/manual/installation/install#installing_zabbix_daemons) to compile Zabbix proxy from sources. ##### 3 Installation des nouveaux binaires Utilisez les [instructions](/fr/manual/installation/install#installation_des_demons_zabbix) pour compiler le proxy Zabbix depuis les sources. # 3 Inventory # 3 Inventaire # 3 Item types # 3 Types d'éléments # 3 JSONPath functionality # 3 Fonctionnalité JSONPath # 3 Link indicators # 3 Indicateurs de lien # 3 Low-level discovery # 3 Découverte de bas niveau # 3 Manual closing of problems # 3 Fermeture manuelle des problèmes # 3 MIB files # 3 Fichiers MIB # 3 Nesting # 3 Imbrication # 3 New item # 3 Nouvel élément # 3 Passive and active agent checks # 3 Vérifications actives et passives des agents # 3 Passive and active agent checks # 3 Vérifications passives et actives des agents # 3 PSK problems [comment]: # (tags: ssl) # 3 Problèmes PSK # 3 Receiving notification on unsupported items # 3 Réception de notification pour des éléments non supportés # 3 Recommended UnixODBC settings for Oracle # 3 Paramètres recommandés pour UnixODBC sur Oracle # 3 Recovery operations # 3 Opérations de récupération # 3 Setup from Debian/Ubuntu packages # 3 Configuration depuis les packages Debian/Ubuntu # 3 SLA # 3 SLA # 3 SLA # 3 SLA # 3 SNMP traps manual/config/items/itemtypes/snmptrap # 3 SUSE Linux Enterprise Server # 3 SUSE Linux Enterprise Server # 3 Trigger dependencies # 3 Dépendance des déclencheurs # 3 Triggers ## 3 Déclencheurs # 3 Troubleshooting # 3 Dépannage # 3 User groups # 3 Groupes d'utilisateur # 3 User macros with context # 3 Macros utilisateur avec contexte # 3 User settings # 3 Paramètres utilisateur # 3 Zabbix agent 2 protocol # 3 Protocole de l'agent Zabbix 2 # 3 Zabbix agent (UNIX) # 3 Zabbix agent (UNIX) # 3 Zabbix features # 3 Fonctionnalités de Zabbix # 3. Zabbix processes Please use the sidebar to access content in the Zabbix process section. # 3. Processus Zabbix Veuillez utiliser la barre latérale pour accéder au contenu de la section Processus Zabbix, # 4 Aggregation in graphs # 4 Agrégation dans les graphiques ##### 4 Configure the sources When configuring the sources for a Zabbix server or proxy, you must specify the database type to be used. Only one database type can be compiled with a server or proxy process at a time. To see all of the supported configuration options, inside the extracted Zabbix source directory run: ./configure --help To configure the sources for a Zabbix server and agent, you may run something like: ./configure --enable-server --enable-agent --with-mysql --enable-ipv6 --with-net-snmp --with-libcurl --with-libxml2 --with-openipmi To configure the sources for a Zabbix server (with PostgreSQL etc.), you may run: ./configure --enable-server --with-postgresql --with-net-snmp To configure the sources for a Zabbix proxy (with SQLite etc.), you may run: ./configure --prefix=/usr --enable-proxy --with-net-snmp --with-sqlite3 --with-ssh2 To configure the sources for a Zabbix agent, you may run: ./configure --enable-agent or, for Zabbix agent 2: ./configure --enable-agent2 ::: noteclassic A configured Go environment with a currently supported [Go version](https://golang.org/doc/devel/release#policy) is required for building Zabbix agent 2. See [golang.org](https://golang.org/doc/install) for installation instructions. ::: Notes on compilation options: - Command-line utilities zabbix\_get and zabbix\_sender are compiled if --enable-agent option is used. - --with-libcurl and --with-libxml2 configuration options are required for virtual machine monitoring; --with-libcurl is also required for SMTP authentication and `web.page.*` Zabbix agent [items](/manual/config/items/itemtypes/zabbix_agent). Note that cURL 7.20.0 or higher is [required](/manual/installation/requirements) with the --with-libcurl configuration option. - Zabbix always compiles with the PCRE library (since version 3.4.0); installing it is not optional. --with-libpcre=\[DIR\] only allows pointing to a specific base install directory, instead of searching through a number of common places for the libpcre files. - You may use the --enable-static flag to statically link libraries. If you plan to distribute compiled binaries among different servers, you must use this flag to make these binaries work without required libraries. Note that --enable-static does not work in [Solaris](https://docs.oracle.com/cd/E18659_01/html/821-1383/bkajp.html). - Using --enable-static option is not recommended when building server. In order to build the server statically, you must have a static version of every external library needed. There is no strict check for that in configure script. - Add optional path to the MySQL configuration file --with-mysql=/<path\_to\_the\_file>/mysql\_config to select the desired MySQL client library when there is a need to use one that is not located in the default location. It is useful when there are several versions of MySQL installed or MariaDB installed alongside MySQL on the same system. - Use --with-oracle flag to specify location of the OCI API. ::: noteimportant If ./configure fails due to missing libraries or some other circumstance, please see the `config.log` file for more details on the error. For example, if `libssl` is missing, the immediate error message may be misleading: checking for main in -lmysqlclient... no configure: error: Not found mysqlclient library While `config.log` has a more detailed description: /usr/bin/ld: cannot find -lssl /usr/bin/ld: cannot find -lcrypto ::: See also: - [Compiling Zabbix with encryption support](/manual/encryption#compiling_zabbix_with_encryption_support) for encryption support - [Known issues](/manual/installation/known_issues#compiling_zabbix_agent_on_hp-ux) with compiling Zabbix agent on HP-UX ##### 4 Configuration des sources Lors de la configuration des sources pour un serveur ou un proxy Zabbix, vous devez spécifier le type de base de données à utiliser. Un seul type de base de données peut être compilé avec un serveur ou un processus proxy à la fois. Pour voir toutes les options de configuration prises en charge, dans le répertoire source de Zabbix, exécutez : ./configure --help Pour configurer les sources d'un serveur et d'un agent Zabbix, vous pouvez exécuter quelque chose comme : ./configure --enable-server --enable-agent --with-mysql --enable-ipv6 --with-net-snmp --with-libcurl --with-libxml2 --with-openipmi Pour configurer les sources d'un serveur Zabbix (avec PostgreSQL, etc.), vous pouvez exécuter : ./configure --enable-server --with-postgresql --with-net-snmp Pour configurer les sources d'un proxy Zabbix (avec SQLite, etc.), vous pouvez exécuter : ./configure --prefix=/usr --enable-proxy --with-net-snmp --with-sqlite3 --with-ssh2 Pour configurer les sources d'un agent Zabbix, vous pouvez exécuter : ./configure --enable-agent ou, pour l'agent Zabbix 2 : ./configure --enable-agent2 ::: noteclassic Un environnement Go configuré avec une [version Go](https://golang.org/doc/devel/release#policy) actuellement prise en charge est requis pour créer l'agent Zabbix 2. Voir [golang.org](https://golang.org/doc/install) pour les instructions d'installation. ::: Remarques sur les options de compilation : - Les utilitaires de ligne de commande zabbix\_get et zabbix\_sender sont compilés si l'option --enable-agent est utilisée. - Les options de configuration --with-libcurl et --with-libxml2 sont requises pour la surveillance des machines virtuelles ; --with-libcurl est également requis pour l'authentification SMTP et les [éléments](/manual/config/items/itemtypes/zabbix_agent) d'agent Zabbix `web.page.*` . Notez que cURL 7.20.0 ou supérieur est [obligatoire](/manual/installation/requirements) avec l'option de configuration --with-libcurl. - Zabbix compile toujours avec la bibliothèque PCRE (depuis la version 3.4.0) ; son installation n'est pas facultative. --with-libpcre=\[DIR\] permet uniquement de pointer vers un répertoire d'installation de base spécifique, au lieu de chercher dans un certain nombre d'endroits communs pour les fichiers libpcre. - Vous pouvez utiliser l'option --enable-static pour lier statiquement les bibliothèques. Si vous envisagez de distribuer des binaires compilés entre différents serveurs, vous devez utiliser cet indicateur pour faire fonctionner ces binaires sans les bibliothèques requises. Notez que --enable-static ne fonctionne pas dans [Solaris](https://docs.oracle.com/cd/E18659_01/html/821-1383/bkajp.html). - L'utilisation de l'option --enable-static n'est pas recommandée lors de la construction du serveur. Afin de construire le serveur de manière statique, vous devez disposer d'une version statique de chaque bibliothèque externe nécessaire. Il n'y a pas de vérification stricte pour cela dans le script de configuration. - Ajoutez un chemin facultatif au fichier de configuration MySQL --with-mysql=/<path\_to\_the\_file>/mysql\_config pour sélectionner la bibliothèque cliente MySQL souhaitée lorsqu'il est nécessaire d'en utiliser une qui ne se trouve pas dans le localisation par défaut. Il est utile lorsque plusieurs versions de MySQL sont installées ou que MariaDB est installée avec MySQL sur le même système. - Utilisez l'option --with-oracle pour spécifier l'emplacement de l'API OCI. ::: noteimportant Si ./configure échoue en raison de bibliothèques manquantes ou d'autres circonstances, veuillez consulter le fichier `config.log` pour plus de détails sur l'erreur. Par exemple, si `libssl` est manquant, le message d'erreur immédiat peut être trompeur : checking for main in -lmysqlclient... no configure: error: Not found mysqlclient library Tandis que `config.log` a une description plus détaillée : /usr/bin/ld: cannot find -lssl /usr/bin/ld: cannot find -lcrypto ::: Voir également : - [Compiler Zabbix avec prise en charge du chiffrement](/manual/encryption#compiling_zabbix_with_encryption_support) pour la prise en charge du chiffrement - [Problèmes connus](/manual/installation/known_issues#compiling_zabbix_agent_on_hp-ux) avec la compilation de l'agent Zabbix sur HP-UX # 4 Discovery of SNMP OIDs # 4 Découverte des OID SNMP # 4 Discovery rules # 4 Règles de découverte # 4 Discovery rules # 4 Règles de découverte # 4 Discovery status # 4 Statut de découverte # 4 Global search It is possible to search Zabbix frontend for hosts, host groups and templates. The search input box is located below the Zabbix logo in the menu. The search can be started by pressing *Enter* or clicking on the  search icon.  If there is a host that contains the entered string in any part of the name, a dropdown will appear, listing all such hosts (with the matching part highlighted in orange). The dropdown will also list a host if that host's visible name is a match to the technical name entered as a search string; the matching host will be listed, but without any highlighting. # 4 Recherche globale Il est possible de rechercher dans l'interface Zabbix des hôtes, des groupes d'hôtes et des modèles. La zone de saisie de recherche est située sous le logo Zabbix dans le menu. La recherche peut être lancée en appuyant sur *Entrée* ou en cliquant sur l'icône de recherche .  Si un hôte contient la chaîne saisie dans n'importe quelle partie du nom, une liste déroulante apparaîtra, répertoriant tous ces hôtes (avec la partie correspondante surlignée en orange). La liste déroulante répertorie également un hôte si le nom visible de cet hôte correspond au nom technique saisi comme chaîne de recherche ; l'hôte correspondant sera répertorié, mais sans aucune mise en surbrillance. # 4 History and trends # 4 Historique et tendances # 4 History functions All functions listed here are supported in: - [Trigger expressions](/manual/config/triggers/expression) - [Calculated items](/manual/config/items/itemtypes/calculated) Some general notes on function parameters: - Function parameters are separated by a comma - Optional function parameters (or parameter parts) are indicated by `<` `>` - Function-specific parameters are described with each function - `/host/key` and `(sec|#num)<:time shift>` parameters must never be quoted # 4 Fonctions d'historique Toutes les fonctions répertoriées ici sont prises en charge dans : - [Expressions de déclenchement](/manual/config/triggers/expression) - [Éléments calculés](/manual/config/items/itemtypes/calculated) Quelques notes générales sur les paramètres de fonction : - Les paramètres des fonctions sont séparés par une virgule - Les paramètres optionnels des fonctions (ou parties de paramètres) sont indiqués par des chevrons : `<` `>` - Les paramètres spécifiques des fonctions sont décrits avec chaque fonction - Les paramètres `/host/key` et `(sec|#num)<:time shift>` ne doivent jamais être mis entre guillemets # 4 Host dashboards # 4 Tableaux de bord d'hôte # 4 Host prototypes # 4 Prototypes d'hôtes # 4 Host prototypes # 4 Prototypes d'hôtes # 4 Installation from packages # 4 Installation à partir de packages # 4. Installation Please use the sidebar to access content in the Installation section. # 4. Installation Veuillez utiliser la barre latérale pour accéder au contenu dans la section Installation. ##### 4 Install new server binaries Use these [instructions](/manual/installation/install#installing_zabbix_daemons) to compile Zabbix server from sources. ##### 4 Installation des nouveaux binaires du serveur Utilisez les [instructions](/fr/manual/installation/install#installation_des_demons_zabbix) pour compiler le serveur Zabbix depuis les sources. # 4 IPMI checks # 4 Vérifications IPMI # 4 JavaScript preprocessing # 4 Prétraitement JavaScript # 4 Latest data # 4 Dernières données # 4 Low-level discovery macros # 4 Macros de découverte de bas niveau # 4 Maintenance #4 Maintenance # 4 Mass update # 4 Mise à jour de masse # 4 Network maps # 4 Cartes du réseau # 4 New trigger [comment]: # (tags: trigger) # 4 Nouveau déclencheur # 4 Notes on low-level discovery # 4 Notes sur la découverte de bas niveau # 4 Recommended UnixODBC settings for MSSQL # 4 Paramètres UnixODBC recommandés pour MSSQL # 4 Reports # 4 Rapports ##### 4 Review proxy configuration parameters There are no mandatory changes in this version to proxy [parameters](/manual/appendix/config/zabbix_proxy). ##### 4 Exam des paramètres de configuration des proxys Il n'y a pas de modifications obligatoires dans cette version pour les [paramètres du proxy](/manual/appendix/config/zabbix_proxy). # 4 Secure connection to the database # 4 Sécuriser la connexion à la base de données # 4 Setup example # 4 Exemple de configuration # 4 SLA report # 4 Rapport SLA # 4 Trapper items # 4 Éléments Trapper # 4 Triggers top 100 # 4 Top 100 des déclencheurs # 4 Update operations # 4 Opérations de mise à jour ##### 4 Update repository configuration package To proceed with the upgrade your current repository package has to be updated. # rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/8/x86_64/zabbix-release-6.0-1.el8.noarch.rpm ##### 4 Mise à jour du package de configuration du dépôt Pour poursuivre la mise à jour, votre package de dépôt actuel doit être mis à jour. # rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/8/x86_64/zabbix-release-6.0-1.el8.noarch.rpm # 4 User groups # 4 Groupes d'utilisateurs # 4 Using macros in messages # 4 Utiliser des macros dans les messages # 4 Webhook # 4 Webhook # 4 Windows agent installation from MSI # 4 Installation de l'agent Windows à partir de MSI # 4 Zabbix agent 2 plugin protocol Please refer to the [connection protocol](https://www.zabbix.com/documentation/guidelines/en/plugins#connection-protocol) section on *Building plugins* page for more information. # 4 Protocole du plugin de l'agent Zabbix 2 Veuillez vous référer à la section [protocole de connexion](https://www.zabbix.com/documentation/guidelines/en/plugins#connection-protocol) sur la page *Création de plugin* pour plus d'informations. # 4 Zabbix agent 2 plugin protocol Zabbix agent 2 protocol is based on code, size and data model. # 4 Protocole du plug-in agent Zabbix 2 Le protocole de l'agent Zabbix 2 est basé sur le code, la taille et le modèle de données. # 4 Zabbix agent 2 (UNIX) # 4 Zabbix agent 2 (UNIX) # 4 Zabbix overview # 4 Aperçu de Zabbix # 5 Actions # 5 Actions # 5 Audit # 5 Audit # 5 Configuration # 5 Configuration # 5 CSV to JSON preprocessing # 5 Prétraitement CSV vers JSON # 5 Customizing trigger severities Trigger severity names and colors for severity related GUI elements can be configured in *Administration → General → Trigger displaying options*. Colors are shared among all GUI themes. # 5 Personnalisation des sévérités des déclencheurs Les noms et les couleurs de sévérités des déclencheurs pour les éléments GUI liés à la sévérité peuvent être configurés dans *Administration → Général → Affichage du déclencheur.*. Les couleurs sont partagées entre tous les thèmes de l'interface graphique. # 5 Discovery of JMX objects # 5 Découverte d'objets JMX # 5 Discovery rules Please use the sidebar to see discovery rule configuration examples for various cases. # 5 Règles de découverte Veuillez utiliser la barre latérale pour voir des exemples de configuration de règle de découverte pour différents cas. # 5 Escalations # 5 Escalades # 5 Event correlation # 5 Corrélation d'événements # 5 Expression macros # 5 Macros d'expression # 5 Favorite graphs # 5 Graphiques favoris # 5 Frontend maintenance mode # 5 Mode maintenance de l'interface Web # 5 Installation from containers # 5 Installation depuis les containers # 5 Java gateway # 5 Passerelle Java # 5 Mac OS agent installation from PKG # 5 Installation de l'agent Mac OS à partir de PKG # 5 Maps [comment]: # (tags: map) # 5 Cartes # 5 Media types # 5 Types de média # 5 Minimum permission level for Windows agent items # 5 Niveau d'autorisation minimum pour les éléments de l'agent Windows # 5. Quickstart Please use the sidebar to access content in the Quickstart section. # 5. Démarrage rapide Veuillez utiliser la barre latérale pour accéder au contenu de la section Démarrage rapide. # 5 Receiving problem notification # 5 Recevoir une notification de problème ##### 5 Review server configuration parameters See the upgrade notes for details on [mandatory changes](/manual/installation/upgrade_notes_600#configuration_parameters). For new optional parameters, see the [What's new](/manual/introduction/whatsnew600#configuration_parameters) section. ##### 5 Exam des paramètres de configuration du serveur Consultez les notes de mise à niveau pour plus de détails sur les [modifications obligatoires](/manual/installation/upgrade_notes_600#configuration_parameters) (le cas échéant). Pour les nouveaux paramètres facultatifs, consultez la section [Quoi de neuf](/manual/introduction/whatsnew600#configuration_parameters). # 5 Simple checks # 5 Vérifications simples ##### 5 Start new Zabbix agent Start the new Zabbix agent. Check log files to see if the agent has started successfully. ##### 5 Démarrage du nouvel agent Zabbix Démarrez le nouvel agent Zabbix. Vérifiez les fichiers de logs pour vérifier que l’agent a démarré correctement. ##### 5 Start new Zabbix proxy Start the new Zabbix proxy. Check log files to see if the proxy has started successfully. Zabbix proxy will automatically upgrade the database. Database upgrade takes place similarly as when starting [Zabbix server](/manual/installation/upgrade#start_new_zabbix_binaries). ##### 5 Démarrage du nouveau proxy Zabbix Démarrez le nouveau proxy Zabbix. Vérifiez les fichiers de logs pour voir si le proxy a démarré correctement. Zabbix mettra automatiquement à jour la base de données. La mise à jour de la base de données a lieu de la même manière que lors du démarrage du [serveur Zabbix](/fr/manual/installation/upgrade). # 5 TimescaleDB setup # 5 Configuration TimescaleDB ##### 5 Upgrade Zabbix components To upgrade Zabbix components you may run something like: # apt-get install --only-upgrade zabbix-server-mysql zabbix-frontend-php zabbix-agent If using PostgreSQL, substitute `mysql` with `pgsql` in the command. If upgrading the proxy, substitute `server` with `proxy` in the command. If upgrading the Zabbix agent 2, substitute `zabbix-agent`with `zabbix-agent2`in the command. Then, to upgrade the web frontend with Apache correctly, also run: # apt-get install zabbix-apache-conf Distributions **prior to Debian 10 (buster) / Ubuntu 18.04 (bionic) / Raspbian 10 (buster)** do not provide PHP 7.2 or newer, which is required for Zabbix frontend 5.0. See [information](/manual/installation/frontend/frontend_on_rhel7) about installing Zabbix frontend on older distributions. ##### 5 Mise à niveau des composants Zabbix Pour mettre à niveau les composants Zabbix, vous pouvez exécuter quelque chose comme : # apt-get install --only-upgrade zabbix-server-mysql zabbix-frontend-php zabbix-agent Si vous utilisez PostgreSQL, remplacez `mysql` par `pgsql` dans la commande. Si vous mettez à niveau le proxy, remplacez `server` par `proxy` dans la commande. Si vous mettez à niveau l'agent Zabbix 2, remplacez `zabbix-agent` par `zabbix-agent2`dans la commande. Ensuite, pour mettre à jour correctement l'interface Web avec Apache, exécutez également : # apt-get install zabbix-apache-conf Les distributions **avant Debian 10 (buster) / Ubuntu 18.04 (bionic) / Raspbian 10 (buster)** ne fournissent pas PHP 7.2 ou plus récent, qui est requis pour l'interface Zabbix 5.0. Voir les [informations](/manual/installation/frontend/frontend_on_rhel7) sur l'installation de l'interface Zabbix sur les anciennes distributions. ##### 5 Upgrade Zabbix components To upgrade Zabbix components you may run something like: # yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent If using PostgreSQL, substitute `mysql` with `pgsql` in the command. If upgrading the proxy, substitute `server` with `proxy` in the command. If upgrading the agent 2, substitute `zabbix-agent` with `zabbix-agent2` in the command. To upgrade the web frontend with Apache **on RHEL 8** correctly, also run: # yum install zabbix-apache-conf and make the necessary [changes](/manual/installation/install_from_packages/rhel#zabbix_frontend_configuration) to this file. To upgrade the web frontend **on RHEL 7** follow [distribution-specific instructions](/manual/installation/frontend/frontend_on_rhel7) (extra steps are required to install PHP 7.2 or newer). ##### 5 Mise à niveau des composants Zabbix Pour mettre à niveau les composants Zabbix, vous pouvez exécuter quelque chose comme : # # yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent Si vous utilisez PostgreSQL, remplacez `mysql` par `pgsql` dans la commande. Si vous mettez à niveau le proxy, remplacez `server` par `proxy` dans la commande. Si vous mettez à niveau l'agent Zabbix 2, remplacez `zabbix-agent` par `zabbix-agent2`dans la commande. Ensuite, pour mettre à jour correctement l'interface Web avec Apache **sur RHEL 8**, exécutez également : # yum install zabbix-apache-conf et apportez les [modifications](/manual/installation/install_from_packages/rhel#zabbix_frontend_configuration) nécessaires à ce fichier. Pour mettre à niveau l'interface Web **sur RHEL 7**, suivez les [instructions spécifiques à la distribution](/manual/installation/frontend/frontend_on_rhel7) (des étapes supplémentaires sont nécessaires pour installer PHP 7.2 ou une version plus récente). # 5 User parameters # 5 Paramètres utilisateurs # 5 User roles # 5 Rôles des utilisateurs # 5 Web scenarios # 5 Scénarios Web # 5 Web scenarios # 5 Scénarios Web # 5 What's new in Zabbix 6.0.0 ::: noteimportant Zabbix 6.0.0 is not released yet. ::: # 5 Nouveautés dans Zabbix 5.0.0 ::: noteimportant Zabbix 6.0.0 n'est pas encore sorti.¶ ::: # 5 Zabbix agent (Windows) # 5 Agent Zabbix (Windows) # 5 Zabbix sender protocol Please refer to the [trapper item](/manual/appendix/items/trapper) page for more information. # 5 Protocole d'envoi Zabbix Veuillez vous référer à la page [Éléments Trapper](/manual/appendix/items/trapper) pour plus d'informations. ### 6.0.13 ### 6.0.13 ### 6.0.14 ### 6.0.14 ### 6.0.15 ### 6.0.15 ### 6.0.3 ### 6.0.3 ### 6.0.7 ### 6.0.7 ### 6.0.9 ### 6.0.9 ##### 64 bit Open MinGW environment (Windows command prompt) and navigate to *build/mingw* directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make PCRE=c:\dev\pcre OPENSSL=c:\dev\openssl ::: noteclassic Both 32- and 64- bit versions can be built on a 64-bit platform, but only a 32-bit version can be built on a 32-bit platform. When working on the 32-bit platform, follow the same steps as for 64-bit version on 64-bit platform. ::: ##### 64 bit Ouvrir l'environnement MinGW (invite de commande Windows) et accéder au répertoire *build/mingw* dans l'arborescence des sources Zabbix. Exécuter : mingw32-make clean mingw32-make PCRE=c:\dev\pcre OPENSSL=c:\dev\openssl ::: noteclassic Les versions 32 et 64 bits peuvent être créées sur une plate-forme 64 bits, mais seule une version 32 bits peut être créée sur une plate-forme 32 bits. Lorsque vous travaillez sur la plate-forme 32 bits, suivez les mêmes étapes que pour la version 64 bits sur la plate-forme 64 bits. ::: # 6 Action log # 6 Journal des actions # 6 Administration # 6 Administration # 6 Discovery #6 Découverte # 6 Discovery of IPMI sensors # 6 Découverte des capteurs IPMI # 6 Elasticsearch setup ::: noteimportant Elasticsearch support is experimental! ::: Zabbix supports the storage of historical data by means of Elasticsearch instead of a database. Users can choose the storage place for historical data between a compatible database and Elasticsearch. The setup procedure described in this section is applicable to Elasticsearch version 7.X. In case an earlier or later version of Elasticsearch is used, some functionality may not work as intended. ::: notewarning If all history data is stored in Elasticsearch, trends are **not** calculated nor stored in the database. With no trends calculated and stored, the history storage period may need to be extended. ::: # 6 Configuration d'Elasticsearch ::: noteimportant La prise en charge d'Elasticsearch est expérimentale ! ::: Zabbix prend en charge le stockage des données historiques au moyen d'Elasticsearch au lieu d'une base de données. Les utilisateurs peuvent choisir le lieu de stockage des données historiques entre une base de données compatible et Elasticsearch. La procédure de configuration décrite dans cette section s'applique à Elasticsearch version 7.X. Si une version antérieure ou ultérieure d'Elasticsearch est utilisée, certaines fonctionnalités peuvent ne pas fonctionner comme prévu. ::: notewarning Si toutes les données d'historique sont stockées dans Elasticsearch, les tendances ne sont **pas** calculées ni stockées dans la base de données. En l'absence de tendances calculées et stockées, la période de stockage de l'historique peut devoir être prolongée. ::: # 6 Encoding of returned values Zabbix server expects every returned text value in the UTF8 encoding. This is related to any type of checks: zabbix agent, ssh, telnet, etc. Different monitored systems/devices and checks can return non-ASCII characters in the value. For such cases, almost all possible zabbix keys contain an additional item key parameter - **<encoding>**. This key parameter is optional but it should be specified if the returned value is not in the UTF8 encoding and it contains non-ASCII characters. Otherwise the result can be unexpected and unpredictable. A description of behavior with different database backends in such cases follows. # 6 Encodage des valeurs renvoyées Le serveur Zabbix attend chaque valeur de texte renvoyée encodée en UTF8. Ceci est lié à tout type de vérification : agent zabbix, ssh, telnet, etc. Différents systèmes/périphériques supervisés et différentes vérifications peuvent renvoyer des caractères non-ASCII dans la valeur. Dans ce cas, presque toutes les clés zabbix possibles contiennent un paramètre de clé d’élément supplémentaire - **<encoding>**. Ce paramètre de clé est facultatif, mais il convient de l'indiquer si la valeur renvoyée ne figure pas dans le codage UTF8 et s'il contient des caractères non-ASCII. Sinon, le résultat peut être inattendu et imprévisible. Vous trouverez ci-dessous une description du comportement avec différents moteurs de base de données. # 6 Event correlation # 6 Corrélation des événements # 6 Favorite maps # 6 Cartes préférées # 6 Header # 6 En-tête # 6 Loadable modules # 6 Modules chargeables # 6 Log file monitoring [comment]: # (tags: logrt, logfile, log) # 6 Supervision des fichiers journaux # 6 Mass update # 6 Modification collective # 6 New template # 6 Nouveau modèle # 6 Page parameters # 6 Paramètres de la page ##### 6 Review and edit configuration files - edit the Zabbix agent configuration file **/usr/local/etc/zabbix\_agentd.conf** You need to configure this file for every host with zabbix\_agentd installed. You must specify the Zabbix server **IP address** in the file. Connections from other hosts will be denied. - edit the Zabbix server configuration file **/usr/local/etc/zabbix\_server.conf** You must specify the database name, user and password (if using any). The rest of the parameters will suit you with their defaults if you have a small installation (up to ten monitored hosts). You should change the default parameters if you want to maximize the performance of Zabbix server (or proxy) though. - if you have installed a Zabbix proxy, edit the proxy configuration file **/usr/local/etc/zabbix\_proxy.conf** You must specify the server IP address and proxy hostname (must be known to the server), as well as the database name, user and password (if using any). ::: noteclassic With SQLite the full path to database file must be specified; DB user and password are not required. ::: ##### 6 Examiner et modifier les fichiers de configuration - éditez le fichier de configuration de l'agent Zabbix **/usr/local/etc/zabbix\_agentd.conf** Vous devez configurer ce fichier pour chaque hôte où zabbix\_agentd est installé. Vous devez spécifier l'**adresse IP** du serveur Zabbix dans le fichier. Les connexions des autres hôtes seront refusées. - éditez le fichier de configuration du serveur Zabbix **/usr/local/etc/zabbix\_server.conf** Vous devez spécifier le nom de la base de données, l'utilisateur et le mot de passe (si vous en utilisez un). Le reste des paramètres devrait vous convenir avec leurs valeurs par défaut si vous avez une petite installation (jusqu'à dix hôtes surveillés). Vous devrez cependant modifier les paramètres par défaut si vous souhaitez optimiser les performances du serveur Zabbix (ou du proxy). - Si vous avez installé un proxy Zabbix, éditez le fichier de configuration du proxy **/usr/local/etc/zabbix\_proxy.conf** Vous devez spécifier l'adresse IP du serveur et le nom d'hôte du proxy (qui doit être connu du serveur), ainsi que le nom de la base de données, l'utilisateur et le mot de passe (si vous en utilisez un). ::: noteclassic Avec SQLite, le chemin complet du fichier de la base de données doit être spécifié ; l'utilisateur de la base de données et le mot de passe ne sont pas obligatoires. ::: ##### 6 Review component configuration parameters Make sure to review [Upgrade notes](/manual/installation/upgrade_notes_600) to check if any changes in the configuration parameters are required. ##### 6 Examen des paramètres de configuration des composants Assurez-vous de consulter les [Notes de mise à jour](/manual/installation/upgrade_notes_600) pour vérifier si des modifications des paramètres de configuration sont nécessaires. ##### 6 Review component configuration parameters See the upgrade notes for details on [mandatory changes](/manual/installation/upgrade_notes_600#configuration_parameters). ##### 6 Exam des paramètres de configuration des composants Consultez les notes de mise à niveau pour plus de détails sur les [modifications obligatoires](/manual/installation/upgrade_notes_600#configuration_parameters) (le cas échéant). ##### 6 Review component configuration parameters See the upgrade notes for details on [mandatory changes](/manual/installation/upgrade_notes_600#configuration_parameters) (if any). For new optional parameters, see the [What's new](/manual/introduction/whatsnew600#configuration_parameters) section. ##### 6 Exam des paramètres de configuration des composants Consultez les notes de mise à niveau pour plus de détails sur les [modifications obligatoires](/manual/installation/upgrade_notes_600#configuration_parameters) (le cas échéant). Pour les nouveaux paramètres facultatifs, consultez la section [Quoi de neuf](/manual/introduction/whatsnew600#configuration_parameters). # 6 Sender # 6 Sender ##### 6 Start new Zabbix binaries Start new binaries. Check log files to see if the binaries have started successfully. Zabbix server will automatically upgrade the database. When starting up, Zabbix server reports the current (mandatory and optional) and required database versions. If the current mandatory version is older than the required version, Zabbix server automatically executes the required database upgrade patches. The start and progress level (percentage) of the database upgrade is written to the Zabbix server log file. When the upgrade is completed, a "database upgrade fully completed" message is written to the log file. If any of the upgrade patches fail, Zabbix server will not start. Zabbix server will also not start if the current mandatory database version is newer than the required one. Zabbix server will only start if the current mandatory database version corresponds to the required mandatory version. 8673:20161117:104750.259 current database version (mandatory/optional): 03040000/03040000 8673:20161117:104750.259 required mandatory version: 03040000 Before you start the server: - Make sure the database user has enough permissions (create table, drop table, create index, drop index) - Make sure you have enough free disk space. ##### 6 Démarrer les nouveaux binaires Zabbix Démarrez les nouveaux binaires. Vérifiez les fichiers de logs pour voir si les fichiers binaires ont démarré avec succès. Le serveur Zabbix mettra automatiquement à jour la base de données. Au démarrage, le serveur Zabbix signale les versions de base de données actuelles (obligatoires et facultatives) et requises. Si la version actuelle est antérieure à la version requise, le serveur Zabbix exécute automatiquement les correctifs requis de mise à jour de base de données. La progression (en pourcentage) de la mise à jour de la base de données est écrite dans le fichier de logs du serveur Zabbix. Lorsque la mise à jour est terminée, un message "Mise à jour de la base de données entièrement terminée" est écrit dans le fichier de logs. Si l'un des correctifs de mise à jour échoue, le serveur Zabbix ne démarre pas. Le serveur Zabbix ne démarrera pas non plus si la version de base de données actuelle est plus récente que celle requise. Le serveur Zabbix démarre uniquement si la version de base de données obligatoire actuelle correspond à la version obligatoire requise. 8673:20161117:104750.259 current database version (mandatory/optional): 03040000/03040000 8673:20161117:104750.259 required mandatory version: 03040000 Avant de démarrer le serveur : - Assurez-vous que l'utilisateur de la base de données dispose des autorisations nécessaires (créer une table, supprimer une table, créer un index, supprimer un index) ; - Assurez-vous d'avoir suffisamment d'espace disque libre. # 6 Supported functions Click on the respective function group to see more details. |Function group|Functions| |--|--------| |[Aggregate functions](/manual/appendix/functions/aggregate)|avg, bucket\_percentile, count, histogram\_quantile, item\_count, kurtosis, mad, max, min, skewness, stddevpop, stddevsamp, sum, sumofsquares, varpop, varsamp| |[Bitwise functions](/manual/appendix/functions/bitwise)|bitand, bitlshift, bitnot, bitor, bitrshift, bitxor| |[Date and time functions](/manual/appendix/functions/time)|date, dayofmonth, dayofweek, now, time| |[History functions](/manual/appendix/functions/history)|change, changecount, count, countunique, find, first, fuzzytime, last, logeventid, logseverity, logsource, monodec, monoinc, nodata, percentile, rate| |[Trend functions](/manual/appendix/functions/trends)|baselinedev, baselinewma, trendavg, trendcount, trendmax, trendmin, trendstl, trendsum| |[Mathematical functions](/manual/appendix/functions/math)|abs, acos, asin, atan, atan2, avg, cbrt, ceil, cos, cosh, cot, degrees, e, exp, expm1, floor, log, log10, max, min, mod, pi, power, radians, rand, round, signum, sin, sinh, sqrt, sum, tan, truncate| |[Operator functions](/manual/appendix/functions/operator)|between, in| |[Prediction functions](/manual/appendix/functions/prediction)|forecast, timeleft| |[String functions](/manual/appendix/functions/string)|ascii, bitlength, bytelength, char, concat, insert, left, length, ltrim, mid, repeat, replace, right, rtrim, trim| These functions are supported in [trigger expressions](/manual/config/triggers/expression) and [calculated items](/manual/config/items/itemtypes/calculated). # 6 Fonctions prises en charge Cliquez sur le groupe de fonctions respectif pour voir plus de détails. |Groupe de fonctions|Fonctions| |--|--------| |[Fonctions d'agrégation](/manual/appendix/functions/aggregate)|avg, bucket\_percentile, count, histogram\_quantile, item\_count, kurtosis, mad, max, min, skewness, stddevpop, stddevsamp, sum, sumofsquares, varpop, varsamp| |[Fonctions binaires](/manual/appendix/functions/bitwise)|bitand, bitlshift, bitnot, bitor, bitrshift, bitxor| |[Fonctions de date et d'heure](/manual/appendix/functions/time)|date, dayofmonth, dayofweek, now, time| |[Fonctions d'historique](/manual/appendix/functions/history)|change, changecount, count, countunique, find, first, fuzzytime, last, logeventid, logseverity, logsource, monodec, monoinc, nodata, percentile, rate| |[Fonctions de tendance](/manual/appendix/functions/trends)|baselinedev, baselinewma, trendavg, trendcount, trendmax, trendmin, trendstl, trendsum| |[Fonctions mathématiques](/manual/appendix/functions/math)|abs, acos, asin, atan, atan2, avg, cbrt, ceil, cos, cosh, cot, degrees, e, exp, expm1, floor, log, log10, max, min, mod, pi, power, radians, rand, round, signum, sin, sinh, sqrt, sum, tan, truncate| |[Fonctions opérateur](/manual/appendix/functions/operator)|between, in| |[Fonctions de prédiction](/manual/appendix/functions/prediction)|forecast, timeleft| |[Fonctions de chaîne](/manual/appendix/functions/string)|ascii, bitlength, bytelength, char, concat, insert, left, length, ltrim, mid, repeat, replace, right, rtrim, trim| Ces fonctions sont prises en charge dans les [expressions de déclencheur](/manual/config/triggers/expression) et les [éléments calculés](/manual/config/items/itemtypes/calculated). # 6 Tagging # 6 Balisage # 6 Unstable releases # 6 Versions instables # 6 Users # 6 Utilisateurs # 6 Web interface installation This section provides step-by-step instructions for installing Zabbix web interface. Zabbix frontend is written in PHP, so to run it a PHP supported webserver is needed. # 6 Installation de l'interface Web Cette section fournit des instructions étape par étape pour installer l'interface Web de Zabbix. L'interface Zabbix est écrite en PHP, donc pour l'exécuter, un serveur Web prenant en charge PHP est nécessaire. # 6 What's new in Zabbix 6.0.1 # 6 Quoi de neuf dans Zabbix 6.0.1 # 6 Zabbix agent 2 (Windows) # 6 Agent Zabbix 2 (Windows) # 6. Zabbix appliance # 6. Appliance Zabbix # 7 Calculated items # 7 Éléments calculés # 7. Configuration Please use the sidebar to access content in the Configuration section. # 7. Configuration Veuillez utiliser la barre latérale pour accéder au contenu de la section Configuration. # 7 Definitions # 7 Définitions # 7 Discovery # 7 Découverte # 7 Discovery of systemd services # 7 Découverte des services systemd # 7 Geomap # 7 Géocarte # 7 Get # 7 Get ##### 7 Install new Zabbix web interface The minimum required PHP version is 7.2.5. Update if needed and follow [installation instructions](/manual/installation/frontend). ##### 7 Installation de la nouvelle interface Web Zabbix La version PHP minimale requise est 7.2.5. Mettez à jour si nécessaire et suivez les [instructions d'installation](/manual/installation/frontend). # 7 Media types # 7 Types de médias # 7 Notifications # 7 Notifications # 7 Operator functions All functions listed here are supported in: - [Trigger expressions](/manual/config/triggers/expression) - [Calculated items](/manual/config/items/itemtypes/calculated) Some general notes on function parameters: - Function parameters are separated by a comma - Expressions are accepted as parameters |FUNCTION|<|<| |--|--|--| |**Description**|**Function-specific parameters**|**Comments**| |**between** (value,min,max)|<|<| |Check if a value belongs to the given range.|**value** - value to check<br>**min** - minimum value<br>**max** - maximum value|Supported value types: integer, float<br><br>Returns:<br>1 - in range<br>0 - otherwise<br><br>Example:<br>=> **between**(last(/host/key),**1**,**10**)=1 - trigger if the value is between 1 and 10.| |**in** (value,value1,value2,...valueN)|<|<| |Check if a value is equal to at least one of the listed values.|**value** - value to check<br>**value1,value2,...valueN** - listed values (string values must be double-quoted)|Supported value types: all<br><br>Returns:<br>1 - if equal<br>0 - otherwise<br><br>The value is compared to the listed values as numbers, if all of these values can be converted to numeric; otherwise compared as strings.<br><br>Example:<br>=> **in**(last(/host/key),**5**,**10**)=1 - trigger if the last value is equal to 5 or 10<br>=> **in**(**"text"**, last(/host/key),last(/host/key,\#2))=1 - trigger if "text" is equal to either of the last 2 values.| # 7 Fonctions opérateur Toutes les fonctions répertoriées ici sont prises en charge dans : - [Expressions de déclenchement](/manual/config/triggers/expression) - [Éléments calculés](/manual/config/items/itemtypes/calculated) Quelques notes générales sur les paramètres de fonction : - Les paramètres de fonction sont séparés par une virgule - Les expressions sont acceptées comme paramètres |FONCTION|<|<| |--|--|--| |**Description**|**Paramètres spécifiques à la fonction**|**Commentaires**| |**between** (valeur,min,max)|<|<| |Vérifier si une valeur appartient à la plage donnée.|**valeur** - valeur à vérifier<br>**min** - valeur minimale<br>**max** - valeur maximale|Types de valeur pris en charge : entier, float<br><br>Renvoi :<br>1 - dans la plage<br>0 - sinon<br><br>Exemple :<br>=> **between**(last(/host/key),**1**,**10**)=1 - se déclenche si la valeur est comprise entre 1 et 10.| |**in** (valeur,valeur1,valeur2,...valeurN)|<|<| |Vérifier si une valeur est égale à au moins une des valeurs répertoriées.|**valeur** - valeur à vérifier<br>**valeur1,valeur2,...valeurN** - valeurs répertoriées (les valeurs de chaîne doivent être doubles guillemets)|Types de valeurs pris en charge : tous<br><br>Renvoi :<br>1 - si égal<br>0 - sinon<br><br>La valeur est comparée aux valeurs répertoriées sous forme de nombres, si toutes ces valeurs peuvent être converties en numérique ; sinon comparés à des chaînes.<br><br>Exemple :<br>=> **in**(last(/host/key),**5**,**10**)=1 - déclencheur si le la dernière valeur est égale à 5 ou 10<br>=> **in**(**"text"**, last(/host/key),last(/host/key,\#2))=1 - déclencher si "text" est égal à l'une des 2 dernières valeurs.| # 7 Predictive trigger functions # 7 Fonctions prédictives de déclenchement # 7 Real-time export of events, item values, trends # 7 Exportation en temps réel des événements, des valeurs des éléments, des tendances # 7 Real-time export protocol This section presents details of the [real-time export](/manual/appendix/install/real_time_export) protocol in a newline-delimited JSON format for: - [trigger events](#trigger_events) - [item values](#item_values) - [trends](#trends) All files have a .ndjson extension. Each line of the export file is a JSON object. # 7 Protocole d'exportation en temps réel Cette section présente les détails du protocole d'[exportation en temps réel](/manual/appendix/install/real_time_export) dans un format JSON délimité par une nouvelle ligne pour les : - [évènements de déclencheur](#trigger_events) - [valeurs d'éléments](#item_values) - [tendances](#trends) Tous les fichiers ont une extension .ndjson. Chaque ligne du fichier d'exportation est un objet JSON. # 7 Services # 7 Services ##### 7 Start Zabbix processes Start the updated Zabbix components. # systemctl start zabbix-server # systemctl start zabbix-proxy # systemctl start zabbix-agent # systemctl start zabbix-agent2 ##### 7 Démarrage des processus Zabbix Démarrez les composants Zabbix mis à jour. # systemctl start zabbix-server # systemctl start zabbix-proxy # systemctl start zabbix-agent # systemctl start zabbix-agent2 # 7 Upgrade procedure [comment]: # (tags: upgrade) # 7 Procédure de mise à niveau # 7 Visualization # 7 Visualization # 7 What's new in Zabbix 6.0.2 # 7 Quoi de neuf dans Zabbix 6.0.2 # 7 Windows performance counters # 7 Compteurs de performances Windows # 7 Zabbix agent 2 plugins # 7 Plugins de l'agent Zabbix 2 ##### 8 Clear web browser cookies and cache After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly. ##### 8 Suppression des cookies et du cache du navigateur Web Après la mise à niveau, vous devrez peut-être effacer les cookies du navigateur Web et le cache du navigateur Web pour que l'interface Web de Zabbix fonctionne correctement. ##### 8 Clear web browser cookies and cache After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly. ##### 8 Effacer les cookies et le cache du navigateur Web Après la mise à niveau, vous devrez peut-être effacer les cookies du navigateur Web et le cache du navigateur Web pour que l'interface Web de Zabbix fonctionne correctement. ##### 8 Clear web browser cookies and cache After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly. ##### 8 Suppression des cookies et du cache du navigateur Web Après la mise à niveau, vous devrez peut-être effacer les cookies du navigateur Web et le cache du navigateur Web pour que l'interface Web de Zabbix fonctionne correctement. ##### 8 Clear web browser cookies and cache After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly. ##### 8 Effacer les cookies et le cache du navigateur Après la mise à jour, vous devrez peut-être effacer les cookies et le cache du navigateur Web pour que l'interface Web de Zabbix fonctionne correctement. # 8 Creating your own theme # 8 Créer votre propre thème # 8 Discovery of Windows services # 8 Découverte des services Windows # 8 Distribution-specific notes on setting up Nginx for Zabbix # 8 Notes spécifiques à la distribution sur la configuration de Nginx pour Zabbix # 8 Graph # 8 Graphique # 8 Internal checks # 8 Vérifications internes # 8 JS # 8 JS # 8 Mass update # 8 Mise à jour de masse # 8 Prediction functions All functions listed here are supported in: - [Trigger expressions](/manual/config/triggers/expression) - [Calculated items](/manual/config/items/itemtypes/calculated) Some general notes on function parameters: - Function parameters are separated by a comma - Optional function parameters (or parameter parts) are indicated by `<` `>` - Function-specific parameters are described with each function - `/host/key` and `(sec|#num)<:time shift>` parameters must never be quoted # 8 Fonctions prédictives Toutes les fonctions répertoriées ici sont prises en charge dans : - [Expressions de déclenchement](/manual/config/triggers/expression) - [Éléments calculés](/manual/config/items/itemtypes/calculated) Quelques notes générales sur les paramètres de fonction : - Les paramètres de fonction sont séparés par une virgule - Les paramètres de fonction optionnels (ou parties de paramètres) sont indiqués par `<` `>` - Les paramètres spécifiques à la fonction sont décrits avec chaque fonction - Les paramètres `/host/key` et `(sec|#num)<:time shift>` ne doivent jamais être entre guillemets # 8 Scripts # 8 Scripts # 8 Sensor Each sensor chip gets its own directory in the sysfs /sys/devices tree. To find all sensor chips, it is easier to follow the device symlinks from /sys/class/hwmon/hwmon\*, where \* is a real number (0,1,2,...). The sensor readings are located either in /sys/class/hwmon/hwmon\*/ directory for virtual devices, or in /sys/class/hwmon/hwmon\*/device directory for non-virtual devices. A file, called name, located inside hwmon\* or hwmon\*/device directories contains the name of the chip, which corresponds to the name of the kernel driver used by the sensor chip. There is only one sensor reading value per file. The common scheme for naming the files that contain sensor readings inside any of the directories mentioned above is: <type><number>\_<item>, where - **type** - for sensor chips is "in" (voltage), "temp" (temperature), "fan" (fan), etc., - **item** - "input" (measured value), "max" (high threshold), "min" (low threshold), etc., - **number** - always used for elements that can be present more than once (usually starts from 1, except for voltages which start from 0). If files do not refer to a specific element they have a simple name with no number. The information regarding sensors available on the host can be acquired using **sensor-detect** and **sensors** tools (lm-sensors package: <http://lm-sensors.org/>). **Sensors-detect** helps to determine which modules are necessary for available sensors. When modules are loaded the **sensors** program can be used to show the readings of all sensor chips. The labeling of sensor readings, used by this program, can be different from the common naming scheme (<type><number>\_<item> ): - if there is a file called <type><number>\_label, then the label inside this file will be used instead of <type><number><item> name; - if there is no <type><number>\_label file, then the program searches inside the /etc/sensors.conf (could be also /etc/sensors3.conf, or different) for the name substitution. This labeling allows user to determine what kind of hardware is used. If there is neither <type><number>\_label file nor label inside the configuration file the type of hardware can be determined by the name attribute (hwmon\*/device/name). The actual names of sensors, which zabbix\_agent accepts, can be obtained by running **sensors** program with -u parameter (**sensors -u**). In **sensor** program the available sensors are separated by the bus type (ISA adapter, PCI adapter, SPI adapter, Virtual device, ACPI interface, HID adapter). # 8 Capteur Chaque puce de capteur obtient son propre répertoire dans l’arborescence /sys/devices. Pour trouver toutes les puces de capteur, il est plus facile de suivre les liens symboliques du périphérique à partir de /sys/class/hwmon/hwmon\*, où \* est un nombre réel (0,1,2, ...). Les lectures de capteur se trouvent dans le répertoire /sys/class/hwmon/hwmon\*/ pour les périphériques virtuels ou dans le répertoire /sys/class/hwmon/hwmon\*/device pour les périphériques non virtuels. Un fichier, nommé name, situé dans les répertoires hwmon\* ou hwmon\*/device contient le nom de la puce, qui correspond au nom du pilote du noyau utilisé par la puce du capteur. Il n'y a qu'une seule valeur de lecture de capteur par fichier. Le schéma commun pour nommer les fichiers contenant des lectures de capteur dans l’un des répertoires mentionnés ci-dessus est le suivant : <type><numéro>\_<élément>, où - **type** - pour les puces de capteur est "in" (voltage), "temp" (température), "fan" (ventilateur), etc., - **élément** - "input" (valeur mesurée), "max" (seuil haut), "min" (seuil bas), etc., - **numéro** - toujours utilisé pour les éléments pouvant être présents plusieurs fois (commence généralement à 1, sauf pour les voltages qui commencent à 0). Si les fichiers ne font pas référence à un élément spécifique, ils portent un nom simple, sans numéro. Les informations concernant les capteurs disponibles sur l’hôte peuvent être acquises à l’aide des outils **sensor-detect** et **sensor** (package lm-capteurs : <http://lm-sensors.org/>). **Sensors-detect** permet de déterminer quels modules sont nécessaires pour les capteurs disponibles. Lorsque les modules sont chargés, le programme **sensor** peut être utilisé pour afficher les lectures de toutes les puces de capteur. L'étiquetage des lectures de capteur, utilisé par ce programme, peut être différent du schéma de nommage commun (<type><numéro>\_ élément>) : - s'il y a un fichier appelé <type><numéro>\_label, alors le label dans ce fichier sera utilisé au lieu du nom <type><numéro><élément> ; - s'il n'y a pas de fichier <type><numéro>\_label, alors le programme cherche dans /etc/sensors.conf (peut être aussi /etc/sensors3.conf, ou autre) pour la substitution de nom. Cet étiquetage permet à l’utilisateur de déterminer le type de matériel utilisé. S'il n'y a ni fichier <type><numéro>\_label ni étiquette dans le fichier de configuration, le type de matériel peut être déterminé par l'attribut name (hwmon\*/device/name). Les noms réels des capteurs, acceptés par zabbix\_agent, peuvent être obtenus en exécutant le programme **sensors** avec le paramètre -u (**sensors -u**). Dans le programme **sensor** les capteurs disponibles sont séparés par le type de bus (ISA adapter, PCI adapter, SPI adapter, Virtual device, ACPI interface, HID adapter). # 8. Service monitoring # 8. Surveillance des services # 8 Templates # 8 Modèles # 8 What's new in Zabbix 6.0.3 # 8 Quoi de neuf dans Zabbix 6.0.3 # 8 Zabbix Java gateway If you use `startup.sh` and `shutdown.sh` scripts for starting [Zabbix Java gateway](/manual/concepts/java), then you can specify the necessary configuration parameters in the `settings.sh` file. The startup and shutdown scripts source the settings file and take care of converting shell variables (listed in the first column) to Java properties (listed in the second column). If you start Zabbix Java gateway manually by running `java` directly, then you specify the corresponding Java properties on the command line. |Variable|Property|Mandatory|Range|Default|Description| |--------|--------|---------|-----|-------|-----------| |LISTEN\_IP|zabbix.listenIP|no| |0.0.0.0|IP address to listen on.| |LISTEN\_PORT|zabbix.listenPort|no|1024-32767|10052|Port to listen on.| |PID\_FILE|zabbix.pidFile|no| |/tmp/zabbix\_java.pid|Name of PID file. If omitted, Zabbix Java Gateway is started as a console application.| |PROPERTIES\_FILE|zabbix.propertiesFile|no| | |Name of properties file. Can be used to set additional properties using a key-value format in such a way that they are not visible on a command line or to overwrite existing ones.<br>For example: "javax.net.ssl.trustStorePassword=<password>"| |START\_POLLERS|zabbix.startPollers|no|1-1000|5|Number of worker threads to start.| |TIMEOUT|zabbix.timeout|no|1-30|3|How long to wait for network operations.| ::: notewarning Port 10052 is not [IANA registered](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). ::: # 8 Passerelle Java Zabbix Si vous utilisez les scripts `startup.sh` et `shutdown.sh` pour démarrer [la passerelle Java Zabbix](/fr/manual/concepts/java), alors vous pouvez spécifier les paramètres de configuration nécessaires dans le fichier `settings.sh`. Les scripts de démarrage et d'arrêt extraient le fichier de paramètres et prennent en charge la conversion des variables shell (répertoriées dans la première colonne) en propriétés Java (répertoriées dans la deuxième colonne). Si vous démarrez manuellement la passerelle Java Zabbix en exécutant directement `java`, indiquez les propriétés Java correspondantes sur la ligne de commande. |Variable|Propriété|Obligatoire|Range|Défaut|Description| |--------|-----------|-----------|-----|-------|-----------| |LISTEN\_IP|zabbix.listenIP|non| |0.0.0.0|Adresse IP à écouter.| |LISTEN\_PORT|zabbix.listenPort|non|1024-32767|10052|Port à écouter.| |PID\_FILE|zabbix.pidFile|non| |/tmp/zabbix\_java.pid|Nom du fichier PID. S'il est omis, la passerelle Java Zabbix est démarrée en tant qu'application console.| |PROPERTIES\_FILE|zabbix.propertiesFile|non| | |Nom du fichier de propriétés. Peut être utilisé pour définir des propriétés supplémentaires à l'aide d'un format clé-valeur de manière à ce qu'elles ne soient pas visibles sur une ligne de commande ou pour écraser celles existantes.<br>Par exemple : "javax.net.ssl.trustStorePassword=<password>"| |START\_POLLERS|zabbix.startPollers|non|1-1000|5|Nombre de threads de travail à démarrer.| |TIMEOUT|zabbix.timeout|non|1-30|3|Combien de temps attendre pour les opérations du réseau.| ::: notewarning Le port 10052 n'est pas [enregistré IANA](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). ::: # 9 Debug mode # 9 Mode Debug # 9 Discovery of Windows performance counter instances # 9 Découverte des instances de compteur de performance Windows # 9 Graph (classic) # 9 Graphique (classique) # 9 Notes on memtype parameter in proc.mem items # 9 Notes sur le paramètre memtype dans les éléments proc.mem # 9 Queue # 9 File d'attente # 9 Running agent as root Since Zabbix **5.0.0**, the systemd service file for Zabbix agent in [official packages](https://www.zabbix.com/download) explicitly includes directives for `User` and `Group`. Both are set to `zabbix`. It is no longer possible to configure which user Zabbix agent runs as via `zabbix_agentd.conf` file, because the agent will bypass this configuration and run as the user specified in the systemd service file. To run Zabbix agent as root you need to make the modifications described below. # 9 Exécution de l'agent en tant que root À partir de la version **5.0.0**, le fichier de service systemd pour l'agent Zabbix dans les [paquets officiels](https://www.zabbix.com/download)) inclut explicitement des directives pour `User` et `Group`. Les deux sont définis sur `zabbix`. Il n'est plus possible de configurer l'utilisateur sous lequel l'agent Zabbix s'exécute via le fichier `zabbix_agentd.conf`, car l'agent contournera cette configuration et s'exécutera sous l'utilisateur spécifié dans le fichier de service systemd. Pour exécuter l'agent Zabbix en tant que root, vous devez apporter les modifications décrites ci-dessous. # 9 SSH checks # 9 Vérifications SSH # 9 String functions All functions listed here are supported in: - [Trigger expressions](/manual/config/triggers/expression) - [Calculated items](/manual/config/items/itemtypes/calculated) Some general notes on function parameters: - Function parameters are separated by a comma - Expressions are accepted as parameters - String parameters must be double-quoted; otherwise they might get misinterpreted - Optional function parameters (or parameter parts) are indicated by `<` `>` |FUNCTION|<|<| |--|--|--| |**Description**|**Function-specific parameters**|**Comments**| |**ascii** (value)|<|<| |The ASCII code of the leftmost character of the value.|**value** - value to check|Supported value types: string, text, log<br><br>For example, a value like 'Abc' will return '65' (ASCII code for 'A').<br><br>Example:<br>=> **ascii**(last(/host/key))| |**bitlength** (value)|<|<| |The length of value in bits.|**value** - value to check|Supported value types: string, text, log, integer<br><br>Example:<br>=> **bitlength**(last(/host/key))| |**bytelength** (value)|<|<| |The length of value in bytes.|**value** - value to check|Supported value types: string, text, log, integer<br><br>Example:<br>=> **bytelength**(last(/host/key))| |**char** (value)|<|<| |Return the character by interpreting the value as ASCII code.|**value** - value to check|Supported value types: integer<br><br>The value must be in the 0-255 range. For example, a value like '65' (interpreted as ASCII code) will return 'A'.<br><br>Example:<br>=> **char**(last(/host/key))| |**concat** (<value1>,<value2>,...)|<|<| |The string resulting from concatenating referenced item values or constant values. |**value** - a value returned by one of the history functions or a constant value (string, integer, or float number)|Supported value types: string, text, log, float, integer <br><br>For example, a value like 'Zab' concatenated to 'bix' (the constant string) will return 'Zabbix'. <br><br> Must contain at least two parameters. <br><br>Examples:<br>=> **concat**(last(/host/key),**"bix"**)<br>=> **concat**("1 min: ",last(/host/system.cpu.load[all,avg1]),", 15 min: ",last(/host/system.cpu.load[all,avg15])) | |**insert** (value,start,length,replacement)|<|<| |Insert specified characters or spaces into the character string beginning at the specified position in the string.|**value** - value to check<br>**start** - start position<br>**length** - positions to replace<br>**replacement** - replacement string|Supported value types: string, text, log<br><br>For example, a value like 'Zabbbix' will be replaced by 'Zabbix' if 'bb' (starting position 3, positions to replace 2) is replaced by 'b'.<br><br>Example:<br>=> **insert**(last(/host/key),**3**,**2**,**"b"**)| |**left** (value,count)|<|<| |The leftmost characters of the value.|**value** - value to check<br>**count** - number of characters to return|Supported value types: string, text, log<br><br>For example, you may return 'Zab' from 'Zabbix' by specifying 3 leftmost characters to return.<br><br>Example:<br>=> **left**(last(/host/key),**3**) - return three leftmost characters<br><br>See also right().| |**length** (value)|<|<| |The length of value in characters.|**value** - value to check|Supported value types: str, text, log<br><br>Example:<br>=> **length**(last(/host/key)) → length of the latest value<br>=> **length**(last(/host/key,\#3)) → length of the third most recent value<br>=> **length**(last(/host/key,\#1:now-1d)) → length of the most recent value one day ago| |**ltrim** (value,<chars>)|<|<| |Remove specified characters from the beginning of string.|**value** - value to check<br>**chars** - (optional) specify characters to remove<br><br>Whitespace is left-trimmed by default (if no optional characters are specified).|Supported value types: string, text, log<br><br>Example:<br>=> **ltrim**(last(/host/key)) - remove whitespace from the beginning of string<br>=> **ltrim**(last(/host/key),**"Z"**) - remove any 'Z' from the beginning of string<br>=> **ltrim**(last(/host/key),**" Z"**) - remove any space and 'Z' from the beginning of string<br><br>See also: rtrim(), trim()| |**mid** (value,start,length)|<|<| |Return a substring of N characters beginning at the character position specified by 'start'.|**value** - value to check<br>**start** - start position of substring<br>**length** - positions to return in substring|Supported value types: string, text, log<br><br>For example, it is possible return 'abbi' from a value like 'Zabbix' if starting position is 2, and positions to return is 4).<br><br>Example:<br>=> **mid**(last(/host/key),**2**,**4**)="abbi"| |**repeat** (value,count)|<|<| |Repeat a string.|**value** - value to check<br>**count** - number of times to repeat|Supported value types: string, text, log<br><br>Example:<br>=> **repeat**(last(/host/key),**2**) - repeat the value two times| |**replace** (value,pattern,replacement)|<|<| |Find pattern in the value and replace with replacement. All occurrences of the pattern will be replaced.|**value** - value to check<br>**pattern** - pattern to find<br>**replacement** - string to replace the pattern with|Supported value types: string, text, log<br><br>Example:<br>=> **replace**(last(/host/key),**"ibb"**,**"abb"**) - replace all 'ibb' with 'abb'| |**right** (value,count)|<|<| |The rightmost characters of the value.|**value** - value to check<br>**count** - number of characters to return|Supported value types: string, text, log<br><br>For example, you may return 'bix' from 'Zabbix' by specifying 3 rightmost characters to return.<br><br>Example:<br>=> **right**(last(/host/key),**3**) - return three rightmost characters<br><br>See also left().| |**rtrim** (value,<chars>)|<|<| |Remove specified characters from the end of string.|**value** - value to check<br>**chars** - (optional) specify characters to remove<br><br>Whitespace is right-trimmed by default (if no optional characters are specified).|Supported value types: string, text, log<br><br>Example:<br>=> **rtrim**(last(/host/key)) - remove whitespace from the end of string<br>=> **rtrim**(last(/host/key),**"x"**) - remove any 'x' from the end of string<br>=> **rtrim**(last(/host/key),**"x "**) - remove any 'x' or space from the end of string<br><br>See also: ltrim(), trim()| |**trim** (value,<chars>)|<|<| |Remove specified characters from the beginning and end of string.|**value** - value to check<br>**chars** - (optional) specify characters to remove<br><br>Whitespace is trimmed from both sides by default (if no optional characters are specified).|Supported value types: string, text, log<br><br>Example:<br>=> **trim**(last(/host/key)) - remove whitespace from the beginning and end of string<br>=> **trim**(last(/host/key),**"\_"**) - remove '\_' from the beginning and end of string<br><br>See also: ltrim(), rtrim()| # 9 Fonctions de chaîne Toutes les fonctions répertoriées ici sont prises en charge dans : - [Expressions de déclenchement](/manual/config/triggers/expression) - [Éléments calculés](/manual/config/items/itemtypes/calculated) Quelques notes générales sur les paramètres de fonction : - Les paramètres de fonction sont séparés par une virgule - Les expressions sont acceptées comme paramètres - Les paramètres de chaîne doivent être entre guillemets doubles ; sinon ils pourraient être mal interprétés - Les paramètres de fonction optionnels (ou parties de paramètres) sont indiqués par `<` `>` |FONCTION|<|<| |--|--|--| |**Description**|**Paramètres spécifiques à la fonction**|**Commentaires**| |**ascii** (valeur)|<|<| |Le code ASCII du caractère le plus à gauche de la valeur.|**valeur** - valeur à vérifier|Types de valeur pris en charge : chaîne, texte, journal<br><br>Par exemple, une valeur comme 'Abc' renverra '65 ' (code ASCII pour 'A').<br><br>Exemple :<br>=> **ascii**(last(/host/key))| |**bitlength** (valeur)|<|<| |La longueur de la valeur en bits.|**valeur** - valeur à vérifier|Types de valeur pris en charge : chaîne, texte, journal, entier<br><br>Exemple :<br>=> **bitlength**(last(/host/key))| |**bytelength** (valeur)|<|<| |La longueur de la valeur en octets.|**valeur** - valeur à vérifier|Types de valeur pris en charge : chaîne, texte, journal, entier<br><br>Exemple :<br>=> **bytelength**(last(/host/key))| |**char** (value)|<|<| |Renvoyer le caractère en interprétant la valeur comme un code ASCII.|**valeur** - valeur à vérifier|Types de valeur pris en charge : entier<br><br>La valeur doit être comprise entre 0 et 255. Par exemple, une valeur comme '65' (interprétée comme un code ASCII) renverra 'A'.<br><br>Exemple :<br>=> **char**(last(/host/key))| |**concat** (\<valeur1\>,\<valeur2\>,...)|<|<| |La chaîne résultant de la concaténation de valeurs d'éléments référencés ou de valeurs constantes. |**valeur** : une valeur renvoyée par l'une des fonctions d'historique ou une valeur constante (chaîne, entier ou nombre flottant)|Types de valeur pris en charge : chaîne, texte, journal, flottant, entier <br><br>Pour Par exemple, une valeur comme 'Zab' concaténée à 'bix' (la chaîne constante) renverra 'Zabbix'. <br><br> Doit contenir au moins deux paramètres. <br><br>Exemples :<br>=> **concat**(last(/host/key),**"bix"**)<br>=> **concat**("1 min: ",last(/host/system.cpu.load[all,avg1]),", 15 min: ",last(/host/system.cpu.load[all,avg15])) | |**insert** (valeur,début,longueur,remplacement)|<|<| |Insère des caractères ou des espaces spécifiés dans la chaîne de caractères en commençant à la position spécifiée dans la chaîne.|**valeur** - valeur à vérifier<br>**début** - position de début<br>**longueur** - positions à remplacer<br>**remplacement** - chaîne de remplacement|Types de valeurs pris en charge : chaîne, texte, journal<br><br>Par exemple, une valeur comme 'Zabbbix' sera remplacée par 'Zabbix' si 'bb' ( position de départ 3, positions pour remplacer 2) est remplacée par 'b'.<br><br>Exemple :<br>=> **insert**(last(/host/key),**3**,**2**,**"b"**)| |**left** (valeur,compte)|<|<| |Les caractères les plus à gauche de la valeur.|**valeur** - valeur à vérifier<br>**compte** - nombre de caractères à renvoyer|Types de valeur pris en charge : chaîne, texte, journal<br><br>Par exemple , vous pouvez renvoyer 'Zab' à partir de 'Zabbix' en spécifiant 3 caractères les plus à gauche à renvoyer.<br><br>Exemple :<br>=> **left**(last(/host/key),**3**) - renvoie les trois caractères les plus à gauche<br><br>Voir aussi right().| |**length** (valeur)|<|<| |La longueur de la valeur en caractères.|**valeur** - valeur à vérifier|Types de valeur pris en charge : chaîne, texte, journal<br><br>Exemple :<br>=> **length**(last(/ host/key)) → longueur de la dernière valeur<br>=> **length**(last(/host/key,\#3)) → longueur de la troisième valeur la plus récente<br>=> **length **(last(/host/key,\#1:now-1d)) → longueur de la valeur la plus récente il y a un jour| |**ltrim** (valeur,<caractères>)|<|<| |Supprime les caractères spécifiés du début de la chaîne.|**valeur** - valeur à vérifier<br>**caractères** - (facultatif) spécifiez les caractères à supprimer<br><br>Les espaces blancs sont coupés à gauche par défaut ( si aucun caractère facultatif n'est spécifié).|Types de valeur pris en charge : chaîne, texte, journal<br><br>Exemple :<br>=> **ltrim**(last(/host/key)) - supprime les espaces blancs du début de chaîne<br>=> **ltrim**(last(/host/key),**"Z"**) - supprime tout 'Z' du début de chaîne<br>=> **ltrim* *(last(/host/key),**" Z"**) - supprime tout espace et 'Z' au début de la chaîne<br><br>Voir aussi : rtrim(), trim()| |**mid** (valeur,début,longueur)|<|<| |Renvoie une sous-chaîne de N caractères commençant à la position de caractère spécifiée par 'début'.|**valeur** - valeur à vérifier<br>**début** - position de début de la sous-chaîne<br>**longueur** - positions à renvoyer dans la sous-chaîne|Types de valeurs pris en charge : chaîne, texte, journal).<br><br>Exemple :<br>=> **mid**(last(/host/key),**2**,**4**)="abbi"| |**repeat** (value,count)|<|<| |Repeat a string.|**value** - value to check<br>**count** - number of times to repeat|Supported value types: string, text, log<br><br>Example:<br>=> **repeat**(last(/host/key),**2**) - repeat the value two times| |**replace** (valeur,modèle,remplacement)|<|<| |Recherchez le motif dans la valeur et remplacez-le par remplacement. Toutes les occurrences du modèle seront remplacées.|**valeur** - valeur à vérifier<br>**modèle** - modèle à rechercher<br>**remplacement** - chaîne pour remplacer le modèle par|Types de valeur pris en charge : chaîne, texte, journal<br><br>Exemple :<br>=> **replace**(last(/host/key),**"ibb"**,**"abb"**) - remplacer tous les 'ibb' par 'abb'| |**right** (valeur,compte)|<|<| |Les caractères les plus à droite de la valeur.|**valeur** - valeur à vérifier<br>**compte** - nombre de caractères à renvoyer|Types de valeur pris en charge : chaîne, texte, journal<br><br>Par exemple , vous pouvez renvoyer 'bix' à partir de 'Zabbix' en spécifiant 3 caractères les plus à droite à renvoyer.<br><br>Exemple :<br>=> **right**(last(/host/key),**3* *) - renvoie les trois caractères les plus à droite<br><br>Voir aussi left().| |**rtrim** (valeur,<caractères>)|<|<| |Supprime les caractères spécifiés de la fin de la chaîne.|**valeur** - valeur à vérifier<br>**caractères** - (facultatif) spécifiez les caractères à supprimer<br><br>Les espaces blancs sont coupés à droite par défaut ( si aucun caractère facultatif n'est spécifié).|Types de valeur pris en charge : chaîne, texte, journal<br><br>Exemple :<br>=> **rtrim**(last(/host/key)) - supprime les espaces du fin de chaîne<br>=> **rtrim**(last(/host/key),**"x"**) - supprime tout 'x' à la fin de la chaîne<br>=> **rtrim* *(last(/host/key),**"x "**) - supprime tout 'x' ou espace à la fin de la chaîne<br><br>Voir aussi : ltrim(), trim()| |**trim** (valeur,<caractères>)|<|<| |Supprime les caractères spécifiés du début et de la fin de la chaîne.|**valeur** - valeur à vérifier<br>**caractères** - (facultatif) spécifiez les caractères à supprimer<br><br>Les espaces blancs sont coupés des deux côtés par défaut (si aucun caractère facultatif n'est spécifié).|Types de valeur pris en charge : chaîne, texte, journal<br><br>Exemple :<br>=> **trim**(last(/host/key)) - supprimer espace entre le début et la fin de la chaîne<br>=> **trim**(last(/host/key),**"\_"**) - supprime '\_' du début et de la fin de la chaîne< br><br>Voir aussi : ltrim(), rtrim()| # 9 Template changes This page lists all changes to the stock templates that are shipped with Zabbix. Note that upgrading to the latest Zabbix version will not automatically upgrade the templates used. It is suggested to modify the templates in existing installations by: - Downloading the latest templates from the [Zabbix Git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates); - Then, while in *Configuration* → *Templates* you can import them manually into Zabbix. If templates with the same names already exist, the *Delete missing* options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items). # 9 Modifications des modèles Cette page répertorie toutes les modifications apportées aux modèles de stock livrés avec Zabbix. Notez que la mise à niveau vers la dernière version de Zabbix ne mettra pas automatiquement à niveau les modèles utilisés. Il est suggéré de modifier les modèles dans les installations existantes en : - Téléchargeant les derniers modèles depuis le [dépôt Zabbix Git](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates); - Ensuite, dans *Configuration* → *Modèles*, vous pouvez les importer manuellement dans Zabbix. Si des modèles portant les mêmes noms existent déjà, les options *Supprimer manquants* doivent être cochées lors de l'importation pour obtenir une importation propre. De cette façon, les anciens éléments qui ne sont plus dans le modèle mis à jour seront supprimés (notez que cela signifiera la perte de l'historique de ces anciens éléments). # 9 Templates out of the box # 9 Modèles prêts à l'emploi # 9 Value mapping # 9 Table de correspondance des valeurs # 9. Web monitoring # 9. Supervision Web # 9 Web service # 9 Web service # 9 What's new in Zabbix 6.0.4 # 9 Quoi de neuf dans Zabbix 6.0.4 # 9 Zabbix web service # 9 Web service Zabbix #### Absence of data For items with a regular update interval, nothing is displayed in the graph if item data are not collected. However, for trapper items and items with a scheduled update interval (and regular update interval set to 0), a straight line is drawn leading up to the first collected value and from the last collected value to the end of graph; the line is on the level of the first/last value respectively. #### Absence de données Pour les éléments avec un intervalle de mise à jour régulier, rien ne s'affiche dans le graphique si les données de l'élément ne sont pas collectées. Cependant, pour les éléments de trappeur et les éléments avec un intervalle de mise à jour planifié (et un intervalle de mise à jour régulier défini sur 0), une ligne droite est tracée menant à la première valeur collectée et de la dernière valeur collectée à la fin du graphique ; la ligne est au niveau de la première/dernière valeur respectivement. ### Access control ### Contrôle d'accès #### Accessing host dashboards Access to host dashboards is provided: - From the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) that is available in many frontend locations: - click on the host name and then select *Dashboards* from the drop-down menu  - When searching for a host name in [global search](/manual/web_interface/global_search): - click on the *Dashboards* link provided in search results ```{=html} <!-- --> ``` - When clicking on a host name in *Inventory* → *[Hosts](/manual/web_interface/frontend_sections/inventory/hosts)*: - click on the *Dashboards* link provided #### Accéder aux tableaux de bord de l'hôte L'accès aux tableaux de bord de l'hôte est fourni : - Depuis le [menu hôte](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) qui est disponible dans de nombreux emplacements frontaux : - cliquez sur le nom de l'hôte, puis sélectionnez *Tableaux de bord* dans le menu déroulant  - Lors de la recherche d'un nom d'hôte dans [recherche globale](/manual/web_interface/global_search) : - cliquez sur le lien *Tableaux de bord* fourni dans les résultats de recherche ```{=html} <!-- --> ``` - Lorsque vous cliquez sur un nom d'hôte dans *Inventaire* → *[Hosts](/manual/web_interface/frontend_sections/inventory/hosts)* : - cliquez sur le lien *Tableaux de bord* fourni #### Acknowledging an event Acknowledge a single event and leave a message. Request: ```json { "jsonrpc": "2.0", "method": "event.acknowledge", "params": { "eventids": "20427", "action": 6, "message": "Problem resolved." }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "eventids": [ "20427" ] }, "id": 1 } ``` #### Acquittement d'un événement Acquitter un événement et ajouter un message. Requête : ```json { "jsonrpc": "2.0", "method": "event.acknowledge", "params": { "eventids": "20427", "action": 6, "message": "Problem resolved." }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "eventids": [ "20427" ] }, "id": 1 } ``` # action.create # action.create # action.delete # action.delete ### Action filter The action filter object defines a set of conditions that must be met to perform the configured action operations. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.| ### Filtre d'actions L'objet de filtre d'action définit un ensemble de conditions qui doivent être remplies pour effectuer les opérations d'action configurées. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |-------|--------------------------------------------------------|-----------| |**conditions**<br>(obligatoire)|array|Ensemble de conditions de filtre à utiliser pour filtrer les résultats.| |**evaltype**<br>(obligatoire)|integer|Méthode d'évaluation de la condition de filtre.<br><br>Valeurs possibles :<br>0 - et/ou ;<br>1 - et ;<br>2 - ou ;<br>3 - expression personnalisée.| |eval\_formula|string|*(lecture seule)* Expression générée qui sera utilisée pour évaluer les conditions de filtre. L'expression contient des identifiants qui font référence à des conditions de filtre spécifiques par son `formulaid`. La valeur de `eval_formula` est égale à la valeur de `formula` pour les filtres avec une expression personnalisée.| |formula|string|Expression définie par l'utilisateur à utiliser pour évaluer les conditions des filtres avec une expression personnalisée. L'expression doit contenir des identifiants faisant référence à des conditions de filtre spécifiques par son `formulaid`. Les identifiants utilisés dans l'expression doivent correspondre exactement à ceux définis dans les conditions de filtre : aucune condition ne peut rester inutilisée ou omise.<br><br>Requis pour les filtres d'expression personnalisées.| # action.get # action.get #### Action operation condition The action operation condition object defines a condition that must be met to perform the current operation. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |opconditionid|string|*(readonly)* ID of the action operation condition| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>14 - event acknowledged.| |**value**<br>(required)|string|Value to compare with.| |operationid|string|*(readonly)* ID of the operation.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =.| The following operators and values are supported for each operation condition type. |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |14|Event acknowledged|=|Whether the event is acknowledged.<br><br>Possible values:<br>0 - not acknowledged;<br>1 - acknowledged.| #### Condition d'opération d'action L'objet condition d'opération d'action définit une condition qui doit être remplie pour effectuer l'opération en cours. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |opconditionid|string|*(lecture seule)* ID de la condition d'opération d'action.| |**conditiontype**<br>(obligatoire)|integer|Type de condition.<br><br>Valeurs possibles :<br>14 - événement acquitté.| |**value**<br>(obligatoire)|string|Valeur à comparer.| |operationid|string|*(lecture seule)* ID de l'opération.| |operator|integer|Opérateur de condition.<br><br>Valeurs possibles :<br>0 - *(par défaut)* =.| Les opérateurs et valeurs suivants sont pris en charge pour chaque type de condition d'opération. |Condition|Nom de la condition|Opérateurs pris en charge|Valeur attendue| |---------|--------------|-------------------|--------------| |14|Événement acquitté|=|Indique si l'événement est acquitté.<br><br>Valeurs possibles :<br>0 - non acquitté ;<br>1 - acquitté.| #### Action operation message The operation message object contains data about the message that will be sent by the operation. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |default\_msg|integer|Whether to use the default action message text and subject.<br><br>Possible values:<br>0 - use the data from the operation;<br>1 - *(default)* use the data from the media type.| |mediatypeid|string|ID of the media type that will be used to send the message.| |message|string|Operation message text.| |subject|string|Operation message subject.| #### Message d'opération d'action L'objet de message d'opération contient des données sur le message qui sera envoyé par l'opération. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |default\_msg|integer|Indique s'il faut utiliser le texte et l'objet du message d'action par défaut.<br><br>Valeurs possibles :<br>0 - utiliser les données de l'opération ;<br>1 - *(par défaut)* utiliser les données du type de media.| |mediatypeid|string|ID du type de média qui sera utilisé pour envoyer le message.| |message|string|Texte du message de l'opération.| |subject|string|Sujet du message de l'opération.| ### Action operation The action operation object defines an operation that will be performed when an action is executed. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - global script;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.<br><br>Note that only types '0' and '1' are supported for trigger actions, only '0' is supported for internal actions. All types are supported for discovery and autoregistration actions.| |actionid|string|ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing data on global script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.| ### Opération d'action L'objet d'opération d'action définit une opération qui sera effectuée lorsqu'une action est exécutée. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(lecture seule)* ID de l'opération d'action.| |**operationtype**<br>(obligatoire)|integer|Type de l'opération d'action.<br><br>Valeurs possibles :<br>0 - envoi de message ;<br>1 - script global ;<br>2 - ajouter un hôte ;<br>3 - supprimer un hôte ;<br>4 - ajouter à un groupe d'hôtes ;<br>5 - supprimer d'un groupe d'hôtes ;<br>6 - lier à un modèle ;<br>7 - délier du modèle ;<br>8 - activer l'hôte ;<br>9 - désactiver l'hôte ;<br>10 - définir le mode d'inventaire de l'hôte.<br><br>A noter : seuls les types '0' et '1' sont pris en charge pour les actions de déclenchement, seul '0' est pris en charge pour les actions internes. Tous les types sont pris en charge pour les actions de découverte et d'enregistrement automatique.| |actionid|string|ID de l'action à laquelle appartient l'opération.| |esc\_period|string|Durée d'une étape d'escalade en secondes. Doit être supérieur à 60 secondes. Accepte les secondes, les unités de temps avec suffixe et les macros utilisateur. Si la valeur est définie sur 0 ou sur 0s, la période d'escalade de l'action par défaut sera utilisée.<br><br>Par défaut : 0s.<br><br>A noter : les escalades ne sont prises en charge que pour les actions de déclenchement et les actions internes. Dans les actions de déclencheur, les escalades ne sont pas prises en charge dans les opérations de récupération de problème et de mise à jour.| |esc\_step\_from|integer|Étape à partir de laquelle commencer l'escalade.<br><br>Par défaut : 1.<br><br>A noter : les escalades ne sont prises en charge que pour les actions de déclenchement et les actions internes. Dans les actions de déclencheur, les escalades ne sont pas prises en charge dans les opérations de récupération de problème et de mise à jour.| |esc\_step\_to|integer|Étape à laquelle terminer l'escalade.<br><br>Par défaut : 1.<br><br>A noter : les escalades ne sont prises en charge que pour les actions de déclenchement et les actions internes. Dans les actions de déclencheur, les escalades ne sont pas prises en charge dans les opérations de récupération de problème et de mise à jour.| |evaltype|integer|Méthode d'évaluation des conditions de l'opération.<br><br>Valeurs possibles :<br>0 - *(par défaut)* ET / OU ;<br>1 - ET ;<br>2 - OU.| |opcommand|object|Objet contenant les données sur la commande exécutée par l'opération.<br><br>L'objet possède la propriété suivante : `scriptid` - *(string)* ID du script.<br><br>Obligatoire pour les opérations de script global.| |opcommand\_grp|array|Groupes d'hôtes sur lesquels exécuter des scripts globaux.<br><br>Chaque objet possède les propriétés suivantes : <br>`opcommand_grpid` - *(string, lecture seul)* ID de l'objet ;<br>`operationid` - *(string)* ID de l'opération ;<br>`groupid` - *(string)* ID du groupe d'hôtes.<br><br>Obligatoire pour les opérations de script global si `opcommand_hst` n'est pas défini.| |opcommand\_hst|array|Hôte sur lequel exécuter les scripts globaux.<br><br>Chaque objet possède les propriétés suivantes : <br>`opcommand_hstid` - *(string, lecture seule)* ID de l'objet ;<br>`operationid` - *(string)* ID de l'opération ;<br>`hostid` - *(string)* ID du hôte ; si défini à 0, la commande sera exécutée sur l'hôte actuel.<br><br>Obligatoire pour les opérations de script global si `opcommand_grp` n'est pas défini.| |opconditions|array|Conditions d'opération utilisées pour les actions de déclenchement.<br><br>L'objet de condition d'opération est [décrit en détail ci-dessous](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Groupes d'hôtes auxquels ajouter les hôtes.<br><br>Chaque objet possède les propriétés suivantes : <br>`operationid` - *(string)* ID de l'opération;<br>`groupid` - *(string)* ID du groupe d'hôtes.<br><br>Obligatoire pour les opérations "ajouter à un groupe d'hôtes" et "supprimer d'un groupe d'hôtes".| |opmessage|object|Objet contenant les données sur le message envoyé par l'opération.<br><br>L'objet de message d'opération est [décrit en détail ci-dessous](/manual/api/reference/action/object#action_operation_message).<br><br>Obligatoire pour les opérations d'envoi de message.| |opmessage\_grp|array|Groupes d'utilisateurs auxquels envoyer des messages.<br><br>Chaque objet possède les propriétés suivantes : <br>`operationid` - *(string)* ID de l'opération ;<br>`usrgrpid` - *(string)* ID du groupe d'utilisateurs.<br><br>Obligatoire pour les opérations d'envoi de message si `opmessage_usr` n'est pas défini.| |opmessage\_usr|array|Utilisateurs auxquels envoyer des messages.<br><br>Chaque objet possède les propriétés suivantes : <br>`operationid` - *(string)* ID de l'opération ;<br>`userid` - *(string)* ID de l'utilisateur.<br><br>Obligatoire pour les opérations d'envoi de message si `opmessage_grp` n'est pas défini.| |optemplate|array|Modèles auxquels liés les hôtes.<br><br>Chaque objet possède les propriétés suivantes : <br>`operationid` - *(string)* ID de l'opération;<br>`templateid` - *(string)* ID du modèle.<br><br>Obligatoire pour les opérations "lier un modèle" et "lier un modèle".| |opinventory|object|Mode d'inventaire à définir sur l'hôte.<br><br>L'objet possède les propriétés suivantes : <br>`operationid` - *(string)* ID de l'opération ;<br>`inventory_mode` - *(string)* Mode d'inventaire.<br><br>Obligatoire pour les opérations "définir le mode d'inventaire de l'hôte".| ### Action operation The action operation object defines an operation that will be performed when an action is executed. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - global script;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.<br><br>Note that only types '0' and '1' are supported for trigger and service actions, only '0' is supported for internal actions. All types are supported for discovery and autoregistration actions.| |actionid|string|*(readonly)* ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing data on global script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.| ### Opération d'action L'objet d'opération d'action définit une opération qui sera effectuée lorsqu'une action est exécutée. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(lecture seule)* Identifiant de l'opération d'action.| |**operationtype**<br>(obligatoire)|integer|Type d'operation.<br><br>Valeurs possibles : <br>0 - envoyer un message ;<br>1 - script global ;<br>2 - ajouter un hôte ;<br>3 - supprimer un hôte ;<br>4 - ajouter au groupe d'hôtes ;<br>5 - supprimer du groupe d'hôte ;<br>6 - lier au modèle ;<br>7 - délier du modèle ;<br>8 - activer l'hôte ;<br>9 - désactiver l'hôte ;<br>10 - définir le mode d'inventaire de l'hôte.<br><br>Notez que seuls les types '0' et '1' sont supportés pour les actions de déclencheur et de service, seul '0' est supporté pour les actions internes. Tous les types sont supportés pour les actions de découverte et d'enregistrement automatique.| |actionid|string|*(lecture seule)* Identifiant de l'action à laquelle appartient l'opération.| |esc\_period|string|Durée d'une étape d'escalade en secondes. Doit être supérieur à 60 secondes. Accepte les secondes, l'unité de temps avec suffixe et la macro utilisateur. Si défini sur 0 ou 0 s, la période d'escalade d'action par défaut sera utilisée.<br><br>Par défaut : 0 s.<br><br>Notez que les escalades ne sont prises en charge que pour les actions de déclenchement, internes et de service, et uniquement dans des conditions normales opérations.| |esc\_step\_from|integer|Étape à partir de laquelle l'escalade démarre.<br><br>Par défaut : 1.<br><br>Notez que les escalades ne sont prises en charge que pour les actions de déclenchement, internes et de service, et uniquement dans les opérations normales.| |esc\_step\_to|integer|Étape à laquelle l'escalade se termine.<br><br>Par défaut : 1.<br><br>Notez que les escalades ne sont prises en charge que pour les actions de déclenchement, internes et de service, et uniquement dans les opérations normales.| |evaltype|integer|Méthode d'évaluation des conditions de l'opération.<br><br>Valeurs possibles : <br>0 - *(par défaut)* ET / OU ;<br>1 - ET ;<br>2 - OU.| |opcommand|object|Objet contenant des données sur le script global exécuté par l'opération.<br><br>Chaque objet a la propriété suivante : `scriptid` - *(string)* identifiant du script.<br><br>Requis pour les opérations de script global. | |opcommand\_grp|array|Groupes d'hôtes sur lesquels exécuter des scripts globaux.<br><br>Chaque objet a les propriétés suivantes : <br>`opcommand_grpid` - *(string, lecture seule)* identifiant de l'objet ;<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`groupid` - *(string)* identifiant du groupe d'hôtes.<br><br>Requis pour les opérations de script global si `opcommand_hst` n'est pas défini.| |opcommand\_hst|array|Hôte sur lequel exécuter des scripts globaux.<br><br>Chaque objet a les propriétés suivantes :<br>`opcommand_hstid` - *(string, lecture seule)* identifiant de l'objet ;<br>`operationid` - *(string , lecture seule)* identifiant de l'opération ;<br>`hostid` - *(string)* identifiant de l'hôte ; si défini sur 0, la commande sera exécutée sur l'hôte actuel.<br><br>Requis pour les opérations de script global si `opcommand_grp` n'est pas défini.| |opconditions|array|Conditions d'opération utilisées pour les actions de déclenchement.<br><br>L'objet de condition d'opération est [décrit en détail ci-dessous](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Groupes d'hôtes auxquels ajouter des hôtes.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`groupid` - *(string )* identifiant du groupe d'hôtes.<br><br>Requis pour les opérations "ajouter au groupe d'hôtes" et "supprimer du groupe d'hôtes".| |opmessage|object|Objet contenant les données sur le message envoyé par l'opération.<br><br>L'objet de message d'opération est [décrit en détail ci-dessous](/manual/api/reference/action/object#action_operation_message).<br><br> Requis pour les opérations de message.| |opmessage\_grp|array|Groupes d'utilisateurs auxquels envoyer des messages.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`usrgrpid` - *(string )* identifiant du groupe d'utilisateurs.<br><br>Requis pour les opérations de message si `opmessage_usr` n'est pas défini.| |opmessage\_usr|array|Utilisateurs auxquels envoyer des messages.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`userid` - *(string) * identifiant de l'utilisateur.<br><br>Requis pour les opérations de message si `opmessage_grp` n'est pas défini.| |optemplate|array|Modèles auxquels lier les hôtes.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`templateid` - *(chaîne)* identifiant du modèle.<br><br>Requis pour les opérations "lier au modèle" et "dissocier du modèle".| |opinventory|object|Mode d'inventaire défini sur l'hôte. <br><br>L'objet a les propriétés suivantes :<br>`operationid` - *(string, lecture seule)* identifiant de l'opération ;<br>`inventory_mode` - *(string)* Inventory mode.<br> <br>Requis pour les opérations "Définir le mode d'inventaire de l'hôte".| ### Action recovery operation The action recovery operation object defines an operation that will be performed when a problem is resolved. Recovery operations are possible for trigger actions and internal actions. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger actions:<br>0 - send message;<br>1 - global script;<br>11 - notify all involved.<br><br>Possible values for internal actions:<br>0 - send message;<br>11 - notify all involved.| |actionid|string|ID of the action that the recovery operation belongs to.| |opcommand|object|Object containnig data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the recovery operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| ### Opération de récupération d'action L'objet d'opération de récupération d'action définit une opération qui sera effectuée lorsqu'un problème est résolu. Les opérations de récupération sont possibles pour les actions de déclencheur et les actions internes. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(lecture seule)* ID de l'opération d'action.| |**operationtype**<br>(obligatoire)|integer|Type d'opération.<br><br>Valeurs possibles pour les actions de déclenchement :<br>0 - envoi de message ;<br>1 - script global ;<br>11 - informer toutes les personnes impliquées.<br><br>Valeurs possibles pour les actions internes :<br>0 - envoi de message ;<br>11 - informer toutes les personnes impliquées.| |actionid|string|ID de l'action à laquelle l'opération de récupération appartient.| |opcommand|object|Objet contenant les données sur la commande exécutée par l'opération de récupération.<br><br>L'objet possède les propriétés suivantes : `scriptid` - *(string)* ID du script de type d'action.<br><br>Obligatoire pour les opérations de script global.| |opcommand\_grp|array|Groupes d'hôtes sur lesquels exécuter les scripts globaux.<br><br>Chaque objet a les propriétés suivantes : <br>`opcommand_grpid` - *(string, lecture seule)* ID de l'objet ;<br>`operationid` - *(string)* ID de l'opération;<br>`groupid` - *(string)* ID du groupe d'hôtes.<br><br>Obligatoire pour les opérations de script global si `opcommand_hst` n'est pas défini.| |opcommand\_hst|array|Hôtes sur lesquels exécuter les scripts globaux.<br><br>Chaque objet a les propriétés suivantes : <br>`opcommand_hstid` - *(string, lecture seule)* ID de l'objet ;<br>`operationid` - *(string)* ID de l'opération ;<br>`hostid` - *(string)* ID du hôte; Si défini à 0, la commande sera exécutée sur l'hôte actuel.<br><br>Obligatoire pour les opérations de script global si `opcommand_grp` n'est pas défini.| |opmessage|object|Objet contenant les données sur le message envoyé par l'opération de récupération.<br><br>L'objet Message d'opération d'action est [décrit en détail plus haut](/manual/api/reference/action/object#action_operation_message).<br><br>Obligatoire pour les opérations d'envoi de message.| |opmessage\_grp|array|Groupes d'utilisateurs auxquels envoyer lesmessages.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string)* ID de l'opération;<br>`usrgrpid` - *(string)* ID du groupe d'utilisateurs.<br><br>Obligatoire pour les opérations d'envoi de message si `opmessage_usr` n'est pas défini.| |opmessage\_usr|array|Utilisateurs auxquels envoyer les messages.<br><br>Chaque objet a les propriétés suivantes :<br>`operationid` - *(string)* ID de l'opération;<br>`userid` - *(string)* ID de l'utilisateur.<br><br>Obligatoire pour les opérations d'envoi de message si `opmessage_grp` n'est pas défini.| #### Actions and alerts Define actions and operations to notify users about certain events or automatically execute remote commands. Gain access to information about generated alerts and their receivers. [Action API](/manual/api/reference/action) | [Alert API](/manual/api/reference/alert) #### Actions et alertes Définissez des actions et des opérations pour informer les utilisateurs de certains événement ou exécuter automatiquement des commandes à distance. Accédez à des informations sur les alertes générées et leurs destinataires. [API Action](/manual/api/reference/action) | [API Alerte](/manual/api/reference/alert) #### Actions disabled due to deleted objects If a certain object (host, template, trigger, etc.) used in an action condition/operation is deleted, the condition/operation is removed and the action is disabled to avoid incorrect execution of the action. The action can be re-enabled by the user. This behavior takes place when deleting: - host groups ("host group" condition, "remote command" operation on a specific host group); - hosts ("host" condition, "remote command" operation on a specific host); - templates ("template" condition, "link to template" and "unlink from template" operations); - triggers ("trigger" condition); - discovery rules (when using "discovery rule" and "discovery check" conditions). *Note*: If a remote command has many target hosts, and we delete one of them, only this host will be removed from the target list, the operation itself will remain. But, if it's the only host, the operation will be removed, too. The same goes for "link to template" and "unlink from template" operations. Actions are not disabled when deleting a user or user group used in a "send message" operation. #### Actions désactivées en raison d'objets supprimés Si un certain objet (hôte, modèle, déclencheur, etc.) utilisé dans une condition/opération d'action est supprimé, la condition/opération est supprimée et l'action est désactivée pour éviter une exécution incorrecte de l'action. L'action peut être réactivée par l'utilisateur. Ce comportement se produit lors de la suppression : - de groupes d'hôtes (condition "groupe d'hôtes", opération "commande à distance" sur un groupe d'hôtes spécifique) ; - d'hôtes (condition "hôte", opération "commande à distance" sur un hôte spécifique) ; - de modèles (condition "modèle", opérations "Lier au modèle" et "Dissocier du modèle") ; - de déclencheurs (condition de "déclencheur") ; - de règles de découverte (lors de l'utilisation des conditions "règle de découverte" et "vérification de découverte"). *Remarque* : Si une commande distante a plusieurs hôtes cibles et que nous supprimons l'un d'entre eux, seul cet hôte sera supprimé de la liste cible, l'opération elle-même restera. Mais, s'il s'agit du seul hôte, l'opération sera également supprimée. Il en va de même pour les opérations "lier au modèle" et "dissocier du modèle". Les actions ne sont pas désactivées lors de la suppression d'un utilisateur ou d'un groupe d'utilisateurs utilisé dans une opération "envoyer un message". #### Actions Discovery events can be the basis of relevant [actions](/manual/config/notifications/action), such as: - Sending notifications - Adding/removing hosts - Enabling/disabling hosts - Adding hosts to a group - Removing hosts from a group - Linking hosts to/unlinking from a template - Executing remote scripts These actions can be configured with respect to the device type, IP, status, uptime/downtime, etc. For full details on configuring actions for network-discovery based events, see action [operation](/manual/config/notifications/action/operation) and [conditions](/manual/config/notifications/action/conditions) pages. Since network discovery actions are event-based, they will be triggered both when a discovered host is online and when it is offline. It is highly recommended to add an action [condition](/manual/config/notifications/action/conditions) *Discovery status: up* to avoid such actions as *Add host* being triggered upon *Service Lost*/*Service Down* events. Otherwise, if a discovered host is manually removed, it will still generate *Service Lost*/*Service Down* events and will be recreated during the next discovery cycle. ::: noteclassic Linking a discovered host to templates will fail collectively if any of the linkable templates has a unique entity (e.g. item key) that is the same as a unique entity (e.g. item key) already existing on the host or on another of the linkable templates. ::: #### Actions Les événements de découverte peuvent être la base d'[actions](/manual/config/notifications/action) pertinentes, telles que : - L'envoi de notifications - L'ajout/suppression d'hôtes - L'activation/désactivation des hôtes - L'ajout d'hôtes à un groupe - La suppression des hôtes d'un groupe - La liaison (ou la suppression d'un lien) des hôtes à un modèle - L'exécution de scripts à distance Ces actions peuvent être configurées en fonction du type de périphérique, de l'adresse IP, de l'état, de la disponibilité/indisponibilité, etc. Pour plus de détails sur la configuration des actions pour les événements basés sur la découverte du réseau, voir les pages [opération](/manual/config/notifications/action/operation) et [conditions](/manual/config/notifications/action/conditions). Étant donné que les actions de découverte du réseau sont basées sur des événements, elles seront déclenchées à la fois lorsqu'un hôte découvert est en ligne et lorsqu'il est hors ligne. Il est fortement recommandé d'ajouter une action [condition](/manual/config/notifications/action/conditions) *Discovery status: up* pour éviter que des actions telles que *Add host* soient déclenchées lors d'événements du type *Service Lost*/*Service Down*. Sinon, si un hôte découvert est supprimé manuellement, il générera toujours des événements *Service Lost*/*Service Down* et sera recréé lors du prochain cycle de découverte. ::: noteclassic La liaison d'un hôte découvert à des modèles échouera collectivement si l'un des modèles pouvant être liés a une entité unique (par exemple, une clé d'élément) est identique à une autre entité unique (par exemple une clé d'élément) existant déjà sur l'hôte ou sur un autre des modèles pouvant être liés. :::​ #### Actions if communication fails between agent and server Each matching line from `log[]` and `logrt[]` item and a result of each `log.count[]` and `logrt.count[]` item check requires a free slot in the designated 50% area in the agent send buffer. The buffer elements are regularly sent to server (or proxy) and the buffer slots are free again. While there are free slots in the designated log area in the agent send buffer and communication fails between agent and server (or proxy) the log monitoring results are accumulated in the send buffer. This helps to mitigate short communication failures. During longer communication failures all log slots get occupied and the following actions are taken: - `log[]` and `logrt[]` item checks are stopped. When communication is restored and free slots in the buffer are available the checks are resumed from the previous position. No matching lines are lost, they are just reported later. - `log.count[]` and `logrt.count[]` checks are stopped if `maxdelay = 0` (default). Behavior is similar to `log[]` and `logrt[]` items as described above. Note that this can affect `log.count[]` and `logrt.count[]` results: for example, one check counts 100 matching lines in a log file, but as there are no free slots in the buffer the check is stopped. When communication is restored the agent counts the same 100 matching lines and also 70 new matching lines. The agent now sends count = 170 as if they were found in one check. - `log.count[]` and `logrt.count[]` checks with `maxdelay > 0`: if there was no "jump" during the check, then behavior is similar to described above. If a "jump" over log file lines took place then the position after "jump" is kept and the counted result is discarded. So, the agent tries to keep up with a growing log file even in case of communication failure. #### Actions si la communication échoue entre l'agent et le serveur Chaque ligne correspondante de l'élément `log[]` et `logrt[]` et le résultat de chaque `log.count[]` et `logrt.count[]` requièrent un emplacement libre dans la zone de 50% désignée dans le buffer d'envoi de l'agent. Les éléments buffers sont régulièrement envoyés au serveur (ou proxy) et les emplacements de mémoire tampon sont à nouveau libres. Bien qu'il existe des emplacements libres dans la zone des fichiers journaux désignée dans le buffer d'envoi de l'agent et que la communication échoue entre l'agent et le serveur (ou le proxy), les résultats de la surveillance des fichiers journaux sont accumulés dans le buffer d'envoi. Cela aide à atténuer les échecs de communication ponctuel. Pendant les échecs de communication plus longs, tous les emplacements de logs sont occupés et les actions suivantes sont effectuées : - Les vérifications des éléments `log[]` et `logrt[]` sont arrêtées. Lorsque la communication est rétablie et que des emplacements sont libérés dans la mémoire tampon, les vérifications reprennent à partir de la position précédente. Aucune ligne correspondante n'est perdue, elles sont juste reportées plus tard. - Les vérifications `log.count[]` et `logrt.count[]` sont arrêtées si `maxdelay = 0` (par défaut). Le comportement est similaire aux éléments `log[]` et `logrt[]` décrits ci-dessus. Notez que cela peut affecter les résultats de `log.count[]` et de `logrt.count[]` : par exemple, une vérification compte 100 lignes correspondantes dans un fichier journal, mais comme il n'y a pas d'espace libre dans la mémoire tampon, la vérification est arrêtée. Lorsque la communication est restaurée, l'agent compte les mêmes 100 lignes correspondantes et 70 nouvelles lignes correspondantes. L'agent envoie maintenant compteur = 170 comme s'il avait été trouvé dans une vérification. - Les vérifications `log.count[]` et `logrt.count[]` avec `maxdelay > 0` : s'il n'y a pas eu de "saut" pendant la vérification, alors le comportement est similaire à celui décrit ci-dessus. Si un "saut" sur les lignes du fichier journal a eu lieu, la position après le "saut" est conservée et le résultat compté est ignoré. Ainsi, l'agent essaie de suivre un fichier journal en expansion, même en cas d'échec de la communication #### Actions In [actions](/manual/config/notifications/action), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Trigger-based notifications and commands|<|yes| |Trigger-based internal notifications|<|yes| |Problem update notifications|<|yes| |Service-based notifications and commands|<|yes| |Service update notifications|<|yes| |Time period condition|<|no| |*Operations*|<|<| | |Default operation step duration|no| |^|Step duration|no| #### Actions Dans les [actions](/manual/config/notifications/action), les macros utilisateur peuvent être utilisées dans les champs suivants : |Emplacement|<|Plusieurs macros/mix avec du texte^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Notifications et commandes basées sur les déclencheurs|<|oui| |Notifications internes basées sur les déclencheurs|<|oui| |Notifications de mise à jour de problème|<|oui| |Notifications et commandes basées sur les services|<|oui| |Notifications de mise à jour des services|<|oui| |Condition de période de temps|<|non| |*Opérations*|<|<| | |Durée de l'étape d'opération par défaut|non| |^|Durée de l'étape|non| ### Action The action object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |actionid|string|*(readonly)* ID of the action.| |**esc\_period**<br>(required)|string|Default operation step duration. Must be at least 60 seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |**eventsource**<br>(required)|integer|*(constant)* Type of events that the action will handle.<br><br>Refer to the [event "source" property](/manual/api/reference/event/object#event) for a list of supported event types.| |**name**<br>(required)|string|Name of the action.| |status|integer|Whether the action is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |pause\_suppressed|integer|Whether to pause escalation during maintenance periods or not.<br><br>Possible values:<br>0 - Don't pause escalation;<br>1 - *(default)* Pause escalation.<br><br>Note that this parameter is valid for trigger actions only.| |notify\_if\_canceled|integer|Whether to notify when escalation is canceled.<br><br>Possible values:<br>0 - Don't notify when escalation is canceled;<br>1 - *(default)* Notify when escalation is canceled.<br><br>Note that this parameter is valid for trigger actions only.| ### Action L'objet action a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |actionid|string|*(lecture seule)* ID de l'action.| |**esc\_period**<br>(obligatoire)|string|Durée de l'étape d'opération par défaut. Doit être supérieur à 60 secondes. Accepte les secondes, les unités de temps avec suffixe et les macros utilisateur.<br><br>A noter : les escalades ne sont prises en charge que pour les actions de déclencheur et les actions internes. Pour les actions de déclencheur, les escalades ne sont pas prises en charge dans les opérations de récupération de problème et de mise à jour.| |**eventsource**<br>(obligatoire)|integer|*(constante)* Type d'événements que l'action va gérer.<br><br>Se référer à la [propriété "source" de l'événement](/manual/api/reference/event/object#event) pour obtenir la liste des types d'événements supportés.| |**name**<br>(obligatoire)|string|Nom de l'action.| |status|integer|Indique si l'action est activée ou désactivée.<br><br>Valeurs possibles :<br>0 - *(par défaut)* activée ;<br>1 - désactivée.| |pause\_suppressed|integer|Indique si l'escalade est en pause ou non durant une période de maintenance.<br><br>Valeurs possibles :<br>0 - Ne pas mettre en pause l'escalade ;<br>1 - *(par défaut)* Mettre en pause l'escalade.<br><br>A noter : ce paramètre est valide uniquement pour les actions de déclencheur.| |notify\_if\_canceled|integer|Indique d'il faut notifier lorsque l'escalade est annulée.<br><br>Valeurs possibles :<br>0 - Ne pas notifier lorsque l'escalade est annulée ;<br>1 - *(par défaut)* Notifier lorsque l'escalade est annulée.<br><br>A noter : ce paramètre est valide uniquement pour les actions de déclencheur.| ### Action The action object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |actionid|string|*(readonly)* ID of the action.| |**esc\_period**<br>(required)|string|Default operation step duration. Must be at least 60 seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |**eventsource**<br>(required)|integer|*(constant)* Type of events that the action will handle.<br><br>Refer to the [event "source" property](/manual/api/reference/event/object#event) for a list of supported event types.| |**name**<br>(required)|string|Name of the action.| |status|integer|Whether the action is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |pause\_suppressed|integer|Whether to pause escalation during maintenance periods or not.<br><br>Possible values:<br>0 - Don't pause escalation;<br>1 - *(default)* Pause escalation.<br><br>Note that this parameter is valid for trigger actions only.| |notify\_if\_canceled|integer|Whether to notify when escalation is canceled.<br><br>Possible values:<br>0 - Don't notify when escalation is canceled;<br>1 - *(default)* Notify when escalation is canceled.<br><br>Note that this parameter is valid for trigger actions only.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Action L'objet d'action a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |actionid|string|*(lecture seule)* identifiant de l'action.| |**esc\_period**<br>(obligatoire)|string| Durée de l'étape de l'opération par défaut. Doit être d'au moins 60 secondes. Accepte les secondes, l'unité de temps avec suffixe et les macros utilisateur.<br><br>Notez que les escalades ne sont prises en charge que pour les actions de déclenchement, internes et de service, et uniquement dans les opérations normales.| |**eventsource**<br>(obligatoire)|integer|*(constant)* Type d'événements que l'action gérera.<br><br>Reportez-vous à la [propriété "source" de l'événement](/manual/api/reference/event/object#event) pour obtenir la liste des types d'événements pris en charge.| |**name**<br>(obligatoire)|string|Nom de l'action. |status|integer|Si l'action est activée ou désactivée.<br><br>Valeurs possibles :<br>0 - *(par défaut)* activé ;<br>1 - désactivé.| |pause\_suppressed|integer|Indique s'il faut suspendre ou non l'escalade pendant les périodes de maintenance.<br><br>Valeurs possibles :<br>0 - Ne pas interrompre l'escalade ;<br>1 - *(par défaut)* Suspendre l'escalade.<br><br>Notez que ce paramètre n'est valide que pour les actions de déclencheur.| |notify\_if\_canceled|integer|Indique si l'escalade est annulée.<br><br>Valeurs possibles :<br>0 - Ne pas avertir lorsque l'escalade est annulée ;<br>1 - *(par défaut)* Avertir lorsque l'escalade est annulée.<br><br>Notez que ce paramètre n'est valide que pour les actions de déclencheur.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. ### Action The action object has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Name of the action.<br><br>Possible values for users of any type:<br>`edit_dashboards` - Create and edit dashboards;<br>`edit_maps` - Create and edit maps;<br>`add_problem_comments` - Add problem comments;<br>`change_severity` - Change problem severity;<br>`acknowledge_problems` - Acknowledge problems;<br>`close_problems` - Close problems;<br>`execute_scripts` - Execute scripts;<br>`manage_api_tokens` - Manage API tokens.<br><br>Possible values only for users of *Admin* and *Super admin* user types:<br>`edit_maintenance` - Create and edit maintenances;<br>`manage_scheduled_reports` - Manage scheduled reports.| |status|integer|Whether access to perform the action is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| ### Action L'objet action a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**nom**<br>(obligatoire)|string|Nom de l'action.<br><br>Valeurs possibles pour les utilisateurs de tout type :<br>`edit_dashboards` - Créer et modifier des tableaux de bord ;<br>` edit_maps` - Créer et modifier des cartes ;<br>`add_problem_comments` - Ajouter des commentaires sur les problèmes ;<br>`change_severity` - Modifier la sévérité du problème ;<br>`acknowledge_problems` - Acquitter les problèmes ;<br>`close_problems` - Fermer les problèmes ; <br>`execute_scripts` - Exécuter des scripts ;<br>`manage_api_tokens` - Gère les jetons d'API.<br><br>Valeurs possibles uniquement pour les utilisateurs de types d'utilisateurs *Admin* et *Super admin* :<br>`edit_maintenance` - Créer et modifier des maintenances ;<br>`manage_scheduled_reports` - Gérer les rapports planifiés.| |status|integer|Indique si l'accès pour effectuer l'action est activé.<br><br>Valeurs possibles :<br>0 - Désactivé ;<br>1 - *(par défaut)* Activé.| # action.update # action.update ### Action update operation The action update operation object defines an operation that will be performed when a problem is updated (commented upon, acknowledged, severity changed, or manually closed). Update operations are possible for trigger and service actions. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger and service actions:<br>0 - send message;<br>1 - global script;<br>12 - notify all involved.| |opcommand|object|Object containing data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the update operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required only for `send message` operations if `opmessage_usr` is not set.<br>Is ignored for `send update message` operations.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`userid` - *(string)* ID of the user.<br><br>Required only for `send message` operations if `opmessage_grp` is not set.<br>Is ignored for `send update message` operations.| ### Opération de mise à jour de l'action L'objet d'opération de mise à jour d'action définit une opération qui sera effectuée lorsqu'un problème est mis à jour (commenté, acquitté, gravité modifiée ou fermé manuellement). Les opérations de mise à jour sont possibles pour les actions de déclenchement et de service. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |-------|--------------------------------------------------------|-----------| |operationid|string|*(lecture seule)* identifiant de l'opération d'action.| |**operationtype**<br>(obligatoire)|integer|Type d'opération.<br><br>Valeurs possibles pour les actions de déclenchement et de service :<br>0 - envoyer un message ;<br>1 - script global ;<br>12 - informez toutes les personnes impliquées.| |opcommand|object|Objet contenant des données sur le script de type d'action global exécuté par l'opération.<br><br>Chaque objet a la propriété suivante : `scriptid` - *(string)* identifiant du script de type d'action.<br> <br>Requis pour les opérations de script global.| |opcommand\_grp|array|Groupes d'hôtes sur lesquels exécuter des scripts globaux.<br><br>Chaque objet a les propriétés suivantes :<br>`groupid` - *(string)* identifiant du groupe d'hôtes.<br>< br>Requis pour les opérations de script global si `opcommand_hst` n'est pas défini.| |opcommand\_hst|array|Hôte sur lequel exécuter les scripts globaux.<br><br>Chaque objet a les propriétés suivantes :<br>`hostid` - *(string)* identifiant de l'hôte ; si défini sur 0, la commande sera exécutée sur l'hôte actuel.<br><br>Requis pour les opérations de script global si `opcommand_grp` n'est pas défini.| |opmessage|object|Objet contenant les données sur le message envoyé par l'opération de mise à jour.<br><br>L'objet de message d'opération est [décrit en détail ci-dessus](/manual/api/reference/action/object#action_operation_message). | |opmessage\_grp|array|Groupes d'utilisateurs auxquels envoyer des messages.<br><br>Chaque objet a les propriétés suivantes :<br>`usrgrpid` - *(string)* identifiant du groupe d'utilisateurs.<br><br> >Requis uniquement pour les opérations `send message` si `opmessage_usr` n'est pas défini.<br>Est ignoré pour les opérations `send update message`.| |opmessage\_usr|array|Utilisateurs auxquels envoyer des messages.<br><br>Chaque objet a les propriétés suivantes :<br>`userid` - *(string)* identifiant de l'utilisateur.<br><br>Obligatoire uniquement pour les opérations `send message` si `opmessage_grp` n'est pas défini.<br>Est ignoré pour les opérations `send update message`.| #### Active checks Active checks require more complex processing. The agent must first retrieve from the server(s) a list of items for independent processing. The servers to get the active checks from are listed in the 'ServerActive' parameter of the agent [configuration file](/manual/appendix/config/zabbix_agentd). The frequency of asking for these checks is set by the 'RefreshActiveChecks' parameter in the same configuration file. However, if refreshing active checks fails, it is retried after hardcoded 60 seconds. The agent then periodically sends the new values to the server(s). ::: notetip If an agent is behind the firewall you might consider using only Active checks because in this case you wouldn't need to modify the firewall to allow initial incoming connections. ::: #### Vérifications actives Les vérifications actives nécessitent un traitement plus complexe. L'agent doit d'abord récupérer sur le(s) serveur(s) une liste d'éléments pour un traitement indépendant. Les serveurs à partir desquels obtenir les vérifications actives sont répertoriés dans le paramètre 'ServerActive' du [fichier de configuration](/manual/appendix/config/zabbix_agentd) de l'agent. La fréquence des demandes pour ces vérifications est défini par le paramètre 'RefreshActiveChecks' dans le même fichier de configuration. Cependant, si le rafraîchissement des vérifications actives échoue, il sera réessayé après 60 secondes (codées en dur). L'agent envoie alors périodiquement les nouvelles valeurs au(x) serveur(s). ::: notetip Si un agent se trouve derrière le pare-feu, vous pouvez envisager d'utiliser uniquement les vérifications actives, car dans ce cas, vous n'auriez pas besoin de modifier le pare-feu pour autoriser les connexions entrantes initiales. ::: #### Active proxy #### Proxy actif #### Add a trigger dependency Make trigger "14092" dependent on trigger "13565." Request: ```json { "jsonrpc": "2.0", "method": "trigger.adddependencies", "params": { "triggerid": "14092", "dependsOnTriggerid": "13565" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "14092" ] }, "id": 1 } ``` #### Ajouter une dépendance de déclencheur Faire en sorte que le déclencheur "14092" dépende du déclencheur "13565." Requête : ```json { "jsonrpc": "2.0", "method": "trigger.adddependencies", "params": { "triggerid": "14092", "dependsOnTriggerid": "13565" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "14092" ] }, "id": 1 } ``` #### Adding a filter to an LLD rule Add a filter so that the contents of the *{\#FSTYPE}* macro would match the *\@File systems for discovery* regexp. Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "22450", "filter": { "evaltype": 1, "conditions": [ { "macro": "{#FSTYPE}", "value": "@File systems for discovery" } ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "22450" ] }, "id": 1 } ``` #### Ajout d'un filtre à une règle de découverte bas niveau Ajoutez un filtre afin que le contenu de la macro *{\#FSTYPE}* corresponde à l'expression régulière *\@File systems for discovery*. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "22450", "filter": { "evaltype": 1, "conditions": [ { "macro": "{#FSTYPE}", "value": "@File systems for discovery" } ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "22450" ] }, "id": 1 } ``` #### Adding a scheduled downtime Add a downtime for service with ID "4" scheduled weekly from Monday 22:00 till Tuesday 10:00. Request: ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "serviceid": "4", "times": [ { "type": "1", "ts_from": "165600", "ts_to": "201600" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "serviceids": [ "4" ] }, "id": 1 } ``` #### Ajout d'un temps d'arrêt planifié Ajoutez un temps d'arrêt pour le service avec l'ID "4" programmé chaque semaine du lundi 22h00 au mardi 10h00. Requête : ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "serviceid": "4", "times": [ { "type": "1", "ts_from": "165600", "ts_to": "201600" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "serviceids": [ "4" ] }, "id": 1 } ``` ##### Adding host Hosts are added during the discovery process, as soon as a host is discovered, rather than at the end of the discovery process. ::: notetip As network discovery can take some time due to many unavailable hosts/services having patience and using reasonable IP ranges is advisable. ::: When adding a host, its name is decided by the standard **gethostbyname** function. If the host can be resolved, resolved name is used. If not, the IP address is used. Besides, if IPv6 address must be used for a host name, then all ":" (colons) are replaced by "\_" (underscores), since colons are not allowed in host names. ::: noteimportant If performing discovery by a proxy, currently hostname lookup still takes place on Zabbix server. ::: ::: noteimportant If a host already exists in Zabbix configuration with the same name as a newly discovered one, versions of Zabbix prior to 1.8 would add another host with the same name. Zabbix 1.8.1 and later adds **\_N** to the hostname, where **N** is increasing number, starting with 2. ::: ##### Ajout d'hôte Les hôtes sont ajoutés au cours du processus de découverte, dès qu'un hôte est découvert, plutôt qu'à la fin du processus de découverte. ::: notetip Comme la découverte du réseau peut prendre un certain temps en raison du fait que de nombreux hôtes/services indisponibles ont des timeout il est conseillé d'utiliser des plages IP raisonnables. ::: Lors de l'ajout d'un hôte, son nom est déterminé par la fonction standard **gethostbyname**. Si l'hôte peut être résolu, le nom résolu est utilisé. Sinon, l'adresse IP est utilisée. De plus, si l'adresse IPv6 doit être utilisée pour un nom d'hôte, tous les ":" (deux points) sont remplacés par "\_" (underscores), car les deux points ne sont pas autorisés dans les noms d'hôte. ::: noteimportant Si la découverte est effectuée par un proxy, la recherche du nom d'hôte a toujours lieu sur le serveur Zabbix. ::: ::: noteimportant Si un hôte existe déjà dans la configuration de Zabbix et porte le même nom que celui récemment découvert, les versions de Zabbix antérieures à la version 1.8 ajouteraient un autre hôte portant le même nom. Zabbix 1.8.1 et versions ultérieures ajoutent **\_N** au nom d’hôte, où **N** est un nombre croissant, en commençant par 2. ::: #### Adding host Information about configured hosts in Zabbix is available in *Configuration → Hosts* and *Monitoring* → *Hosts*. There is already one pre-defined host, called "Zabbix server", but we want to learn adding another. To add a new host, click on *Create host*. This will present us with a host configuration form.\  All mandatory input fields are marked with a red asterisk. The bare minimum to enter here is: ***Host name*** - Enter a host name. Alphanumerics, spaces, dots, dashes and underscores are allowed. ***Groups*** - Select one or several existing groups by clicking *Select* button or enter a non-existing group name to create a new group. ::: noteclassic All access permissions are assigned to host groups, not individual hosts. That is why a host must belong to at least one group. ::: ***Interfaces: IP address*** - Although not a required field technically, you may want to enter the IP address of the host. Note that if this is the Zabbix server IP address, it must be specified in the Zabbix agent configuration file 'Server' directive. [Other options](/manual/config/hosts/host#configuration) will suit us with their defaults for now. When done, click *Add*. Your new host should be visible in the host list. {width="600"} The Availability column contains indicators of host availability per each interface. We have defined a Zabbix agent interface, so we can use the agent availability icon (with 'ZBX' on it) to understand host availability: -  - host status has not been established; no metric check has happened yet -  - host is available, a metric check has been successful -  - host is unavailable, a metric check has failed (move your mouse cursor over the icon to see the error message). There might be some error with communication, possibly caused by incorrect interface credentials. Check that Zabbix server is running, and try refreshing the page later as well. #### Ajout d'hôte Les informations sur les hôtes configurés dans Zabbix sont disponibles dans *Configuration → Hôtes* et *Surveillance* → *Hôtes*. Il existe déjà un hôte prédéfini, appelé "Zabbix server", mais nous allons apprendre ici à en ajouter un autre. Pour ajouter un nouvel hôte, cliquez sur *Créer un hôte*. Cela nous présentera un formulaire de configuration de l'hôte.\  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Le strict minimum à saisir ici est : ***Nom d'hôte*** - Saisissez un nom d'hôte. Les caractères alphanumériques, les espaces, les points, les tirets et les traits de soulignement sont autorisés. ***Groupes*** - Sélectionnez un ou plusieurs groupes existants en cliquant sur le bouton *Sélectionner* ou entrez un nom de groupe inexistant pour créer un nouveau groupe. ::: noteclassic Toutes les autorisations d'accès sont attribuées à des groupes d'hôtes, et non à des hôtes individuels. C'est pourquoi un hôte doit appartenir à au moins un groupe. ::: ***Interfaces: Adresse IP*** - Bien qu'il ne s'agisse pas d'un champ obligatoire techniquement, vous pouvez entrer l'adresse IP de l'hôte. Notez que s'il s'agit de l'adresse IP du serveur Zabbix, elle doit être spécifiée dans la directive 'Server' du fichier de configuration de l'agent Zabbix. [Les autres options](/manual/config/hosts/host#configuration) nous conviendront avec leurs valeurs par défaut pour l'instant. Une fois terminé, cliquez sur *Ajouter*. Votre nouvel hôte devrait être visible dans la liste des hôtes. {width="600"} La colonne Disponibilité contient des indicateurs de disponibilité de l'hôte pour chaque interface. Nous avons défini une interface d'agent Zabbix, nous pouvons donc utiliser l'icône de disponibilité de l'agent (avec 'ZBX' dessus) pour comprendre la disponibilité de l'hôte : -  - le statut d'hôte n'a pas été établi ; aucune vérification de métrique n'a encore eu lieu -  - l'hôte est disponible, une vérification des métriques a réussi -  - l'hôte n'est pas disponible, une vérification de métrique a échoué (déplacez le curseur de votre souris sur l'icône pour voir le message d'erreur). Il peut y avoir une erreur de communication, probablement causée par des informations d'identification d'interface incorrectes. Vérifiez que le serveur Zabbix est en cours d'exécution et essayez également d'actualiser la page ultérieurement. #### Adding hosts to host groups Add two hosts to host groups with IDs 5 and 6. Request: ```json { "jsonrpc": "2.0", "method": "hostgroup.massadd", "params": { "groups": [ { "groupid": "5" }, { "groupid": "6" } ], "hosts": [ { "hostid": "30050" }, { "hostid": "30001" } ] }, "auth": "f223adf833b2bf2ff38574a67bba6372", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "groupids": [ "5", "6" ] }, "id": 1 } ``` #### Ajout d'hôtes aux groupes d'hôtes Ajoutez deux hôtes aux groupes d'hôtes avec les ID 5 et 6. Requête : ```json { "jsonrpc": "2.0", "method": "hostgroup.massadd", "params": { "groups": [ { "groupid": "5" }, { "groupid": "6" } ], "hosts": [ { "hostid": "30050" }, { "hostid": "30001" } ] }, "auth": "f223adf833b2bf2ff38574a67bba6372", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "groupids": [ "5", "6" ] }, "id": 1 } ``` #### Adding item to template To add an item to the template, go to the item list for 'New host'. In *Configuration → Hosts* click on *Items* next to 'New host'. Then: - mark the checkbox of the 'CPU Load' item in the list - click on *Copy* below the list - select the template to copy item to  All mandatory input fields are marked with a red asterisk. - click on *Copy* If you now go to *Configuration → Templates*, 'New template' should have one new item in it. We will stop at one item only for now, but similarly you can add any other items, triggers or other entities to the template until it's a fairly complete set of entities for given purpose (monitoring OS, monitoring single application). #### Ajout d'un élément au modèle Pour ajouter un élément au modèle, accédez à la liste des éléments pour 'New host'. Dans *Configuration → Hôtes*, cliquez sur *Éléments* à côté de 'New host'. Alors: - cochez la case de l'élément 'CPU Load' dans la liste - cliquez sur *Copier* sous la liste - sélectionnez le modèle dans lequel copier l'élément  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. - cliquez sur *Copier* Si vous allez maintenant dans *Configuration → Modèles*, 'Nouveau template' devrait contenir un nouvel élément. Nous nous arrêterons à un seul élément pour le moment, mais de la même manière, vous pouvez ajouter d'autres éléments, déclencheurs ou autres entités au modèle jusqu'à ce qu'il s'agisse d'un ensemble assez complet d'entités pour un objectif donné (surveillance du système d'exploitation, surveillance d'une seule application). #### Adding lines In addition to shapes, it is also possible to add some lines. Lines can be used to link elements or shapes in a map. To add a line, click on *Add* next to Shape. A new shape will appear at the top left corner of the map. Select it and click on *Line* in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, color, etc. {width="600"} #### Ajouter des lignes En plus des formes, il est également possible d'ajouter quelques lignes. Les lignes peuvent être utilisées pour relier des éléments ou des formes dans une carte. Pour ajouter une ligne, cliquez sur *Ajouter* à côté de Forme. Une nouvelle forme apparaîtra dans le coin supérieur gauche de la carte. Sélectionnez-le et cliquez sur *Ligne* dans le formulaire d'édition pour changer la forme en ligne. Ajustez ensuite les propriétés de la ligne, telles que le type de ligne, la largeur, la couleur, etc. {width="600"} #### Adding LLD macro paths Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "22450", "lld_macro_paths": [ { "lld_macro": "{#MACRO1}", "path": "$.json.path" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "22450" ] }, "id": 1 } ``` #### Ajouter des chemins de macro LLD Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "22450", "lld_macro_paths": [ { "lld_macro": "{#MACRO1}", "path": "$.json.path" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "22450" ] }, "id": 1 } ``` #### Adding macros Add two new macros to two hosts. Request: ```json { "jsonrpc": "2.0", "method": "host.massadd", "params": { "hosts": [ { "hostid": "10160" }, { "hostid": "10167" } ], "macros": [ { "macro": "{$TEST1}", "value": "MACROTEST1" }, { "macro": "{$TEST2}", "value": "MACROTEST2", "description": "Test description" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10160", "10167" ] }, "id": 1 } ``` #### Ajout de macros Ajoutez deux nouvelles macros à deux hôtes. Requête : ```json { "jsonrpc": "2.0", "method": "host.massadd", "params": { "hosts": [ { "hostid": "10160" }, { "hostid": "10167" } ], "macros": [ { "macro": "{$TEST1}", "value": "MACROTEST1" }, { "macro": "{$TEST2}", "value": "MACROTEST2", "description": "Test description" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10160", "10167" ] }, "id": 1 } ``` #### Adding pages To add a new page to a dashboard: - Make sure the dashboard is in the [editing mode](#viewing_and_editing_a_dashboard) - Click on the arrow next to the *Add* button and select the *Add page* option  - Fill the general page parameters and click on *Apply*. If you leave the name empty, the page will be added with a `Page N` name where 'N' is the incremental number of the page. The page display period allows to customize how long a page is displayed in a slideshow.  A new page will be added, indicated by a new tab (*Page 2*).  The pages can be reordered by dragging-and-dropping the page tabs. Reordering maintains the original page naming. It is always possible to go to each page by clicking on its tab. When a new page is added, it is empty. You can add widgets to it as described above. #### Ajouter des pages Pour ajouter une nouvelle page à un tableau de bord : - Assurez-vous que le tableau de bord est en [mode édition](#viewing_and_editing_a_dashboard) - Cliquez sur la flèche à côté du bouton *Ajouter* et sélectionnez l'option *Ajouter une page*  - Remplissez les paramètres généraux de la page et cliquez sur *Appliquer*. Si vous laissez le nom vide, la page sera ajoutée avec un nom `Page N` où 'N' est le numéro incrémentiel de la page. La période d'affichage de la page permet de personnaliser la durée d'affichage d'une page dans un diaporama.  Une nouvelle page sera ajoutée, indiquée par un nouvel onglet (*Page 2*).  Les pages peuvent être réorganisées en glissant-déposant les onglets de page. La réorganisation conserve le nom de la page d'origine. Il est toujours possible d'accéder à chaque page en cliquant sur son onglet. Lorsqu'une nouvelle page est ajoutée, elle est vide. Vous pouvez y ajouter des widgets comme décrit ci-dessus. ##### Adding permissions By default, a new user has no permissions to access hosts. To grant the user rights, click on the group of the user in the *Groups* column (in this case - 'Zabbix administrators'). In the group properties form, go to the *Permissions* tab. {width="600"} This user is to have read-only access to *Linux servers* group, so click on *Select* next to the user group selection field.  In this pop-up, mark the checkbox next to 'Linux servers', then click *Select*. *Linux servers* should be displayed in the selection field. Click the 'Read' button to set the permission level and then *Add* to add the group to the list of permissions. In the user group properties form, click *Update*. ::: noteimportant In Zabbix, access rights to hosts are assigned to [user groups](/manual/config/users_and_usergroups/usergroup), not individual users. ::: Done! You may try to log in using the credentials of the new user. ##### Ajout de permissions Par défaut, un nouvel utilisateur n'a aucune permission pour accéder aux hôtes. Pour accorder les droits à l'utilisateur, cliquez sur le groupe de l'utilisateur dans la colonne *Groupes* (dans ce cas - 'Zabbix administrators'). Dans le formulaire des propriétés du groupe, allez dans l'onglet *Permissions*. {width="600"} Cet utilisateur doit avoir un accès en lecture seule sur le groupe *Linux servers*, donc, cliquez sur *Sélectionner* à côté du champs de sélection du groupe d'utilisateur.  Dans cette fenêtre, activez la case à côte de 'Linux servers', puis cliquez sur *Sélectionner*. *Linux servers* devrait être affiché dans le champs de sélection. Cliquez sur le bouton 'Lecture' pour attribuer le niveau de permission et sur *Ajouter* pour ajouter le groupe dans la liste des permissions. Dans le formulaire de propriétés du groupe d'utilisateurs, cliquez sur *Mettre à jour*. ::: noteimportant Dans Zabbix, les droits d'accès aux hôtes sont assignés aux [groupes d'utilisateurs](/manual/config/users_and_usergroups/usergroup), pas aux utilisateurs individuellement. ::: Terminé ! Vous pouvez essayer de vous connecter en utilisant les informations d'identification du nouvel utilisateur. #### Adding shapes In addition to map elements, it is also possible to add some shapes. Shapes are not map elements; they are just a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Rectangle and ellipse shapes can be added. To add a shape, click on *Add* next to Shape. The new shape will appear at the top left corner of the map. Drag and drop it wherever you like. A new shape is added with default colors. By clicking on the shape, a form is displayed and you can customize the way a shape looks, add text, etc. {width="600"} To select shapes, select one and then hold down *Ctrl* to select the others. With several shapes selected, common properties can be mass updated, similarly as with elements. Text can be added in the shapes. Expression [macros](/manual/appendix/macros/supported_by_location) are supported in the text, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`). To display text only the shape can be made invisible by removing the shape border (select 'None' in the *Border* field). For example, take note of how the {MAP.NAME} macro, visible in the screenshot above, is actually a rectangle shape with text, which can be seen when clicking on the macro:  {MAP.NAME} resolves to the configured map name when viewing the map. If hyperlinks are used in the text, they become clickable when viewing the map. Line wrapping for text is always "on" within shapes. However, within an ellipse, the lines are wrapped as though the ellipse were a rectangle. Word wrapping is not implemented, so long words (words that do not fit the shape) are not wrapped, but are masked (constructor page) or clipped (other pages with maps). #### Ajouter de formes En plus des éléments cartographiques, il est également possible d'ajouter des formes. Les formes ne sont pas des éléments cartographiques ; ils ne sont qu'une représentation visuelle. Par exemple, une forme rectangulaire peut être utilisée comme arrière-plan pour regrouper certains hôtes. Des formes de rectangle et d'ellipse peuvent être ajoutées. Pour ajouter une forme, cliquez sur *Ajouter* à côté de Forme. La nouvelle forme apparaîtra dans le coin supérieur gauche de la carte. Faites-le glisser et déposez-le où vous le souhaitez. Une nouvelle forme est ajoutée avec les couleurs par défaut. En cliquant sur la forme, un formulaire s'affiche et vous pouvez personnaliser l'apparence d'une forme, ajouter du texte, etc. {width="600"} Pour sélectionner des formes, sélectionnez-en une, puis maintenez la touche *Ctrl* enfoncée pour sélectionner les autres. Avec plusieurs formes sélectionnées, les propriétés communes peuvent être mises à jour en masse, comme pour les éléments. Du texte peut être ajouté dans les formes. Les expressions de[macros](/manual/appendix/macros/supported_by_location) sont prises en charge dans le texte, mais uniquement avec les fonctions `avg`, `last`, `min` et `max`, avec le temps comme paramètre (par exemple, `{ ?avg(/hôte/clé,1h)}`). Pour afficher uniquement du texte, la forme peut être rendue invisible en supprimant la bordure de la forme (sélectionnez 'Aucune' dans le champ *Bordure*). Par exemple, notez que la macro {MAP.NAME}, visible dans la capture d'écran ci-dessus, est en fait une forme de rectangle avec du texte, qui peut être vu en cliquant sur la macro :  {MAP.NAME} se résout au nom de la carte configurée lors de l'affichage de la carte. Si des hyperliens sont utilisés dans le texte, ils deviennent cliquables lors de la visualisation de la carte. Le retour à la ligne pour le texte est toujours "activé" dans les formes. Cependant, dans une ellipse, les lignes sont enveloppées comme si l'ellipse était un rectangle. L'habillage de mots n'est pas implémenté, donc les mots longs (mots qui ne correspondent pas à la forme) ne sont pas enveloppés, mais masqués (page constructeur) ou tronqués (autres pages avec des cartes). #### Adding web scenarios To add web scenarios to a template in *Configuration → Templates*, do the following: - Click on *Web* in the row of the template - Configure a web scenario following the usual method of [configuring web scenarios](/manual/web_monitoring#configuring_a_web_scenario) #### Ajout de scénarios Web Pour ajouter des scénarios Web à un modèle dans *Configuration → Modèles*, faites ce qui suit: - Cliquez sur *Web* dans la ligne du modèle - Configurez un scénario Web en suivant la méthode habituelle de [configuration de scénarios Web](/manual/web_monitoring#configuring_a_web_scenario) ##### Additional parameters A third optional parameter is supported by the *bucket\_rate\_foreach* function: bucket_rate_foreach(item filter,time period,<parameter number>) where <parameter number> is the position of the "bucket" value in the item key. For example, if the "bucket" value in myItem\[aaa,0.2\] is '0.2', then its position is 2. The default value of <parameter number> is '1'. ##### Paramètres supplémentaires Un troisième paramètre facultatif est pris en charge par la fonction *bucket\_rate\_foreach* : bucket_rate_foreach(item filter,time period,<parameter number>) où <parameter number> est la position de la valeur "bucket" dans la clé de l'élément. Par exemple, si la valeur "bucket" dans myItem\[aaa,0.2\] est '0.2', alors sa position est 2. La valeur par défaut de <parameter number> est '1'. ### Administration With the Zabbix API you can change administration settings of your monitoring system. ### Administration Avec l'API Zabbix, vous pouvez modifier les paramètres d'administration de votre système de surveillance. #### Advanced configuration {width=600} |Parameter|Description| |--|--------| |_**Additional rules**_|Click on *Add* to define additional status calculation rules.| |*Set status to*|Set service status to either *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster* in case of a condition match.| |*Condition*|Select the condition for direct child services:<br>**if at least (N) child services have (Status) status or above**<br>**if at least (N%) of child services have (Status) status or above**<br>**if less than (N) child services have (Status) status or below**<br>**if less than (N%) of child services have (Status) status or below**<br>**if weight of child services with (Status) status or above is at least (W)**<br>**if weight of child services with (Status) status or above is at least (N%)**<br>**if weight of child services with (Status) status or below is less than (W)**<br>**if weight of child services with (Status) status or below is less than (N%)** <br><br> If several conditions are specified and the situation matches more than one condition, the highest severity will be set.| |*N (W)*|Set the value of N or W (1-100000), or N% (1-100) in the condition.| |*Status*|Select the value of *Status* in the condition: *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster*.| |_**Status propagation rule**_|Rule for propagating the service status to the parent service:<br>**As is** - the status is propagated without change<br>**Increase by** - you may increase the propagated status by 1 to 5 severities<br>**Decrease by** - you may decrease the propagated status by 1 to 5 severities<br>**Ignore this service** - the status is not propagated to the parent service at all<br>**Fixed status** - the status is propagated statically, i.e. as always the same| |_**Weight**_|Weight of the service (integer in the range from 0 (default) to 1000000).| :::noteclassic Additional status calculation rules can only be used to increase severity level over the level calculated according to the main *Status calculation rule* parameter. If according to additional rules the status should be Warning, but according to the *Status calculation rule* the status is Disaster - the service will have status Disaster. ::: #### Configuration avancée {width=600} |Paramètre|Description| |--|--------| |_**Règles supplémentaires**_|Cliquez sur *Ajouter* pour définir des règles de calcul de statut supplémentaires.| |*Définir le statut sur*|Définissez l'état du service sur *OK* (par défaut), *Non classifié*, *Information*, *Avertissement*, *Moyen*, *Élevé* ou *Désastre* en cas de correspondance de condition.| |*Condition*|Sélectionnez la condition pour les services aux enfants directs :<br>**si au moins (N) services aux enfants ont le statut (Statut) ou supérieur**<br>**si au moins (N %) des services aux enfants ont le statut (Statut) ou supérieur**<br>**si moins de (N) services pour enfants ont le statut (Statut) ou inférieur**<br>**si moins de (N %) des services pour enfants ont le statut (Statut) ou inférieur** <br>**si le poids des services pour enfants avec le statut (Statut) ou supérieur est d'au moins (W)**<br>**si le poids des services pour enfants avec le statut (Statut) ou supérieur est d'au moins (N%)* *<br>**si le poids des services pour enfants avec le statut (Statut) ou inférieur est inférieur à (W)**<br>**si le poids des services pour enfants avec le statut (Statut) ou inférieur est inférieur à (N %) ** <br><br> Si plusieurs conditions sont spécifiées et que la situation correspond à plus d'une condition, la gravité la plus élevée sera définie.| |*N (W)*|Définissez la valeur de N ou W (1-100000), ou N% (1-100) dans la condition.| |*Statust|Sélectionnez la valeur de *Statut* dans la condition : *OK* (par défaut), *Non classifié*, *Information*, *Avertissement*, *Moyen*, *Élevé* ou *Désastre*.| |_**Règle de propagation d'état**_|Règle de propagation de l'état du service au service parent :<br>**Tel quel** - l'état est propagé sans modification<br>**Augmenter de** - vous pouvez augmenter l'état propagé de 1 à 5 niveaux de sévérité<br >**Diminuer de** - vous pouvez diminuer le statut propagé de 1 à 5 niveaux de sévérité<br>**Ignorer ce service** - le statut n'est pas du tout propagé au service parent<br>**Statut fixe** - le statut est propagé statiquement, c'est-à-dire toujours le même| |_**Poids**_|Poids du service (entier compris entre 0 (par défaut) et 1 000 000).| :::noteclassic Les règles de calcul d'état supplémentaires ne peuvent être utilisées que pour augmenter le niveau de sévérité par rapport au niveau calculé selon le paramètre principal *Règle de calcul d'état*. Si, selon des règles supplémentaires, le statut doit être Avertissement, mais selon la *règle de calcul du statut*, le statut est Désastre - le service aura le statut Désastre. ::: After receiving a list of active checks the agent marks obsolete persistent files for removal. A persistent file becomes obsolete if: 1) the corresponding log item is no longer monitored, 2) a log item is reconfigured with a different **persistent\_dir** location than before. Removing is done with delay 24 hours because log files in NOTSUPPORTED state are not included in the list of active checks but they may become SUPPORTED later and their persistent files will be useful. If the agent is stopped before 24 hours expire, then the obsolete files will not be deleted as Zabbix agent is not getting info about their location from Zabbix server anymore. ::: notewarning Reconfiguring a log item's **persistent\_dir** back to the old **persistent\_dir** location while the agent is stopped, without deleting the old persistent file by user - will cause restoring the agent state from the old persistent file resulting in missed messages or false alerts. ::: Après avoir reçu une liste de vérifications actives, l'agent marque les fichiers persistants obsolètes pour suppression. Un fichier persistant devient obsolète si : 1) l'élément de journal correspondant n'est plus surveillé, 2) un élément de journal est reconfiguré avec un emplacement **persistent\_dir** différent de celui d'avant. La suppression est effectuée avec un délai de 24 heures car les fichiers journaux à l'état NOTSUPPORTED ne sont pas inclus dans la liste des vérifications actives, mais ils peuvent devenir SUPPORTED plus tard et leurs fichiers persistants seront utiles. Si l'agent est arrêté avant l'expiration de 24 heures, les fichiers obsolètes ne seront pas supprimés car l'agent Zabbix ne reçoit plus d'informations sur leur emplacement depuis le serveur Zabbix. ::: notewarning Reconfigurer le **persistent\_dir** d'un élément de journal vers l'ancien emplacement **persistent\_dir** pendant que l'agent est arrêté, sans supprimer l'ancien fichier persistant par l'utilisateur - entraînera la restauration de l'état de l'agent à partir de l'ancien fichier persistant résultant dans les messages manqués ou les fausses alertes. ::: ##### Agent 2 |Requirement|Mandatory status|Description| |--|-|-------| |*libpcre/libpcre2*|One of|PCRE/PCRE2 library is required for [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) support.<br>The naming may differ depending on the GNU/Linux distribution, for example 'libpcre3' or 'libpcre1'. PCRE v8.x and PCRE2 v10.x (from Zabbix 6.0.0) are supported.<br>Required for log monitoring. Also required on Windows.| |*libopenssl*|No|Required when using encryption.<br>OpenSSL 1.0.1 or later is required on UNIX platforms.<br>The OpenSSL library must have PSK support enabled. LibreSSL is not supported.<br>On Microsoft Windows systems OpenSSL 1.1.1 or later is required.| **Golang libraries** |[git.zabbix.com/ap/plugin-support](https://git.zabbix.com/projects/AP/repos/plugin-support)|Yes|1.X.X|Zabbix own support library. Mostly for plugins. | |[github.com/BurntSushi/locker](https://github.com/BurntSushi/locker)|^|0.0.0|Named read/write locks, access sync. | |[github.com/chromedp/cdproto](https://github.com/chromedp/cdproto)|^|0.0.0|Generated commands, types, and events for the Chrome DevTools Protocol domains. | |[github.com/chromedp/chromedp](https://github.com/chromedp/chromedp)|^|0.6.0|Chrome DevTools Protocol support (report generation). | |[github.com/dustin/gomemcached](https://github.com/dustin/gomemcached)|^|0.0.0|A memcached binary protocol toolkit for go. | |[github.com/eclipse/paho.mqtt.golang](https://github.com/eclipse/paho.mqtt.golang)|^|1.2.0|A library to handle MQTT connections. | |[github.com/fsnotify/fsnotify](https://github.com/fsnotify/fsnotify)|^|1.4.9|Cross-platform file system notifications for Go. | |[github.com/go-ldap/ldap](https://github.com/go-ldap/ldap)|^|3.0.3|Basic LDAP v3 functionality for the GO programming language. | |[github.com/go-ole/go-ole](https://github.com/go-ole/go-ole)|^|1.2.4|Win32 ole implementation for golang. | |[github.com/godbus/dbus](https://github.com/godbus/dbus)|^|4.1.0|Native Go bindings for D-Bus. | |[github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)|^|1.5.0|MySQL driver. | |[github.com/godror/godror](https://github.com/godror/godror)|^|0.20.1|Oracle DB driver. | |[github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)|^|2.0.3|Sqlite3 driver. | |[github.com/mediocregopher/radix/v3](https://github.com/mediocregopher/radix)|^|3.5.0|Redis client. | |[github.com/memcachier/mc/v3](https://github.com/memcachier/mc)|^|3.0.1|Binary Memcached client. | |[github.com/miekg/dns](https://github.com/miekg/dns)|^|1.1.43|DNS library. | |[github.com/omeid/go-yarn](https://github.com/omeid/go-yarn)|^|0.0.1|Embeddable filesystem mapped key-string store. | |[github.com/goburrow/modbus](https://github.com/goburrow/modbus)|^|0.1.0|Fault-tolerant implementation of Modbus. | |[golang.org/x/sys](https://golang.org/x/sys)|^|0.0.0|Go packages for low-level interactions with the operating system.<br>Also used in plugin support lib. Used in MongoDB plugin. | |[github.com/natefinch/npipe](https://github.com/natefinch/npipe)|On Windows|0.0.0|Windows named pipe implementation.<br>Also used in plugin support lib. | |[github.com/goburrow/serial](https://github.com/goburrow/serial)|Yes, indirect^**1**^|0.1.0|Serial library for Modbus. | |[golang.org/x/xerrors](https://golang.org/x/xerrors)|^|0.0.0|Functions to manipulate errors. | |[gopkg.in/asn1-ber.v1](https://gopkg.in/asn1-ber.v1)|^|1.0.0|Encoding/decoding library for ASN1 BER. | |[github.com/go-stack/stack](https://github.com/go-stack/stack)|No, indirect^**1**^|1.8.0| | |[github.com/golang/snappy](https://github.com/golang/snappy)|^|0.0.1| | |[github.com/klauspost/compress](https://github.com/klauspost/compress)|^|1.13.6| | |[github.com/xdg-go/pbkdf2](https://github.com/xdg-go/pbkdf2)|^|1.0.0| | |[github.com/xdg-go/scram](https://github.com/xdg-go/scram)|^|1.0.2| | |[github.com/xdg-go/stringprep](https://github.com/xdg-go/stringprep)|^|1.0.2| | |[github.com/youmark/pkcs8](https://github.com/youmark/pkcs8)|^|0.0.0| | |[golang.org/x/sys](https://golang.org/x/sys)|^|0.0.0| | ^**1**^ "Indirect" means that it is used in one of the libraries that the agent uses. It's required since Zabbix uses the library that uses the package. See also dependencies for loadable plugins: - [PostgreSQL](/manual/installation/requirements/plugins/postgresql) - [MongoDB](/manual/installation/requirements/plugins/mongodb) ##### Agent 2 |Pré-requis|Obligatoire|Description| |--|-|-------| |*libpcre/libpcre2*|L'une des deux|La bibliothèque PCRE/PCRE2 est requise pour la prise en charge de [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE).<br>Le nom peut différer selon la distribution GNU/Linux, par exemple 'libpcre3' ou 'libpcre1'. PCRE v8.x et PCRE2 v10.x (à partir de Zabbix 6.0.0) sont pris en charge.<br>Requis pour la surveillance des journaux. Également requis sous Windows.| |*libopenssl*|Non|Requis lors de l'utilisation du chiffrement.<br>OpenSSL 1.0.1 ou version ultérieure est requis sur les plates-formes UNIX.<br>La bibliothèque OpenSSL doit avoir la prise en charge PSK activée. LibreSSL n'est pas pris en charge.<br>Sur les systèmes Microsoft Windows, OpenSSL 1.1.1 ou version ultérieure est requis.| **Bibliothèques Golang** |Pré-requis|Obligatoire|Version minimale|Description| |--|-|-|-------| |[git.zabbix.com/ap/plugin-support](https://git.zabbix.com/projects/AP/repos/plugin-support)|Oui|0.0.0|Zabbix possède sa propre bibliothèque de support. Principalement pour les plugins.<br>Également utilisé dans le plugin MongoDB. | |[github.com/BurntSushi/locker](https://github.com/BurntSushi/locker)|^|0.0.0|Verrous de lecture/écriture nommés, synchronisation d'accès. | |[github.com/chromedp/cdproto](https://github.com/chromedp/cdproto)|^|0.0.0|Commandes, types et événements générés pour les domaines du protocole Chrome DevTools. | |[github.com/chromedp/chromedp](https://github.com/chromedp/chromedp)|^|0.6.0|Prise en charge du protocole Chrome DevTools (génération de rapports).| |[github.com/dustin/gomemcached](https://github.com/dustin/gomemcached)|^|0.0.0|Une boîte à outils de protocole binaire memcached pour go.| |[github.com/eclipse/paho.mqtt.golang](https://github.com/eclipse/paho.mqtt.golang)|^|1.2.0|Une bibliothèque pour gérer les connexions MQTT. | |[github.com/fsnotify/fsnotify](https://github.com/fsnotify/fsnotify)|^|1.4.9|Notifications du système de fichiers multiplateforme pour Go.| |[github.com/go-ldap/ldap](https://github.com/go-ldap/ldap)|^|3.0.3|Fonctionnalité LDAP v3 de base pour le langage de programmation GO. | |[github.com/go-ole/go-ole](https://github.com/go-ole/go-ole)|^|1.2.4|Implémentation Win32 ole pour golang. | |[github.com/godbus/dbus](https://github.com/godbus/dbus)|^|4.1.0|Fixations Go natives pour D-Bus. | |[github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)|^|1.5.0|Pilote MySQL. | |[github.com/godror/godror](https://github.com/godror/godror)|^|0.20.1|Pilote Oracle DB. | |[github.com/jackc/pgx/v4](https://github.com/jackc/pgx)|^|4.8.2|Pilote PostgreSQL. | |[github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)|^|2.0.3|Pilote Sqlite3. | |[github.com/mediocregopher/radix/v3](https://github.com/mediocregopher/radix)|^|3.5.0|Client Redis. | |[github.com/memcachier/mc/v3](https://github.com/memcachier/mc)|^|3.0.1|Client Binary Memcached. | |[github.com/miekg/dns](https://github.com/miekg/dns)|^|1.1.43|Bibliothèque DNS. | |[github.com/omeid/go-yarn](https://github.com/omeid/go-yarn)|^|0.0.1|Magasin de chaînes de clés mappé par système de fichiers intégrable. | |[github.com/goburrow/modbus](https://github.com/goburrow/modbus)|^|0.1.0|Implémentation tolérante aux pannes de Modbus. | |[golang.org/x/sys](https://golang.org/x/sys)|^|0.0.0|Packages Go pour les interactions de bas niveau avec le système d'exploitation.<br>Également utilisé dans la bibliothèque de support des plugins. Utilisé dans le plug-in MongoDB. | |[github.com/natefinch/npipe](https://github.com/natefinch/npipe)|Sous Windows|0.0.0|Implémentation du canal nommé Windows.<br>Également utilisé dans la bibliothèque de prise en charge des plugins. Utilisé dans le plug-in MongoDB. | |[github.com/goburrow/serial](https://github.com/goburrow/serial)|Oui, indirect^**1**^|0.1.0|Bibliothèque série pour Modbus. | |[github.com/pkg/errors](https://github.com/pkg/errors)|^|0.9.1|Simples primitives de gestion des erreurs.<br>Utilisé dans le plugin MongoDB. | |[golang.org/x/xerrors](https://golang.org/x/xerrors)|^|0.0.0|Fonctions pour manipuler les erreurs. | |[gopkg.in/asn1-ber.v1](https://gopkg.in/asn1-ber.v1)|^|1.0.0|Bibliothèque d'encodage/décodage pour ASN1 BER. | |[gopkg.in/yaml.v2](https://gopkg.in/yaml.v2)|^|2.2.8|Go package pour encoder et décoder les valeurs YAML. | |[github.com/go-stack/stack](https://github.com/go-stack/stack)|Non, indirect^**1**^|1.8.0|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/golang/snappy](https://github.com/golang/snappy)|^|0.0.1|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/klauspost/compress](https://github.com/klauspost/compress)|^|1.13.6|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/xdg-go/pbkdf2](https://github.com/xdg-go/pbkdf2)|^|1.0.0|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/xdg-go/scram](https://github.com/xdg-go/scram)|^|1.0.2|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/xdg-go/stringprep](https://github.com/xdg-go/stringprep)|^|1.0.2|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/youmark/pkcs8](https://github.com/youmark/pkcs8)|^|0.0.0|Package requis pour le plug-in MongoDB mongo-driver lib. | |[golang.org/x/crypto](https://golang.org/x/crypto)|^|0.0.0|Package requis pour le plug-in MongoDB mongo-driver lib. | |[golang.org/x/text](https://golang.org/x/text)|^|0.3.5|Package requis pour le plug-in MongoDB mongo-driver lib. | |[golang.org/x/sys](https://golang.org/x/sys)|^|0.0.0|Package requis pour le plug-in MongoDB mongo-driver lib. | |[github.com/natefinch/npipe](https://github.com/natefinch/npipe)|^|0.0.0|Package requis pour le plug-in MongoDB mongo-driver lib. | ^**1**^ "Indirect" signifie qu'il est utilisé dans l'une des bibliothèques utilisées par l'agent. Nécessaire car Zabbix utilise la bibliothèque qui utilise le package. ##### Agent configuration HA cluster nodes (servers) must be listed in the configuration of Zabbix agent or Zabbix agent 2.  To enable passive checks, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_agentd), separated by a **comma**. ``` Server=zabbix-node-01,zabbix-node-02 ``` To enable active checks, the node names must be listed in the ServerActive [parameter](/manual/appendix/config/zabbix_agentd). Note that for active checks the nodes must be separated by a comma from any other servers, while the nodes themselves must be separated by a **semicolon**, e.g.: ``` ServerActive=zabbix-node-01;zabbix-node-02 ``` ##### Configuration des agents Les nœuds de cluster HA (serveurs) doivent être répertoriés dans la configuration de l'agent Zabbix ou de l'agent Zabbix 2.  Pour activer les vérifications passives, les noms de nœud doivent être répertoriés dans le [paramètre](/manual/appendix/config/zabbix_agentd) du serveur, séparés par une **virgule**. ``` Serveur=zabbix-node-01,zabbix-node-02 ``` Pour activer les vérifications actives, les noms de nœud doivent être répertoriés dans le [paramètre](/manual/appendix/config/zabbix_agentd) ServerActive. Notez que pour les vérifications actives, les nœuds doivent être séparés par une virgule de tout autre serveur, tandis que les nœuds eux-mêmes doivent être séparés par un **point-virgule**, par exemple : ``` ServeurActive=zabbix-node-01;zabbix-node-02 ``` **Agent configuration** Now you need to configure the agents. Add the next line to the agent configuration files: HostMetadataItem=system.uname This way you make sure host metadata will contain "Linux" or "Windows" depending on the host an agent is running on. An example of host metadata in this case: Linux: Linux server3 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux Windows: Windows WIN-0PXGGSTYNHO 6.0.6001 Windows Server 2008 Service Pack 1 Intel IA-32 Do not forget to restart the agent after making any changes to the configuration file. ##### Configuration de l'agent Vous devez maintenant configurer les agents. Ajoutez la ligne suivante aux fichiers de configuration de l'agent : ``` HostMetadataItem=system.uname ``` Ainsi, vous vous assurez que les métadonnées de l'hôte contiendront "Linux" ou "Windows" en fonction de l'hôte sur lequel un agent s'exécute. Un exemple de métadonnées hôte dans ce cas : ``` Linux : Linux server3 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/LinuxWindows : Windows WIN-0PXGGSTYNHO 6.0.6001 Windows Server 2008 Service Pack 1 Intel IA-32 ``` N'oubliez pas de redémarrer l'agent après avoir apporté des modifications au fichier de configuration. ### Agent data request The agent data request contains the gathered item values. | Field |<| Type | Mandatory | Value | |-|------|--|-|-----------------------| | request |<| _string_ | yes | `agent data` | | host |<| _string_ | yes | Host name. | | version |<| _string_ | yes | The agent version: \<major>.\<minor>. | | session |<| _string_ | yes | Unique session identifier generated each time when agent is started. | | data |<| _array of objects_ | yes | Item values. | | | id | _number_ | yes | The value identifier (incremental counter used for checking duplicated values in the case of network problems). | |^| itemid | _number_ | yes | Item identifier. | |^| value | _string_ | no | The item value. | |^| lastlogsize | _number_ | no | The item lastlogsize. | |^| mtime | _number_ | no | The item mtime. | |^| state | _number_ | no | The item state. | |^| source | _string_ | no | The value event log source. | |^| eventid | _number_ | no | The value event log eventid. | |^| severity | _number_ | no | The value event log severity. | |^| timestamp | _number_ | no | The value event log timestamp. | |^| clock | _number_ | yes | The value timestamp (seconds since Epoch). | |^| ns | _number_ | yes | The value timestamp nanoseconds. | Example: ```json { "request": "agent data", "data": [ { "id": 1, "itemid": 5678, "value": "2.4.0", "clock": 1400675595, "ns": 76808644 }, { "id": 2, "itemid": 1234, "lastlogsize": 112, "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).", "clock": 1400675595, "ns": 77053975 } ], "host": "Zabbix server", "version": "6.0", "sessionid": "1234456akdsjhfoui" } ``` ### Demande de données agent La demande de données agent contient les valeurs d'élément collectées. | Champ |<| Type | Obligatoire | Valeur | |-|------|--|-|-----------------------| | request |<| _string_ | oui | `agent data` | | host |<| _string_ | oui | Nom d'hôte. | | version |<| _string_ | oui | La version de l'agent : \<majeur>.\<mineur>. | | session |<| _string_ | oui | Identifiant de session unique généré à chaque démarrage de l'agent. | | data |<| _array of objects_ | oui | Valeurs des éléments. | | | id | _number_| oui | L'identifiant de la valeur (compteur incrémental utilisé pour vérifier les valeurs dupliquées en cas de problèmes de réseau). | |^| itemid | _number_| oui | Identificateur d'élément. | |^| calue| _string_ | non | La valeur de l'élément. | |^| lastlogsize | _number_| non | Dernière taille du journal de l'élément. | |^| mtime | _number_| non | Heure de l'élément. | |^| state | _number_| non | L'état de l'élément. | |^| source | _string_ | non | Source du journal des événements de valeur. | |^| eventid | _number_| non | La valeur eventid du journal des événements. | |^| severity | _number_| non | La sévérité du journal des événements de la valeur. | |^| timestamp | _number_| non | Horodatage du journal des événements de la valeur. | |^| clock | _number_| oui | L'horodatage de la valeur (secondes depuis Epoch). | |^| ns | _number_| oui | La valeur d'horodatage en nanosecondes. | Exemple: ```json { · "request": "agent data", · "data": [ · { · "id": 1, · "itemid": 5678, · "value": "2.4.0", · "clock": 1400675595, · "ns": 76808644 · }, · { · "id": 2, · "itemid": 1234, · "lastlogsize": 112, · "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).", · "clock": 1400675595, · "ns": 77053975 · } · ], · "host": "Zabbix server", · "version": "6.0", · "sessionid": "1234456akdsjhfoui" } ``` ### Agent data response The agent data response is sent by the server back to agent after processing the agent data request. | Field | Type | Mandatory | Value | |-|-|-|--------| | response | _string_ | yes | `success` \| `failed` | | info | _string_ | yes | Item processing results. | Example: ```json { "response": "success", "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ``` ### Réponse des données agent La réponse de données agent est renvoyée par le serveur à l'agent après le traitement de la demande de données agent. | Champ | Type | Obligatoire | Valeur | |-|-|-|--------| | response | _string_ | oui | `success` \| `failed` | | info | _string_ | oui | Résultats du traitement des éléments. | Exemple: ```json { · "response": "success", · "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ``` #### Agent on UNIX-like systems Zabbix agent on UNIX-like systems is run on the host being monitored. #### Agent sur les systèmes de type Unix L’agent Zabbix sur les systèmes de type Unix s'exécute sur l’hôte qui est surveillé. #### Agent on Windows systems Zabbix agent on Windows runs as a Windows service. #### Agent sur les systèmes Windows L'agent Zabbix sur Windows s'exécute en tant que service Windows. ##### Agent operation with persistent file On startup Zabbix agent knows nothing about persistent files. Only after receiving a list of active checks from Zabbix server \(proxy\) the agent sees that some log items should be backed by persistent files under specified directories. During agent operation the persistent files are opened for writing (with fopen(filename, "w")) and overwritten with the latest data. The chance of losing persistent file data if the overwriting and file system mirror split happen at the same time is very small, no special handling for it. Writing into persistent file is NOT followed by enforced synchronization to storage media \(fsync\(\) is not called\). Overwriting with the latest data is done after successful reporting of matching log file record or metadata \(processed log size and modification time\) to Zabbix server. That may happen as often as every item check if log file keeps changing. No special actions during agent shutdown. ##### Fonctionnement de l'agent avec fichier persistant Au démarrage, l'agent Zabbix ne sait rien des fichiers persistants. Ce n'est qu'après avoir reçu une liste des vérifications actives du serveur Zabbix \(proxy\) que l'agent constate que certains éléments du journal doivent être sauvegardés par des fichiers persistants dans des répertoires spécifiés. Pendant le fonctionnement de l'agent, les fichiers persistants sont ouverts en écriture (avec fopen(filename, "w")) et écrasés par les dernières données. Le risque de perdre des données de fichiers persistantes si l'écrasement et la séparation du miroir du système de fichiers se produisent en même temps est très faible, aucune gestion spéciale n'est nécessaire. L'écriture dans un fichier persistant N'EST PAS suivie d'une synchronisation forcée avec le support de stockage \(fsync\(\) n'est pas appelé\). L'écrasement avec les dernières données est effectué après le signalement réussi de l'enregistrement de fichier journal ou des métadonnées correspondants \(taille du journal traité et heure de modification\) au serveur Zabbix. Cela peut se produire aussi souvent que chaque élément vérifie si le fichier journal continue de changer. Aucune action spéciale lors de l'arrêt de l'agent. ##### Agent |Requirement|Mandatory status|Description| |--|-|-------| |*libpcre/libpcre2*|One of|PCRE/PCRE2 library is required for [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) support.<br>The naming may differ depending on the GNU/Linux distribution, for example 'libpcre3' or 'libpcre1'. PCRE v8.x and PCRE2 v10.x (from Zabbix 6.0.0) are supported.<br>Required for log monitoring. Also required on Windows.| |*libpthread*|Yes|Required for mutex and read-write lock support (could be part of libc). Not required on Windows.| |*libresolv*|^|Required for DNS resolution (could be part of libc). Not required on Windows.| |*libiconv*|^|Required for text encoding/format conversion to UTF-8 in log items, file content, file regex and regmatch items (could be part of libc). Not required on Windows.| |*libgnutls* or *libopenssl*|No|Required if using [encryption](/manual/encryption#compiling_zabbix_with_encryption_support).<br>Minimum versions: *libgnutls* - 3.1.18, *libopenssl* - 1.0.1<br>On Microsoft Windows OpenSSL 1.1.1 or later is required.| |*libldap*|^|Required if LDAP is used. Not supported on Windows.| |*libcurl*|^|Required for `web.page.*` Zabbix agent [items](/manual/config/items/itemtypes/zabbix_agent). Not supported on Windows.<br>Version 7.28.0 or higher is recommended.| |*libmodbus*|^|Only required if Modbus monitoring is used.<br>Version 3.0 or higher.| ::: noteclassic Starting from version 5.0.3, Zabbix agent will not work on AIX platforms below versions 6.1 TL07 / AIX 7.1 TL01. ::: ##### Agent |Pré-requis|Obligation|Description| |--|-|-------| |*libpcre/libpcre2*|L'une des bibliothèques|PCRE/PCRE2 est requise pour la prise en charge de [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE).<br>La dénomination peut différer selon la distribution GNU/Linux , par exemple 'libpcre3' ou 'libpcre1'. PCRE v8.x et PCRE2 v10.x (à partir de Zabbix 6.0.0) sont pris en charge.<br>Requis pour la surveillance des journaux. Également requis sous Windows.| |*libpthread*|Oui|Requis pour la prise en charge du mutex et du verrouillage en lecture-écriture (peut faire partie de la libc). Non requis sous Windows.| |*libresolv*|^|Requis pour la résolution DNS (peut faire partie de la libc). Non requis sous Windows.| |*libiconv*|^|Requis pour l'encodage de texte/la conversion de format en UTF-8 dans les éléments de journal, le contenu du fichier, l'expression régulière de fichier et les éléments de correspondance de règle (peut faire partie de la libc). Non requis sous Windows.| |*libgnutls* or *libopenssl*|Non|Requis si vous utilisez l'[encryptage](/manual/encryption#compiling_zabbix_with_encryption_support).<br>Versions minimales : *libgnutls* - 3.1.18, *libopenssl* - 1.0.1<br>Sur Microsoft Windows, OpenSSL 1.1.1 ou version ultérieure est requis .| |*libldap*|^|Requis si LDAP est utilisé. Non pris en charge sous Windows.| |*libcurl*|^|Requis pour les éléments agent Zabbix [`web.page.*`](/manual/config/items/itemtypes/zabbix_agent). Non pris en charge sur Windows.<br>La version 7.28.0 ou supérieure est recommandée.| |*libmodbus*|^|Nécessaire uniquement si la surveillance Modbus est utilisée.<br>Version 3.0 ou supérieure.| ::: noteclassic À partir de la version 5.0.3, l'agent Zabbix ne fonctionnera pas sur les plates-formes AIX inférieures aux versions 6.1 TL07 / AIX 7.1 TL01. ::: #### Agent upgrade process ::: noteimportant Upgrading agents is not mandatory. You only need to upgrade agents if it is required to access the new functionality. ::: The upgrade procedure described in this section may be used for upgrading both the Zabbix agent and the Zabbix agent 2. #### Processus de mise à niveau de l'agent ::: noteimportant La mise à niveau des agents n'est pas obligatoire. Vous ne devez mettre à niveau les agents que si cela est nécessaire pour accéder à la nouvelle fonctionnalité. ::: La procédure de mise à niveau décrite dans cette section peut être utilisée pour mettre à niveau à la fois l'agent Zabbix et l'agent Zabbix 2. ##### Agent Zabbix agents are deployed on monitoring targets to actively monitor local resources and applications and report the gathered data to Zabbix server. Since Zabbix 4.4, there are two types of agents available: the [Zabbix agent](/manual/concepts/agent) (lightweight, supported on many platforms, written in C) and the [Zabbix agent 2](/manual/concepts/agent2) (extra-flexible, easily extendable with plugins, written in Go). ##### Agent Les Agents Zabbix sont déployés sur des cibles de surveillance pour superviser activement les ressources locales et les applications, et envoyer les données collectées au serveur Zabbix. Depuis Zabbix 4.4, il existe deux types d'agents disponibles : l'[Agent Zabbix](/manual/concepts/agent) (léger, pris en charge sur de nombreuses plates-formes, écrit en C) et l'[Agent Zabbix 2](/manual/concepts/agent2) (extra-flexible, facilement extensible avec des plugins, écrit en Go). ##### AIX, HP-UX If `watch` command is not available, one can try while [ 1 ]; do ps -fu zabbix; sleep 1; clear; done ##### AIX, HP-UX Si la commande `watch` n'est pas disponible , vous pouvez essayer : while [ 1 ]; do ps -fu zabbix; sleep 1; clear; done #### AIX See values supported for 'memtype' parameter on AIX in the table. |Supported value|Description|Source in procentry64 structure|Tries to be compatible with| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|pi\_size| | |pmem|Percentage of real memory|pi\_prm|ps -o pmem| |rss|Resident set size|pi\_trss + pi\_drss|ps -o rssize| |size|Size of process (code + data)|pi\_dvm|"ps gvw" SIZE column| |dsize|Data size|pi\_dsize|<| |tsize|Text (code) size|pi\_tsize|"ps gvw" TSIZ column| |sdsize|Data size from shared library|pi\_sdsize|<| |drss|Data resident set size|pi\_drss| | |trss|Text resident set size|pi\_trss| | #### AIX Vous trouverez les valeurs prises en charge pour le paramètre 'memtype' sous AIX dans le tableau suivant. |Valeur prise en charge|Description|Source dans la structure procentry64|Essaye d'être compatible avec| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Taille de la mémoire virtuelle|pi\_size| | |pmem|Pourcentage de mémoire réelle|pi\_prm|ps -o pmem| |rss|Taille de l'ensemble résident|pi\_trss + pi\_drss|ps -o rssize| |size|Taille du processus (code + données)|pi\_dvm|"ps gvw" SIZE column| |dsize|Taille des données|pi\_dsize|<| |tsize|Taille du texte (code)|pi\_tsize|"ps gvw" Colonne TSIZ| |sdsize|Taille des données de la bibliothèque partagée|pi\_sdsize|<| |drss|Taille de l'ensemble résident des données|pi\_drss| | |trss|Taille de l'ensemble résident du texte|pi\_trss| | #### Alerter process crash in RHEL 7 Instances of a Zabbix server alerter process crash have been encountered in RHEL 7. Please see [ZBX-10461](https://support.zabbix.com/browse/ZBX-10461) for details. #### Plantage du processus Alerter dans RHEL 7 Des plantages des instances du processus d'alerte du serveur Zabbix ont été rencontrées dans RHEL 7. Veuillez consulter [ZBX-10461](https://support.zabbix.com/browse/ZBX-10461) pour plus de détails. # alert.get # alert.get ### Alert ::: noteclassic Alerts are created by the Zabbix server and cannot be modified via the API. ::: The alert object contains information about whether certain action operations have been executed successfully. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |alertid|string|ID of the alert.| |actionid|string|ID of the action that generated the alert.| |alerttype|integer|Alert type.<br><br>Possible values:<br>0 - message;<br>1 - remote command.| |clock|timestamp|Time when the alert was generated.| |error|string|Error text if there are problems sending a message or running a command.| |esc\_step|integer|Action escalation step during which the alert was generated.| |eventid|string|ID of the event that triggered the action.| |mediatypeid|string|ID of the media type that was used to send the message.| |message|text|Message text. Used for message alerts.| |retries|integer|Number of times Zabbix tried to send the message.| |sendto|string|Address, user name or other identifier of the recipient. Used for message alerts.| |status|integer|Status indicating whether the action operation has been executed successfully.<br><br>Possible values for message alerts:<br>0 - message not sent.<br>1 - message sent.<br>2 - failed after a number of retries.<br>3 - new alert is not yet processed by alert manager.<br><br>Possible values for command alerts:<br>0 - command not run.<br>1 - command run.<br>2 - tried to run the command on the Zabbix agent but it was unavailable.| |subject|string|Message subject. Used for message alerts.| |userid|string|ID of the user that the message was sent to.| |p\_eventid|string|ID of problem event, which generated the alert.| |acknowledgeid|string|ID of acknowledgment, which generated the alert.| ### Alerte ::: noteclassic Les alertes sont créées par le serveur Zabbix et ne peuvent pas être modifiées via l'API. ::: L'objet alerte contient des informations indiquant si certaines opérations d'action ont été exécutées avec succès. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |-------|--------------------------------------------------------|-----------| |alertid|string|identifiant de l'alerte.| |actionid|string|identifiant de l'action qui a généré l'alerte.| |alerttype|integer|Type d'alerte.<br><br>Valeurs possibles :<br>0 - message ;<br>1 - commande à distance.| |horloge|horodatage|Heure à laquelle l'alerte a été générée.| |error|string|Texte d'erreur en cas de problème lors de l'envoi d'un message ou de l'exécution d'une commande.| |esc\_step|integer|Étape d'escalade de l'action au cours de laquelle l'alerte a été générée.| |eventid|string|identifiant de l'événement qui a déclenché l'action.| |mediatypeid|string|identifiant du type de média qui a été utilisé pour envoyer le message.| |message|text|Texte du message. Utilisé pour les alertes de message.| |retries|integer|Nombre de fois que Zabbix a essayé d'envoyer le message.| |sendto|string|Adresse, nom d'utilisateur ou autre identifiant du destinataire. Utilisé pour les alertes de message.| |status|integer|Statut indiquant si l'opération d'action a été exécutée avec succès.<br><br>Valeurs possibles pour les alertes de message :<br>0 - message non envoyé.<br>1 - message envoyé.<br>2 - a échoué après un certain nombre de tentatives.<br>3 - la nouvelle alerte n'est pas encore traitée par le gestionnaire d'alertes.<br><br>Valeurs possibles pour les alertes de commande :<br>0 - la commande n'est pas exécutée.<br>1 - la commande est exécutée .<br>2 - a essayé d'exécuter la commande sur l'agent Zabbix mais elle n'était pas disponible.| |subject|string|Objet du message. Utilisé pour les alertes de message.| |userid|string|identifiant de l'utilisateur auquel le message a été envoyé.| |p\_eventid|string|identifiant de l'événement problématique qui a généré l'alerte.| |acknowledgeid|string|identifiant de l'accusé de réception qui a généré l'alerte.| All of these parameters can be changed in *Administration* → *General* → *Housekeeping* after the installation. ::: notetip You may want to run the timescaledb-tune tool provided by TimescaleDB to optimize PostgreSQL configuration parameters in your `postgresql.conf`. ::: Tous ces paramètres peuvent être modifiés dans *Administration* → *Général* → *Nettoyage* après l'installation. ::: notetip Vous pouvez exécuter l'outil timescaledb-tune fourni par TimescaleDB pour optimiser les paramètres de configuration de PostgreSQL dans votre `postgresql.conf`. ::: ##### Allow specific check, deny others - Whitelist specific checks with AllowKey parameters, deny others with `DenyKey=*` For example: # Allow reading logs: AllowKey=vfs.file.*[/var/log/*] # Allow localtime checks AllowKey=system.localtime[*] # Deny all other keys DenyKey=* ##### Autoriser une vérification spécifique, refuser les autres - Whitelist des vérifications spécifiques avec les paramètres AllowKey, refuser les autres avec `DenyKey=*` Par exemple : # Autoriser la lecture des journaux : AllowKey=vfs.file.*[/var/log/*] # Autoriser les vérifications de l'heure locale AllowKey=system.localtime[*] # Refuser toutes les autres clés DenyKey=* ### AND/OR evaluation in LLD filters The evaluation of AND/OR expressions in the low-level discovery filters/overrides may fail in this version. Fixed in Zabbix 6.0.12. ### Évaluation ET/OU dans les filtres LLD L'évaluation des expressions ET/OU dans les filtres/substitutions de découverte de bas niveau peut échouer dans cette version. Corrigé dans Zabbix 6.0.12. ##### Anomaly detection Zabbix 5.2 introduced new trend functions useful for baseline monitoring. However, they still require defining relative thresholds (e.g. check that web traffic in September, 2021 is less than 2x higher compared to September, 2020). There are use cases when such thresholds are hard to define. For instance, the web traffic of a new but highly popular web site can organically grow many times over a year but the growth rate is unknown. Yet, a sudden traffic spike due to DDOS attack must generate an alert regardless of organic traffic growth. Anomaly detection algorithms do exactly this - find data that doesn't look normal (outliers) in a context of other values. New [history function](/manual/appendix/functions/history) trendstl() has been added which uses 'decomposition' method to calculate the anomaly rate. It splits a single time series sequence into three other sequences: - trend sequence that only contains big changes in the original data (e.g. website traffic shows growth) - season sequence that only contains seasonal changes (e.g. less website traffic in summer, more in autumn) - remainder sequence that only contains residual values that can not be interpreted as parts of trend or season  Anomaly detection works with remainder sequence and checks if there are values that are too far from the majority of remainder values. "Far" means that the absolute value from the remainder sequence is N times greater than the standard or mean deviation. ##### Détection d'anomalie Zabbix 5.2 a introduit de nouvelles fonctions de tendance utiles pour la surveillance de référence. Cependant, ils nécessitent toujours de définir des seuils relatifs (par exemple, vérifier que le trafic Web en septembre 2021 est moins de 2x supérieur à celui de septembre 2020). Il existe des cas d'utilisation où de tels seuils sont difficiles à définir. Par exemple, le trafic Web d'un site Web nouveau très populaire peut croître de manière organique plusieurs fois au cours d'une année, mais le taux de croissance est inconnu. Pourtant, un pic de trafic soudain dû à une attaque DDOS doit générer une alerte quelle que soit la croissance organique du trafic. Les algorithmes de détection d'anomalies font exactement cela - trouver des données qui ne semblent pas normales (valeurs aberrantes) dans un contexte d'autres valeurs. La nouvelle [fonction d'historique](/manual/appendix/functions/history) trendstl() a été ajoutée et utilise la méthode de "décomposition" pour calculer le taux d'anomalies. Il divise une seule séquence de série chronologique en trois autres séquences : - séquence de tendance qui ne contient que de grands changements dans les données d'origine (par exemple, le trafic du site Web montre une croissance) - séquence de saison qui ne contient que des changements saisonniers (par exemple, moins de trafic sur le site Web en été, plus en automne) - séquence restante qui ne contient que des valeurs résiduelles qui ne peuvent pas être interprétées comme des parties de tendance ou de saison  La détection d'anomalies fonctionne avec la séquence restante et vérifie s'il y a des valeurs qui sont trop éloignées de la majorité des valeurs restantes. "Loin" signifie que la valeur absolue de la séquence restante est N fois supérieure à l'écart type ou moyen. ##### Another example with an inline regex modifier Use of the following regular expression including multiple inline modifiers to match the characters after a specific line: (?<=match (?i)everything(?-i) after this line\n)(?sx).*# we add s modifier to allow . match newline characters  Chosen Expression type: "Result is TRUE". Characters after a specific line are matched. ::: noteimportant **g** modifier can't be specified in line. The list of available modifiers can be found in [pcresyntax man page](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16). For more information about PCRE syntax please refer to [PCRE HTML documentation](https://www.pcre.org/original/doc/html/pcrepattern.html). ::: ##### Un autre exemple avec un modificateur de regex en ligne Utilisation de l'expression régulière suivante, y compris plusieurs modificateurs en ligne pour faire correspondre les caractères après une ligne spécifique : (?<=match (?i)everything(?-i) after this line\n)(?sx).*# nous ajoutons le modificateur s pour autoriser . à faire correspondre les caractères de nouvelle ligne  Type d'expression choisi : "Le résultat est VRAI". Les caractères après une ligne spécifique sont mis en correspondance. ::: noteimportant Le modificateur **g** ne peut pas être spécifié en ligne. La liste des modificateurs disponibles se trouve dans [page de manuel pcresyntax](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16). Pour plus d'informations sur la syntaxe PCRE, veuillez consulter la [documentation HTML PCRE](https://www.pcre.org/original/doc/html/pcrepattern.html). ::: ##### API changes See the list of [API changes](/manual/api/changes_5.4_-_6.0) in Zabbix 6.0.0. ##### Modifications de l'API Voir la liste des [modifications d'API](/manual/api/changes_5.4_-_6.0) dans Zabbix 6.0.0. ### API information Retrieve the version of the Zabbix API so that your application could use version-specific features. [API info API](/manual/api/reference/apiinfo) ### Information sur l'API Récupérez la version de l'API Zabbix afin que votre application puisse utiliser des fonctionnalités spécifiques à la version. [API info API](/manual/api/reference/apiinfo) # apiinfo.version # apiinfo.version #### API login A large number of open user sessions can be created when using custom scripts with the `user.login` [method](/manual/api/reference/user/login) without a following `user.logout`. #### Connexion à l'API Un grand nombre de sessions utilisateur ouvertes peuvent être créées lors de l'utilisation de scripts personnalisés avec la [méthode](/manual/api/reference/user/login) `user.login` sans `user.logout` par la suite. #### API Tokens Manage authorization tokens. [Token API](/manual/api/reference/token) #### Tokens d'API Gérez les jetons d'authentification. [API Token](/manual/api/reference/token) ### API versions To simplify API versioning, since Zabbix 2.0.4, the version of the API matches the version of Zabbix itself. You can use the [apiinfo.version](/manual/api/reference/apiinfo/version) method to find out the version of the API you're working with. This can be useful for adjusting your application to use version-specific features. We guarantee feature backward compatibility inside of a major version. When making backward incompatible changes between major releases, we usually leave the old features as deprecated in the next release, and only remove them in the release after that. Occasionally, we may remove features between major releases without providing any backward compatibility. It is important that you never rely on any deprecated features and migrate to newer alternatives as soon as possible. ::: notetip You can follow all of the changes made to the API in the [API changelog](/manual/api/changes_5.4_-_6.0). ::: ### Versions de l'API TPour simplifier la gestion des versions de l'API, depuis Zabbix 2.0.4, la version de l'API correspond à la version de Zabbix elle-même. Vous pouvez utiliser la méthode [apiinfo.version](/manual/api/reference/apiinfo/version) pour connaître la version de l'API avec laquelle vous travaillez. Cela peut être utile pour ajuster votre application afin qu'elle utilise les fonctionnalités spécifiques à la version. Nous garantissons la compatibilité ascendante des fonctionnalités dans une version majeure. Lorsque nous effectuons des modifications incompatibles entre les versions majeures, nous conservons généralement les anciennes fonctionnalités comme obsolètes dans la version suivante et nous les supprimons ensuite de la version suivante. Parfois, nous pouvons supprimer des fonctionnalités entre versions majeures sans fournir de compatibilité ascendante. Il est important que vous ne vous reposiez jamais sur des fonctionnalités obsolètes et que vous migriez vers de nouvelles alternatives dès que possible. ::: notetip Vous pouvez suivre toutes les modifications apportées à l'API dans le [journal des modifications de l'API](/manual/api/changes_5.4_-_6.0). ::: # Appendix 1. Reference commentary # Annexe 1. Commentaire de référence # Appendix 2. Changes from 5.4 to 6.0 # Annexe 2. Changements de 5.4 à 6.0 #### Architecture Zabbix consists of several major software components. Their responsibilities are outlined below. #### Architecture Zabbix se compose de plusieurs composants logiciels majeurs. Leurs responsabilités sont décrites ci-dessous. #### A real life scenario In this example, we would like to set up network discovery for the local network having an IP range of 192.168.1.1-192.168.1.254. In our scenario we want to: - discover those hosts that have Zabbix agent running - run discovery every 10 minutes - add a host to monitoring if the host uptime is more than 1 hour - remove hosts if the host downtime is more than 24 hours - add Linux hosts to the "Linux servers" group - add Windows hosts to the "Windows servers" group - use the template *Linux* for Linux hosts - use the template *Windows* for Windows hosts #### Scénario concret Dans cet exemple, nous souhaiterions configurer la détection de réseau pour le réseau local ayant une plage d'adresses IP : 192.168.1.1-192.168.1.254. Dans notre scénario, nous voulons : - découvrir les hôtes sur lesquels l'agent Zabbix est en cours d'exécution - lancer la découverte toutes les 10 minutes - ajouter un hôte à la surveillance si le temps de disponibilité de l'hôte est supérieur à 1 heure - supprimer des hôtes si le temps d'inactivité de l'hôte est supérieur à 24 heures - ajouter des hôtes Linux au groupe "Linux servers" - ajouter des hôtes Windows au groupe "Windows servers" - utiliser *Template OS Linux* pour les hôtes Linux - utiliser *Template OS Windows* pour les hôtes Windows ##### AS/400 IBM AS/400 platform can be monitored using SNMP. More information is available at <http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg244504.html?Open>. ##### AS/400 La plate-forme IBM AS/400 peut être supervisée via SNMP. De plus amples informations sont disponibles sur <http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg244504.html?Open>. #### Assigning different hosts Replace the hosts currently assigned to maintenance with two different ones. Request: ```json { "jsonrpc": "2.0", "method": "maintenance.update", "params": { "maintenanceid": "3", "hosts": [ {"hostid": "10085"}, {"hostid": "10084"} ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3" ] }, "id": 1 } ``` #### Attribuer différents hôtes Remplacez les hôtes actuellement affectés à la maintenance par deux hôtes différents. Requête : ```json { "jsonrpc": "2.0", "method": "maintenance.update", "params": { "maintenanceid": "3", "hosts": [ {"hostid": "10085"}, {"hostid": "10084"} ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3" ] }, "id": 1 } ``` #### Attempting to use Zabbix sender compiled with TLS support to send data to Zabbix server/proxy compiled without TLS #### Tentative d'utiliser le sender Zabbix compilé avec le support TLS pour envoyer des données au serveur/proxy Zabbix compilé sans TLS ##### Attributes returning composite data It becomes more complicated when your attribute returns composite data. For example: your attribute name is "apple" and it returns a hash representing its parameters, like "weight", "color" etc. Your key may look like this: jmx[com.example:Type=Hello,apple.weight] This is how an attribute name and a hash key are separated, by using a dot symbol. Same way, if an attribute returns nested composite data the parts are separated by a dot: jmx[com.example:Type=Hello,fruits.apple.weight] ##### Attributs renvoyant des données composites Cela devient plus compliqué lorsque votre attribut renvoie des données composites. Par exemple : votre nom d'attribut est "apple" et il renvoie un hachage représentant ses paramètres, comme "poids", "couleur", etc. Votre clé peut ressembler à ceci : jmx[com.example:Type=Hello,apple.weight] C'est ainsi qu'un nom d'attribut et une clé de hachage sont séparés, en utilisant le symbole point. De même, si un attribut renvoie des données composites imbriquées, les parties sont séparées par un point : jmx[com.example:Type=Hello,fruits.apple.weight] ##### Attributes returning tabular data Tabular data attributes consist of one or multiple composite attributes. If such an attribute is specified in the attribute name parameter then this item value will return the complete structure of the attribute in JSON format. The individual element values inside the tabular data attribute can be retrieved using preprocessing. Tabular data attribute example: jmx[com.example:type=Hello,foodinfo] Item value: ``` {.javascript} [ { "a": "apple", "b": "banana", "c": "cherry" }, { "a": "potato", "b": "lettuce", "c": "onion" } ] ``` ##### Attributs renvoyant des données tabulaires Les attributs de données tabulaires consistent en un ou plusieurs attributs composites. Si un tel attribut est spécifié dans le paramètre de nom d'attribut, cette valeur d'élément renverra la structure complète de l'attribut au format JSON. Les valeurs d'élément individuelles à l'intérieur de l'attribut de données tabulaires peuvent être récupérées à l'aide du prétraitement. Exemple d'attribut de données tabulaire : jmx[com.example:type=Hello,foodinfo] Valeur de l'article : ``` {.javascript} [ { "a": "apple", "b": "banana", "c": "cherry" }, { "a": "potato", "b": "lettuce", "c": "onion" } ] ``` ### Audit log filter Multiple actions now can be selected in the audit log filter in *Reports* -> *[Audit](/manual/web_interface/frontend_sections/reports/audit)*: {width="600"} This is useful to see all related actions (for example, successful and failed logins into the frontend) in the audit list. ### Filtre du journal d'audit Plusieurs actions peuvent désormais être sélectionnées dans le filtre du journal d'audit dans *Rapports* -> *[Audit](/manual/web_interface/frontend_sections/reports/audit)* : {width="600"} Ceci est utile pour voir toutes les actions associées (par exemple, les connexions réussies et échouées à l'interface) dans la liste d'audit. # auditlog.get # auditlog.get ##### Audit log In order to improve audit logging in Zabbix and make the Audit log complete and reliable, the previously existing database structure had to be reworked. During an upgrade DB tables `auditlog` and `auditlog_details` will be replaced by the new table `auditlog` with a different format. **Old audit records will not be preserved.** New [section](/manual/web_interface/frontend_sections/administration/general#audit_log) *Audit log* has been added to the *Administration→General* menu allowing to enable (default) or disable audit logging. Housekeeping settings for audit, previously located under the *Housekeeper* menu section, have also been moved to the new *Audit log* section. Existing housekeeping settings will be saved. ##### Journal d'audit Afin d'améliorer la journalisation d'audit dans Zabbix et de rendre le journal d'audit complet et fiable, la structure de la base de données existante a dû être retravaillée. Lors d'une mise à niveau, les tables de base de données `auditlog` et `auditlog_details` seront remplacées par la nouvelle table `auditlog` avec un format différent. **Les anciens enregistrements d'audit ne seront pas conservés.** Une nouvelle [section](/manual/web_interface/frontend_sections/administration/general#audit_log) *Journal d'audit* a été ajoutée au menu *Administration→Général* permettant d'activer (par défaut) ou de désactiver la journalisation d'audit. Les paramètres d'entretien ménager pour l'audit, auparavant situés dans la section de menu *Nettoyage*, ont également été déplacés vers la nouvelle section *Journal d'audit*. Les paramètres de nettoyage existants seront enregistrés. #### Authenticating a user Authenticate a user. Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.login", "params": { "username": "Admin", "password": "zabbix" }, "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": "0424bd59b807674191e7d77572075f33", "id": 1 } ``` #### Authentification d'un utilisateur Authentifier un utilisateur. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.login", "params": { "username": "Admin", "password": "zabbix" }, "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": "0424bd59b807674191e7d77572075f33", "id": 1 } ``` #### Authentication Before you can access any data inside of Zabbix you'll need to log in and obtain an authentication token. This can be done using the [user.login](/manual/api/reference/user/login) method. Let us suppose that you want to log in as a standard Admin user. Then your JSON request will look like this: ```json { "jsonrpc": "2.0", "method": "user.login", "params": { "user": "Admin", "password": "zabbix" }, "id": 1, "auth": null } ``` Let's take a closer look at the request object. It has the following properties: - `jsonrpc` - the version of the JSON-RPC protocol used by the API; the Zabbix API implements JSON-RPC version 2.0; - `method` - the API method being called; - `params` - parameters that will be passed to the API method; - `id` - an arbitrary identifier of the request; - `auth` - a user authentication token; since we don't have one yet, it's set to `null`. If you provided the credentials correctly, the response returned by the API will contain the user authentication token: ```json { "jsonrpc": "2.0", "result": "0424bd59b807674191e7d77572075f33", "id": 1 } ``` The response object in turn contains the following properties: - `jsonrpc` - again, the version of the JSON-RPC protocol; - `result` - the data returned by the method; - `id` - identifier of the corresponding request. #### Authentification Avant de pouvoir accéder aux données de Zabbix, vous devez vous connecter et obtenir un jeton d'authentification. Ceci peut être fait en utilisant la méthode [user.login](/manual/api/reference/user/login). Supposons que vous souhaitiez vous connecter en tant qu’administrateur Zabbix standard. Votre demande JSON ressemblera à ceci : ```json { "jsonrpc": "2.0", "method": "user.login", "params": { "user": "Admin", "password": "zabbix" }, "id": 1, "auth": null } ``` Examinons de plus près l'objet de la requête. Il a les propriétés suivantes : - `jsonrpc` - version du protocole JSON-RPC utilisée par l'API ; l'API Zabbix implémente JSON-RPC version 2.0 ; - `method` - la méthode API appelée ; - `params` - paramètres qui seront transmis à la méthode API ; - `id` - un identifiant arbitraire de la requête; - `auth` - un jeton d'authentification utilisateur ; comme nous n'en avons pas encore, il est défini à `null`. Si vous avez correctement fourni les informations d'identification, la réponse renvoyée par l'API contiendra le jeton d'authentification de l'utilisateur : ```json { "jsonrpc": "2.0", "result": "0424bd59b807674191e7d77572075f33", "id": 1 } ``` L'objet de réponse contient à son tour les propriétés suivantes : - `jsonrpc` - encore une fois, la version du protocole JSON-RPC ; - `result` - les données retournées par la méthode ; - `id` - identifiant de la requête correspondante. #### Authentication Change authentication configuration options. [Authentication API](/manual/api/reference/authentication) #### Authentification Modifiez les options de configuration de l'authentification. [API Authentification](/manual/api/reference/authentication) # authentication.get # authentication.get # authentication.update # authentication.update ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Alexei Vladishev <<alex@zabbix.com>> ------------------------------------------------------------------------ [ ]{#index} ##### Authorization |Parameter|Description| |--|--------| |*Login attempts*|Number of unsuccessful login attempts before the possibility to log in gets blocked.| |*Login blocking interval*|Period of time for which logging in will be prohibited when *Login attempts* limit is exceeded.| ##### Autorisation |Paramètre|Description| |--|--------| |*Tentatives de connexion*|Nombre de tentatives de connexion infructueuses avant que la possibilité de se connecter ne soit bloquée.| |*Intervalle de blocage de connexion*|Période pendant laquelle la connexion sera interdite lorsque la limite de *tentatives de connexion* est dépassée.| ## AUTHOR Zabbix LLC ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Zabbix LLC ------------------------------------------------------------------------ [ ]{#index} ## AUTHOR Zabbix LLC ------------------------------------------------------------------------ [ ]{#index} ## AUTEUR Zabbix LLC ------------------------------------------------------------------------ [ ]{#index} ##### Automatic mode Host inventory can also be populated automatically. For that to work, when configuring a host the inventory mode in the *Host inventory* tab must be set to *Automatic*. Then you can [configure host items](/manual/config/items/item) to populate any host inventory field with their value, indicating the destination field with the respective attribute (called *Item will populate host inventory field*) in item configuration. Items that are especially useful for automated inventory data collection: - system.hw.chassis\[full|type|vendor|model|serial\] - default is \[full\], root permissions needed - system.hw.cpu\[all|cpunum,full|maxfreq|vendor|model|curfreq\] - default is \[all,full\] - system.hw.devices\[pci|usb\] - default is \[pci\] - system.hw.macaddr\[interface,short|full\] - default is \[all,full\], interface is regexp - system.sw.arch - system.sw.os\[name|short|full\] - default is \[name\] - system.sw.packages\[regexp,manager,short|full\] - default is \[all,all,full\] ##### Mode automatique L'inventaire de l'hôte peut également être rempli automatiquement. Pour que cela fonctionne, lorsque vous configurez un hôte, le mode inventaire dans l'onglet *Inventaire d'Hôte* doit être défini sur *Automatique*. Ensuite, vous pouvez [configurer les éléments de l'hôte](/manual/config/items/item) pour remplir n'importe quel champ d'inventaire de l'hôte avec leur valeur, en indiquant le champ de destination avec l'attribut correspondant (appelé *L'élément remplira le champ de l'inventaire de l'hôte*) dans la configuration de l'élément . Les éléments particulièrement utiles pour la collecte automatique de données d'inventaire sont : - system.hw.chassis\[full|type|vendor|model|serial\] - par défaut est \[full\], nécessite les droits root - system.hw.cpu\[all|cpunum,full|maxfreq|vendor|model|curfreq\] - par défaut est \[all,full\] - system.hw.devices\[pci|usb\] - par défaut est \[pci\] - system.hw.macaddr\[interface,short|full\] - par défaut est \[all,full\], interface est une expression régulière - system.sw.arch - system.sw.os\[name|short|full\] - par défaut est \[name\] - system.sw.packages\[regexp,manager,short|full\] - par défaut est \[all,all,full\] #### Autoregistration actions The following conditions can be used in actions based on active agent autoregistration: |Condition type|Supported operators|Description| |--|--|------| |*Host metadata*|contains<br>does not contain<br>matches<br>does not match|Specify host metadata or host metadata to exclude.<br>**contains** - host metadata contains the string.<br>**does not contain** - host metadata does not contain the string.<br>Host metadata can be specified in an [agent configuration file](/manual/appendix/config/zabbix_agentd).<br>**matches** - host metadata matches regular expression.<br>**does not match** - host metadata does not match regular expression.| |*Host name*|contains<br>does not contain<br>matches<br>does not match|Specify a host name or a host name to exclude.<br>**contains** - host name contains the string.<br>**does not contain** - host name does not contain the string.<br>**matches** - host name matches regular expression.<br>**does not match** - host name does not match regular expression.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.| #### Actions d'enregistrement automatique Les conditions suivantes peuvent être utilisées dans les actions basées sur l'enregistrement automatique de l'agent actif : |Type de condition|Opérateurs pris en charge|Description| |--|--|------| |*Métadonnées de l'hôte*|contient<br>ne contient pas<br>correspond à<br>ne correspond pas|Spécifiez les métadonnées de l'hôte ou les métadonnées de l'hôte à exclure.<br>**contient** - les métadonnées de l'hôte contiennent la chaîne.<br>**ne contient pas ** - les métadonnées de l'hôte ne contiennent pas la chaîne.<br>Les métadonnées de l'hôte peuvent être spécifiées dans un [fichier de configuration de l'agent](/manual/appendix/config/zabbix_agentd).<br>**correspond à** - les métadonnées de l'hôte correspondent à l'expression régulière.<br>**ne correspond pas à** - les métadonnées de l'hôte ne correspondent pas à l'expression régulière.| |*Nom de l'hôte*|contient<br>ne contient pas<br>correspond à<br>ne correspond pas|Spécifiez un nom d'hôte ou un nom d'hôte à exclure.<br>**contient** - le nom d'hôte contient la chaîne.<br>**ne contient pas** - le nom d'hôte ne contient pas la chaîne.<br>**correspond à** - le nom d'hôte correspond à l'expression régulière.<br>**ne correspond pas à** - le nom d'hôte ne correspond pas à l'expression régulière.| |*Proxy*|égal<br>n'est pas égal|Spécifiez un proxy ou un proxy à exclure.<br>**égal** - en utilisant ce proxy.<br>**n'est pas égal** - en utilisant un autre proxy que celui-ci.| # autoregistration.get # autoregistration.get # autoregistration.update # autoregistration.update ##### Average request count to Nginx server View the average request count per second per day to the Nginx server: - add the request count per second item to the data set - select the aggregate function `avg` and specify interval `1d` - a bar graph is displayed, where each bar represents the average number of requests per second per day ##### Nombre moyen de requêtes vers le serveur Nginx Afficher le nombre moyen de requêtes par seconde et par jour sur le serveur Nginx : - ajouter le nombre de requêtes par seconde à l'ensemble de données - sélectionner la fonction d'agrégation `avg` et spécifier l'intervalle `1d` - un graphique à barres s'affiche, où chaque barre représente le nombre moyen de requêtes par seconde et par jour ### Backward incompatible changes ### Modifications rétrocompatibles #### Batch migration of history tables * Prepare directories for Data Pump. Data Pump must have read and write permissions to these directories. Example: ``` {.bash} mkdir -pv /export/history chown -R oracle:oracle /export ``` * Create a directory object and grant read and write permissions to this object to the user used for Zabbix authentication ('zabbix' in the example below). Under *sysdba* role, run: ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; ``` * Export tables. Replace N with the desired thread count. ``` {.bash} expdp zabbix/password@oracle_host/service \ DIRECTORY=history \ TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \ PARALLEL=N ``` * Import tables. Replace N with the desired thread count. ``` {.bash} impdp zabbix/password@oracle_host/service \ DIRECTORY=history \ TABLES=history_uint_old \ REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \ data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ``` * Follow [post-migration instructions](#post-migration) to drop the old tables. #### Migration par lots des tables d'historique * Préparez les répertoires pour le Data Pump. Le Data Pump doit disposer d'autorisations de lecture et d'écriture sur ces répertoires. Exemple: ``` {.bash} mkdir -pv /export/history chown -R oracle:oracle /export ``` * Créez un objet répertoire et accordez des autorisations de lecture et d'écriture sur cet objet à l'utilisateur utilisé pour l'authentification Zabbix ('zabbix' dans l'exemple ci-dessous). Sous le rôle *sysdba*, exécutez : ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; ``` * Exportez les tables. Remplacez N par le nombre de fils souhaité. ``` {.bash} expdp zabbix/password@oracle_host/service \ DIRECTORY=history \ TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \ PARALLEL=N ``` * Importer les tableaux. Remplacez N par le nombre de fils souhaité. ``` {.bash} impdp zabbix/password@oracle_host/service \ DIRECTORY=history \ TABLES=history_uint_old \ REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \ data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ``` * Suivez les [instructions post-migration](#post-migration) pour supprimer les anciennes tables. # Best practices for secure Zabbix setup [comment]: # (tags: ssl) # Meilleures pratiques pour une configuration sécurisée de Zabbix [comment] : # (tags: ssl) ##### Better navigation between item configuration and latest data A new context menu for items has been introduced in *[Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data)* allowing to access the item configuration and available graphs:  Conversely, a new context menu has been introduced in the [item list](/manual/web_interface/frontend_sections/configuration/hosts/items) in configuration menu allowing to access the latest data for the item and other useful options:  This menu replaces the wizard option in previous versions. A similar menu has also been introduced for [template items](/manual/web_interface/frontend_sections/configuration/_templates/items) and [item prototypes](/manual/discovery/low_level_discovery/item_prototypes). ##### Meilleure navigation entre la configuration des éléments et les dernières données Un nouveau menu contextuel pour les éléments a été introduit dans *[Dernières données](/manual/web_interface/frontend_sections/monitoring/latest_data)* permettant d'accéder aux configuration des éléments et graphiques disponibles :  Inversement, un nouveau menu contextuel a été introduit dans la [liste d'éléments](/manual/web_interface/frontend_sections/configuration/hosts/items) dans le menu de configuration permettant d'accéder aux dernières données de l'élément et à d'autres options utiles :  Ce menu remplace l'option de l'assistant dans les versions précédentes. Un menu similaire a également été introduit pour les [éléments de modèle](/manual/web_interface/frontend_sections/configuration/_templates/items) et les [prototypes d'élément](/manual/discovery/low_level_discovery/item_prototypes). ## Breaking changes ## Changements radicaux ## Breaking changes ## Changements radicaux ## Breaking changes ## Changements radicaux ### Breaking changes #### Loadable plugin versioning [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 now use the same versioning system as Zabbix itself. The following version changes have been made: - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13 These plugins are supported for any minor version of Zabbix 6.0. Note that source code repository for each plugin now contains a dedicated *release/6.0* branch (previously, there was only *master* branch). ### Changements majeurs #### Gestion des versions des plugins chargeables Les [plugins chargeables](/manual/config/items/plugins#chargeable) pour l'agent Zabbix 2 utilisent désormais le même système de gestion des versions que Zabbix lui-même. Les modifications de version suivantes ont été apportées : - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13 Ces plugins sont pris en charge pour toute version mineure de Zabbix 6.0. Notez que le référentiel de code source de chaque plugin contient désormais une branche *release/6.0* dédiée (auparavant, il n'y avait qu'une branche *master*). · ### Breaking changes #### Loadable plugin versioning [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 now use the same versioning system as Zabbix itself. The following version changes have been made: - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13 These plugins are supported for any minor version of Zabbix 6.0. Note that source code repository for each plugin now contains a dedicated *release/6.0* branch (previously, there was only *master* branch). ### Changements majeurs #### Gestion des versions des plugins chargeables Les [plugins chargeables](/manual/config/items/plugins#chargeable) pour l'agent Zabbix 2 utilisent désormais le même système de gestion des versions que Zabbix lui-même. Les modifications de version suivantes ont été apportées : - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13 Ces plugins sont pris en charge pour toute version mineure de Zabbix 6.0. Notez que le référentiel de code source de chaque plugin contient désormais une branche *release/6.0* dédiée (auparavant, il n'y avait qu'une branche *master*). · ##### BSD systems If `watch` command is not installed, a similar effect can be achieved with while [ 1 ]; do ps x; sleep 0.2; clear; done ##### Systèmes BSD Si la commande `watch` n'est pas installée, un effet similaire peut être réalisé avec while [ 1 ]; do ps x; sleep 0.2; clear; done ##### Build 32bit PCRE 1\. Run: mingw32-make clean 2\. Delete *CMakeCache.txt*: del CMakeCache.txt rmdir /q /s CMakeFiles 3\. Run cmake: cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32 4\. Next, run: mingw32-make install ##### Construire PCRE 32 bits 1\. Exécuter : mingw32-make clean 2\. Supprimer *CMakeCache.txt* : del CMakeCache.txt rmdir /q /s CMakeFiles 3\. Exécuter cmake : cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32 4\. Ensuite, exécuter : mingw32-make install ##### Build 64bit PCRE 1\. Delete old configuration/cache if exists: del CMakeCache.txt rmdir /q /s CMakeFiles 2\. Run cmake (CMake can be installed from <https://cmake.org/download/>): cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre 3\. Next, run: mingw32-make clean mingw32-make install ##### Construire PCRE 64 bits 1\. Supprimer l'ancienne configuration/le cache s'il existe : del CMakeCache.txt rmdir /q /s CMakeFiles 2\. Exécuter cmake (CMake peut être installé à partir de <https://cmake.org/download/>) : cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre 3\. Ensuite, exécuter : mingw32-make clean mingw32-make install #### Building inventory #### Construction de l’inventaire ### Built-in objects ### Objets intégrés ##### Bulk processing Bulk processing is supported for dependent items. To enable caching and indexing, the *Prometheus pattern* preprocessing must be the **first** preprocessing step. When *Prometheus pattern* is first preprocessing step then the parsed Prometheus data is cached and indexed by the first `<label>==<value>` condition in the *Prometheus pattern* preprocessing step. This cache is reused when processing other dependent items in this batch. For optimal performance, the first label should be the one with most different values. If there is other preprocessing to be done before the first step, it should be moved either to the master item or to a new dependent item which would be used as the master item for the dependent items. ##### Traitement de masse Le traitement de masse est pris en charge pour les éléments dépendants. Pour activer la mise en cache et l'indexation, le prétraitement *Motif Prometheus* doit être la **première** étape de prétraitement. Lorsque *Motif Prometheus* est la première étape de prétraitement, les données Prometheus analysées sont mises en cache et indexées par la première condition `<label>==<value>` dans l'étape de prétraitement *Motif Prometheus*. Ce cache est réutilisé lors du traitement d'autres éléments dépendants dans ce lot. Pour des performances optimales, la première étiquette doit être celle avec les valeurs les plus différentes. S'il y a un autre prétraitement à effectuer avant la première étape, il doit être déplacé soit vers l'élément principal, soit vers un nouvel élément dépendant qui serait utilisé comme élément principal pour les éléments dépendants. ##### Bulk processing for Prometheus metrics As bulk processing of dependent items has been introduced in the preprocessing queue for Prometheus metrics, dependent items will no longer be processed in parallel and that may have an affect on how fast they are processed. ##### Traitement en masse des métriques Prometheus Étant donné que le traitement en masse des éléments dépendants a été introduit dans la file d'attente de prétraitement pour les métriques Prometheus, les éléments dépendants ne seront plus traités en parallèle, ce qui peut avoir une incidence sur la vitesse à laquelle ils sont traités. ##### Buttons | | | |---|---| ||Clone the service.<br>When a service is cloned, its parent links are preserved, while the child links are not.| ##### Boutons | | | |---|---| ||Cloner le service.<br>Lorsqu'un service est cloné, ses liens parents sont préservés, tandis que les liens enfants ne le sont pas.| ##### Buttons Buttons to the right offer the following options: | | | |--|--------| ||Go to map constructor to edit the map content.| ||Add map to the favorites widget in the [Dashboard](dashboard).| ||The map is in the favorites widget in the [Dashboard](dashboard). Click to remove map from the favorites widget.| View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons à droite offrent les options suivantes : | | | |--|--------| ||Aller au constructeur de la carte pour modifier le contenu de la carte.| ||Ajouter la carte aux widgets favoris dans le [Tableau de bord](dashboard).| ||La carte est dans les widgets favoris du [tableau de bord](dashboard). Cliquez pour supprimer la carte des widgets favoris.| Les boutons de mode d'affichage communs à toutes les sections sont décrits sur le la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons *Create host* allows to create a [new host](/manual/config/hosts/host). This button is available for Admin and Super Admin users only. View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons *Créer un hôte* permet de créer un [nouvel hôte](/manual/config/hosts/host). Ce bouton est disponible uniquement pour les utilisateurs Admin et Super Admin. Les boutons de mode d'affichage communs à toutes les sections sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons The button to the right offers the following option: | | | |--|--------| ||Export content from all pages to a CSV file.| View mode buttons, being common for all sections, are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Le bouton à droite offre l'option suivante : | | | |--|--------| ||Exporter le contenu de toutes les pages vers un fichier CSV.| Les boutons du mode d'affichage, communs à toutes les sections, sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons de mode d'affichage communs à toutes les sections sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons de mode d'affichage communs à toutes les sections sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons de mode d'affichage communs à toutes les sections sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons de mode d'affichage communs à toutes les sections sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). ##### Buttons View mode buttons, being common for all sections, are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page. ##### Boutons Les boutons de mode d'affichage, communs à toutes les sections, sont décrits sur la page [Surveillance](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons). By default, the widget displays all enabled hosts with valid geographical coordinates defined in the host configuration. It is possible to configure host filtering in the widget parameters. The valid host coordinates are: - Latitude: from -90 to 90 (can be integer or float number) - Longitude: from -180 to 180 (can be integer or float number) Par défaut, le widget affiche tous les hôtes activés avec des coordonnées géographiques valides définies dans la configuration de l'hôte. Il est possible de configurer le filtrage des hôtes dans les paramètres du widget. Les coordonnées valides de l'hôte sont : - Latitude : de -90 à 90 (peut être un entier ou un nombre flottant) - Longitude : de -180 à 180 (peut être un entier ou un nombre flottant) ### Ceph |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |ceph.df.details\[connString,<user>,<apikey>\]|<|<|<| |Cluster’s data usage and distribution among pools.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.stats\[connString,<user>,<apikey>\]|<|<|<| |Aggregated and per OSD statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.discovery\[connString,<user>,<apikey>\]|<|<|<| |List of discovered OSDs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.dump\[connString,<user>,<apikey>\]|<|<|<| |Usage thresholds and statuses of OSDs.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.ping\[connString,<user>,<apikey>\]|<|<|<| |Tests whether a connection to Ceph can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br><br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.pool.discovery\[connString,<user>,<apikey>\]|<|<|<| |List of discovered pools. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.status\[connString,<user>,<apikey>\]|<|<|<| |Overall cluster's status.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | ### Ceph |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |ceph.df.details \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Utilisation et distribution des données du cluster entre les pools.|Objet JSON|**connString** - URI ou nom de session.<br>**utilisateur, mot de passe** - Identifiants de connexion Ceph.| | |ceph.osd.stats \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Statistiques agrégées et par OSD.|Objet JSON|**connString** - URI ou nom de session.<br>**utilisateur, mot de passe** - Identifiants de connexion Ceph.| | |ceph.osd.discovery \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Liste des OSD découverts. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Ceph .| | |ceph.osd.dump \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Seuils d'utilisation et statuts des OSD.|Objet JSON|**connString** - URI ou nom de session.<br>**utilisateur, mot de passe** - Identifiants de connexion Ceph.| | |ceph.ping \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Teste si une connexion à Ceph peut être établie.|0 - la connexion est interrompue (en cas d'erreur, y compris les problèmes d'authentification et de configuration)<br>1 - la connexion est réussie.|**connString** - URI ou nom de session .<br>**utilisateur, mot de passe** - Identifiants de connexion Ceph.| | |ceph.pool.discovery \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Liste des pools découverts. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Ceph .| | |ceph.status \[connString, \<utilisateur\>, \<apikey\>\]|<|<|<| |Statut global du cluster.|Objet JSON|**connString** - URI ou nom de session.<br>**utilisateur, mot de passe** - Identifiants de connexion Ceph.| | #### Change dashboard owner Available only for admins and super admins. Request: ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.update", "params": { "dashboardid": "2", "userid": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 2 } ``` #### Changement de propriétaire d'un tableau de bord Disponible uniquement pour les administrateurs et les super-administrateurs. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.update", "params": { "dashboardid": "2", "userid": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 2 } ``` #### Change hosts monitored by a proxy Update the proxy to monitor the two given hosts. Request: ```json { "jsonrpc": "2.0", "method": "proxy.update", "params": { "proxyid": "10293", "hosts": [ { "hostid": "10294" }, { "hostid": "10295" }, ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10293" ] }, "id": 1 } ``` #### Changement des hôtes surveillés par un proxy Mettez à jour le proxy pour surveiller les deux hôtes donnés. Requête : ```json { "jsonrpc": "2.0", "method": "proxy.update", "params": { "proxyid": "10293", "hosts": [ { "hostid": "10294" }, { "hostid": "10295" }, ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10293" ] }, "id": 1 } ``` #### Change map owner Available only for admins and super admins. Request: ```json { "jsonrpc": "2.0", "method": "map.update", "params": { "sysmapid": "9", "userid": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 2 } ``` #### Changement du propriétaire de la carte Disponible uniquement pour les administrateurs et les super administrateurs. Requête : ```json { "jsonrpc": "2.0", "method": "map.update", "params": { "sysmapid": "9", "userid": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 2 } ``` #### Change proxy status Change the proxy to an active proxy and rename it to "Active proxy". Request: ```json { "jsonrpc": "2.0", "method": "proxy.update", "params": { "proxyid": "10293", "host": "Active proxy", "status": "5" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10293" ] }, "id": 1 } ``` #### Modification du statut du proxy Changez le proxy en proxy actif et renommez-le en "Active proxy". Requête : ```json { "jsonrpc": "2.0", "method": "proxy.update", "params": { "proxyid": "10293", "host": "Active proxy", "status": "5" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10293" ] }, "id": 1 } ``` #### Change script command Change the command of the script to "/bin/ping -c 10 {HOST.CONN} 2>&1". Request: ```json { "jsonrpc": "2.0", "method": "script.update", "params": { "scriptid": "1", "command": "/bin/ping -c 10 {HOST.CONN} 2>&1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "1" ] }, "id": 1 } ``` #### Modification de la commande d'un script Changez la commande du script en "/bin/ping -c 10 {HOST.CONN} 2>&1". Requête : ```json { "jsonrpc": "2.0", "method": "script.update", "params": { "scriptid": "1", "command": "/bin/ping -c 10 {HOST.CONN} 2>&1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "1" ] }, "id": 1 } ``` #### CHANGES IN 6.0.0 #### CHANGEMENTS EN 6.0.0 #### CHANGES IN 6.0.13 New templates are available: - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http). #### CHANGEMENTS EN 6.0.13 De nouveaux modèles sont disponibles : - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP Voir les instructions de configuration pour les [modèles HTTP](/manual/config/templates_out_of_the_box/http). #### CHANGES IN 6.0.2 The template *Generic Java JMX* now contains two discovery rules: - Garbage collector discovery - Memory pool discovery #### CHANGEMENTS EN 6.0.2 Le modèle *Generic Java JMX* contient désormais deux règles de découverte : - Garbage collector discovery - Memory pool discovery #### CHANGES IN 6.0.3 A new template *OpenWeatherMap by HTTP* is available. The following changes have been made in the existing templates: - In the templates *Windows services by Zabbix agent*, *Windows services by Zabbix agent active*, *Windows by Zabbix agent*, *Windows by Zabbix agent active* {$SERVICE.NAME.NOT_MATCHES} macro value has been updated to filter out an extended list of services. - The template *PostgreSQL by Zabbix agent 2* now will check the number of slow queries and generate a problem if the amount exceeds a threshold. #### CHANGEMENTS EN 6.0.3 Un nouveau modèle *OpenWeatherMap by HTTP* est disponible. Les modifications suivantes ont été apportées aux modèles existants : - Dans les modèles *Windows services by Zabbix agent*, *Windows services by Zabbix agent active*, *Windows by Zabbix agent*, *Windows by Zabbix agent active*, la valeur de la macro {$SERVICE.NAME.NOT_MATCHES} a été mise à jour pour filtrer une liste étendue de services. - Le modèle *PostgreSQL by Zabbix agent 2* vérifiera désormais le nombre de requêtes lentes et générera un problème si le nombre dépasse un seuil. #### CHANGES IN 6.0.4 New templates are available: - *TrueNAS SNMP* - monitoring of TrueNAS storage OS by SNMP - *Proxmox VE by HTTP* - see setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http) The templates *SMART by Zabbix agent 2* and *SMART by Zabbix agent 2 (active)* have been updated: - the *Attribute discovery* LLD rule has been deleted, whereas the *Disk discovery* LLD rule will now discover disks based on the pre-defined vendor-specific set of attributes; - **smart.disk.get** item can now return information about a specific disk only, instead of all disks. New macros allowing to define warning and critical thresholds of the filesystem utilization for virtual file system monitoring have been added to the templates *HOST-RESOURCES-MIB storage SNMP*, *Linux by Prom*, *Linux filesystems SNMP*, *Linux filesystems by Zabbix agent active*, *Linux filesystems by Zabbix agent*, *Mellanox SNMP*, *PFSense SNMP*, *Windows filesystems by Zabbix agent active*, *Windows filesystems by Zabbix agent*. Filesystem utilization triggers have been updated to use these macros. #### CHANGEMENTS EN 6.0.4 De nouveaux modèles sont disponibles : - *TrueNAS SNMP* - surveillance du système d'exploitation de stockage TrueNAS par SNMP - *Proxmox VE by HTTP* - voir les instructions de configuration pour les [modèles HTTP](/manual/config/templates_out_of_the_box/http) Les modèles *SMART by Zabbix agent 2* et *SMART by Zabbix agent 2 (active)* ont été mis à jour : - la règle LLD *Attribute discovery* a été supprimée, tandis que la règle LLD *Disk discovery* découvrira désormais les disques en fonction de l'ensemble d'attributs prédéfinis spécifiques au fournisseur ; - l'élément **smart.disk.get** peut désormais renvoyer des informations sur un disque spécifique uniquement, au lieu de tous les disques. De nouvelles macros permettant de définir des seuils d'avertissement et critiques d'utilisation du système de fichiers pour la surveillance du système de fichiers virtuel ont été ajoutées aux modèles *HOST-RESOURCES-MIB storage SNMP*, *Linux by Prom*, *Linux filesystems SNMP*, *Linux filesystems by Zabbix agent active*, *Linux filesystems by Zabbix agent*, *Mellanox SNMP*, *PFSense SNMP*, *Windows filesystems by Zabbix agent active*, *Windows filesystems by Zabbix agent*. Les déclencheurs d'utilisation du système de fichiers ont été mis à jour pour utiliser ces macros. #### CHANGES IN 6.0.5 New templates are available: - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http). #### CHANGEMENT EN 6.0.5 De nouveaux modèles sont disponibles : - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP Voir les instructions de configuration pour les [modèles HTTP](/manual/config/templates_out_of_the_box/http). #### CHANGES IN 6.0.6 New templates are available: - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http). #### CHANGEMENTS EN 6.0.6 De nouveaux modèles sont disponibles : - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP Voir les instructions de configuration pour les [modèles HTTP](/manual/config/templates_out_of_the_box/http). #### CHANGES IN 6.0.7 A new [template](/manual/config/templates_out_of_the_box/http) *HPE Synergy by HTTP* is available. The templates *HashiCorp Consul Node by HTTP* and *HashiCorp Consul Cluster by HTTP* now support Consul namespaces. #### CHANGEMENTS EN 6.0.7 Un nouveau [modèle](/manual/config/templates_out_of_the_box/http) *HPE Synergy by HTTP* est disponible. Les modèles *HashiCorp Consul Node by HTTP* et *HashiCorp Consul Cluster by HTTP* prennent désormais en charge les espaces de noms Consul. #### CHANGES IN 6.0.8 A new [template](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense by SNMP* is available. #### CHANGEMENTS EN 6.0.8 Un nouveau [modèle](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense par SNMP* est disponible. ##### Changes in templates - The {\#FSLABEL} macro has been added to the corresponding item names and descriptions in *Windows by Zabbix agent* and *Windows by Zabbix agent active* templates - The vfs.file.cksum\[/etc/passwd\] agent item has been changed to vfs.file.cksum\[/etc/passwd,sha256\] - A new check zabbix\[process,odbc poller,avg,busy\] has been added to *Zabbix server*, *Zabbix proxy*, *Remote Zabbix server* and *Remote Zabbix proxy* templates. The metric is used for monitoring the average time for which ODBC processes have been busy during the last minute (in percentage). ##### Modifications dans les modèles - La macro {\#FSLABEL} a été ajoutée aux noms et descriptions d'éléments correspondants dans les modèles *Windows by Zabbix agent* et *Windows by Zabbix agent active* - L'élément d'agent vfs.file.cksum\[/etc/passwd\] a été remplacé par vfs.file.cksum\[/etc/passwd,sha256\] - Une nouvelle vérification zabbix\[process,odbc poller,avg,busy\] a été ajoutée aux modèles *Zabbix server*, *Zabbix proxy*, *Remote Zabbix server* et *Remote Zabbix proxy*. La métrique est utilisée pour surveiller le temps moyen pendant lequel les processus ODBC ont été occupés au cours de la dernière minute (en pourcentage). #### Change the IP range of a discovery rule Change the IP range of a discovery rule to "192.168.2.1-255". Request: ``` {.java} { "jsonrpc": "2.0", "method": "drule.update", "params": { "druleid": "6", "iprange": "192.168.2.1-255" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "druleids": [ "6" ] }, "id": 1 } ``` #### Modification de la plage IP d'une règle de découverte Définir la plage d'adresses IP d'une règle de découverte à "192.168.2.1-255". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "drule.update", "params": { "druleid": "6", "iprange": "192.168.2.1-255" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "druleids": [ "6" ] }, "id": 1 } ``` #### Changing a host interface port Change the port of a host interface. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.update", "params": { "interfaceid": "30048", "port": "30050" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30048" ] }, "id": 1 } ``` #### Changement d'un port d'interface hôte Changer le port d'une interface hôte. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.update", "params": { "interfaceid": "30048", "port": "30050" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30048" ] }, "id": 1 } ``` ##### Changing dependency for inherited triggers disabled The possibility to change dependencies for triggers inherited from a template is now disabled. The reason is that upon updating the dependencies of a template trigger, the dependencies of inherited triggers are overwritten. Thus it is more reliable always to set trigger dependencies only on the root template level. ##### Modification de la dépendance pour les déclencheurs hérités désactivée La possibilité de modifier les dépendances des déclencheurs hérités d'un modèle est désormais désactivée. La raison en est que lors de la mise à jour des dépendances d'un déclencheur de modèle, les dépendances des déclencheurs hérités sont écrasées. Ainsi, il est toujours plus fiable de définir des dépendances de déclencheur uniquement au niveau du modèle racine. #### Changing event's severity Change severity for multiple events and leave a message. Request: ```json { "jsonrpc": "2.0", "method": "event.acknowledge", "params": { "eventids": ["20427", "20428"], "action": 12, "message": "Maintenance required to fix it.", "severity": 4 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "eventids": [ "20427", "20428" ] }, "id": 1 } ``` #### Changement de sévérité d'un événement Modifier la sévérité de plusieurs événements et ajouter un message. Requête : ```json { "jsonrpc": "2.0", "method": "event.acknowledge", "params": { "eventids": ["20427", "20428"], "action": 12, "message": "Maintenance required to fix it.", "severity": 4 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "eventids": [ "20427", "20428" ] }, "id": 1 } ``` #### Changing mappings for one value map. Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.update", "params": { "valuemapid": "2", "mappings": [ { "type": "0", "value": "0", "newvalue": "Online" }, { "type": "0", "value": "1", "newvalue": "Offline" } ] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "2" ] }, "id": 1 } ``` #### Modification des correspondances pour une carte de valeurs. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.update", "params": { "valuemapid": "2", "mappings": [ { "type": "0", "value": "0", "newvalue": "Online" }, { "type": "0", "value": "1", "newvalue": "Offline" } ] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "2" ] }, "id": 1 } ``` #### Changing proxy setting The hosts discovered by different proxies are always treated as different hosts. While this allows to perform discovery on matching IP ranges used by different subnets, changing proxy for an already monitored subnet is complicated because the proxy changes must be also applied to all discovered hosts. For example the steps to replace proxy in a discovery rule: 1. disable discovery rule 2. sync proxy configuration 3. replace the proxy in the discovery rule 4. replace the proxy for all hosts discovered by this rule 5. enable discovery rule #### Modification des paramètres de proxy Les hôtes découverts par différents proxys sont toujours traités comme des hôtes différents. Bien que cela permette d'effectuer une découverte sur des plages d'adresses IP correspondantes utilisées par différents sous-réseaux, le changement de proxy pour un sous-réseau déjà surveillé est compliqué car les changements de proxy doivent également être appliqués à tous les hôtes découverts. Par exemple, voici les étapes pour remplacer le proxy dans une règle de découverte : 1. désactiver la règle de découverte 2. synchroniser la configuration du proxy 3. remplacer le proxy dans la règle de découverte 4. remplacer le proxy pour tous les hôtes découverts par cette règle 5. activer la règle de découverte #### Changing the excluded downtimes for an SLA Add a planned 4 hour long RAM upgrade downtime on the 6th of April, 2022, while keeping (needs to be defined anew) a previously existing software upgrade planned on the 4th of July for the SLA with ID "5". Request: ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "slaid": "5", "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" }, { "name": "RAM upgrade", "period_from": "1649192400", "period_to": "1649206800" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` #### Modification des temps d'arrêt exclus pour un SLA Ajoutez un temps d'arrêt de mise à niveau de la RAM planifié de 4 heures le 6 avril 2022, tout en conservant (doit être défini à nouveau) une mise à niveau logicielle existante prévue le 4 juillet pour le SLA avec l'ID "5". Requête : ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "slaid": "5", "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" }, { "name": "RAM upgrade", "period_from": "1649192400", "period_to": "1649206800" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` #### Changing the interface of an item prototype Change the host interface that will be used by discovered items. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.update", "params": { "itemid": "27428", "interfaceid": "132" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "27428" ] }, "id": 1 } ``` #### Modification de l'interface d'un prototype d'élément Modifiez l'interface hôte qui sera utilisée par les éléments découverts. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.update", "params": { "itemid": "27428", "interfaceid": "132" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "27428" ] }, "id": 1 } ``` #### Changing the schedule of an SLA Switch the SLA with ID "5" to a 24x7 schedule. Request: ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "slaid": "5", "schedule": [] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` #### Modification de la planification d'un SLA Basculez le SLA avec l'ID "5" vers un horaire 24x7. Requête : ```json { "jsonrpc": "2.0", "method": "service.update", "params": { "slaid": "5", "schedule": [] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` #### Changing the size of a graph prototype Change the size of a graph prototype to 1100 to 400 pixels. Request: ```json { "jsonrpc": "2.0", "method": "graphprototype.update", "params": { "graphid": "439", "width": 1100, "height": 400 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "graphids": [ "439" ] }, "id": 1 } ``` #### Modification de la taille d'un prototype de graphique Modifiez la taille d'un prototype de graphique entre 1 100 et 400 pixels. Requête : ```json { "jsonrpc": "2.0", "method": "graphprototype.update", "params": { "graphid": "439", "width": 1100, "height": 400 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "graphids": [ "439" ] }, "id": 1 } ``` #### Changing the value of a global macro Change the value of a global macro to "public". Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.updateglobal", "params": { "globalmacroid": "1", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "1" ] }, "id": 1 } ``` #### Modification de la valeur d'une macro globale Modifier la valeur d'une macro globale à "public". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.updateglobal", "params": { "globalmacroid": "1", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "1" ] }, "id": 1 } ``` #### Changing the value of a host macro Change the value of a host macro to "public". Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.update", "params": { "hostmacroid": "1", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "1" ] }, "id": 1 } ``` #### Modification de la valeur d'une macro d'hôte Modifier la valeur d'une macro d'hôte à "public". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.update", "params": { "hostmacroid": "1", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "1" ] }, "id": 1 } ``` #### Changing user role Change a role of a user. Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.update", "params": { "userid": "12", "roleid": "6" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "12" ] }, "id": 1 } ``` #### Modification du rôle de l'utilisateur Modifier le rôle d'un utilisateur. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.update", "params": { "userid": "12", "roleid": "6" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "12" ] }, "id": 1 } ``` #### Changing value map name Change value map name to "Device status". Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.update", "params": { "valuemapid": "2", "name": "Device status" }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "2" ] }, "id": 1 } ``` #### Modification du nom de la carte de valeurs Remplacez le nom de la carte de valeurs par "Device status". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.update", "params": { "valuemapid": "2", "name": "Device status" }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "2" ] }, "id": 1 } ``` ### 'Check now' request object The 'Check now' task request object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|ID of item and low-level discovery rules.| ### Objet de requête 'Vérifier maintenant' L'objet de demande de tâche 'Vérifier maintenant' a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|ID de l'élément et règles de découverte de bas niveau.| #### Check of pre-requisites Make sure that all software prerequisites are met. {width="550"} |Pre-requisite|Minimum value|Description| |--|--|------| |*PHP version*|7.2.5| | |*PHP memory\_limit option*|128MB|In php.ini:<br>memory\_limit = 128M| |*PHP post\_max\_size option*|16MB|In php.ini:<br>post\_max\_size = 16M| |*PHP upload\_max\_filesize option*|2MB|In php.ini:<br>upload\_max\_filesize = 2M| |*PHP max\_execution\_time option*|300 seconds (values 0 and -1 are allowed)|In php.ini:<br>max\_execution\_time = 300| |*PHP max\_input\_time option*|300 seconds (values 0 and -1 are allowed)|In php.ini:<br>max\_input\_time = 300| |*PHP session.auto\_start option*|must be disabled|In php.ini:<br>session.auto\_start = 0| |*Database support*|One of: MySQL, Oracle, PostgreSQL.|One of the following modules must be installed:<br>mysql, oci8, pgsql| |*bcmath*| |php-bcmath| |*mbstring*| |php-mbstring| |*PHP mbstring.func\_overload option*|must be disabled|In php.ini:<br>mbstring.func\_overload = 0| |*sockets*| |php-net-socket. Required for user script support.| |*gd*|2.0.28|php-gd. PHP GD extension must support PNG images (*--with-png-dir*), JPEG (*--with-jpeg-dir*) images and FreeType 2 (*--with-freetype-dir*).| |*libxml*|2.6.15|php-xml| |*xmlwriter*| |php-xmlwriter| |*xmlreader*| |php-xmlreader| |*ctype*| |php-ctype| |*session*| |php-session| |*gettext*| |php-gettext<br>Since Zabbix 2.2.1, the PHP gettext extension is not a mandatory requirement for installing Zabbix. If gettext is not installed, the frontend will work as usual, however, the translations will not be available.| Optional pre-requisites may also be present in the list. A failed optional prerequisite is displayed in orange and has a *Warning* status. With a failed optional pre-requisite, the setup may continue. ::: noteimportant If there is a need to change the Apache user or user group, permissions to the session folder must be verified. Otherwise Zabbix setup may be unable to continue. ::: #### Vérification des pré-requis Assurez-vous que toutes les conditions logicielles préalables sont remplies. {width="550"} |Pré-requis|Valeur minimale|Description| |--|--|------| |*PHP version*|7.2.5| | |*option PHP memory\_limit*|128MB|Dans php.ini:<br>memory\_limit = 128M| |*option PHP post\_max\_size*|16MB|Dans php.ini:<br>post\_max\_size = 16M| |*option PHP upload\_max\_filesize*|2MB|Dans php.ini:<br>upload\_max\_filesize = 2M| |*option PHP max\_execution\_time*|300 secondes (valeurs 0 et -1 sont permises)|Dans php.ini:<br>max\_execution\_time = 300| |*option PHP max\_input\_time*|300 secondes (valeurs 0 et -1 sont permises)|Dans php.ini:<br>max\_input\_time = 300| |*option PHP session.auto\_start*|doit être désactivé|Dans php.ini:<br>session.auto\_start = 0| |*Base de données*|Une parmi : MySQL, Oracle, PostgreSQL.|L'un des modules suivants doit être installé :<br>mysql, oci8, pgsql| |*bcmath*| |php-bcmath| |*mbstring*| |php-mbstring| |*option PHP mbstring.func\_overload*|doit être désactivé|Dans php.ini:<br>mbstring.func\_overload = 0| |*sockets*| |php-net-socket. Requis pour la prise en charge des scripts utilisateur.| |*gd*|2.0.28|php-gd. L'extension PHP GD doit prendre en charge les images PNG (*--with-png-dir*), JPEG (*--with-jpeg-dir*) et FreeType 2 (*--with-freetype-dir*).| |*libxml*|2.6.15|php-xml| |*xmlwriter*| |php-xmlwriter| |*xmlreader*| |php-xmlreader| |*ctype*| |php-ctype| |*session*| |php-session| |*gettext*| |php-gettext<br>Depuis Zabbix 2.2.1, l'extension PHP gettext n'est plus obligatoire pour l'installation de Zabbix. Si gettext n'est pas installé, l'interface fonctionnera comme d'habitude, cependant, les traductions ne seront pas disponibles.| Des pré-requis facultatifs peuvent également être présents dans la liste. Un prérequis facultatif échoué est affiché en orange et a un statut *Avertissement*. En cas d'échec d'un prérequis facultatif, la configuration peut continuer. ::: noteimportant S'il est nécessaire de modifier l'utilisateur ou le groupe d'utilisateurs Apache, les autorisations d'accès au dossier de session doivent être vérifiées. Sinon, l'installation de Zabbix risque de ne pas pouvoir continuer. ::: #### Check status of nodes at specific IP addresses Request: ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "output": ["name", "status"], "filter": { "address": ["192.168.1.7", "192.168.1.13"] } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "name": "node3", "status": "0" }, { "name": "node-active", "status": "3" } ], "id": 1 } ``` #### Vérifier l'état des nœuds à des adresses IP spécifiques Requête : ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "output": ["name", "status"], "filter": { "address": ["192.168.1.7", "192.168.1.13"] } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "name": "node3", "status": "0" }, { "name": "node-active", "status": "3" } ], "id": 1 } ``` #### Chromium for Zabbix web service on Ubuntu 20 Though in most cases, Zabbix web service can run with Chromium, on Ubuntu 20.04 using Chromium causes the following error: Cannot fetch data: chrome failed to start:cmd_run.go:994: WARNING: cannot create user data directory: cannot create "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. This error occurs because `/var/lib/zabbix` is used as a home directory of user 'zabbix'. #### Chromium pour le service Web Zabbix sur Ubuntu 20 Bien que dans la plupart des cas, le service Web Zabbix puisse fonctionner avec Chromium, sur Ubuntu 20.04, l'utilisation de Chromium provoque l'erreur suivante : Cannot fetch data: chrome failed to start:cmd_run.go:994: WARNING: cannot create user data directory: cannot create "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. Cette erreur se produit car `/var/lib/zabbix` est utilisé comme répertoire personnel de l'utilisateur 'zabbix'. #### Ciphersuites Ciphersuites by default are configured internally during Zabbix startup and, before Zabbix 4.0.19, 4.4.7, are not user-configurable. Since Zabbix 4.0.19, 4.4.7 also user-configured ciphersuites are supported for GnuTLS and OpenSSL. Users may [configure](#user-configured_ciphersuites) ciphersuites according to their security policies. Using this feature is optional (built-in default ciphersuites still work). For crypto libraries compiled with default settings Zabbix built-in rules typically result in the following ciphersuites (in order from higher to lower priority): |Library|Certificate ciphersuites|PSK ciphersuites| |-------|-------------------|-------------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| #### Suite de chiffrement Les suites de chiffrement par défaut sont configurées en interne lors du démarrage de Zabbix et, avant Zabbix 4.0.19, 4.4.7, ne sont pas configurables par l'utilisateur. Depuis Zabbix 4.0.19, 4.4.7, les suites de chiffrement configurées par l'utilisateur sont également prises en charge pour GnuTLS et OpenSSL. Les utilisateurs peuvent [configurer](#user-configured_ciphersuites) des suites de chiffrement en fonction de leurs politiques de sécurité. L'utilisation de cette fonctionnalité est facultative (les suites de chiffrement par défaut intégrées fonctionnent toujours). Pour les bibliothèques de chiffrement compilées avec les paramètres par défaut, les règles intégrées de Zabbix entraînent généralement les suites de chiffrement suivantes (dans l'ordre de priorité la plus élevée à la plus faible) : |Librairie|Suite de chiffrement Certificat|Suite de chiffrement PSK| |-------|-------------------|-------------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| #### Clear history Request: ``` {.java} { "jsonrpc": "2.0", "method": "history.clear", "params": [ "10325", "13205" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "10325", "13205" ] }, "id": 1 } ``` #### Effacer l'historique Requête : ``` {.java} { "jsonrpc": "2.0", "method": "history.clear", "params": [ "10325", "13205" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "10325", "13205" ] }, "id": 1 } ``` ### Code |Type|Size|Comments| |-----|-----|----------| |Byte| 4 |Payload type, currently only JSON is supported.| ### Code |Type|Taille|Commentaires| |-----|-----|----------| |Octet| 4 |Type de charge utile, actuellement seul JSON est pris en charge.| ##### Collapsed menu When the menu is collapsed to icons only, a full menu reappears as soon as the mouse cursor is placed upon it. Note that it reappears over page content; to move page content to the right you have to click on the expand button. If the mouse cursor again is placed outside the full menu, the menu will collapse again after two seconds. You can also make a collapsed menu reappear fully by hitting the Tab key. Hitting the Tab key repeatedly will allow to focus on the next menu element. ##### Menu réduit Lorsque le menu est réduit à des icônes uniquement, un menu complet réapparaît dès que le curseur de la souris est placé dessus. Notez qu'il réapparaît sur le contenu de la page ; pour déplacer le contenu de la page vers la droite, vous devez cliquer sur le bouton de développement. Si le curseur de la souris est à nouveau placé en dehors du menu complet, le menu se réduira à nouveau après deux secondes. Vous pouvez également faire réapparaître complètement un menu réduit en appuyant sur la touche Tab. Appuyer plusieurs fois sur la touche Tab permettra de se concentrer sur l'élément de menu suivant. ##### Column configuration {width="600"} ##### Configuration des colonnes {width="600"} #### Command-line based installation #### Installation basée sur la ligne de commande [comment]: # attributes: noaside # 11 Recipes for monitoring # 11 Recettes pour la supervision [comment]: # attributes: noaside # 12 Performance tuning ::: noteimportant This is a work in progress. ::: # 12 Optimisation des performances ::: noteimportant Il s'agit d'un travail en cours de réalisation. ::: [comment]: # (tags: proxy) # 4 Proxy # 4 Proxy Common column parameters: | | | |--|--------| |*Name*|Name of the column.| |*Data*|Data type to display in the column:<br>**Item value** - value of the specified item<br>**Host name** - host name of the item specified in the *Item value* column<br>**Text** - static text string| |*Base color*|Background color of the column; fill color if *Item value* data is displayed as bar/indicators.<br>For *Item value* data the default color can be overridden by custom color, if the item value is over one of the specified "Thresholds".| Paramètres de colonne communs : | | | |--|--------| |*Nom*|Nom de la colonne.| |*Données*|Type de données à afficher dans la colonne :<br>**Valeur de l'élément** - valeur de l'élément spécifié<br>**Nom d'hôte** - nom d'hôte de l'élément spécifié dans la colonne *valeur de l'élément*<br>**Texte** - chaîne de texte statique| |*Couleur de base*|Couleur de fond de la colonne ; couleur de remplissage si les données *Valeur de l'élément* sont affichées sous forme de barres/indicateurs.<br>Pour les données *Valeur de l'élément*, la couleur par défaut peut être remplacée par une couleur personnalisée, si la valeur de l'élément est supérieure à l'un des "seuils" spécifiés.| ##### Common parameters - `/host/key` is a common mandatory first parameter for the functions referencing the host item history - `(sec|#num)<:time shift>` is a common second parameter for the functions referencing the host item history, where: - **sec** - maximum [evaluation period](/manual/config/triggers#evaluation_period) in seconds (time [suffixes](/manual/appendix/suffixes) can be used), or - **\#num** - maximum [evaluation range](/manual/config/triggers#evaluation_period) in latest collected values (if preceded by a hash mark) - **time shift** (optional) allows to move the evaluation point back in time. See [more details](/manual/config/triggers/expression#time_shift) on specifying time shift. ##### Paramètres communs - `/host/key` est un premier paramètre commun obligatoire pour les fonctions se référant à l'historique de l'élément collecté d'un hôte - `(sec|#num)<:time shift>` est le second paramètre pour les fonctions faisant référence à l'historique de l'élément collecté d'un hôte, avec : - **sec** - [plage d'évaluation](/manual/config/triggers#evaluation_period) en secondes (les [suffixes de temps](/manual/appendix/suffixes) peuvent être utilisés), ou - **\#num** - [plage d'évaluation](/manual/config/triggers#evaluation_period) en nombre de valeurs collectées (si précédé d'un signe dièse) - **décalage temporel** (facultatif) permet de déplacer le point d'évaluation dans le temps. Voir [plus de détails](/manual/config/triggers/expression#time_shift) sur la spécification du décalage temporel. ##### Common parameters - `/host/key` is a common mandatory first parameter for the functions referencing the host item history - `(sec|#num)<:time shift>` is a common second parameter for the functions referencing the host item history, where: - **sec** - maximum [evaluation period](/manual/config/triggers#evaluation_period) in seconds (time [suffixes](/manual/appendix/suffixes) can be used), or - **\#num** - maximum [evaluation range](/manual/config/triggers#evaluation_period) in latest collected values (if preceded by a hash mark) - **time shift** (optional) allows to move the evaluation point back in time. See [more details](/manual/config/triggers/expression#time_shift) on specifying time shift. ##### Paramètres communs - `/host/key` est un premier paramètre commun obligatoire pour les fonctions se référant à l'historique de l'élément d'hôte - `(sec|#num)<:time shift>` est un deuxième paramètre courant pour les fonctions faisant référence à l'historique de l'élément d'hôte, où : - **sec** - [période d'évaluation](/manual/config/triggers#evaluation_period) maximum en secondes (les [suffixes](/manual/appendix/suffixes) peuvent être utilisés), ou - **\#num** - [période d'évaluation](/manual/config/triggers#evaluation_period) maximum en nombre de valeurs collectées (si précédées d'un signe dièse) - **décalage horaire** (facultatif) permet de déplacer le point d'évaluation dans le temps. Voir [plus de détails](/manual/config/triggers/expression#time_shift) sur la spécification du décalage horaire. ##### Common parameters - `/host/key` is a common mandatory first parameter for the functions referencing the host item history - `(sec|#num)<:time shift>` is a common second parameter for the functions referencing the host item history, where: - **sec** - maximum [evaluation period](/manual/config/triggers#evaluation_period) in seconds (time [suffixes](/manual/appendix/suffixes) can be used), or - **\#num** - maximum [evaluation range](/manual/config/triggers#evaluation_period) in latest collected values (if preceded by a hash mark) - **time shift** (optional) allows to move the evaluation point back in time. See [more details](/manual/config/triggers/expression#time_shift) on specifying time shift. ##### Paramètres communs - `/host/key` est un premier paramètre commun obligatoire pour les fonctions se référant à l'historique de l'élément d'hôte - `(sec|#num)<:time shift>` est un deuxième paramètre courant pour les fonctions faisant référence à l'historique de l'élément d'hôte, où : - **sec** - [période d'évaluation](/manual/config/triggers#evaluation_period) maximum en secondes (les [suffixes](/manual/appendix/suffixes) peuvent être utilisés), ou - **\#num** - [période d'évaluation](/manual/config/triggers#evaluation_period) maximum en nombre de valeurs collectées (si précédées d'un signe dièse) - **décalage horaire** (facultatif) permet de déplacer le point d'évaluation dans le temps. Voir [plus de détails](/manual/config/triggers/expression#time_shift) sur la spécification du décalage horaire. ##### Common parameters - `/host/key` is a common mandatory first parameter - `time period:time shift` is a common second parameter, where: - **time period** - the time period (minimum '1h'), defined as \<N>\<time unit> where `N` - the number of time units, `time unit` - h (hour), d (day), w (week), M (month) or y (year). - **time shift** - the time period offset (see function examples) ##### Paramètres communs - `/host/key` est un premier paramètre obligatoire commun - `time period:time shift` est un deuxième paramètre commun, où : - **time period** - la période de temps (minimum '1h'), définie comme \<N>\<unité de temps> où `N` - le nombre d'unités de temps, `unité de temps` - h (heure), d (jour), w (semaine), M (mois) ou y (année). - **time shift** - le décalage horaire (voir exemples de fonctions) ##### Common use cases of global and host macros - use a global macro in several locations; then change the macro value and apply configuration changes to all locations with one click - take advantage of templates with host-specific attributes: passwords, port numbers, file names, regular expressions, etc. ##### Cas d'utilisation courants des macros globales et hôtes - utiliser une macro globale à plusieurs endroits ; puis modifiez la valeur de la macro et appliquez les modifications de configuration à tous les emplacements en un seul clic - tirez parti de modèles avec des attributs spécifiques à l'hôte : mots de passe, numéros de port, noms de fichiers, expressions régulières, etc. ##### Communication with Zabbix server |Parameter|Description| |--|--------| |*Network timeout*|How many seconds to wait before closing an idle socket (if a connection to Zabbix server has been established earlier, but frontend can not finish read/send data operation during this time, the connection will be dropped). Allowed range: 1 - 300s (default: 3s).| |*Connection timeout*|How many seconds to wait before stopping an attempt to connect to Zabbix server. Allowed range: 1 - 30s (default: 3s).| |*Network timeout for media type test*|How many seconds to wait for a response when testing a media type. Allowed range: 1 - 300s (default: 65s).| |*Network timeout for script execution*|How many seconds to wait for a response when executing a script. Allowed range: 1 - 300s (default: 60s).| |*Network timeout for item test*|How many seconds to wait for returned data when testing an item. Allowed range: 1 - 300s (default: 60s).| |*Network timeout for scheduled report test*|How many seconds to wait for returned data when testing a scheduled report. Allowed range: 1 - 300s (default: 60s).| ##### Communication avec le serveur Zabbix |Paramètre|Description| |--|--------| |*Délai d'expiration du réseau*|Combien de secondes à attendre avant de fermer un socket inactif (si une connexion au serveur Zabbix a été établie plus tôt, mais que le frontend ne peut pas terminer l'opération de lecture/envoi de données pendant ce temps, la connexion sera interrompue). Plage autorisée : 1 - 300s (par défaut : 3s).| |*Délai de connexion*|Combien de secondes attendre avant d'arrêter une tentative de connexion au serveur Zabbix. Plage autorisée : 1 - 30s (par défaut : 3s).| |*Délai d'expiration du réseau pour le test du type de média*|Combien de secondes attendre une réponse lors du test d'un type de média. Plage autorisée : 1 - 300s (par défaut : 65s).| |*Délai d'expiration du réseau pour l'exécution du script*|Combien de secondes attendre une réponse lors de l'exécution d'un script. Plage autorisée : 1 - 300s (par défaut : 60s).| |*Délai d'expiration du réseau pour le test de l'élément*|Combien de secondes attendre les données renvoyées lors du test d'un élément. Plage autorisée : 1 - 300s (par défaut : 60s).| |*Délai d'expiration du réseau pour le test de rapport planifié*|Combien de secondes attendre les données renvoyées lors du test d'un rapport planifié. Plage autorisée : 1 - 300s (par défaut : 60s).| #### Comparing the import of a template Compare the template contained in the XML string to the current system elements, and show what will be changed if this template will be imported. Request: ```json { "jsonrpc": "2.0", "method": "configuration.importcompare", "params": { "format": "xml", "rules": { "discoveryRules": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "graphs": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "groups": { "createMissing": true, "updateExisting": true }, "httptests": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "items": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "templateLinkage": { "createMissing": true, "deleteMissing": true }, "templates": { "createMissing": true, "updateExisting": true }, "templateDashboards": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "triggers": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "valueMaps": { "createMissing": true, "updateExisting": true, "deleteMissing": true } }, "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:30:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key><delay>3m</delay></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter>&lt;dt&gt;Server uptime: (.*)&lt;/dt&gt;</parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>648006da5971424ead0c47ddbbf1ea2e</uuid><name>CPU utilization</name><key>system.cpu.util</key><value_type>FLOAT</value_type><units>%</units><triggers><trigger><uuid>736225012c534ec480c2a66a91322ce0</uuid><expression>avg(/New template/system.cpu.util,3m)&gt;70</expression><name>CPU utilization too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templates": { "updated": [ { "before": { "uuid": "5aef0444a82a4d8cb7a95dc4c0c85330", "template": "New template", "name": "New template" }, "after": { "uuid": "5aef0444a82a4d8cb7a95dc4c0c85330", "template": "New template", "name": "New template" }, "items": { "added": [ { "after": { "uuid": "648006da5971424ead0c47ddbbf1ea2e", "name": "CPU utilization", "key": "system.cpu.util", "value_type": "FLOAT", "units": "%" }, "triggers": { "added": [ { "after": { "uuid": "736225012c534ec480c2a66a91322ce0", "expression": "avg(/New template/system.cpu.util,3m)>70", "name": "CPU utilization too high on 'New host' for 3 minutes", "priority": "WARNING" } } ] } } ], "removed": [ { "before": { "uuid": "6805d4c39a624a8bab2cc8ab63df1ab3", "name": "CPU load", "key": "system.cpu.load", "value_type": "FLOAT" }, "triggers": { "removed": [ { "before": { "uuid": "ab4c2526c2bc42e48a633082255ebcb3", "expression": "avg(/New template/system.cpu.load,3m)>2", "name": "CPU load too high on 'New host' for 3 minutes", "priority": "WARNING" } } ] } } ], "updated": [ { "before": { "uuid": "7f1e6f1e48aa4a128e5b6a958a5d11c3", "name": "Zabbix agent ping", "key": "agent.ping" }, "after": { "uuid": "7f1e6f1e48aa4a128e5b6a958a5d11c3", "name": "Zabbix agent ping", "key": "agent.ping", "delay": "3m" } } ] } } ] } }, "id": 1 } ``` #### Comparer l'importation d'un modèle Compare le modèle contenu dans la chaîne XML aux éléments système actuels, et montre ce qui sera changé si ce modèle est importé. Requête : ```json { "jsonrpc": "2.0", "method": "configuration.importcompare", "params": { "format": "xml", "rules": { "discoveryRules": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "graphs": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "groups": { "createMissing": true, "updateExisting": true }, "httptests": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "items": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "templateLinkage": { "createMissing": true, "deleteMissing": true }, "templates": { "createMissing": true, "updateExisting": true }, "templateDashboards": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "triggers": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "valueMaps": { "createMissing": true, "updateExisting": true, "deleteMissing": true } }, "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:30:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key><delay>3m</delay></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter><dt>Server uptime: (.*)</dt></parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>648006da5971424ead0c47ddbbf1ea2e</uuid><name>CPU utilization</name><key>system.cpu.util</key><value_type>FLOAT</value_type><units>%</units><triggers><trigger><uuid>736225012c534ec480c2a66a91322ce0</uuid><expression>avg(/New template/system.cpu.util,3m)>70</expression><name>CPU utilization too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templates": { "updated": [ { "before": { "uuid": "5aef0444a82a4d8cb7a95dc4c0c85330", "template": "New template", "name": "New template" }, "after": { "uuid": "5aef0444a82a4d8cb7a95dc4c0c85330", "template": "New template", "name": "New template" }, "items": { "added": [ { "after": { "uuid": "648006da5971424ead0c47ddbbf1ea2e", "name": "CPU utilization", "key": "system.cpu.util", "value_type": "FLOAT", "units": "%" }, "triggers": { "added": [ { "after": { "uuid": "736225012c534ec480c2a66a91322ce0", "expression": "avg(/New template/system.cpu.util,3m)>70", "name": "CPU utilization too high on 'New host' for 3 minutes", "priority": "WARNING" } } ] } } ], "removed": [ { "before": { "uuid": "6805d4c39a624a8bab2cc8ab63df1ab3", "name": "CPU load", "key": "system.cpu.load", "value_type": "FLOAT" }, "triggers": { "removed": [ { "before": { "uuid": "ab4c2526c2bc42e48a633082255ebcb3", "expression": "avg(/New template/system.cpu.load,3m)>2", "name": "CPU load too high on 'New host' for 3 minutes", "priority": "WARNING" } } ] } } ], "updated": [ { "before": { "uuid": "7f1e6f1e48aa4a128e5b6a958a5d11c3", "name": "Zabbix agent ping", "key": "agent.ping" }, "after": { "uuid": "7f1e6f1e48aa4a128e5b6a958a5d11c3", "name": "Zabbix agent ping", "key": "agent.ping", "delay": "3m" } } ] } } ] } }, "id": 1 } ``` #### Compiling PCRE 1. Download the PCRE or PCRE2 (supported since Zabbix 6.0) library (<https://pcre.org/>). 2. Extract to directory *E:\\pcre2-10.39*. 3. Install CMake from <https://cmake.org/download/>, during install select: and ensure that cmake\\bin is on your path (tested version 3.9.4). 4. Create a new, empty build directory, preferably a subdirectory of the source dir. For example, *E:\\pcre2-10.39\\build*. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui. Do not try to start Cmake from the Windows Start menu, as this can lead to errors. 6. Enter *E:\\pcre2-10.39* and *E:\\pcre2-10.39\\build* for the source and build directories, respectively. 7. Hit the "Configure" button. 8. When specifying the generator for this project select "NMake Makefiles". 9. Create a new, empty install directory. For example, *E:\\pcre2-10.39-install*. 10. The GUI will then list several configuration options. Make sure the following options are selected: - **PCRE\_SUPPORT\_UNICODE\_PROPERTIES** ON - **PCRE\_SUPPORT\_UTF** ON - **CMAKE\_INSTALL\_PREFIX** *E:\\pcre2-10.39-install* 11. Hit "Configure" again. The adjacent "Generate" button should now be active. 12. Hit "Generate". 13. In the event that errors occur, it is recommended that you delete the CMake cache before attempting to repeat the CMake build process. In the CMake GUI, the cache can be deleted by selecting "File > Delete Cache". 14. The build directory should now contain a usable build system - *Makefile*. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the *Makefile* mentioned above. 16. Run NMake command: `E:\pcre2-10.39\build> nmake install ` #### Compilation du PCRE 1. Télécharger la bibliothèque PCRE ou PCRE2 (prise en charge depuis Zabbix 6.0) depuis le référentiel pcre.org : (<https://github.com/PhilipHazel/pcre2/releases/download/pcre2-10.39/pcre2-10.39.zip>) 2. Extraire dans le répertoire *E:\\pcre2-10.39* 3. Installer CMake à partir de <https://cmake.org/download/>, lors de l'installation, sélectionner et s'assurer que cmake\\bin est sur votre chemin (version testée 3.9.4). 4. Créer un nouveau répertoire de construction vide, de préférence un sous-répertoire du répertoire source. Par exemple, *E:\\pcre2-10.39\\build*. 5. Ouvrir une fenêtre de ligne de commande, par ex. l'invite de commande x64 Native Tools pour VS 2017 et à partir de cet environnement shell, exécuter cmake-gui. Ne pas essayer de démarrer Cmake à partir du menu Démarrer de Windows, car cela peut entraîner des erreurs. 6. Saisir *E:\\pcre2-10.39* et *E:\\pcre2-10.39\\build* pour les répertoires source et build, respectivement. 7. Appuyer sur le bouton "Configurer". 8. Lors de la spécification du générateur pour ce projet, sélectionner "NMake Makefiles". 9. Créer un nouveau répertoire d'installation vide. Par exemple, *E:\\pcre2-10.39-install*. 10. L'interface graphique listera alors plusieurs options de configuration. S'assurer que les options suivantes sont bien sélectionnées : - **PCRE\_SUPPORT\_UNICODE\_PROPERTIES** ON - **PCRE\_SUPPORT\_UTF** ON - **CMAKE\_INSTALL\_PREFIX** *E:\\pcre2-10.39-install* 11. Appuyer à nouveau sur "Configurer". Le bouton "Générer" adjacent devrait maintenant être actif. 12. Appuyer sur "Générer". 13. En cas d'erreurs, il est recommandé de supprimer le cache CMake avant de tenter de répéter le processus de génération CMake. Dans l'interface graphique de CMake, le cache peut être supprimé en sélectionnant "Fichier > Supprimer le cache". 14. Le répertoire de construction devrait maintenant contenir un système de construction utilisable - *Makefile*. 15. Ouvrir une fenêtre de ligne de commande, par ex. l'invite de commande x64 Native Tools pour VS 2017 et accéder au * Makefile * mentionné ci-dessus. 16. Exécuter la commande NMake : `E:\pcre2-10.39\build> nmake install ` #### Compiling Zabbix agent 2 #### Compilation de l'agent Zabbix 2 #### Compiling Zabbix agent on HP-UX If you install the PCRE library from a popular HP-UX package site <http://hpux.connect.org.uk>, for example from file `pcre-8.42-ia64_64-11.31.depot`, you get only the 64-bit version of the library installed in the /usr/local/lib/hpux64 directory. In this case, for successful agent compilation customized options need to be used for the "configure" script, e.g.: CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64 #### Compilation de l'agent Zabbix sur HP-UX Si vous installez la bibliothèque PCRE à partir d'un site de packages HP-UX populaire <http://hpux.connect.org.uk>, par exemple à partir du fichier `pcre-8.42-ia64_64-11.31.depot`, vous n'obtenez que la version 64-bit de la bibliothèque installée dans le répertoire /usr/local/lib/hpux64. Dans ce cas, pour une compilation réussie de l'agent, des options personnalisées doivent être utilisées avec le script "configure", par exemple : CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64 #### Compiling Zabbix The following steps will help you to compile Zabbix from sources on MS Windows 10 (64-bit). When compiling Zabbix with/without TLS support the only significant difference is in step 4. 1. On a Linux machine check out the source from git:`` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git $ cd zabbix $ ./bootstrap.sh $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd` $ make dbschema $ make dist `` 2. Copy and unpack the archive, e.g. zabbix-4.4.0.tar.gz, on a Windows machine. 3. Let's assume that sources are in e:\\zabbix-4.4.0. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. Go to E:\\zabbix-4.4.0\\build\\win32\\project. 4. Compile zabbix\_get, zabbix\_sender and zabbix\_agent. - without TLS: `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib ` - with TLS: `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib ` 5. New binaries are located in e:\\zabbix-4.4.0\\bin\\win64. Since OpenSSL was compiled with 'no-shared' option, Zabbix binaries contain OpenSSL within themselves and can be copied to other machines that do not have OpenSSL. #### Compilation de Zabbix Les étapes suivantes vous aideront à compiler Zabbix à partir de sources sur MS Windows 10 (64 bits). Lors de la compilation de Zabbix avec/sans prise en charge TLS, la seule différence significative est à l'étape 4. 1. Sur une machine Linux, vérifiez la source à partir du git : `` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git $ cd zabbix $ ./bootstrap.sh $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd` $ faire dbschema $ faire dist `` 2. Copiez et décompressez l'archive, par ex. zabbix-4.4.0.tar.gz, sur une machine Windows. 3. Supposons que les sources sont dans e:\\zabbix-4.4.0. Ouvrir une fenêtre de ligne de commande, par ex. l'invite de commande des outils natifs x64 pour VS RC 2017. Accédez à E:\\zabbix-4.4.0\\build\\win32\\project. 4. Compilez zabbix\_get, zabbix\_sender et zabbix\_agent. - sans TLS : `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib ` - avec TLS : `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib ` 5. Les nouveaux fichiers binaires sont situés dans e:\\zabbix-4.4.0\\bin\\win64. Comme OpenSSL a été compilé avec l'option 'no-shared', les binaires Zabbix contiennent OpenSSL en eux-mêmes et peuvent être copiés vers d'autres machines qui n'ont pas OpenSSL. ### Conditions The following conditions can be used in service actions: |Condition type|Supported operators|Description| |--|--|------| |*Service*|equals<br>does not equal|Specify a service or a service to exclude.<br>**equals** - event belongs to this service.<br>**does not equal** - event does not belong to this service.<br>Specifying a parent service implicitly selects all child services. To specify the parent service only, all nested services have to be additionally set with the **does not equal** operator.| |*Service name*|contains<br>does not contain|Specify a string in the service name or a string to exclude.<br>**contains** - event is generated by a service, containing this string in the name.<br>**does not contain** - this string cannot be found in the service name.| |*Service tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag or an event tag to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag<br>**does not equal** - event does not have this tag<br>**contains** - event has a tag containing this string<br>**does not contain** - event does not have a tag containing this string.| |*Service tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag and value combination or a tag and value combination to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag and value<br>**does not equal** - event does not have this tag and value<br>**contains** - event has a tag and value containing these strings<br>**does not contain** - event does not have a tag and value containing these strings.| :::noteimportant Make sure to define [message templates](/manual/config/notifications/media#overview) for Service actions in the *Administration->Media types* menu. Otherwise, the notifications will not be sent. ::: ### Conditions Les conditions suivantes peuvent être utilisées dans les actions de maintenance : |Type de condition|Opérateurs pris en charge|Description| |--|--|------| |*Service*|égal<br>n'est pas égal|Spécifiez un service ou un service à exclure.<br>**égal** - l'événement appartient à ce service.<br>**n'est pas égal** - l'événement n'est pas égal n'appartiennent pas à ce service.<br>Spécifier un service parent sélectionne implicitement tous les services enfants. Pour spécifier uniquement le service parent, tous les services imbriqués doivent être définis en plus avec l'opérateur **n'est pas égal**.| |*Nom du service*|contient<br>ne contient pas|Spécifiez une chaîne dans le nom du service ou une chaîne à exclure.<br>**contient** - l'événement est généré par un service, contenant cette chaîne dans le nom. <br>**ne contient pas** - cette chaîne est introuvable dans le nom du service.| |*Nom du tag de service*|égal<br>n'est pas égal<br>contient<br>ne contient pas|Spécifiez un tag d'événement ou un tag d'événement à exclure. Les tags d'événement de service peuvent être définies dans la section de configuration de service *Tags*.<br>**égal** - l'événement a ce tag<br>**n'est pas égal** - l'événement n'a pas ce tag<br>** contient** - l'événement a un tag contenant cette chaîne<br>**ne contient pas** - l'événement n'a pas de tag contenant cette chaîne.| |*Valeur du tag de service*|égal<br>n'est pas égal<br>contient<br>ne contient pas|Spécifiez une combinaison de tag d'événement et de valeur ou une combinaison de tag et de valeur à exclure. Les tags d'événement de service peuvent être définies dans la section de configuration de service *Tags*.<br>**égal** - l'événement a ce tag et cette valeur<br>**n'est pas égal** - l'événement n'a pas ce tag et cette valeur< br>**contient** - l'événement a un tag et une valeur contenant ces chaînes<br>**ne contient pas** - l'événement n'a pas de tag et de valeur contenant ces chaînes.| :::noteimportant Assurez-vous de définir des [modèles de message](/manual/config/notifications/media#overview) pour les actions de service dans le menu *Administration->Types de médias*. Sinon, les notifications ne seront pas envoyées. ::: #### Configurable fields The **key** is a unique item identifier (per host). You can create any key name using supported symbols. Calculation definition should be entered in the **Formula** field. There is virtually no connection between the formula and the key. The key parameters are not used in the formula in any way. The syntax of a simple formula is: function(/host/key,<parameter1>,<parameter2>,...) where: | | | |--|--------| |*function*|One of the [supported functions](/manual/appendix/functions): last, min, max, avg, count, etc| |*host*|Host of the item that is used for calculation.<br>The current host can be omitted (i.e. as in `function(//key,parameter,...)`).| |*key*|Key of the item that is used for calculation.| |*parameter(s)*|Parameters of the function, if required.| ::: noteimportant [User macros](/manual/config/macros/user_macros) in the formula will be expanded if used to reference a function parameter, item filter parameter, or a constant. User macros will NOT be expanded if referencing a function, host name, item key, item key parameter or operator. ::: A more complex formula may use a combination of functions, operators and brackets. You can use all functions and [operators](/manual/config/triggers/expression#operators) supported in trigger expressions. The logic and operator precedence are exactly the same. Unlike trigger expressions, Zabbix processes calculated items according to the item update interval, not upon receiving a new value. All items that are referenced by history functions in the calculated item formula must exist and be collecting data. Also, if you change the item key of a referenced item, you have to manually update any formulas using that key. A calculated item may become unsupported in several cases: - referenced item(s) - is not found - is disabled - belongs to a disabled host - is not supported (except with nodata() function and [operators](/manual/config/triggers/expression#operators) with unknown values) - no data to calculate a function - division by zero - incorrect syntax used #### Champs configurables La **clé** est un identifiant d'élément unique (par hôte). Vous pouvez créer n'importe quel nom de clé à l'aide des symboles pris en charge. La définition du calcul doit être saisie dans le champ **Formule**. Il n'y a pratiquement aucun lien entre la formule et la clé. Les paramètres clés ne sont en aucun cas utilisés dans la formule. La syntaxe d'une formule simple est : fonction(/hôte/clé,<paramètre1>,<paramètre2>,...) où : | | | |--|--------| |*fonction*|L'une des [fonctions prises en charge](/manual/appendix/functions): last, min, max, avg, count, etc| |*hôte*|Hôte de l'élément utilisé pour le calcul.<br>L'hôte actuel peut être omis (comme dans`fonction(//clé,paramètre,...)`).| |*clé*|Clé de l'élément utilisé pour le calcul.| |*paramètre(s)*|Paramètres de la fonction, si nécessaire.| ::: noteimportant Les [macros utilisateur](/manual/config/macros/user_macros) de la formule seront développées si elles sont utilisées pour référencer un paramètre de fonction, un paramètre de filtre d'élément ou une constante. Les macros utilisateur ne seront PAS développées si elles font référence à une fonction, un nom d'hôte, une clé d'élément, un paramètre de clé d'élément ou un opérateur. ::: Une formule plus complexe peut utiliser une combinaison de fonctions, d'opérateurs et de parenthèses. Vous pouvez utiliser toutes les fonctions et tous les [opérateurs](/manual/config/triggers/expression#operators) pris en charge dans les expressions de déclencheur. La logique et la priorité des opérateurs sont exactement les mêmes. Contrairement aux expressions de déclencheur, Zabbix traite les éléments calculés en fonction de l'intervalle de mise à jour des éléments, et non lors de la réception d'une nouvelle valeur. Tous les éléments référencés par les fonctions d'historique dans la formule d'élément calculé doivent exister et collecter des données. De plus, si vous modifiez la clé d'élément d'un élément référencé, vous devez mettre à jour manuellement toutes les formules utilisant cette clé. Un élément calculé peut devenir non pris en charge dans plusieurs cas : - l'article(s) référencé(s) - n'est pas trouvé - est désactivé - appartient à un hôte désactivé - n'est pas pris en charge (sauf avec la fonction nodata() et les [opérateurs](/manual/config/triggers/expression#operators) avec des valeurs inconnues) - pas de donnée pour calculer une fonction - division par zéro - syntaxe incorrecte utilisée #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration #### Configuration ### Configuration 1. Create disabled Script item on the main VMware host (where the **eventlog[]** item is present) with the following parameters:  - *Name*: VMware metrics - *Type*: Script - *Key*: vmware.metrics - *Type of information*: Text - *Script*: copy and paste the [script](#script) provided below - *Timeout*: 10 - *History storage period*: Do not keep history - *Enabled*: unmarked #### Script try { Zabbix.log(4, 'vmware metrics script'); var result, resp, req = new HttpRequest(); req.addHeader('Content-Type: application/xml'); req.addHeader('SOAPAction: "urn:vim25/6.0"'); login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:Login>\ <urn:_this type="SessionManager">SessionManager</urn:_this>\ <urn:userName>{$VMWARE.USERNAME}</urn:userName>\ <urn:password>{$VMWARE.PASSWORD}</urn:password>\ </urn:Login>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}", login); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:RetrieveProperties>\ <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\ <urn:specSet>\ <urn:propSet>\ <urn:type>PerformanceManager</urn:type>\ <urn:pathSet>perfCounter</urn:pathSet>\ </urn:propSet>\ <urn:objectSet>\ <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\ </urn:objectSet>\ </urn:specSet>\ </urn:RetrieveProperties>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}", query); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } Zabbix.log(4, 'vmware metrics=' + resp); result = resp; logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:Logout>\ <urn:_this type="SessionManager">SessionManager</urn:_this>\ </urn:Logout>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}",logout); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } } catch (error) { Zabbix.log(4, 'vmware call failed : '+error); result = {}; } return result; Once the item is configured, press *Test* button, then press *Get value*. {width=600} Copy received XML to any XML formatter and find the desired metric. An example of XML for one metric: <PerfCounterInfo xsi:type="PerfCounterInfo"> <key>6</key> <nameInfo> <label>Usage in MHz</label> <summary>CPU usage in megahertz during the interval</summary> <key>usagemhz</key> </nameInfo> <groupInfo> <label>CPU</label> <summary>CPU</summary> <key>cpu</key> </groupInfo> <unitInfo> <label>MHz</label> <summary>Megahertz</summary> <key>megaHertz</key> </unitInfo> <rollupType>average</rollupType> <statsType>rate</statsType> <level>1</level> <perDeviceLevel>3</perDeviceLevel> </PerfCounterInfo> Use XPath to extract the counter path from received XML. For the example above, the XPath will be: |field |xPath | value | |--|--|--| |group | //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average | Resulting performance counter path in this case is: `cpu/usagemhz[average]` ### Configuration 1. Créez un élément de script désactivé sur l'hôte VMware principal (où l'élément **eventlog[]** est présent) avec les paramètres suivants :  - *Nom* : métriques VMware - *Type* : Script - *Clé* : vmware.metrics - *Type d'information* : Texte - *Script* : copiez et collez le [script](#script) fourni ci-dessous - *Expiration* : 10 - *Période de stockage de l'historique* : Ne gardez pas l'historique - *Activé* : non coché #### Script try { Zabbix.log(4, 'vmware metrics script'); var result, resp, req = new HttpRequest(); req.addHeader('Content-Type: application/xml'); req.addHeader('SOAPAction: "urn:vim25/6.0"'); login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:Login>\ <urn:_this type="SessionManager">SessionManager</urn:_this>\ <urn:userName>{$VMWARE.USERNAME}</urn:userName>\ <urn:password>{$VMWARE.PASSWORD}</urn:password>\ </urn:Login>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}", login); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:RetrieveProperties>\ <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\ <urn:specSet>\ <urn:propSet>\ <urn:type>PerformanceManager</urn:type>\ <urn:pathSet>perfCounter</urn:pathSet>\ </urn:propSet>\ <urn:objectSet>\ <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\ </urn:objectSet>\ </urn:specSet>\ </urn:RetrieveProperties>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}", query); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } Zabbix.log(4, 'vmware metrics=' + resp); result = resp; logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\ <soapenv:Header/>\ <soapenv:Body>\ <urn:Logout>\ <urn:_this type="SessionManager">SessionManager</urn:_this>\ </urn:Logout>\ </soapenv:Body>\ </soapenv:Envelope>' resp = req.post("{$VMWARE.URL}",logout); if (req.getStatus() != 200) { throw 'Response code: '+req.getStatus(); } } catch (error) { Zabbix.log(4, 'vmware call failed : '+error); result = {}; } return result; Une fois l'élément configuré, appuyez sur le bouton *Test*, puis appuyez sur *Obtenir la valeur*. {width=600} Copiez le XML reçu dans n'importe quel formateur XML et trouvez la métrique souhaitée. Exemple de XML pour une métrique : <PerfCounterInfo xsi:type="PerfCounterInfo"> <key>6</key> <nameInfo> <label>Usage in MHz</label> <summary>CPU usage in megahertz during the interval</summary> <key>usagemhz</key> </nameInfo> <groupInfo> <label>CPU</label> <summary>CPU</summary> <key>cpu</key> </groupInfo> <unitInfo> <label>MHz</label> <summary>Megahertz</summary> <key>megaHertz</key> </unitInfo> <rollupType>average</rollupType> <statsType>rate</statsType> <level>1</level> <perDeviceLevel>3</perDeviceLevel> </PerfCounterInfo> Utilisez XPath pour extraire le chemin du compteur du XML reçu. Pour l'exemple ci-dessus, le XPath sera : |champ |xPath | valeur | |--|--|--| |group| //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average | Le chemin du compteur de performances résultant dans ce cas est : `cpu/usagemhz[average]` #### Configuration Debug mode can be activated for individual users who belong to a user group: - when configuring a [user group](/manual/config/users_and_usergroups/usergroup#configuration); - when viewing configured [user groups](//manual/web_interface/frontend_sections/administration/user_groups). When *Debug mode* is enabled for a user group, its users will see a *Debug* button in the lower right corner of the browser window:  Clicking on the *Debug* button opens a new window below the page contents which contains the SQL statistics of the page, along with a list of API calls and individual SQL statements: {width="600"} In case of performance problems with the page, this window may be used to search for the root cause of the problem. ::: notewarning Enabled *Debug mode* negatively affects frontend performance. ::: #### Configuration Le mode debug peut être activé pour des utilisateurs individuels appartenant à un groupe d'utilisateurs : - lors de la configuration d'un [groupe d'utilisateur](/fr/manual/config/users_and_usergroups/usergroup#configuration); - lors de la visualisation de la configuration des [groupes d'utilisateurs](/fr/manual/web_interface/frontend_sections/administration/user_groups). Quand le *mode Debug* est activé pour un groupe d'utilisateur, cet utilisateur verra un bouton *Debug* dans le coin en bas à droite du navigateur :  En cliquant sur le bouton *Debug* cela ouvre une nouvelle fenêtre sous le contenu de la page contenant les statistiques SQL de la page, ainsi qu'une liste des appels API et des instructions SQL individuelles : {width="600"} En cas de problèmes de performance avec la page, cette fenêtre pourrait être utilisée pour chercher la cause racine du problème. ::: notewarning Activer le *mode Debug* affecte négativement les performances de l'interface web. ::: # configuration.export # configuration.export #### Configuration file For details on configuring Zabbix agent see the configuration file options for [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) or [Windows agent](/manual/appendix/config/zabbix_agentd_win). #### Fichier de configuration Pour plus de détails sur la configuration de l'agent Zabbix, voir les options du fichier de configuration pour [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) ou l'[agent Windows]/manual/appendix/config/zabbix_agentd_win). ##### Configuration file See the [configuration file](/manual/appendix/config/zabbix_proxy) options for details on configuring zabbix\_proxy. ##### Fichier de configuration Voir les options du [fichier de configuration](/manual/appendix/config/zabbix_proxy) pour les détails sur la configuration de zabbix\_proxy. ##### Configuration file See the [configuration file](/manual/appendix/config/zabbix_server) options for details on configuring zabbix\_server. ##### Fichier de configuration Voir les options du [fichier de configuration](/manual/appendix/config/zabbix_server) pour plus de détails sur la configuration de zabbix\_server. #### Configuration file The configuration parameters of agent 2 are mostly compatible with Zabbix agent with some exceptions. |New parameters|Description| |--|--------| |*ControlSocket*|The runtime control socket path. Agent 2 uses a control socket for [runtime commands](#runtime_control).| |*EnablePersistentBuffer*,<br>*PersistentBufferFile*,<br>*PersistentBufferPeriod*|These parameters are used to configure persistent storage on agent 2 for active items.| |*ForceActiveChecksOnStart*|Determines whether the agent should perform active checks immediately after restart or spread evenly over time. Supported since Zabbix 6.0.2.| |*Plugins*|Plugins may have their own parameters, in the format `Plugins.<Plugin name>.<Parameter>=<value>`. A common plugin parameter is *System.Capacity*, setting the limit of checks that can be executed at the same time.| |*StatusPort*|The port agent 2 will be listening on for HTTP status request and display of a list of configured plugins and some internal parameters| |**Dropped parameters**|**Description**| |*AllowRoot*, *User*|Not supported because daemonization is not supported.| |*LoadModule*, *LoadModulePath*|Loadable modules are not supported.| |*StartAgents*|This parameter was used in Zabbix agent to increase passive check concurrency or disable them. In Agent 2, the concurrency is configured at a plugin level and can be limited by a capacity setting. Whereas disabling passive checks is not currently supported.| |*HostInterface*, *HostInterfaceItem*|Not yet supported.| For more details see the configuration file options for [zabbix\_agent2](/manual/appendix/config/zabbix_agent2). #### Fichier de configuration Les paramètres de configuration de l'agent 2 sont pour la plupart compatibles avec l'agent Zabbix à quelques exceptions près. |Nouveaux paramètres|Description| |--|--------| |*ControlSocket*|Le chemin du socket de contrôle d'exécution. L'agent 2 utilise un socket de contrôle pour les [commandes d'exécution](#runtime_control).| |*EnablePersistentBuffer*,<br>*PersistentBufferFile*,<br>*PersistentBufferPeriod*|Ces paramètres sont utilisés pour configurer le stockage persistant sur l'agent 2 pour les éléments actifs.| |*ForceActiveChecksOnStart*|Détermine si l'agent doit effectuer des vérifications actives immédiatement après le redémarrage ou réparties uniformément dans le temps. Pris en charge depuis Zabbix 6.0.2.| |*Plugins*|Les plugins peuvent avoir leurs propres paramètres, au format `Plugins.<Plugin name>.<Parameter>=<value>`. Un paramètre de plugin courant est *System.Capacity*, définissant la limite des vérifications pouvant être exécutées en même temps.| |*StatusPort*|L'agent de port 2 écoutera la demande d'état HTTP et affichera une liste de plugins configurés et certains paramètres internes| |**Paramètres abandonnés**|**Description**| |*AllowRoot*,*User*|Non pris en charge car la démonisation n'est pas prise en charge.| |*LoadModule*,*LoadModulePath*|Les modules chargeables ne sont pas pris en charge.| |*StartAgents*|Ce paramètre a été utilisé dans l'agent Zabbix pour augmenter la simultanéité des vérifications passives ou pour les désactiver. Dans l'agent 2, la simultanéité est configurée au niveau du plug-in et peut être limitée par un paramètre de capacité. Alors que la désactivation des vérifications passives n'est actuellement pas prise en charge.| |*HostInterface*,*HostInterfaceItem*|Pas encore pris en charge.| Pour plus de détails, consultez les options du fichier de configuration pour [zabbix\_agent2](/manual/appendix/config/zabbix_agent2). #### Configuration Global notifications can be enabled per user in the *Messaging* tab of [profile configuration](/manual/web_interface/user_profile).  |Parameter|Description| |---------|-----------| |*Frontend messaging*|Mark the checkbox to enable global notifications.| |*Message timeout*|You can set for how long the message will be displayed. By default, messages will stay on screen for 60 seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 5m, 2h, 1d.| |*Play sound*|You can set how long the sound will be played.<br>**Once** - sound is played once and fully.<br>**10 seconds** - sound is repeated for 10 seconds.<br>**Message timeout** - sound is repeated while the message is visible.| |*Trigger severity*|You can set the trigger severities that global notifications and sounds will be activated for. You can also select the sounds appropriate for various severities.<br>If no severity is marked then no messages will be displayed at all.<br>Also, recovery messages will only be displayed for those severities that are marked. So if you mark *Recovery* and *Disaster*, global notifications will be displayed for the problems and the recoveries of disaster severity triggers.| |*Show suppressed problems*|Mark the checkbox to display notifications for problems which would otherwise be suppressed (not shown) because of host maintenance.| #### Configuration Les notifications globales peuvent être activées par utilisateur dans l'onglet *Messagerie* de la [configuration du profil](/manual/web_interface/user_profile).  |Paramètres|Description| |-----------|-----------| |*Message dans l'interface*|Cochez la case pour activer les notifications globales.| |*Expiration du message*|Vous pouvez définir la durée d'affichage du message. Par défaut, les messages restent à l'écran pendant 60 secondes.<br>Les [suffixes](/fr/manual/appendix/suffixes) temporels sont pris en charge, par exemple : 30s, 5m, 2h, 1d.| |*Jouer un son*|Vous pouvez définir la durée pendant laquelle le son sera joué.<br>**Une fois** - le son est joué une fois complètement.<br>**10 secondes** - le son est répété pendant 10 secondes.<br>**Expiration du message** - le son est répété tant que le message est visible.| |*Sévérité du déclencheur*|Vous pouvez définir les gravités de déclenchement pour lesquelles les notifications globales et les sons sont activés. Vous pouvez également sélectionner les sons correspondant à diverses sévérités.<br>Si aucune sévérité n'est marquée, aucun message ne sera affiché.<br>De plus, les messages de récupération ne seront affichés que pour les sévérités marquées. Ainsi, si vous marquez *Récupération* et *Désastre*, des notifications globales seront affichées pour les problèmes et les récupérations de déclencheurs de sévérité désastre.| |*Afficher les problèmes supprimés*|Cochez la case pour afficher les notifications relatives aux problèmes qui seraient autrement supprimés (non affichés) en raison de la maintenance de l'hôte.| # configuration.import # configuration.import # configuration.importcompare # configuration.importcompare ### Configuration import See changes in the [configuration import](/manual/introduction/whatsnew6013#configuration-import) process. ### Importation de configurations Voir les changements dans le processus [importation de configurations](/manual/introduction/whatsnew6013#configuration-import). #### Configuration In order to enable maintenance mode, the `maintenance.inc.php` file (located in `/conf` of Zabbix HTML document directory on the web server) must be modified to uncomment the following lines: // Maintenance mode. define('ZBX_DENY_GUI_ACCESS', 1); // Array of IP addresses, which are allowed to connect to frontend (optional). $ZBX_GUI_ACCESS_IP_RANGE = array('127.0.0.1'); // Message shown on warning screen (optional). $ZBX_GUI_ACCESS_MESSAGE = 'We are upgrading MySQL database till 15:00. Stay tuned...'; #### Configuration Pour activer le mode maintenance, le fichier `maintenance.inc.php` (situé dans /conf du répertoire HTML Zabbix sur le serveur Web) doit être modifié pour supprimer les commentaires et ressembler à : // Maintenance mode. define('ZBX_DENY_GUI_ACCESS', 1); // Array of IP addresses, which are allowed to connect to frontend (optional). $ZBX_GUI_ACCESS_IP_RANGE = array('127.0.0.1'); // Message shown on warning screen (optional). $ZBX_GUI_ACCESS_MESSAGE = 'We are upgrading MySQL database till 15:00. Stay tuned...'; #### Configuration ODBC configuration is done by editing **odbcinst.ini** and **odbc.ini** files. These configuration files can be found in */etc* folder. The file **odbcinst.ini** may be missing and in this case it is necessary to create it manually. **odbcinst.ini** [mysql] Description = General ODBC for MySQL Driver = /usr/lib64/libmyodbc5.so Setup = /usr/lib64/libodbcmyS.so FileUsage = 1 Please consider the following examples of **odbc.ini** configuration parameters. - An example with a connection through an IP: ```{=html} <!-- --> ``` [TEST_MYSQL] Description = MySQL database 1 Driver = mysql Port = 3306 Server = 127.0.0.1 - An example with a connection through an IP and with the use of credentials. A Zabbix database is used by default: ```{=html} <!-- --> ``` [TEST_MYSQL_FILLED_CRED] Description = MySQL database 2 Driver = mysql User = root Port = 3306 Password = zabbix Database = zabbix Server = 127.0.0.1 - An example with a connection through a socket and with the use of credentials. A Zabbix database is used by default: ```{=html} <!-- --> ``` [TEST_MYSQL_FILLED_CRED_SOCK] Description = MySQL database 3 Driver = mysql User = root Password = zabbix Socket = /var/run/mysqld/mysqld.sock Database = zabbix All other possible configuration parameter options can be found in [MySQL official documentation](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html) web page. #### Configuration La configuration ODBC est effectuée en éditant les fichiers **odbcinst.ini** et **odbc.ini**. Ces fichiers de configuration peuvent être trouvés dans le dossier */etc*. Le fichier **odbcinst.ini** peut être manquant et dans ce cas il est nécessaire de le créer manuellement. **odbcinst.ini** [mysql] Description = General ODBC for MySQL Driver = /usr/lib64/libmyodbc5.so Setup = /usr/lib64/libodbcmyS.so FileUsage = 1 Veuillez prendre en compte les exemples suivants de paramètres de configuration **odbc.ini**. - Un exemple avec une connexion via une adresse IP : ```{=html} <!-- --> ``` [TEST_MYSQL] Description = MySQL database 1 Driver = mysql Port = 3306 Server = 127.0.0.1 - Un exemple avec une connexion via une adresse IP et avec l'utilisation d'informations d'identification. Une base de données Zabbix est utilisée par défaut : ```{=html} <!-- --> ``` [TEST_MYSQL_FILLED_CRED] Description = MySQL database 2 Driver = mysql User = root Port = 3306 Password = zabbix Database = zabbix Server = 127.0.0.1 - Un exemple avec une connexion via un socket et avec l'utilisation d'informations d'identification. Une base de données Zabbix est utilisée par défaut : ```{=html} <!-- --> ``` [TEST_MYSQL_FILLED_CRED_SOCK] Description = MySQL database 3 Driver = mysql User = root Password = zabbix Socket = /var/run/mysqld/mysqld.sock Database = zabbix Toutes les autres options de paramètres de configuration possibles peuvent être trouvées dans la page web de [documentation officielle de MySQL](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html). ### Configuration Once you have [installed](/manual/installation/install) and [configured](/manual/appendix/config/zabbix_proxy) a proxy, it is time to configure it in the Zabbix frontend. #### Configuration Une fois le proxy [installé](/fr/manual/installation/install) et [configuré](/fr/manual/appendix/config/zabbix_proxy), il est temps de le configurer dans l'interface Zabbix. #### Configuration Overall, the process of setting up the notification should feel familiar to those who have set up alerts in Zabbix before. #### Configuration Globalement, le processus de configuration des notifications devrait sembler familier à ceux qui ont déjà configuré des alertes dans Zabbix. #### Configuration parameters For Zabbix server/proxy new configuration parameters have been added for Vault authentication and retrieving database credentials: - VaultToken - Vault authentication token (see Zabbix [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) configuration file for details) - VaultURL - Vault server HTTP\[S\] URL - VaultDBPath - Vault path from where credentials for database will be retrieved by keys 'password' and 'username' (for example: secret/zabbix/database) Zabbix server and Zabbix proxy read the Vault-related configuration parameters from zabbix\_server.conf and zabbix\_proxy.conf upon startup. Zabbix server and Zabbix proxy will additionally read "VAULT\_TOKEN" environment variable once during startup and unset it so that it would not be available through forked scripts; it is an error if both VaultToken and VAULT\_TOKEN contain value. ::: noteclassic Forward slash and colon are reserved symbols. Forward slash can only be used to separate mount point from path (e.g. secret/zabbix where mount point is "secret" and "zabbix" is path) and, in case of Vault macros, colon can only be used to separate path from key. It is possible to URL-encode "/" and ":" if there is need to create mount point with name that is separated by forward slash (e.g. foo/bar/zabbix where mount point is "foo/bar" and path is "zabbix" as "foo%2Fbar/zabbix") and if mount point name or path needs to contain colon. ::: #### Paramètres de configuration Pour le serveur/proxy Zabbix, de nouveaux paramètres de configuration ont été ajoutés pour l'authentification Vault et la récupération des informations d'identification de la base de données : - VaultToken - Jeton d'authentification de coffre-fort (voir le fichier de configuration [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) Zabbix pour plus de détails) - VaultURL - URL HTTP\[S\] du serveur de Vault - VaultDBPath - Chemin de Vault à partir duquel les informations d'identification pour la base de données seront récupérées par les clés 'password' et 'username' (par exemple : secret/zabbix/database) Le serveur Zabbix et le proxy Zabbix lisent les paramètres de configuration liés à Vault depuis zabbix\_server.conf et zabbix\_proxy.conf au démarrage. Le serveur Zabbix et le proxy Zabbix liront en outre la variable d'environnement "VAULT\_TOKEN" une fois au démarrage et la désactiveront afin qu'elle ne soit pas disponible via des scripts externes ou mal intentionnés ; c'est une erreur si VaultToken et VAULT\_TOKEN contiennent une valeur. ::: noteclassic La barre oblique et les deux-points sont des symboles réservés. La barre oblique ne peut être utilisée que pour séparer le point de montage du chemin (par exemple, secret/zabbix où le point de montage est "secret" et "zabbix" est le chemin) et, dans le cas des macros Vault, les deux-points ne peuvent être utilisés que pour séparer le chemin de la clé. Il est possible d'encoder l'URL "/" et ":" s'il est nécessaire de créer un point de montage avec un nom séparé par une barre oblique (par exemple, foo/bar/zabbix où le point de montage est "foo/bar" et le chemin est " zabbix" comme "foo%2Fbar/zabbix") et si le nom ou le chemin du point de montage doit contenir deux-points. ::: #### Configuration Providing you have the HTTP master item configured, you need to create a [dependent item](/manual/config/items/itemtypes/dependent_items) that uses a Prometheus preprocessing step: - Enter general dependent item parameters in the configuration form - Go to the Preprocessing tab - Select a Prometheus preprocessing option (*Prometheus pattern* or *Prometheus to JSON*)  The following parameters are specific to the *Prometheus pattern* preprocessing option: |Parameter|Description|Examples| |--|------|------| |*Pattern*|To define the required data pattern you may use a query language that is similar to Prometheus query language (see [comparison table](#query-language-comparison)), e.g.:<br><metric name> - select by metric name<br>{\_\_name\_\_="<metric name>"} - select by metric name<br>{\_\_name\_\_=\~"<regex>"} - select by metric name matching a regular expression<br>{<label name>="<label value>",...} - select by label name<br>{<label name>=\~"<regex>",...} - select by label name matching a regular expression<br>{\_\_name\_\_=\~".\*"}==<value> - select by metric value<br>Or a combination of the above:<br><metric name>{<label1 name>="<label1 value>",<label2 name>=\~"<regex>",...}==<value><br><br>Label value can be any sequence of UTF-8 characters, but the backslash, double-quote and line feed characters have to be escaped as `\\`, `\"` and `\n` respectively; other characters shall not be escaped.|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Result processing*|Specify whether to return the value, the label or apply the appropriate function (if the pattern matches several lines and the result needs to be aggregated):<br>**value** - return metric value (error if multiple lines matched)<br>**label** - return value of the label specified in the *Label* field (error if multiple metrics are matched)<br>**sum** - return the sum of values<br>**min** - return the minimum value<br>**max** - return the maximum value<br>**avg** - return the average value<br>**count** - return the count of values<br>This field is only available for the *Prometheus pattern* option. |See also examples of using parameters below.| |*Output*|Define label name (optional). In this case the value corresponding to the label name is returned.<br>This field is only available for the *Prometheus pattern* option, if 'Label' is selected in the *Result processing* field.| | **Examples of using parameters** 1. The most common use case is to return the **value**. To return the value of `/var/db` from: > `node_disk_usage_bytes{path="/var/cache"} 2.1766144e+09`<br> > `node_disk_usage_bytes{path="/var/db"} 20480`<br> > `node_disk_usage_bytes{path="/var/dpkg"} 8192`<br> > `node_disk_usage_bytes{path="/var/empty"} 4096` use the following parameters: * *Pattern* - `node_disk_usage_bytes{path="/var/db"}` * *Result processing* - select 'value' 2. You may also be interested in the **average** value of all `node_disk_usage_bytes` parameters: * *Pattern* - `node_disk_usage_bytes` * *Result processing* - select 'avg' 3. While Prometheus supports only numerical data, it is popular to use a workaround that allows to return the relevant textual description as well. This can be accomplished with a filter and specifying the label. So, to return the value of the 'color' label from > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="green"} 1`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="red"} 0`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="yellow"} 0` use the following parameters: * *Pattern* - `elasticsearch_cluster_health_status {cluster="elasticsearch"} == 1` * *Result processing* - select 'label' * *Label* - specify 'color' The filter (based on the numeric value '1') will match the appropriate row, while the label will return the health status description (currently 'green'; but potentially also 'red' or 'yellow'). #### Configuration Si l'élément maître HTTP est configuré, vous devez créer un [élément dépendant](/manual/config/items/itemtypes/dependent_items) qui utilise une étape de prétraitement Prometheus : - Saisissez les paramètres généraux de l'élément dépendant dans le formulaire de configuration - Accédez à l'onglet Prétraitement - Sélectionnez une option de prétraitement Prometheus (*Motif Prometheus* ou *Prometheus vers JSON*)  Les paramètres suivants sont spécifiques à l'option de prétraitement *Motif Prometheus* : |Paramètre|Description|Exemples| |--|------|------| |*Motif*|Pour définir le modèle de données requis, vous pouvez utiliser un langage de requête similaire au langage de requête Prometheus (voir la [table de comparaison](#query-language-comparison)), par exemple :<br>\<nom métrique\> - sélectionner par nom de métrique<br>{\_\_name\_\_="\<nom métrique\>"} - sélectionner par nom de métrique<br>{\_\_name\_\_=\~"\<regex\>"} - sélectionner par nom de métrique correspondant à une expression régulière<br>{\<nom étiquette\>="<\valeur étiquette\>",...} - sélectionner par nom d'étiquette<br>{\<nom étiquette\>=\~"\<regex\>",...} - sélectionner par nom d'étiquette correspondant à une expression régulière<br>{\_\_name\_\_=\~".\*"}==\<valeur\> - sélectionner par valeur de métrique<br>Ou une combinaison des éléments ci-dessus :<br>\<nom métrique\>{\<nom étiquette1\>="\<valeur étiquette1\>",\<nom étiquette2\>=\~"\<regex\>",...}==\<valeur\><br><br>La valeur de l'étiquette peut être n'importe quelle séquence de caractères UTF-8, mais les caractères de barre oblique inverse, de guillemet double et de saut de ligne doivent être échappés sous la forme `\\`, `\"` et `\n` respectivement ; les autres caractères ne doivent pas être échappés .|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Traitement du résultat*|Indiquez s'il faut renvoyer la valeur, l'étiquette ou appliquer la fonction appropriée (si le modèle correspond à plusieurs lignes et que le résultat doit être agrégé) :<br>**valeur** - renvoie la valeur de la métrique (erreur si plusieurs lignes correspondent)<br>**étiquette** - renvoie la valeur du libellé spécifié dans le champ *Étiquette* (erreur si plusieurs métriques correspondent)<br>**sum** - renvoie la somme des valeurs<br >**min** - renvoie la valeur minimale<br>**max** - renvoie la valeur maximale<br>**avg** - renvoie la valeur moyenne<br>**count** - renvoie le nombre de valeurs<br>Ce champ n'est disponible que pour l'option *Motif Prometheus*. |Voir aussi des exemples d'utilisation de paramètres ci-dessous.| |*Sortie*|Définir le nom de l'étiquette (optionnel). Dans ce cas, la valeur correspondant au nom de l'étiquette est renvoyée.<br>Ce champ n'est disponible que pour l'option *Motif Prometheus*, si 'Étiquette' est sélectionné dans le champ *Traitement du résultat*.| | **Exemples d'utilisation de paramètres** 1. Le cas d'usage le plus courant consiste à renvoyer la **valeur**. Pour renvoyer la valeur de `/var/db` à partir de : > `node_disk_usage_bytes{path="/var/cache"} 2.1766144e+09`<br> > `node_disk_usage_bytes{path="/var/db"} 20480`<br> > `node_disk_usage_bytes{path="/var/dpkg"} 8192`<br> > `node_disk_usage_bytes{path="/var/empty"} 4096` utilisez les paramètres suivants : * *Motif* - `node_disk_usage_bytes{path="/var/db"}` * *Traitement du résultat* - sélectionnez 'valeur' 2. Vous pouvez également être intéressé par la valeur **moyenne** de tous les paramètres `node_disk_usage_bytes` : * *Motif* - `node_disk_usage_bytes` * *Traitement du résultat* - sélectionnez 'avg' 3. Alors que Prometheus ne prend en charge que les données numériques, il est courant d'utiliser une solution de contournement qui permet également de renvoyer la description textuelle pertinente. Cela peut être accompli avec un filtre et en spécifiant l'étiquette. Ainsi, pour renvoyer la valeur de l'étiquette 'color' de > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="green"} 1`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="red"} 0`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="yellow"} 0` utilisez les paramètres suivants : * *Motif* - `elasticsearch_cluster_health_status {cluster="elasticsearch"} == 1` * *Traitement du résultat* - sélectionnez 'étiquette' * *Étiquette* - spécifiez 'color' Le filtre (basé sur la valeur numérique '1') correspondra à la ligne appropriée, tandis que l'étiquette renverra la description de l'état de santé (actuellement 'green' ; mais potentiellement aussi 'red' ou 'yellow'). #### Configuration Real-time export of trigger events, item values and trends is configured by specifying a directory for the export files - see the `ExportDir` parameter in server [configuration](/manual/appendix/config/zabbix_server). Two other parameters are available: - `ExportFileSize` may be used to set the maximum allowed size of an individual export file. When a process needs to write to a file it checks the size of the file first. If it exceeds the configured size limit, the file is renamed by appending .old to its name and a new file with the original name is created. ::: noteimportant A file will be created per each process that will write data (i.e. approximately 4-30 files). As the default size per export file is 1G, keeping large export files may drain the disk space fast. ::: - `ExportType` allows to specify which entity types (events, history, trends) will be exported. #### Configuration L'exportation en temps réel des événements déclencheurs, des valeurs des éléments et des tendances est configurée en spécifiant un répertoire pour les fichiers d'exportation - voir le paramètre `ExportDir` dans la [configuration](/manual/appendix/config/zabbix_server) du serveur. Deux autres paramètres sont disponibles : - `ExportFileSize` peut être utilisé pour définir la taille maximale autorisée d'un fichier d'exportation individuel. Lorsqu'un processus doit écrire dans un fichier, il vérifie d'abord la taille du fichier. S'il dépasse la limite de taille configurée, le fichier est renommé en ajoutant .old à son nom et un nouveau fichier avec le nom d'origine est créé. ::: noteimportant Un fichier sera créé pour chaque processus qui écrira des données (c'est-à-dire environ 4 à 30 fichiers). Comme la taille par défaut par le fichier d'exportation est de 1 Go, conserver des fichiers d'exportation volumineux peut épuiser l'espace disque très rapidement. ::: - `ExportType` permet de spécifier quels types d'entités (événements, historique, tendances) seront exportés. ##### Configuration syncer Performance of the configuration syncer has been improved. It is recommended to increase the CacheSize on server/proxy if there is a large amount of templates. It is also recommended to remove unused templates. Note that the default CacheSize on server/proxy has been increased to 32M. ##### Synchroniseur de configuration Les performances du synchroniseur de configuration ont été améliorées. Il est recommandé d'augmenter le CacheSize sur le serveur/proxy s'il y a une grande quantité de modèles. Il est également recommandé de supprimer les modèles inutilisés. Notez que le CacheSize par défaut sur le serveur/proxy a été augmenté à 32M. #### Configuration Tags can be entered in a dedicated tab, for example, in trigger configuration:  #### Configuration Les tags peuvent être saisies dans un onglet dédié, par exemple dans la configuration du déclencheur :  #### Configuration The **Item** tab contains general item attributes.  All mandatory input fields are marked with a red asterisk. |Parameter|Description| |---------|-----------| |*Name*|Item name.| |*Type*|Item type. See individual [item type](itemtypes) sections.| |*Key*|Item key (up to 2048 characters).<br>The supported [item keys](itemtypes) can be found in individual item type sections.<br>The key must be unique within a single host.<br>If key type is 'Zabbix agent', 'Zabbix agent (active)' or 'Simple check', the key value must be supported by Zabbix agent or Zabbix server.<br>See also: the correct [key format](/manual/config/items/item/key).| |*Type of information*|Type of data as stored in the database after performing conversions, if any.<br>**Numeric (unsigned)** - 64bit unsigned integer<br>**Numeric (float)** - 64bit floating point number<br>This type will allow precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of [PostgreSQL 11 and earlier versions](/manual/installation/known_issues#floating_point_values)).<br>Receiving values in scientific notation is also supported. E.g. 1.23E+7, 1e308, 1.1E-4.<br>**Character** - short text data<br>**Log** - long text data with optional log related properties (timestamp, source, severity, logeventid)<br>**Text** - long text data. See also [text data limits](#text-data-limits).<br>For item keys that return data only in one specific format, matching type of information is selected automatically.| |*Host interface*|Select the host interface. This field is available when editing an item on the host level.| |*Units*|If a unit symbol is set, Zabbix will add post processing to the received value and display it with the set unit postfix.<br>By default, if the raw value exceeds 1000, it is divided by 1000 and displayed accordingly. For example, if you set *bps* and receive a value of 881764, it will be displayed as 881.76 Kbps.<br>The [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) memory standard is used for processing **B** (byte), **Bps** (bytes per second) units, which are divided by 1024. Thus, if units are set to **B** or **Bps** Zabbix will display:<br>1 as 1B/1Bps<br>1024 as 1KB/1KBps<br>1536 as 1.5KB/1.5KBps<br>Special processing is used if the following time-related units are used:<br>**unixtime** - translated to "yyyy.mm.dd hh:mm:ss". To translate correctly, the received value must be a *Numeric (unsigned)* type of information.<br>**uptime** - translated to "hh:mm:ss" or "N days, hh:mm:ss"<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:56:04"<br>**s** - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"<br>Only 3 upper major units are shown, like "1m 15d 5h" or "2h 4m 46s". If there are no days to display, only two levels are displayed - "1m 5h" (no minutes, seconds or milliseconds are shown). Will be translated to "< 1 ms" if the value is less than 0.001.<br>*Note* that if a unit is prefixed with `!`, then no unit prefixes/processing is applied to item values. See [unit conversion](#unit_conversion).| |*Update interval*|Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>*Note*: The update interval can only be set to '0' if custom intervals exist with a non-zero value. If set to '0', and a custom interval (flexible or scheduled) exists with a non-zero value, the item will be polled during the custom interval duration.<br>*Note* that the first item poll after the item became active or after update interval change might occur earlier than the configured value.<br>An existing passive item can be polled for value immediately by pushing the *Execute now* [button](#form_buttons).| |*Custom intervals*|You can create custom rules for checking the item:<br>**Flexible** - create an exception to the *Update interval* (interval with different frequency)<br>**Scheduling** - create a custom polling schedule.<br>For detailed information see [Custom intervals](/manual/config/items/item/custom_intervals).<br>[Time suffixes](/manual/appendix/suffixes) are supported in the *Interval* field, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Scheduling is supported since Zabbix 3.0.0.<br>*Note*: Not available for Zabbix agent active items.| |*History storage period*|Select either:<br>**Do not keep history** - item history is not stored. Useful for master items if only dependent items need to keep history.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping detailed history in the database (1 hour to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 2h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green  info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (1d)*.<br>It is recommended to keep the recorded values for the smallest possible time to reduce the size of value history in the database. Instead of keeping a long history of values, you can keep longer data of trends.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Trend storage period*|Select either:<br>**Do not keep trends** - trends are not stored.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping aggregated (hourly min, max, avg, count) history in the database (1 day to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 24h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green  info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (7d)*.<br>*Note:* Keeping trends is not available for non-numeric data - character, log and text.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Value mapping*|Apply value mapping to this item. [Value mapping](/manual/config/items/mapping) does not change received values, it is for displaying data only.<br>It works with *Numeric(unsigned)*, *Numeric(float)* and *Character* items.<br>For example, "Windows service states".| |*Log time format*|Available for items of type **Log** only. Supported placeholders:<br>\* **y**: *Year (1970-2038)*<br>\* **M**: *Month (01-12)*<br>\* **d**: *Day (01-31)*<br>\* **h**: *Hour (00-23)*<br>\* **m**: *Minute (00-59)*<br>\* **s**: *Second (00-59)*<br>If left blank the timestamp will not be parsed.<br>For example, consider the following line from the Zabbix agent log file:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>It begins with six character positions for PID, followed by date, time, and the rest of the line.<br>Log time format for this line would be "pppppp:yyyyMMdd:hhmmss".<br>Note that "p" and ":" chars are just placeholders and can be anything but "yMdhms".| |*Populates host inventory field*|You can select a host inventory field that the value of item will populate. This will work if automatic [inventory](/manual/config/hosts/inventory) population is enabled for the host.<br>This field is not available if *Type of information* is set to 'Log'.| |*Description*|Enter an item description.| |*Enabled*|Mark the checkbox to enable the item so it will be processed.| |*Latest data*|Click on the link to view the latest data for the item.<br>This link is only available when editing an already existing item.| ::: noteclassic Item type specific fields are described on [corresponding pages](itemtypes). ::: ::: noteclassic When editing an existing [template](/manual/config/templates) level item on a host level, a number of fields are read-only. You can use the link in the form header and go to the template level and edit them there, keeping in mind that the changes on a template level will change the item for all hosts that the template is linked to. ::: The **Tags** tab allows to define item-level [tags](/manual/config/tagging).  #### Configuration L'onglet **Elément** contient les attributs généraux de l\'élément.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. |Paramètre|Description| |---------|-----------| |*Name*|Nom de l'élément.| |*Type*|Type d'élément. Voir les sections sur les [types d'éléments].| |*Key*|Clé d'élément (jusqu'à 2 048 caractères). <br>Les [clés d'élément](types d'élément) prises en charge peuvent être trouvées dans les sections sur les types d'éléments. <br>La clé doit être unique au sein d'un même hôte. <br>Si le type de clé est 'Agent Zabbix', 'Agent Zabbix (actif)' ou 'Simple check', la valeur de la clé doit être prise en charge par l'agent Zabbix ou le serveur Zabbix. <br>Voir également : [format de clé](/manual/config/items/élément/clé) correct.| |*Type of information*|Type de données telles qu'elles sont stockées dans la base de données après avoir effectué les conversions, le cas échéant. <br>**Numérique (non signé)** - Entier non signé 64 bits <br>**Numérique (flottant)** - Nombre à virgule flottante 64 bits <br>Ceci permettra une précision d'environ 15 chiffres et une plage d'environ -1,79E+308 à 1,79E+308 (à l'exception de [PostgreSQL 11 et versions antérieures](/manual/installation/known_issues#floating_point_values)).<br>La gestion des valeurs en notation scientifique est également prise en charge. Par exemple. 1.23E+7, 1e308, 1.1E-4.<br>**Caractère** - données textuelles courtes<br>**Log** - données textuelles longues avec des propriétés facultatives liées au log (horodatage, source, gravité, logeventid) <br>**Texte** - données textuelles longues. Voir aussi [limites de données textuelles](#text-data-limits).<br>Pour les clés d'élément qui ne renvoient des données que dans un format spécifique, le type d'informations correspondant est sélectionné automatiquement.| |*Host interface*|Sélection de l\'interface de l\'hôte. Ce champ est disponible lors de la modification d'un élément au niveau de l\'hôte.| |*Units*|Si un symbole d'unité est défini, Zabbix ajoutera un post-traitement à la valeur reçue et l\'affichera avec le suffixe d\'unité défini.<br>Par défaut, si la valeur brute dépasse 1 000, elle est divisée par 1 000 et affichée en conséquence. Par exemple, si vous définissez *bps* et recevez une valeur de 881764, elle sera affichée sous la forme 881,76 Kbps.<br>La norme de mémoire [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) est utilisée pour traiter les unités **B** (octet), **Bps** (octets par seconde), qui sont divisées par 1024. Ainsi, si les unités sont définies sur **B** ou **Bps**, Zabbix affichera : <br>1 comme 1B/1Bps<br>1024 comme 1KB/1KBps<br>1536 comme 1.5KB/1.5KBps<br>Un traitement spécial est utilisé si les unités temporelles suivantes sont utilisées :<br>**unixtime** - traduit par "aaaa.mm.jj hh:mm:ss". Pour traduire correctement, la valeur reçue doit être un type d'information *Numérique (non signé)*.<br>**uptime** - traduit en "hh:mm:ss" ou "N days, hh:mm:ss"<br>Par exemple, si vous recevez la valeur comme 881764 (secondes), elle sera affichée comme "10 jours, 04:56:04"<br>**s** - traduit par "aaa mmm jjhhh mmm sss ms " ; le paramètre est traité comme un nombre de secondes.<br>Par exemple, si vous recevez la valeur comme 881764 (secondes), elle sera affichée comme "10d 4h 56m"<br>Seules 3 unités majeures supérieures sont affichées, comme "1m 15d 5h" ou "2h 4m 46s". S'il n'y a pas de jours à afficher, seuls deux niveaux sont affichés - "1m 5h" (aucune minute, seconde ou milliseconde n'est affichée). Sera traduit en "< 1 ms" si la valeur est inférieure à 0,001.<br>*Notez* que si une unité est préfixée par ` !`, aucun préfixe/traitement d'unité n'est appliqué aux valeurs d'élément. Voir [conversion d'unité](#unit_conversion).| |*Update interval*|Récupère une nouvelle valeur pour cet élément toutes les N secondes. L'intervalle de mise à jour maximal autorisé est de 86 400 secondes (1 jour).<br>[Les suffixes temporels](/manual/appendix/suffixes) sont pris en charge, par ex. 30s, 1m, 2h, 1d.<br>[Les macros utilisateur](/manual/config/macros/user_macros) sont supportées.<br>Une seule macro doit remplir tout le champ. Les macros multiples dans un champ ou les macros mélangées avec du texte ne sont pas prises en charge.<br>*Remarque* : L'intervalle de mise à jour ne peut être défini sur "0" que s'il existe des intervalles personnalisés avec une valeur différente de zéro. S'il est défini sur "0" et qu'un intervalle personnalisé (flexible ou programmé) existe avec une valeur différente de zéro, l'élément sera interrogé pendant la durée de l'intervalle personnalisé.<br>*Notez* que le premier élément interrogé après que l'élément soit devenu actif ou après un changement d'intervalle de mise à jour peut se produire plus tôt que la valeur configurée.<br>Un élément passif existant peut être interrogé pour une valeur immédiatement en appuyant sur le bouton *Exécuter maintenant* (#form_buttons).| |*Custom intervals*|Vous pouvez créer des règles personnalisées pour vérifier l'élément :<br>**Flexible** - créer une exception à l'*intervalle de mise à jour* (intervalle avec une fréquence différente)<br>**Planification** - créer un calendrier d'interrogation personnalisé.<br>Pour des informations détaillées, voir [Intervalles personnalisés](/manual/config/items/item/custom_intervals).<br>[Les suffixes de temps](/manual/appendix/suffixes) sont pris en charge dans le champ *Interval*, par ex. 30s, 1m, 2h, 1d.<br>[Les macros utilisateur](/manual/config/macros/user_macros) sont supportées.<br>Une seule macro doit remplir tout le champ. Les macros multiples dans un champ ou les macros mélangées avec du texte ne sont pas prises en charge.<br>La planification est prise en charge depuis Zabbix 3.0.0.<br>*Remarque* : Non disponible pour les éléments actifs de l'agent Zabbix.| |*History storage period*|Sélectionnez :<br>**Ne pas conserver l'historique** : l'historique des éléments n'est pas stocké. Utile pour les éléments principaux si seuls les éléments dépendants doivent conserver l'historique.<br>Ce paramètre ne peut pas être remplacé dans les [paramètres](/manual/web_interface/frontend_sections/administration/general#housekeeper) de la procédure de nettoyage.<br>**Période de stockage** - spécifiez la durée de conservation de l'historique détaillé dans la base de données (1 heure à 25 ans). Les données plus anciennes seront supprimées par la procédure de nettoyage. Stocké en secondes.<br>[Les suffixes temporels](/manual/appendix/suffixes) sont pris en charge, par ex. 2h, 1j. [Les macros utilisateur](/manual/config/macros/user_macros) sont prises en charge.<br>La valeur *Période de stockage* peut être remplacée globalement dans *Administration → Général → [Nettoyage](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>Si un paramètre prioritaire global existe, une icône d'information verte  s'affiche. Si vous placez votre souris dessus, un message d\'avertissement s\'affiche, par ex. *Remplacé par les paramètres globaux de nettoyage (1d)*.<br> Il est recommandé de conserver les valeurs enregistrées le moins longtemps possible afin de réduire la taille de l'historique des valeurs dans la base de données. Au lieu de conserver un long historique des valeurs, vous pouvez conserver des données plus longues avec les tendances.<br>Voir également : [Historique et tendances](/manual/config/items/history_and_trends).| |*Trend storage period*|Sélectionnez soit :<br>**Ne pas conserver les tendances** - les tendances ne sont pas stockées.<br>Ce paramètre ne peut pas être remplacé dans les [paramètres](/manual/web_interface/frontend_sections/administration/general#housekeeper) de la procédure de nettoyage.<br>**Période de stockage** : spécifiez la durée de conservation de l'historique agrégé (min, max, moy, comptage) dans la base de données (1 jour à 25 ans). Les données plus anciennes seront supprimées par la procédure de nettoyage. Stocké en secondes.<br>[Les suffixes temporels](/manual/appendix/suffixes) sont pris en charge, par ex. 24h, 1j. [Les macros utilisateur](/manual/config/macros/user_macros) sont prises en charge.<br>La valeur *Période de stockage* peut être remplacée globalement dans *Administration → Général → [Nettoyage](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>Si un paramètre prioritaire global existe, une icône d'information verte  s'affiche. Si vous placez votre souris dessus, un message d'avertissement s'affiche, par ex. *Remplacé par les paramètres généraux du nettoyage (7d)*.<br> *Remarque :* La conservation des tendances n'est pas disponible pour les données non numériques - caractères, log et texte. <br> Voir aussi [Historique et tendances](/manual/config/items/history_and_trends).| |*Value mapping*|Appliquez le mappage de valeur à cet élément. [Le mappage de valeur](/manual/config/items/mapping) ne modifie pas les valeurs reçues, il sert uniquement à afficher les données.<br>Il fonctionne avec les éléments *Numérique (non signé)*, *Numérique (flottant)* et *Caractère*.<br>Par exemple, "États du service Windows".| |*Log time format*|Disponible uniquement pour les éléments de type **Log**. Espaces réservés pris en charge :<br>\* **y** : *Année (1970-2038)*<br>\* **M** : *Mois (01-12)*<br>\* **d** : *Jour (01-31)*<br>\* **h** : *Heure (00-23)*<br>\* **m** : *Minute (00-59)*<br >\* **s** : *Seconde (00-59)*<br>Si laissé vide, l'horodatage ne sera pas analysé.<br>Par exemple, considérez la ligne suivante du fichier de log de l'agent Zabbix :<br> " 23480:20100328:154718.045 L'agent Zabbix a démarré. Zabbix 1.8.2 (révision 11211)."<br>Il commence par six positions de caractères pour le PID, suivis de la date, de l'heure et du reste de la ligne.<br>Le format de cette ligne serait "pppppp:yyyyMMdd:hhmmss".<br>Notez que les caractères "p" et ":" ne sont que des espaces réservés et peuvent être autre chose que "yMdhms".| |*Populates host inventory field*|Vous pouvez sélectionner un champ d'inventaire d\'hôte que la valeur de l'élément remplira. Cela fonctionnera si le remplissage automatique de l'[inventaire](/manual/config/hosts/inventory) est activé pour l'hôte.<br>Ce champ n'est pas disponible si *Type d'information* est défini sur 'Log'.| |*Description*|Entrez une description de l\'élément.| |*Enabled*|Cochez la case pour activer l\'élément afin qu'il soit traité.| |*Latest data*|Cliquez sur le lien pour afficher les dernières données de l'élément.<br>Ce lien n'est disponible que lors de la modification d'un élément déjà existant.| ::: noteclassic Les champs spécifiques aux types d'éléments sont décrits dans les [pages correspondantes] (types d'éléments). ::: ::: noteclassic Lors de la modification d'un élément de niveau [modèle](/manual/config/templates) existant au niveau de l'hôte, un certain nombre de champs sont en lecture seule. Vous pouvez utiliser le lien dans l'en-tête du formulaire et accéder au niveau du modèle et les y modifier, en gardant à l'esprit que les modifications au niveau du modèle modifieront l'élément pour tous les hôtes auxquels le modèle est lié. ::: L'onglet **Tags** permet de définir des [tags](/manual/config/tagging) au niveau de l'élément.  #### Configuration The low-level discovery rule should be created as a [dependent item](/manual/config/items/itemtypes/dependent_items) to the HTTP master item that collects Prometheus data. #### Configuration La règle de découverte de bas niveau doit être créée en tant qu'[élément dépendant](/manual/config/items/itemtypes/dependent_items) de l'élément principal HTTP qui collecte les données Prometheus. #### Configuration The options for aggregation are available in data set settings when configuring a [graph widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph).  You may pick the aggregation function and the time interval. As the data set may comprise several items, there is also another option allowing to show aggregated data for each item separately or for all data set items as one aggregated value. #### Configuration Les options d'agrégation sont disponibles dans les paramètres de l'ensemble de données lors de la configuration d'un [widget graphique](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph).  Vous pouvez choisir la fonction d'agrégation et l'intervalle de temps. Comme l'ensemble de données peut comprendre plusieurs éléments, il existe également une autre option permettant d'afficher les données agrégées pour chaque élément séparément ou pour tous les éléments de l'ensemble de données sous la forme d'une valeur agrégée. ### Configuration The Zabbix API allows you to manage the configuration of your monitoring system. ### Configuration L'API Zabbix vous permet de gérer la configuration de votre système de supervision. [API Configuration](/manual/api/reference/configuration) #### Configuration Those remote commands that are executed on Zabbix agent (custom scripts) must be first enabled in the agent [configuration](/manual/appendix/config/zabbix_agentd). Make sure that the AllowKey=system.run[<command>,\*] parameter is added for each allowed command in agent configuration to allow specific command with nowait mode. Restart agent daemon if changing this parameter. ::: noteimportant Remote commands do not work with active Zabbix agents. ::: Then, when configuring a new action in *Configuration → Actions*: - Define the appropriate conditions. In this example, set that the action is activated upon any disaster problems with one of Apache applications:  - In the *[Operations](/manual/config/notifications/action/operation#configuring_an_operation)* tab, click on Add in the Operations/Recovery operations/Update operations block - From the Operation dropdown field select one of the predefined scripts  - Select the target list for the script #### Configuration Les commandes à distance exécutées sur l'agent Zabbix (scripts personnalisés) doivent d'abord être activées dans le fichier de [configuration de l'agent](/manual/appendix/config/zabbix_agentd). Assurez-vous que le paramètre AllowKey=system.run[<command>,\*] est ajouté pour chaque commande autorisée dans la configuration de l'agent pour autoriser une commande spécifique avec le mode nowait. Redémarrez le démon de l'agent si vous modifiez ce paramètre. ::: noteimportant Les commandes à distance ne fonctionnent pas avec les agents Zabbix actifs. ::: Ensuite, lors de la configuration d’une nouvelle action dans *Configuration → Actions* : - Définir les conditions appropriées. Dans cet exemple, indiquez que l'action est activée en cas de problème au niveau désastre avec l'une des applications Apache :  - Dans l'onglet *[Opérations](/manual/config/notifications/action/operation#configuring_an_operation)*, cliquez sur Ajouter dans le bloc Opérations/Opérations de récupération/Opérations de mise à jour - Dans le champ déroulant Opération, sélectionnez l'un des scripts prédéfinis  - Sélectionnez la liste cible pour le script #### Configuration To add the widget, select *Geomap* as type.  #### Configuration Pour ajouter le widget, sélectionnez *Geocarte* comme type.  #### Configuration To assign triggers as link indicators, do the following: - select a map element - click on *Edit* in the *Links* section for the appropriate link - click on *Add* in the *Link indicators* block and select one or more triggers {width="600"} All mandatory input fields are marked with a red asterisk. Added triggers can be seen in the *Link indicators* list. You can set the link type and color for each trigger directly from the list. When done, click on *Apply*, close the form and click on *Update* to save the map changes. #### Configuration Pour affecter des déclencheurs en tant qu'indicateurs de lien, procédez comme suit : - sélectionnez un élément de la carte - cliquez sur *Modifier* dans la section *Liens* pour le lien approprié - cliquez sur *Ajouter* dans le bloc *Indicateurs de liens* et sélectionnez un ou plusieurs déclencheurs {width="600"} Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les déclencheurs ajoutés peuvent être vus dans la liste *Indicateurs de lien*. Vous pouvez définir le type de lien et la couleur pour chaque déclencheur directement à partir de la liste. Une fois terminé, cliquez sur *Appliquer*, fermez le formulaire et cliquez sur *Mettre à jour* pour enregistrer les modifications de la carte. #### Configuration To be able to send and receive notifications from Zabbix you have to: - [define the media](/manual/config/notifications/media) to send a message to ::: notewarning The default trigger severity ('Not classified') **must be** checked in user media [configuration](/manual/config/notifications/media/email#user_media) if you want to receive notifications for non-trigger events such as discovery, active agent autoregistration or internal evens. ::: - [configure an action operation](/manual/config/notifications/action/operation) that sends a message to one of the defined media ::: noteimportant Zabbix sends notifications only to those users that have at least 'read' permissions to the host that generated the event. At least one host of a trigger expression must be accessible. ::: You can configure custom scenarios for sending messages using [escalations](/manual/config/notifications/action/escalations). To successfully receive and read e-mails from Zabbix, e-mail servers/clients must support standard 'SMTP/MIME e-mail' format since Zabbix sends UTF-8 data (If the subject contains ASCII characters only, it is not UTF-8 encoded.). The subject and the body of the message are base64-encoded to follow 'SMTP/MIME e-mail' format standard. Message limit after all macros expansion is the same as message limit for [Remote commands](/manual/config/notifications/action/operation/remote_command). #### Configuration Pour pouvoir envoyer et recevoir des notifications de Zabbix, vous devez : - [définir le média](/manual/config/notifications/media) auquel envoyer un message ::: notewarning La sévérité du déclencheur par défaut ('Non classé') **doit être** vérifiée dans la [configuration](/manual/config/notifications/media/email#user_media) du média de l'utilisateur si vous souhaitez recevoir des notifications d'événements non déclencheur tels que la découverte, l'enregistrement automatique de l'agent actif ou les événements internes. ::: - [configurer une opération d'action](/manual/config/notifications/action/operation) qui envoie un message à l'un des médias définis ::: noteimportant Zabbix envoie des notifications uniquement aux utilisateurs disposant d'au moins des autorisations de 'lecture' sur l'hôte ayant généré l'événement. Au moins un hôte d'une expression de déclencheur doit être accessible. ::: Vous pouvez configurer des scénarios personnalisés pour l'envoi de messages à l'aide de l'[escalade](/manual/config/notifications/action/escalations). Pour recevoir correctement et lire les mails de Zabbix, les serveurs/clients de messagerie doivent prendre en charge le format standard de courrier électronique 'SMTP/MIME', car Zabbix envoie des données UTF-8 (si le sujet contient uniquement des caractères ASCII, ce n'est pas encodé en UTF-8.). Le sujet et le corps du message sont codés en base64 pour suivre le format standard 'e-mail SMTP/MIME'. La limite de messages après le développement de toutes les macros est identique à la limite de messages pour les [commandes à distances](/manual/config/notifications/action/operation/remote_command). #### Configuration To configure a CSV to JSON preprocessing step: - Go to the Preprocessing tab in [item](/manual/config/items/preprocessing)/[discovery rule](/manual/discovery/low_level_discovery#preprocessing) configuration - Click on *Add* - Select the *CSV to JSON* option {width="600"} The first parameter allows to set a custom delimiter. Note that if the first line of CSV input starts with "Sep=" and is followed by a single UTF-8 character then that character will be used as the delimiter in case the first parameter is not set. If the first parameter is not set and a delimiter is not retrieved from the "Sep=" line, then a comma is used as a separator. The second optional parameter allows to set a quotation symbol. If the *With header row* checkbox is marked, the header line values will be interpreted as column names (see [Header processing](#csv_header_processing) for more information). If the *Custom on fail* checkbox is marked, the item will not become unsupported in case of a failed preprocessing step. Additionally custom error handling options may be set: discard the value, set a specified value or set a specified error message. #### Configuration Pour configurer une étape de prétraitement CSV vers JSON : - Accédez à l'onglet Prétraitement dans la configuration de l'[élément](/manual/config/items/preprocessing)/la [règle de découverte](/manual/discovery/low_level_discovery#preprocessing) - Cliquez sur *Ajouter* - Sélectionnez l'option *CSV vers JSON* {width="600"} Le premier paramètre permet de définir un délimiteur personnalisé. Notez que si la première ligne de l'entrée CSV commence par "Sep=" et est suivie d'un seul caractère UTF-8, ce caractère sera utilisé comme délimiteur si le premier paramètre n'est pas défini. Si le premier paramètre n'est pas défini et qu'un délimiteur n'est pas extrait de la ligne "Sep=", une virgule est utilisée comme séparateur. Le deuxième paramètre optionnel permet de définir un symbole de citation. Si la case *Avec ligne d'en-tête* est cochée, les valeurs de la ligne d'en-tête seront interprétées comme des noms de colonne (voir [Traitement des en-têtes](#csv_header_processing) pour plus d'informations). Si la case *Personnalisé en cas d'échec* est cochée, l'élément ne deviendra pas non pris en charge en cas d'échec d'une étape de prétraitement. De plus, des options personnalisées de gestion des erreurs peuvent être définies : ignorer la valeur, définir une valeur spécifiée ou définir un message d'erreur spécifié. #### Configuration To configure a user group: - Go to *Administration → User groups* - Click on *Create user group* (or on the group name to edit an existing group) - Edit group attributes in the form The **User group** tab contains general group attributes:  All mandatory input fields are marked with a red asterisk. |Parameter|Description| |--|--------| |*Group name*|Unique group name.| |*Users*|To add users to the group start typing the name of an existing user. When the dropdown with matching user names appears, scroll down to select.<br>Alternatively you may click the *Select* button to select users in a popup.| |*Frontend access*|How the users of the group are authenticated.<br>**System default** - use default authentication method (set [globally](/manual/web_interface/frontend_sections/administration/authentication))<br>**Internal** - use Zabbix internal authentication (even if LDAP authentication is used globally).<br>Ignored if HTTP authentication is the global default.<br>**LDAP** - use LDAP authentication (even if internal authentication is used globally).<br>Ignored if HTTP authentication is the global default.<br>**Disabled** - access to Zabbix frontend is forbidden for this group| |*Enabled*|Status of user group and group members.<br>*Checked* - user group and users are enabled<br>*Unchecked* - user group and users are disabled| |*Debug mode*|Mark this checkbox to activate [debug mode](/manual/web_interface/debug_mode) for the users.| The **Permissions** tab allows you to specify user group access to host group (and thereby host) data: {width="600"} Current permissions to host groups are displayed in the *Permissions* block. If current permissions of the host group are inherited by all nested host groups, that is indicated by the *including subgroups* text in the parenthesis after the host group name. You may change the level of access to a host group: - **Read-write** - read-write access to a host group; - **Read** - read-only access to a host group; - **Deny** - access to a host group denied; - **None** - no permissions are set. Use the selection field below to select host groups and the level of access to them (note that selecting *None* will remove host group from the list if the group is already in the list). If you wish to include nested host groups, mark the *Include subgroups* checkbox. This field is auto-complete so starting to type the name of a host group will offer a dropdown of matching groups. If you wish to see all host groups, click on *Select*. Note that it is possible for Super Admin users in host group [configuration](/manual/config/hosts/host#creating_a_host_group) to enforce the same level of permissions to the nested host groups as the parent host group. The **Tag filter** tab allows you to set tag-based permissions for user groups to see problems filtered by tag name and its value:  To select a host group to apply a tag filter for, click *Select* to get the complete list of existing host groups or start to type the name of a host group to get a dropdown of matching groups. If you want to apply tag filters to nested host groups, mark the *Include subgroups* checkbox. Tag filter allows to separate the access to host group from the possibility to see problems. For example, if a database administrator needs to see only "MySQL" database problems, it is required to create a user group for database administrators first, than specify "Service" tag name and "MySQL" value.  If "Service" tag name is specified and value field is left blank, corresponding user group will see all problems for selected host group with tag name "Service". If both tag name and value fields are left blank but host group selected, corresponding user group will see all problems for selected host group. Make sure a tag name and tag value are correctly specified otherwise a corresponding user group will not see any problems. Let's review an example when a user is a member of several user groups selected. Filtering in this case will use OR condition for tags. | | | | | | | | |---|---|---|---|---|---|---| |**User group A**|<|<|**User group B**|<|<|**Visible result for a user (member) of both groups**| |*Tag filter*|<|<|<|<|<|^| |*Host group*|*Tag name*|*Tag value*|*Host group*|*Tag name*|*Tag value*|^| |Templates/Databases|Service|MySQL|Templates/Databases|Service|Oracle|Service: MySQL or Oracle problems visible| |Templates/Databases|*blank*|*blank*|Templates/Databases|Service|Oracle|All problems visible| |*not selected*|*blank*|*blank*|Templates/Databases|Service|Oracle|<Service:Oracle> problems visible| ::: noteimportant Adding a filter (for example, all tags in a certain host group "Templates/Databases") results in not being able to see the problems of other host groups. ::: #### Configuration Pour configurer un groupe d'utilisateurs : - Allez dans *Administration → Groupes d'utilisateurs* - Cliquez sur *Créer un groupe d'utilisateurs* (ou sur le nom du groupe pour modifier un groupe existant) - Modifiez les attributs de groupe dans le formulaire L'onglet **Groupe d'utilisateurs** contient les attributs généraux du groupe :  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. |Paramètre|Description| |--|--------| |*Nom du groupe*|Nom de groupe unique.| |*Utilisateurs*|Pour ajouter des utilisateurs au groupe, commencez à taper le nom d'un utilisateur existant. Lorsque la liste déroulante avec les noms d'utilisateur correspondants apparaît, faites défiler vers le bas pour sélectionner.<br>Vous pouvez également cliquer sur le bouton *Sélectionner* pour sélectionner les utilisateurs dans une fenêtre contextuelle.| |*Accès à l'interface*|Comment les utilisateurs du groupe sont authentifiés.<br>**Valeur système par défaut** - utiliser la méthode d'authentification par défaut (définie [globalement](/manual/web_interface/frontend_sections/administration/authentication))<br> **Interne** - utilise l'authentification interne Zabbix (même si l'authentification LDAP est utilisée globalement).<br>Ignoré si l'authentification HTTP est la valeur par défaut globale.<br>**LDAP** - utilise l'authentification LDAP (même si l'authentification interne est utilisé globalement).<br>Ignoré si l'authentification HTTP est la valeur globale par défaut.<br>**Désactivé** - l'accès à l'interface Zabbix est interdit pour ce groupe| |*Activé*|Statut du groupe d'utilisateurs et des membres du groupe.<br>*Coché* - le groupe d'utilisateurs et les utilisateurs sont activés<br>*Décoché* - le groupe d'utilisateurs et les utilisateurs sont désactivés| |*Mode debug*|Cochez cette case pour activer le [mode debug](/manual/web_interface/debug_mode) pour les utilisateurs.| L'onglet **Autorisations** vous permet de spécifier l'accès du groupe d'utilisateurs aux données du groupe d'hôtes (et donc de l'hôte) : {width="600"} Les autorisations actuelles des groupes d'hôtes sont affichées dans le bloc *Permissions*. Si les autorisations actuelles du groupe d'hôtes sont héritées par tous les groupes d'hôtes imbriqués, cela est indiqué par le texte *incluant les sous-groupes* entre parenthèses après le nom du groupe d'hôtes. Vous pouvez modifier le niveau d'accès à un groupe d'hôtes : - **Lecture-écriture** : accès en lecture-écriture à un groupe d'hôtes ; - **Lecture** - accès en lecture seule à un groupe d'hôtes ; - **Interdit** - accès à un groupe d'hôtes refusé ; - **Aucun** : aucune autorisation n'est définie. Utilisez le champ de sélection ci-dessous pour sélectionner les groupes d'hôtes et leur niveau d'accès (notez que la sélection de *Aucun* supprimera le groupe d'hôtes de la liste si le groupe est déjà dans la liste). Si vous souhaitez inclure des groupes d'hôtes imbriqués, cochez la case *Inclure les sous-groupes*. Ce champ est auto-complété, donc commencer à taper le nom d'un groupe d'hôtes offrira une liste déroulante des groupes correspondants. Si vous souhaitez voir tous les groupes d'hôtes, cliquez sur *Sélectionner*. Notez qu'il est possible pour les utilisateurs super administrateurs dans la [configuration](/manual/config/hosts/host#creating_a_host_group) du groupe d'hôtes d'appliquer le même niveau d'autorisations aux groupes d'hôtes imbriqués que le groupe d'hôtes parent. L'onglet **Filtre de tag de problème** vous permet de définir des autorisations basées sur les tags pour que les groupes d'utilisateurs voient les problèmes filtrés par nom de tag et sa valeur :  Pour sélectionner un groupe d'hôtes auquel appliquer un filtre de tag, cliquez sur *Sélectionner* pour obtenir la liste complète des groupes d'hôtes existants ou commencez à saisir le nom d'un groupe d'hôtes pour obtenir une liste déroulante des groupes correspondants. Si vous souhaitez appliquer des filtres de tag aux groupes d'hôtes imbriqués, cochez la case *Inclure les sous-groupes*. Le filtre de tag permet de séparer l'accès au groupe d'hôtes de la possibilité de voir les problèmes. Par exemple, si un administrateur de base de données n'a besoin de voir que les problèmes de base de données "MySQL", il doit d'abord créer un groupe d'utilisateurs pour les administrateurs de base de données, puis spécifier le nom de la tag "Service" et la valeur "MySQL".  Si le nom de tag "Service" est spécifié et que le champ de valeur est laissé vide, le groupe d'utilisateurs correspondant verra tous les problèmes du groupe d'hôtes sélectionné avec le nom de tag "Service". Si les champs de nom de tag et de valeur sont laissés vides mais que le groupe d'hôtes est sélectionné, le groupe d'utilisateurs correspondant verra tous les problèmes du groupe d'hôtes sélectionné. Assurez-vous qu'un nom de tag et une valeur de tag sont correctement spécifiés, sinon un groupe d'utilisateurs correspondant ne verra aucun problème. Reprenons un exemple lorsqu'un utilisateur est membre de plusieurs groupes d'utilisateurs sélectionnés. Dans ce cas, le filtrage utilisera la condition OU pour les tags. | | | | | | | | |---|---|---|---|---|---|---| |**Groupe d'utilisateurs A**|<|<|**Groupe d'utilisateurs B**|<|<|**Résultat visible pour un utilisateur (membre) des deux groupes**| |*Filtre de tag*|<|<|<|<|<|^| |*Groupe d'hôtes*|*Nom de tag*|*Valeur de tag*|*Groupe d'hôtes*|*Nom de tag*|*Valeur de tag*|^| |Templates/Databases|Service|MySQL|Templates/Databases|Service|Oracle|Problèmes visibles Service: MySQL ou Oracle| |Templates/Databases|*Vide*|*Vide*|Templates/Databases|Service|Oracle|Tous les problèmes visibles| |*not selected*|*Vide*|*Vide*|Templates/Databases|Service|Oracle|Problèmes visibles \<Service:Oracle\>| ::: noteimportant L'ajout d'un filtre (par exemple, tous les tags d'un certain groupe d'hôtes "Templates/Databases") entraîne l'impossibilité de voir les problèmes des autres groupes d'hôtes. ::: #### Configuration To configure custom alertscripts as the media type: - Go to *Administration → Media types* - Click on *Create media type* The **Media type** tab contains general media type attributes:  All mandatory input fields are marked with a red asterisk. The following parameters are specific for the script media type: |Parameter|Description| |--|--------| |*Script name*|Enter the name of the script.| |*Script parameters*|Add command-line parameters to the script.<br>{ALERT.SENDTO}, {ALERT.SUBJECT} and {ALERT.MESSAGE} [macros](/manual/appendix/macros/supported_by_location) are supported in script parameters.<br>Customizing script parameters is supported since Zabbix 3.0.| See [common media type parameters](/manual/config/notifications/media#common_parameters) for details on how to configure default messages and alert processing options. ::: notewarning Even if an alertscript doesn't use default messages, message templates for operation types used by this media type must still be defined, otherwise a notification will not be sent. ::: ::: noteimportant As parallel processing of media types is implemented since Zabbix 3.4.0, it is important to note that with more than one script media type configured, these scripts may be processed in parallel by alerter processes. The total number of alerter processes is limited by the StartAlerters [parameter](/manual/appendix/config/zabbix_server). ::: #### Configuration Pour configurer des scripts d'alerte personnalisés comme type de média : - Allez dans *Administration → Types de média* - Cliquez sur *Créer un type de média* L'onglet **Type de média** contient les attributs généraux du type de média :  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les paramètres suivants sont spécifiques au type de média de script : |Paramètre|Description| |--|--------| |*Nom du script*|Entrez le nom du script.| |*Paramètres de script*|Ajouter des paramètres de ligne de commande au script.<br>Les [macros](/manual/appendix/macros/supported_by_location) {ALERT.SENDTO}, {ALERT.SUBJECT} et {ALERT.MESSAGE} sont pris en charge dans les paramètres de script.<br>La personnalisation des paramètres de script est prise en charge depuis Zabbix 3.0.| Voir les [paramètres de type de média communs](/manual/config/notifications/media#common_parameters) pour plus de détails sur la façon de configurer les messages par défaut et les options de traitement des alertes. ::: notewarning Même si un script d'alerte n'utilise pas de messages par défaut, les modèles de message pour les types d'opérations utilisés par ce type de média doivent toujours être définis, sinon aucune notification ne sera envoyée. ::: ::: noteimportant Comme le traitement parallèle des types de médias est implémenté depuis Zabbix 3.4.0, il est important de noter qu'avec plus d'un type de média de script configuré, ces scripts peuvent être traités en parallèle par les processus alerteurs. Le nombre total de processus d'alerte est limité par le [paramètre](/manual/appendix/config/zabbix_server) StartAlerters. ::: #### Configuration To configure event correlation rules globally: - Go to *Configuration* → *Event correlation* - Click on *Create correlation* to the right (or on the correlation name to edit an existing rule) - Enter parameters of the correlation rule in the form {width="600"} All mandatory input fields are marked with a red asterisk. |Parameter|Description| |--|--------| |*Name*|Unique correlation rule name.| |*Type of calculation*|The following options of calculating conditions are available:<br>**And** - all conditions must be met<br>**Or** - enough if one condition is met<br>**And/Or** - AND with different condition types and OR with the same condition type<br>**Custom expression** - a user-defined calculation formula for evaluating action conditions. It must include all conditions (represented as uppercase letters A, B, C, ...) and may include spaces, tabs, brackets ( ), **and** (case sensitive), **or** (case sensitive), **not** (case sensitive).| |*Conditions*|List of conditions. See below for details on configuring a condition.| |*Description*|Correlation rule description.| |*Operations*|Mark the checkbox of the operation to perform when event is correlated. The following operations are available:<br>**Close old events** - close old events when a new event happens. Always add a condition based on the old event when using the *Close old events* operation or all existing problems could be closed.<br>**Close new event** - close the new event when it happens| |*Enabled*|If you mark this checkbox, the correlation rule will be enabled.| To configure details of a new condition, click on  in the Conditions block. A popup window will open where you can edit the condition details.  |Parameter|Description| |--|--------| |*New condition*|Select a condition for correlating events.<br>*Note* that if no old event condition is specified, all old events may be matched and closed. Similarly if no new event condition is specified, all new events may be matched and closed.<br>The following conditions are available:<br>**Old event tag** - specify the old event tag for matching.<br>**New event tag** - specify the new event tag for matching.<br>**New event host group** - specify the new event host group for matching.<br>**Event tag pair** - specify new event tag and old event tag for matching. In this case there will be a match if the **values** of the tags in both events match. Tag *names* need not match.<br>This option is useful for matching runtime values, which may not be known at the time of configuration (see also [Example 1](/manual/config/event_correlation/global#examples)).<br>**Old event tag value** - specify the old event tag name and value for matching, using the following operators:<br>*equals* - has the old event tag value<br>*does not equal* - does not have the old event tag value<br>*contains* - has the string in the old event tag value<br>*does not contain* - does not have the string in the old event tag value<br>**New event tag value** - specify the new event tag name and value for matching, using the following operators:<br>*equals* - has the new event tag value<br>*does not equal* - does not have the new event tag value<br>*contains* - has the string in the new event tag value<br>*does not contain* - does not have the string in the new event tag value| ::: notewarning Because misconfiguration is possible, when similar event tags may be created for **unrelated** problems, please review the cases outlined below! ::: - Actual tags and tag values only become visible when a trigger fires. If the regular expression used is invalid, it is silently replaced with an \*UNKNOWN\* string. If the initial problem event with an \*UNKNOWN\* tag value is missed, there may appear subsequent OK events with the same \*UNKNOWN\* tag value that may close problem events which they shouldn't have closed. ```{=html} <!-- --> ``` - If a user uses the {ITEM.VALUE} macro without macro functions as the tag value, the 255-character limitation applies. When log messages are long and the first 255 characters are non-specific, this may also result in similar event tags for unrelated problems. #### Configuration Pour configurer globalement les règles de corrélation d'événements : - Allez dans *Configuration* → *Corrélation d'événement* - Cliquez sur *Créer une corrélation* à droite (ou sur le nom de la corrélation pour modifier une règle existante) - Entrez les paramètres de la règle de corrélation dans le formulaire {width="600"} Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. |Paramètre|Description| |--|--------| |*Nom*|Nom unique de la règle de corrélation.| |*Type de calcul*|Les options suivantes de calcul des conditions sont disponibles :<br>**Et** - toutes les conditions doivent être remplies<br>**Ou** - assez si une condition est remplie<br>** Et/Ou** - ET avec différents types de condition et Ou avec le même type de condition<br>**Expression personnalisée** - une formule de calcul définie par l'utilisateur pour évaluer les conditions d'action. Il doit inclure toutes les conditions (représentées par des lettres majuscules A, B, C, ...) et peut inclure des espaces, des tabulations, des parenthèses ( ), **and** (sensible à la casse), **or** (sensible à la casse) , **not** (sensible à la casse).| |*Conditions*|Liste des conditions. Voir ci-dessous pour plus de détails sur la configuration d'une condition.| |*Description*|Description de la règle de corrélation.| |*Opérations*|Cochez la case de l'opération à effectuer lorsque l'événement est corrélé. Les opérations suivantes sont disponibles :<br>**Fermer les anciens événements** : fermez les anciens événements lorsqu'un nouvel événement se produit. Ajoutez toujours une condition basée sur l'ancien événement lorsque vous utilisez l'opération *Fermer les anciens événements* ou tous les problèmes existants pourraient être fermés.<br>**Fermer le nouvel événement** - fermer le nouvel événement lorsqu'il se produit| |*Activé*|Si vous cochez cette case, la règle de corrélation sera activée.| Pour configurer les détails d'une nouvelle condition, cliquez sur  dans le bloc Conditions. Une fenêtre contextuelle s'ouvrira dans laquelle vous pourrez modifier les détails de la condition.  |Paramètre|Description| |--|--------| |*Nouvelle condition*|Sélectionnez une condition pour corréler les événements.<br>*Notez* que si aucune ancienne condition d'événement n'est spécifiée, tous les anciens événements peuvent être mis en correspondance et fermés. De même, si aucune nouvelle condition d'événement n'est spécifiée, tous les nouveaux événements peuvent être mis en correspondance et fermés.<br>Les conditions suivantes sont disponibles :<br>**Nom de l'ancien tag d'événement** : spécifiez l'ancien tag d'événement pour la correspondance.<br>**Nom du nouveau tag d'événement** : spécifiez le nouveau tag d'événement pour la correspondance.<br>**Nouveau groupe d'hôte d'événement** : spécifiez le nouveau groupe d'hôtes d'événements pour la correspondance.<br>**Paire de tags d'événement** : spécifiez un nouvel événement tag et ancien tag d'événement pour la correspondance. Dans ce cas, il y aura correspondance si les **valeurs** des tags des deux événements correspondent. Les *noms* des tags ne doivent pas correspondre.<br>Cette option est utile pour faire correspondre les valeurs d'exécution, qui peuvent ne pas être connues au moment de la configuration (voir aussi [Exemple 1](/manual/config/event_correlation/global#examples)) .<br>**Ancienne valeur du tag d'événement** : spécifiez le nom et la valeur de l'ancien tag d'événement pour la correspondance, à l'aide des opérateurs suivants :<br>*égal* : a l'ancienne valeur de tag d'événement<br>*n'est pas égal* - n'a pas l'ancienne valeur de tag d'événement<br>*contient* - a la chaîne dans l'ancienne valeur de tag d'événement<br>*ne contient pas* - n'a pas la chaîne dans l'ancienne valeur de tag d'événement<br>** Nouvelle valeur de tag d'événement** : spécifiez le nom et la valeur du nouveau tag d'événement pour la correspondance, à l'aide des opérateurs suivants :<br>*égal* - a la nouvelle valeur de tag d'événement<br>*n'est pas égal* - n'a pas le nouveau valeur du tag d'événement<br>*contient* - contient la chaîne dans la nouvelle valeur du tag d'événement<br>*ne contient pas* - ne contient pas la chaîne dans la nouvelle valeur du tag d'événement| ::: notewarning Étant donné qu'une mauvaise configuration est possible, lorsque des tags d'événement similaires peuvent être créées pour des problèmes **non liés**, veuillez examiner les cas décrits ci-dessous ! ::: - Les tags réels et les valeurs de tag ne deviennent visibles que lorsqu'un déclencheur se déclenche. Si l'expression régulière utilisée n'est pas valide, elle est silencieusement remplacée par une chaîne \*UNKNOWN\*. Si l'événement de problème initial avec une valeur de tag \*UNKNOWN\* est manqué, des événements OK ultérieurs peuvent apparaître avec la même valeur de tag \*UNKNOWN\* qui peuvent fermer des événements de problème qu'ils n'auraient pas dû fermer. ```{=html} <!-- --> ``` - Si un utilisateur utilise la macro {ITEM.VALUE} sans fonctions de macro comme valeur de tag, la limite de 255 caractères s'applique. Lorsque les messages de journal sont longs et que les 255 premiers caractères ne sont pas spécifiques, cela peut également entraîner des tags d'événement similaires pour des problèmes sans rapport. #### Configuration To configure, select *Action log* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Sort entries by*|Sort entries by:<br>**Time** (descending or ascending)<br>**Type** (descending or ascending)<br>**Status** (descending or ascending)<br>**Recipient** (descending or ascending).| |*Show lines*|Set how many action log lines will be displayed in the widget.| #### Configuration Pour configurer, sélectionnez *Journal d'action* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Trier les entrées par*|Trier les entrées par :<br>**Heure** (décroissant ou croissant)<br>**Type** (décroissant ou croissant)<br>**Statut** (décroissant ou croissant) <br>**Destinataire** (décroissant ou croissant).| |*Afficher les lignes*|Définir le nombre de lignes du journal d'action qui seront affichées dans le widget.| #### Configuration To configure, select *Clock* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Time type*|Select local, server, or specified host time.<br>Server time will be identical to the time zone set globally or for the Zabbix user.| |*Item*|Select the item for displaying time. To display host time, use the `system.localtime[local]` [item](/manual/config/items/itemtypes/zabbix_agent). This item must exist on the host.<br>This field is available only when *Host time* is selected.| #### Configuration Pour configurer, sélectionnez *Horloge* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) pour tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Type d'heure*|Sélectionnez l'heure locale, du serveur ou de l'hôte spécifié.<br>L'heure du serveur sera identique au fuseau horaire défini globalement ou pour l'utilisateur Zabbix.| |*Elément*|Sélectionnez l'élément pour lequel afficher l'heure. Pour afficher l'heure de l'hôte, utilisez l'[élément](/manual/config/items/itemtypes/zabbix_agent) `system.localtime[local]`. Cet élément doit exister sur l'hôte.<br>Ce champ n'est disponible que lorsque *Heure de l'hôte* est sélectionné.| #### Configuration To configure, select *Data overview* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Host groups*|Select host groups. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove the selected.| |*Hosts*|Select hosts. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove the selected.| |*Tags*|Specify tags to limit the number of item data displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hosts location*|Select host location - left or top.| #### Configuration Pour configurer, sélectionnez *Aperçu des données* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Groupes d'hôtes*|Sélectionnez les groupes d'hôtes. Ce champ est auto-complété, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer la sélection.| |*Hôtes*|Sélectionnez les hôtes. Ce champ est auto-complété, donc commencer à taper le nom d'un hôte offrira une liste déroulante des hôtes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer la sélection.| |*Tags*|Spécifiez des tags pour limiter le nombre de données d'éléments affichées dans le widget. Il est possible d'inclure et d'exclure des tag et des valeurs de tag spécifiques. Plusieurs conditions peuvent être définies. La correspondance des noms de tag est toujours sensible à la casse.<br>Plusieurs opérateurs sont disponibles pour chaque condition :<br>**Existe** - inclut les noms de tag spécifiés<br>**Égal** - inclut les noms de tag spécifiés et valeurs (sensible à la casse)<br>**Contient** - inclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse)<br>**N'existe pas** - exclut les valeurs spécifiées noms de tag<br>**N'est pas égal** - exclut les noms et valeurs de tag spécifiés (sensible à la casse)<br>**Ne contient pas** - exclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse)<br>Il existe deux types de calcul pour les conditions :<br>**Et/Ou** - toutes les conditions doivent être remplies, les conditions ayant le même nom de tag seront regroupées par la condition Ou<br >**Ou** - suffisant si une condition est remplie| |*Afficher les problèmes supprimés*|Cochez la case pour afficher les problèmes qui seraient autrement supprimés (non affichés) en raison de la maintenance de l'hôte.| |*Localisation de l'hôte*|Sélectionnez l'emplacement de l'hôte - à gauche ou en haut.| #### Configuration To configure, select *Graph* as type: {width="600"} The **Data set** tab allows to add data sets and define their visual representation: | | | | |-|----------|----------------------------------------| |*Data set*|<|Select hosts and items to display on the graph. Alternatively, you may enter host and item patterns. Wildcard patterns may be used (for example, `*` will return results that match zero or more characters). To specify a wildcard pattern, just enter the string manually and press *Enter*. While you are typing, note how all matching hosts are displayed in the dropdown.<br>Up to 50 items may be displayed in the graph.<br>Host pattern and item pattern fields are mandatory.<br>The wildcard symbol is always interpreted, therefore it is not possible to add, for example, an item named "item\*" individually, if there are other matching items (e.g. item2, item3).| | |*Base color*|Adjust base color, either from the color picker or manually. The base color is used to calculate different colors for each item of the data set. Base color input field is mandatory.| |^|*Draw*|Choose the draw type of the metric. Possible draw types are *Line* (set by default), *Points*, *Staircase* and *Bar*.<br>Note that if there's only one data point in the line/staircase graph it is drawn as a point regardless of the draw type. The point size is calculated from the line width, but it cannot be smaller than 3 pixels, even if the line width is less.| |^|*Width*|Set the line width. This option is available when *Line* or *Staircase* draw type is selected.| |^|*Point size*|Set the point size. This option is available when *Points* draw type is selected.| |^|*Transparency*|Set the transparency level.| |^|*Fill*|Set the fill level. This option is available when *Line* or *Staircase* draw type is selected.| |^|*Missing data*|Select the option for displaying missing data:<br>**None** - the gap is left empty<br>**Connected** - two border values are connected<br>**Treat as 0** - the missing data is displayed as 0 values<br>Not applicable for the *Points* and *Bar* draw type.| |^|*Y-axis*|Select the side of the graph where the Y-axis will be displayed.| |^|*Time shift*|Specify time shift if required. You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. Negative values are allowed.| |^|*Aggregation function*|Specify which aggregation function to use:<br>**min** - display the smallest value<br>**max** - display the largest value<br>**avg** - display the average value<br>**sum** - display the sum of values<br>**count** - display the count of values<br>**first** - display the first value<br>**last** - display the last value<br>**none** - display all values (no aggregation)<br>Aggregation allows to display an aggregated value for the chosen interval (5 minutes, an hour, a day), instead of all values. See also: [Aggregation in graphs](/manual/config/visualization/graphs/aggregate).<br>This option is supported since Zabbix 4.4.| |^|*Aggregation interval*|Specify the interval for aggregating values. You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. A numeric value without a suffix will be regarded as seconds.<br>This option is supported since Zabbix 4.4.| |^|*Aggregate*|Specify whether to aggregate:<br>**Each item** - each item in the dataset will be aggregated and displayed separately.<br>**Data set** - all dataset items will be aggregated and displayed as one value.<br>This option is supported since Zabbix 4.4.| Existing data sets are displayed in a list. You may: -  - click on this button to add a new data set -  - click on the color icon to expand/collapse data set details -  - click on the move icon and drag a data set to a new place in the list #### Configuration Pour configurer, sélectionnez *Graphique* comme type : {width="600"} L'onglet **Jeu de données** permet d'ajouter des ensembles de données et de définir leur représentation visuelle : | | | | |-|----------|----------------------------------------| |*Jeu de données*|<|Sélectionnez les hôtes et les éléments à afficher sur le graphique. Vous pouvez également entrer des modèles d'hôte et d'élément. Des modèles génériques peuvent être utilisés (par exemple, `*` renverra des résultats qui correspondent à zéro ou plusieurs caractères). Pour spécifier un modèle de caractère générique, entrez simplement la chaîne manuellement et appuyez sur *Entrée*. Pendant que vous tapez, notez comment tous les hôtes correspondants sont affichés dans la liste déroulante.<br>Jusqu'à 50 éléments peuvent être affichés dans le graphique.<br>Les champs Modèle d'hôte et Modèle d'élément sont obligatoires.<br>Le symbole générique est toujours interprété, il n'est donc pas possible d'ajouter, par exemple, un élément nommé "élément\*" individuellement, s'il existe d'autres éléments correspondants (par exemple, élément2, élément3).| | |*Couleur de base*|Ajustez la couleur de base, soit à partir du sélecteur de couleurs, soit manuellement. La couleur de base est utilisée pour calculer différentes couleurs pour chaque élément de l'ensemble de données. Le champ de saisie de la couleur de base est obligatoire.| |^|*Traçage*|Choisissez le type de traçage de la métrique. Les types de tracé possibles sont *Ligne* (défini par défaut), *Points*, *Escalier* et *Barre*.<br>Notez que s'il n'y a qu'un seul point de données dans le graphique en ligne/escalier, il est dessiné comme un point quel que soit le type de tirage. La taille en points est calculée à partir de la largeur de la ligne, mais elle ne peut pas être inférieure à 3 pixels, même si la largeur de la ligne est inférieure.| |^|*Largeur*|Définit la largeur de la ligne. Cette option est disponible lorsque le type de tracé *Ligne* ou *Escalier* est sélectionné.| |^|*Taille du point*|Définissez la taille du point. Cette option est disponible lorsque le type de tirage *Points* est sélectionné.| |^|*Transparence*|Définissez le niveau de transparence.| |^|*Remplissage*|Définir le niveau de remplissage. Cette option est disponible lorsque le type de tracé *Ligne* ou *Escalier* est sélectionné.| |^|*Donnée manquante*|Sélectionnez l'option d'affichage des données manquantes :<br>**Aucune** - l'espace est laissé vide<br>**Connectée** - deux valeurs de bordure sont connectées<br>**Traitée comme 0** - les données manquantes sont affichées sous forme de valeurs 0<br>Non applicable pour les types de tirage *Points* et *Barre*.| |^|*Axe Y*|Sélectionnez le côté du graphique où l'axe Y sera affiché.| |^|*Décalage horaire*|Spécifiez le décalage horaire si nécessaire. Vous pouvez utiliser les [suffixes horaires](/manual/appendix/suffixes#time_suffixes) dans ce champ. Les valeurs négatives sont autorisées.| |^|*Fonction d'agrégation*|Spécifiez la fonction d'agrégation à utiliser :<br>**min** - affiche la plus petite valeur<br>**max** - affiche la plus grande valeur<br>**moy** - afficher la valeur moyenne<br>**somme** - afficher la somme des valeurs<br>**nombre** - afficher le nombre de valeurs<br>**premier** - afficher la première valeur<br>** dernier** - affiche la dernière valeur<br>**aucun** - affiche toutes les valeurs (pas d'agrégation)<br>L'agrégation permet d'afficher une valeur agrégée pour l'intervalle choisi (5 minutes, une heure, un jour), à la place de toutes les valeurs. Voir aussi : [Agrégation dans les graphiques](/manual/config/visualization/graphs/aggregate).<br>Cette option est prise en charge depuis Zabbix 4.4.| |^|*Intervalle d'agrégation*|Spécifiez l'intervalle d'agrégation des valeurs. Vous pouvez utiliser [suffixes horaires](/manual/appendix/suffixes#time_suffixes) dans ce champ. Une valeur numérique sans suffixe sera considérée comme des secondes.<br>Cette option est prise en charge depuis Zabbix 4.4.| |^|*Agrégat*|Spécifier s'il faut agréger :<br>**Chaque élément** - chaque élément de l'ensemble de données sera agrégé et affiché séparément.<br>**Jeu de données** - tous les éléments de l'ensemble de données seront agrégés et affiché comme une seule valeur.<br>Cette option est prise en charge depuis Zabbix 4.4.| Les jeux de données existants sont affichés dans une liste. Vous pouvez : -  - cliquer sur ce bouton pour ajouter un nouveau jeu de données -  - cliquer sur l'icône de couleur pour développer/réduire les détails du jeu de données -  - cliquer sur l'icône de déplacement et faites glisser un ensemble de données vers un nouvel emplacement dans la liste #### Configuration To configure, select *Graph (classic)* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Source*|Select graph type:<br>**Graph** - custom graph<br>**Simple graph** - simple graph| |*Graph*|Select the custom graph to display.<br>This option is available if 'Graph' is selected as *Source*.| |*Item*|Select the item to display in a simple graph.<br>This option is available if 'Simple graph' is selected as *Source*.| |*Show legend*|Unmark this checkbox to hide the legend on the graph (marked by default).| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set graph to display different data depending on the selected host.| Information displayed by the classic graph widget can be downloaded as .png image using the [widget menu](/manual/web_interface/frontend_sections/monitoring/dashboard#widget_menu):  A screenshot of the widget will be saved to the Downloads folder. #### Configuration Pour configurer, sélectionnez *Graph (classic)* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Source*|Sélectionnez le type de graphique :<br>**Graphique** - graphique personnalisé<br>**Graphique simple** - graphique simple| |*Graphique*|Sélectionnez le graphique personnalisé à afficher.<br>Cette option est disponible si 'Graphique' est sélectionné comme *Source*.| |*Élément*|Sélectionnez l'élément à afficher dans un graphique simple.<br>Cette option est disponible si 'Graphique simple' est sélectionné comme *Source*.| |*Afficher la légende*|Décochez cette case pour masquer la légende sur le graphique (cochée par défaut).| |*[Élément dynamique](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Définissez le graphique pour afficher différentes données en fonction de l'hôte sélectionné.| Les informations affichées par le widget graphique classique peuvent être téléchargées sous forme d'image .png à l'aide du [menu widget](/manual/web_interface/frontend_sections/monitoring/dashboard#widget_menu) :  Une capture d'écran du widget sera enregistrée dans le dossier Téléchargements. #### Configuration To configure, select *Graph prototype* as widget type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Source*|Select source: either a **Graph prototype** or a **Simple graph prototype**.| |*Graph prototype*|Select a graph prototype to display discovered graphs of the graph prototype.<br>This option is available if 'Graph prototype' is selected as Source.| |*Item prototype*|Select an item prototype to display simple graphs based on discovered items of an item prototype.<br>This option is available if 'Simple graph prototype' is selected as Source.| |*Show legend*|Mark this checkbox to show the legend on the graphs (marked by default).| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set graphs to display different data depending on the selected host.| |*Columns*|Enter the number of columns of graphs to display within a graph prototype widget.| |*Rows*|Enter the number of rows of graphs to display within a graph prototype widget.| While the *Columns* and *Rows* settings allow fitting more than one graph in the widget, there still may be more discovered graphs than there are columns/rows in the widget. In this case paging becomes available in the widget and a slide-up header allows to switch between pages using the left and right arrows.  #### Configuration Pour configurer, sélectionnez *Prototype de graphique* comme type de widget :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Source*|Sélectionnez la source : soit un **prototype de graphique**, soit un **prototype de graphique simple**.| |*Prototype de graphique*|Sélectionnez un prototype de graphique pour afficher les graphiques découverts du prototype de graphique.<br>Cette option est disponible si 'Prototype de graphique' est sélectionné comme Source.| |*Prototype d'élément*|Sélectionnez un prototype d'élément pour afficher des graphiques simples basés sur les éléments découverts d'un prototype d'élément.<br>Cette option est disponible si 'Prototype de graphique simple' est sélectionné comme Source.| |*Afficher la légende*|Cochez cette case pour afficher la légende sur les graphiques (marquée par défaut).| |*[Élément dynamique](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Définissez des graphiques pour afficher différentes données en fonction de l'hôte sélectionné.| |*Colonnes*|Entrez le nombre de colonnes de graphiques à afficher dans un widget de prototype de graphique.| |*Lignes*|Entrez le nombre de lignes de graphiques à afficher dans un widget de prototype de graphique.| Bien que les paramètres *Colonnes* et *Lignes* permettent d'insérer plus d'un graphique dans le widget, il peut encore y avoir plus de graphiques découverts qu'il n'y a de colonnes/lignes dans le widget. Dans ce cas, la pagination devient disponible dans le widget et une en-tête coulissante permet de basculer entre les pages à l'aide des flèches gauche et droite.  #### Configuration To configure, select *Host availability* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Host groups*|Select host group(s). This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove the selected.| |*Interface type*|Select which host interfaces you want to see availability data for.<br>Availability of all interfaces is displayed by default if nothing is selected.| |*Layout*|Select horizontal display (columns) or vertical display (lines).| |*Show hosts in maintenance*|Include hosts that are in maintenance in the statistics.| #### Configuration Pour configurer, sélectionnez *Disponibilité de l'hôte* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Groupes d'hôtes*|Sélectionnez le(s) groupe(s) d'hôtes. Ce champ est auto-complété, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer la sélection.| |*Type d'interface*|Sélectionnez les interfaces hôtes pour lesquelles vous souhaitez voir les données de disponibilité.<br>La disponibilité de toutes les interfaces est affichée par défaut si rien n'est sélectionné.| |*Mise en page*|Sélectionnez l'affichage horizontal (colonnes) ou l'affichage vertical (lignes).| |*Afficher les hôtes en maintenance*|Inclure les hôtes en maintenance dans les statistiques.| #### Configuration To configure, select *Item value* as the widget type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |_**Item**_ |Select the item. | |_**Show**_ |Mark the checkbox to display the respective element (description, value, time, change indicator). Unmark to hide.<br>At least one element must be selected. | |_**Advanced configuration**_ |Mark the checkbox to display [advanced configuration](#advanced-configuration) options. | |_**[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic-widgets)**_ |Mark the checkbox to display a different value depending on the selected host. | #### Configuration Pour configurer, sélectionnez *Valeur d'élément* comme type de widget :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |_**Élément**_ |Sélectionnez l'élément. | |_**Afficher**_ |Cochez la case pour afficher l'élément respectif (description, valeur, heure, indicateur de changement). Décochez pour masquer.<br>Au moins un élément doit être sélectionné. | |_**Configuration avancée**_ |Cochez la case pour afficher les options de [configuration avancée](#configuration-avancée). | |_**[Élément dynamique](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic-widgets)**_ |Cochez la case pour afficher une valeur différente selon l'hôte sélectionné. | #### Configuration To configure, select *Plain text* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Items*|Select the items.| |*Items location*|Choose the location of selected items to be displayed in the widget.| |*Show lines*|Set how many latest data lines will be displayed in the widget.| |*Show text as HTML*|Set to display text as HTML.| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set to display different data depending on the selected host.| #### Configuration Pour configurer, sélectionnez *Texte brut* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) pour tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Eléments*|Sélectionner les éléments.| |*Emplacement des éléments*|Choisir l'emplacement des éléments sélectionnés à afficher dans le widget.| |*Afficher les lignes*|Définir le nombre de dernières lignes de données qui seront affichées dans le widget.| |*Afficher le texte au format HTML*|Défini pour afficher le texte au format HTML.| |*[Élément dynamique](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Défini pour afficher différentes données en fonction de l'hôte sélectionné.| #### Configuration To configure, select *Problem hosts* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: |Parameter|Description| |--|--------| |*Host groups*|Enter host groups to display in the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host data from these host groups will be displayed in the widget. If no host groups are entered, all host groups will be displayed.| |*Exclude host groups*|Enter host groups to hide from the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host data from these host groups will not be displayed in the widget. For example, hosts 001, 002, 003 may be in Group A and hosts 002, 003 in Group B as well. If we select to *show* Group A and *exclude* Group B at the same time, only data from host 001 will be displayed in the Dashboard.| |*Hosts*|Enter hosts to display in the widget. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts.<br>If no hosts are entered, all hosts will be displayed.| |*Problem*|You can limit the number of problem hosts displayed by the problem name. If you enter a string here, only those hosts with problems whose name contains the entered string will be displayed. Macros are not expanded.| |*Severity*|Mark the problem severities to be displayed in the widget.| |*Tags*|Specify problem tags to limit the number of problems displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hide groups without problems*|Mark the *Hide groups without problems* option to hide data from host groups without problems in the widget.| |*Problem display*|Display problem count as:<br>**All** - full problem count will be displayed<br>**Separated** - unacknowledged problem count will be displayed separated as a number of the total problem count<br>**Unacknowledged only** - only the unacknowledged problem count will be displayed.| #### Configuration Pour configurer, sélectionnez *Hôtes problématiques* comme type :  En plus des paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : |Paramètre|Description| |--|--------| |*Groupes d'hôtes*|Entrez les groupes d'hôtes à afficher dans le widget. Ce champ est à saisie automatique, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants.<br> La spécification d'un groupe d'hôtes parent sélectionne implicitement tous les groupes d'hôtes imbriqués.<br> Les données d'hôte de ces groupes d'hôtes seront affichées dans le widget. Si aucun groupe d'hôtes n'est entré, tous les groupes d'hôtes seront affichés.| |*Exclure les groupes d'hôtes*|Entrez les groupes d'hôtes à masquer du widget. Ce champ est à saisie automatique, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants.<br> La spécification d'un groupe d'hôtes parent sélectionne implicitement tous les groupes d'hôtes imbriqués.<br> Les données d'hôte de ces groupes d'hôtes ne seront pas affiché dans le widget. Par exemple, les hôtes 001, 002, 003 peuvent appartenir au groupe A et les hôtes 002, 003 au groupe B également. Si nous choisissons de *montrer* le groupe A et *exclure* le groupe B en même temps, seules les données de l'hôte 001 seront affichées dans le tableau de bord.| |*Hôtes*|Entrez les hôtes à afficher dans le widget. Ce champ est auto-complété, donc commencer à taper le nom d'un hôte offrira une liste déroulante des hôtes correspondants.<br>Si aucun hôte n'est entré, tous les hôtes seront affichés.| |*Problème*|Vous pouvez limiter le nombre d'hôtes problématiques affichés par le nom du problème. Si vous saisissez une chaîne ici, seuls les hôtes ayant des problèmes dont le nom contient la chaîne saisie seront affichés. Les macros ne sont pas développées.| |*Sévérité*|Marquez les sévérités du problème à afficher dans le widget.| |*Tags*|Spécifiez des tags de problème pour limiter le nombre de problèmes affichés dans le widget. Il est possible d'inclure et d'exclure des tags et des valeurs de tag spécifiques. Plusieurs conditions peuvent être définies. La correspondance des noms de tag est toujours sensible à la casse.<br>Plusieurs opérateurs sont disponibles pour chaque condition :<br>**Existe** - inclut les noms de tag spécifiés<br>**Égal** - inclut les noms de tag spécifiés et valeurs (sensible à la casse)<br>**Contient** - inclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse)<br>**N'existe pas** - exclut les valeurs spécifiées noms de tag<br>**N'est pas égal** - exclut les noms et valeurs de tag spécifiés (sensible à la casse)<br>**Ne contient pas** - exclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie ( correspondance de sous-chaîne, insensible à la casse)<br>Il existe deux types de calcul pour les conditions :<br>**Et/Ou** - toutes les conditions doivent être remplies, les conditions ayant le même nom de tag seront regroupées par la condition Ou<br >**Ou** - suffisant si une condition est remplie| |*Afficher les problèmes supprimés*|Cochez la case pour afficher les problèmes qui seraient autrement supprimés (non affichés) en raison de la maintenance de l'hôte.| |*Masquer les groupes sans problème*|Cochez l'option *Masquer les groupes sans problème* pour masquer les données des groupes hôtes sans problème dans le widget.| |*Affichage des problèmes*|Afficher le nombre de problèmes comme :<br>**Tous** - le nombre total de problèmes sera affiché<br>**Séparé** - le nombre de problèmes non reconnus sera affiché séparé comme un nombre du nombre total de problèmes <br>**Non acquitté uniquement** - seul le nombre de problèmes non acquittés sera affiché.| #### Configuration To configure, select *Top hosts* as type: {width="600"} #### Configuration Pour configurer, sélectionnez *Top des hôtes* comme type. {width="600"} #### Configuration To configure, select *Trigger overview* as type:  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Show*|Filter triggers by trigger state:<br>**Recent problems** - *(default)* show triggers that recently have been or still are in a PROBLEM state (resolved and unresolved);<br>**Problems** - show triggers that are in a PROBLEM state (unresolved);<br>**Any** - show all triggers.| |*Host groups*|Select the host group(s). This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.| |*Hosts*|Select hosts. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove the selected.| |*Tags*|Specify tags to filter the triggers displayed in the widget.<br>It is possible to include as well as exclude specific tags and tag values.<br>Several conditions can be set. Tag name matching is always case-sensitive.<br><br>**Note:** If the parameter *Show* is set to 'Any', all triggers will be displayed even if tags are specified. However, while recent trigger state changes (displayed as blinking blocks) will update for all triggers, the trigger state details (problem severity color and whether the problem is acknowledged) will only update for triggers that match the specified tags.<br><br>There are several operators available for each condition:<br>**Exists** - include the specified tag names;<br>**Equals** - include the specified tag names and values (case-sensitive);<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive);<br>**Does not exist** - exclude the specified tag names;<br>**Does not equal** - exclude the specified tag names and values (case-sensitive);<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive).<br><br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the *Or* condition;<br>**Or** - enough if one condition is met.| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hosts location*|Select host location - left or top.| #### Configuration Pour configurer, sélectionnez *Aperçu des déclencheurs* comme type :  Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#paramètres-communs) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Afficher*|Filtrer par statut de problème :<br>**Problèmes récents** - *(par défaut)* afficher les déclencheurs qui ont récemment été ou sont encore dans un état PROBLÈME (résolus et non résolus) ;<br>**Problèmes** - afficher les déclencheurs qui sont dans un état PROBLÈME (non résolus) ;<br>**Tous** - afficher tous les déclencheurs.| |*Groupes d'hôtes*|Sélectionnez le(s) groupe(s) d'hôtes. Ce champ est auto-complété, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants.| |*Hôtes*|Sélectionnez les hôtes. Ce champ est auto-complété, donc commencer à taper le nom d'un hôte offrira une liste déroulante des hôtes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer la sélection.| |*Tags*|Spécifiez les balises pour filtrer les déclencheurs affichés dans le widget.<br>Il est possible d'inclure et d'exclure des balises et des valeurs de balises spécifiques.<br>Plusieurs conditions peuvent être définies. La correspondance des noms de balises est toujours sensible à la casse.<br><br>**Remarque :** Si le paramètre *Afficher* est défini sur "Tous", tous les déclencheurs seront affichés même si des balises sont spécifiées. Cependant, alors que les modifications récentes de l'état du déclencheur (affichées sous forme de blocs clignotants) seront mises à jour pour tous les déclencheurs, les détails de l'état du déclencheur (couleur de la gravité du problème et si le problème est reconnu) ne seront mis à jour que pour les déclencheurs qui correspondent aux balises spécifiées.<br><br >Plusieurs opérateurs sont disponibles pour chaque condition :<br>**Exists** - inclut les noms de balises spécifiés ;<br>**Equals** - inclut les noms et les valeurs de balises spécifiés (sensible à la casse) ;<br> **Contient** - inclut les noms de balises spécifiés où les valeurs de balises contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse) ;<br>**N'existe pas** - exclut les noms de balises spécifiés ;<br>** N'est pas égal** - exclut les noms et les valeurs de balise spécifiés (sensible à la casse) ;<br>**Ne contient pas** - exclut les noms de balise spécifiés où les valeurs de balise contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse) ).<br><br>Il existe deux types de calcul pour les conditions :<br>**Et/Ou** - toutes les conditions doivent être remplies, les conditions ayant le même nom de balise seront regroupées par la condition *Ou* ;<br>**Ou** - suffisant si une condition est remplie.| |*Afficher les problèmes supprimés*|Cochez la case pour afficher les problèmes qui seraient autrement supprimés (non affichés) en raison de la maintenance de l'hôte.| |*Emplacement de l'hôte*|Sélectionnez l'emplacement de l'hôte - à gauche ou en haut.| #### Configuration To configure SMS as the media type: - Go to *Administration → Media types* - Click on *Create media type* (or click on *SMS* in the list of pre-defined media types). The following parameters are specific for the SMS media type: |Parameter|Description| |---------|-----------| |*GSM modem*|Set the serial device name of the GSM modem.| See [common media type parameters](/manual/config/notifications/media#common_parameters) for details on how to configure default messages and alert processing options. Note that parallel processing of sending SMS notifications is not possible. ### Configuration Pour configurer les SMS en tant que type de média : - Allez dans *Administration → Types de média* - Cliquez sur *Créer un type de média* (ou cliquez sur *SMS* dans la liste des types de médias prédéfinis). Les paramètres suivants sont spécifiques au type de média SMS : | Paramètre | Description | | --- | --- | | *Modem GSM* | Définissez le nom du périphérique série du modem GSM. | Voir les [paramètres de type de support communs](/manual/config/notifications/media#common_parameters) pour plus de détails sur la façon de configurer les messages par défaut et les options de traitement des alertes. Notez que le traitement parallèle de l'envoi de notifications par SMS n'est pas possible. #### Configuration To create an ad-hoc graph, do the following: - Go to *Monitoring* → *Latest data* - Use filter to display items that you want - Mark checkboxes of the items you want to graph - Click on *Display stacked graph* or *Display graph* buttons {width="600"} Your graph is created instantly: {width="600"} Note that to avoid displaying too many lines in the graph, only the average value for each item is displayed (min/max value lines are not displayed). Triggers and trigger information is not displayed in the graph. In the created graph window you have the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) available and the possibility to switch from the "normal" line graph to a stacked one (and back). {width="600"} #### Configuration Pour créer un graphique ad hoc, procédez comme suit : - Allez dans *Surveillance* → *Dernières données* - Utilisez le filtre pour afficher les éléments que vous souhaitez - Cochez les cases des éléments que vous souhaitez représenter graphiquement - Cliquez sur les boutons *Afficher le graphique empilé* ou *Afficher le graphique* {width="600"} Votre graphique est créé instantanément : {width="600"} Notez que pour éviter d'afficher trop de lignes dans le graphique, seule la valeur moyenne de chaque élément est affichée (les lignes de valeur min/max ne sont pas affichées). Les déclencheurs et les informations sur les déclencheurs ne sont pas affichés dans le graphique. Dans la fenêtre graphique créée, est mis à disposition un [sélecteur de période de temps](/manual/config/visualization/graphs/simple#time_period_selector) et la possibilité de passer du graphique linéaire "normal" à un graphique empilé (et inversement). {width="600"} ### Configuration To create a new service action, go to the *Service actions* subsection of the *Services* menu, then click on *Create action* in the upper right corner. Service actions are configured in the same way as other types of actions in Zabbix. For more details, see configuring [actions](/manual/config/notifications/action#configuring-an-action). The key differences are: - User access to service actions depends on access rights to services granted by user's [role](/manual/web_interface/frontend_sections/administration/user_roles). - Service actions support different set of [conditions](#conditions). ### Configuration Pour créer une nouvelle action de service, rendez-vous dans la sous-section *Actions de service* du menu *Services*, puis cliquez sur *Créer une action* dans le coin supérieur droit. Les actions de service sont configurées de la même manière que les autres types d'actions dans Zabbix. Pour plus de détails, voir la configuration des [actions](/manual/config/notifications/action#configuring-an-action). Les principales différences sont : - L'accès de l'utilisateur aux actions de service dépend des droits d'accès aux services accordés par le [rôle](/manual/web_interface/frontend_sections/administration/user_roles) de l'utilisateur. - Les actions de service prennent en charge différents ensembles de [conditions](#conditions). #### Configuration To define user macros, go to the corresponding location in the frontend: - for global macros, visit *Administration → General → Macros* - for host and template level macros, open host or template properties and look for the *Macros* tab ::: notetip 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, if the macro type is *text* exporting the template to XML and importing it in another system will still allow it to work as expected. Values of secret macros are not [exported](/manual/xml_export_import). ::: A user macro has the following attributes: {width="600"} |Parameter|Description| |--|--------| |*Macro*|Macro name. The name must be wrapped in curly brackets and start with a dollar sign.<br>Example: {$FRONTEND\_URL}. The following characters are allowed in the macro names: **A-Z** (uppercase only) , **0-9** , **\_** , **.**| |*Value*|Macro value. Three value types are supported:<br>**Text** (default) - plain-text value<br>**Secret text** - the value is masked with asterisks, which could be useful to protect sensitive information such as passwords or shared keys.<br>**Vault secret** - the value contains a reference path (as 'path:key', for example “secret/zabbix:password”) to a [Vault secret](/manual/config/secrets)<br><br>*Note* that while the value of a secret macro is hidden from sight, the value can be revealed through the use in items. For example, in an external script an 'echo' statement referencing a secret macro may be used to reveal the macro value to the frontend because Zabbix server has access to the real macro value.<br><br>To select the value type click on the button at the end of the value input field:<br> icon indicates a text macro;<br> icon indicates a secret text macro. Upon hovering, the value field transforms into a  button, which allows to enter a new value of the macro (to exit without saving a new value, click the backwards arrow ().<br> icon indicates a secret Vault macro.<br><br>Maximum length of a user macro value is 2048 characters (255 characters in versions before 5.2.0).| |*Description*|Text field used to provide more information about this macro.| ::: noteclassic URLs that contain a secret macro will not work as the macro in them will be resolved as "\*\*\*\*\*\*". ::: ::: noteimportant In trigger expressions user macros will resolve if referencing a parameter or constant. They will NOT resolve if referencing a host, item key, function, operator or another trigger expression. Secret macros cannot be used in trigger expressions. ::: #### Configuration Pour définir des macros utilisateur, rendez-vous à l'emplacement correspondant dans l'interface : - pour les macros globales, visitez *Administration → Général → Macros* - pour les macros au niveau de l'hôte et du modèle, ouvrez les propriétés de l'hôte ou du modèle et recherchez l'onglet *Macros* ::: notetip Si une macro utilisateur est utilisée dans des éléments ou des déclencheurs dans un modèle, il est suggéré d'ajouter cette macro au modèle même si elle est définie au niveau global. Ainsi, si le type de macro est *texte*, l'exportation du modèle vers XML et son importation dans un autre système lui permettront toujours de fonctionner comme prévu. Les valeurs des macros secrètes ne sont pas [exportées](/manual/xml_export_import). ::: Une macro utilisateur possède les attributs suivants : {width="600"} |Paramètre|Description| |--|--------| |*Macro*|Nom de la macro. Le nom doit être entouré d'accolades et commencer par un signe dollar.<br>Exemple : {$FRONTEND\_URL}. Les caractères suivants sont autorisés dans les noms de macro : **A-Z** (majuscules uniquement) , **0-9** , **\_** , **.**| |*Valeur*|Valeur de la macro. Trois types de valeurs sont pris en charge :<br>**Texte** (par défaut) - valeur en texte brut<br>**Texte secret** - la valeur est masquée par des astérisques, ce qui peut être utile pour protéger des informations sensibles telles que les mots de passe ou des clés partagées.<br>**Secret du coffre-fort** - la valeur contient un chemin de référence (comme 'path:key', par exemple "secret/zabbix:password") vers un [Secret du coffre-fort](/manual/config/secrets)<br><br>*Notez* que même si la valeur d'une macro secrète est cachée, la valeur peut être révélée par l'utilisation dans les objets. Par exemple, dans un script externe, une instruction 'echo' faisant référence à une macro secrète peut être utilisée pour révéler la valeur de la macro à l'interface car le serveur Zabbix a accès à la valeur réelle de la macro.<br><br>Pour sélectionner le type de valeur, cliquez sur sur le bouton à la fin du champ de saisie de valeur :<br>l'icône  indique une macro de texte ;<br>l'icône  indique une macro de texte secrète. Au survol, le champ valeur se transforme en bouton , qui permet de saisir une nouvelle valeur de la macro (pour sortir sans enregistrer une nouvelle valeur, cliquer sur la flèche vers l'arrière ().<br>l'icône  indique une macro Secret du coffre-fort.<br><br>La longueur maximale d'une valeur de macro utilisateur est de 2 048 caractères (255 caractères dans les versions antérieures à 5.2.0).| |*Description*|Champ de texte utilisé pour fournir plus d'informations sur cette macro.| ::: noteclassic Les URL qui contiennent une macro secrète ne fonctionneront pas car la macro qu'elles contiennent sera résolue comme "\*\*\*\*\*\*". ::: ::: noteimportant Dans les expressions de déclencheur, les macros utilisateur seront résolues si elles font référence à un paramètre ou à une constante. Ils ne seront PAS résolus s'ils font référence à un hôte, une clé d'élément, une fonction, un opérateur ou une autre expression de déclencheur. Les macros secrètes ne peuvent pas être utilisées dans les expressions de déclencheur. ::: #### Configuration To ensure proper communication between all elements involved make sure server configuration file and frontend configuration file parameters are properly configured. #### Configuration Pour assurer une bonne communication entre tous les éléments impliqués, assurez-vous que les paramètres du fichier de configuration du serveur et du fichier de configuration frontal sont correctement configurés. #### Configuration To execute a passive check immediately: - click on *Execute now* in an existing item (or discovery rule) configuration form:  - click on *Execute now* for selected items/rules in the list of items/discovery rules:  In the latter case several items/rules can be selected and "executed now" at once. #### Configuration Pour exécuter une vérification passive immédiatement : - cliquer sur *Exécuter maintenant* dans un formulaire de configuration d'élément (ou de règle de découverte) existant :  - cliquer sur *Exécuter maintenant* pour les éléments/règles sélectionnés dans la liste des éléments/règles de découverte :  Dans ce dernier cas, plusieurs éléments/règles peuvent être sélectionnés et "exécutés maintenant" en même temps. #### Configuration To start using a webhook integration: 1. Locate required .xml file in the `templates/media` directory of the downloaded Zabbix version or download it from Zabbix [git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse) 2. [Import](/manual/xml_export_import/media#importing) the file into your Zabbix installation. The webhook will appear in the list of media types. 3. Configure the webhook according to instructions in the *Readme.md* file (you may click on a webhook's name above to quickly access *Readme.md*). To create a custom webhook from scratch: - Go to *Administration → Media types* - Click on *Create media type* The **Media type** tab contains various attributes specific for this media type:  All mandatory input fields are marked with a red asterisk. The following parameters are specific for the webhook media type: |Parameter|Description| |--|--------| |*Parameters*|Specify the webhook variables as the attribute and value pairs.<br>For preconfigured webhooks, a list of parameters varies, depending on the service. Check the webhook's *Readme.md* file for parameter description.<br>For new webhooks, several common variables are included by default (URL:<empty>, HTTPProxy:<empty>, To:{ALERT.SENDTO}, Subject:{ALERT.SUBJECT}, <Message:%7BALERT.MESSAGE>}), feel free to keep or remove them.<br>All [macros](/manual/appendix/macros/supported_by_location) that are supported in problem notifications are supported in the parameters.<br>If you specify an HTTP proxy, the field supports the same functionality as in the item configuration [HTTP proxy](/manual/config/items/itemtypes/http#configuration) field. The proxy string may be prefixed with `[scheme]://` to specify which kind of proxy is used (e.g. https, socks4, socks5; see [documentation](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html)).| |*Script*|Enter JavaScript code in the block that appears when clicking in the parameter field (or on the view/edit button next to it). This code will perform the webhook operation.<br>The script is a function code that accepts parameter - value pairs. The values should be converted into JSON objects using JSON.parse() method, for example: `var params = JSON.parse(value);`.<br><br>The code has access to all parameters, it may perform HTTP GET, POST, PUT and DELETE requests and has control over HTTP headers and request body.<br>The script must contain a return operator, otherwise it will not be valid. It may return OK status along with an optional list of tags and tag values (see *Process tags* option) or an error string.<br><br>Note, that the script is executed only after an alert is created. If the script is configured to return and process tags, these tags will not get resolved in {EVENT.TAGS} and {EVENT.RECOVERY.TAGS} macros in the initial problem message and recovery messages because the script has not had the time to run yet.<br><br>See also: [Webhook development guidelines](https://www.zabbix.com/documentation/guidelines/en/webhooks), [Webhook script examples](/manual/config/notifications/media/webhook/webhook_examples), [Additional JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects).<br>| |*Timeout*|JavaScript execution timeout (1-60s, default 30s).<br>Time suffixes are supported, e.g. 30s, 1m.| |*Process tags*|Mark the checkbox to process returned JSON property values as tags. These tags are added to the already existing (if any) problem event tags in Zabbix.<br>If a webhook uses tags (the Process tags checkbox is marked), the webhook should always return a JSON object containing at least an empty object for tags:`var result = {tags: {}};`.<br>Examples of tags that can be returned: *Jira ID: PROD-1234*, *Responsible: John Smith*, *Processed:<no value>*, etc.| |*Include event menu entry*|Mark the checkbox to include an entry in the [event menu](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) linking to the created external ticket.<br>If marked, the webhook should not be used to send notifications to different users (consider creating a [dedicated user](/manual/config/notifications/media/webhook#user_media) instead) or in several alert actions [related to a single problem event](/manual/config/notifications/media/webhook#configuring_alert_actions).| |*Menu entry name*|Specify the menu entry name.<br>{EVENT.TAGS.<tag name>} macro is supported.<br>This field is only mandatory if *Include event menu entry* is selected.| |*Menu entry URL*|Specify the underlying URL of the menu entry.<br>{EVENT.TAGS.<tag name>} macro is supported.<br>This field is only mandatory if *Include event menu entry* is selected.| See [common media type parameters](/manual/config/notifications/media#common_parameters) for details on how to configure default messages and alert processing options. ::: notewarning Even if a webhook doesn't use default messages, message templates for operation types used by this webhook must still be defined. ::: #### Configuration Pour commencer à utiliser une intégration de webhook : 1. Localisez le fichier .xml requis dans le répertoire `templates/media` de la version téléchargée de Zabbix ou téléchargez-le depuis le [dépôt git](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse) Zabbix. 2. [Importez](/manual/xml_export_import/media#importing) le fichier dans votre installation Zabbix. Le webhook apparaîtra dans la liste des types de médias. 3. Configurez le webhook conformément aux instructions du fichier *Readme.md* (vous pouvez cliquer sur le nom d'un webhook ci-dessus pour accéder rapidement à *Readme.md*). Pour créer un webhook personnalisé à partir de zéro : - Allez dans *Administration → Types de média* - Cliquez sur *Créer un type de média* L'onglet **Type de média** contient divers attributs spécifiques à ce type de média :  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les paramètres suivants sont spécifiques au type de média webhook : |Paramètre|Description| |--|--------| |*Paramètres*|Spécifiez les variables du webhook en tant que paires d'attributs et de valeurs.<br>Pour les webhooks préconfigurés, une liste de paramètres varie en fonction du service. Consultez le fichier *Readme.md* du webhook pour la description des paramètres.<br>Pour les nouveaux webhooks, plusieurs variables communes sont incluses par défaut (URL : \<vide\>, HTTPProxy : \<vide\>, To : {ALERT.SENDTO}, Subject : {ALERT.SUBJECT}, Message : {ALERT.MESSAGE}), n'hésitez pas à les conserver ou à les supprimer.<br>Toutes les [macros](/manual/appendix/macros/supported_by_location) prises en charge dans les notifications de problème sont prises en charge dans les paramètres.<br>Si vous spécifiez un proxy HTTP, le champ prend en charge la même fonctionnalité que dans le champ de configuration de l'élément [proxy HTTP](/manual/config/items/itemtypes/http#configuration). La chaîne de proxy peut être précédée de `[scheme]://` pour spécifier le type de proxy utilisé (par exemple, https, socks4, socks5 ; voir la [documentation](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html)).| |*Script*|Entrez le code JavaScript dans le bloc qui apparaît lorsque vous cliquez dans le champ de paramètre (ou sur le bouton afficher/modifier à côté). Ce code effectuera l'opération de webhook.<br>Le script est un code de fonction qui accepte les paires paramètre - valeur. Les valeurs doivent être converties en objets JSON à l'aide de la méthode JSON.parse(), par exemple : `var params = JSON.parse(value);`.<br><br>Le code a accès à tous les paramètres, il peut effectuer HTTP GET, POST, PUT et DELETE et contrôle les en-têtes HTTP et le corps de la requête.<br>Le script doit contenir un opérateur de retour, sinon il ne sera pas valide. Il peut renvoyer l'état OK avec une liste facultative de tags et de valeurs de tag (voir l'option *Traiter les tags*) ou une chaîne d'erreur.<br><br>Notez que le script n'est exécuté qu'après la création d'une alerte. Si le script est configuré pour renvoyer et traiter des tags, ces tags ne seront pas résolus dans les macros {EVENT.TAGS} et {EVENT.RECOVERY.TAGS} dans le message de problème initial et les messages de récupération car le script n'a pas eu le temps de s'exécuter pour le moment.<br><br>Voir aussi : [Consignes de développement Webhook](https://www.zabbix.com/documentation/guidelines/en/webhooks), [Exemples de scripts Webhook](/manual/config/notifications/media/webhook/webhook_examples), [Objets JavaScript supplémentaires](/manual/config/items/preprocessing/javascript/javascript_objects).<br>| |*Expiration*|Délai d'exécution JavaScript (1-60s, 30s par défaut).<br>Les suffixes de temps sont pris en charge, par ex. 30s, 1m.| |*Traiter les tags*|Cochez la case pour traiter les valeurs de propriété JSON renvoyées en tant que tags. Ces tags sont ajoutées aux tags d'événement de problème déjà existants (le cas échéant) dans Zabbix.<br>Si un webhook utilise des tags (la case Traiter les tags est cochée), le webhook doit toujours renvoyer un objet JSON contenant au moins un objet vide pour les tags: `var result = {tags: {}};`.<br>Exemples de tags pouvant être renvoyés : *Jira ID : PROD-1234*, *Responsible : John Smith*, *Processed : \<pas de valeur\>* , etc | |*Inclure dans le menu de l'événement*|Cochez la case pour inclure une entrée dans le [menu de l'événement](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) liant au ticket externe créé.<br>Si coché, le webhook ne doit pas être utilisé pour envoyer des notifications à différents utilisateurs (envisagez plutôt de créer un [utilisateur dédié](/manual/config/notifications/media/webhook#user_media)) ou dans plusieurs actions d'alerte [liées à un seul événement problématique](/manual/config/notifications/media/webhook#configuring_alert_actions).| |*Nom de l'entrée de menu*|Spécifiez le nom de l'entrée de menu.<br>La macro {EVENT.TAGS.\<nom tag\>} est prise en charge.<br>Ce champ n'est obligatoire que si *Inclure dans le menu de l'événement* est sélectionné.| |*URL de l'entrée de menu*|Spécifiez l'URL sous-jacente de l'entrée de menu.<br>La macro {EVENT.TAGS.\<nom tag\>} est prise en charge.<br>Ce champ n'est obligatoire que si *Inclure dans le menu de l'événement* est sélectionné .| Voir les [paramètres de type de média communs](/manual/config/notifications/media#common_parameters) pour plus de détails sur la façon de configurer les messages par défaut et les options de traitement des alertes. ::: notewarning Même si un webhook n'utilise pas de messages par défaut, les modèles de message pour les types d'opérations utilisés par ce webhook doivent toujours être définis. ::: #### Configuration Two steps are required to close a problem manually. #### Configuration Deux étapes sont nécessaires pour résoudre un problème manuellement. ##### Configure database for Zabbix proxy Edit zabbix\_proxy.conf: # vi /etc/zabbix/zabbix_proxy.conf DBHost=localhost DBName=zabbix DBUser=zabbix DBPassword=<password> In DBName for Zabbix proxy use a separate database from Zabbix server. In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL. Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. See [SELinux configuration](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) for instructions. ##### Configurer la base de données pour le proxy Zabbix Modifiez zabbix\_proxy.conf : # vi /etc/zabbix/zabbix_proxy.conf DBHost=localhost DBName=zabbix DBUser=zabbix DBPassword=<password> Dans DBName pour le proxy Zabbix, utilisez une base de données distincte du serveur Zabbix. Dans DBPassword, utilisez le mot de passe de la base de données Zabbix pour MySQL ; Mot de passe utilisateur PosgreSQL pour PosgreSQL. Utilisez `DBHost=` avec PostgreSQL. Vous voudrez peut-être conserver le paramètre par défaut `DBHost=localhost` (ou une adresse IP), mais cela obligerait PostgreSQL à utiliser un socket réseau pour se connecter à Zabbix. Reportez-vous à la [section correspondante](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) pour obtenir des instructions pour RHEL/CentOS. #### Configure DB connection Enter details for connecting to the database. Zabbix database must already be created. {width="550"} If the *Database TLS encryption* option is checked, then additional fields for [configuring the TLS connection](/manual/appendix/install/db_encrypt) to the database appear in the form (MySQL or PostgreSQL only). If HashiCorp Vault option is selected for storing credentials, additional fields are available for specifying the Vault API endpoint, secret path and authentication token: {width="550"} #### Configuration de la connexion à la base de données Entrez les détails de connexion à la base de données. La base de données Zabbix doit déjà être créée. {width="550"} Si l'option *Cryptage TLS de la base de données* est cochée, des champs supplémentaires pour [configurer la connexion TLS](/manual/appendix/install/db_encrypt) à la base de données apparaissent dans le formulaire (MySQL ou PostgreSQL uniquement). Si l'option HashiCorp Vault est sélectionnée pour stocker les informations d'identification, des champs supplémentaires sont disponibles pour spécifier le point de terminaison de l'API Vault, le chemin secret et le jeton d'authentification : {width="550"} ###### Configure request A request to execute the *Configure* function of the *Configurator* interface. | | | |---|---| |direction|agent → plugin| |response|n/a| Parameters specific to *Configure* requests: |Name|Type|Comments| |---------|--------|----------| |global_options|JSON object|JSON object containing global agent configuration options.| |private_options|JSON object (optional)|JSON object containing private plugin configuration options, if provided.| *Example:* {"id":6,"type":8,"global_options":{...},"private_options":{...}} ###### Requête de configuration Une requête pour exécuter la fonction *Configure* de l'interface *Configurateurr*. | | | |---|---| |direction|agent → plugin| |réponse|n/a| Paramètres spécifiques aux requêtes *Configure* : |Nom|Type|Commentaires| |---------|--------|----------| |global_options|Objet JSON|Objet JSON contenant les options de configuration globales de l'agent.| |private_options|Objet JSON (facultatif)|Objet JSON contenant les options de configuration du plug-in privé, le cas échéant.| *Exemple :* {"id":6,"type":8,"global_options":{...},"private_options":{...}} #### Configuring agent Both generations of Zabbix agents run as a Windows service. For Zabbix agent 2, replace *agentd* with *agent2* in the instructions below. You can run a single instance of Zabbix agent or multiple instances of the agent on a Microsoft Windows host. A single instance can use the default configuration file `C:\zabbix_agentd.conf` or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file). An example configuration file is available in Zabbix source archive as `conf/zabbix_agentd.win.conf`. See the [configuration file](/manual/appendix/config/zabbix_agentd_win) options for details on configuring Zabbix Windows agent. #### Configuration de l'agent Les deux générations d'agents Zabbix s'exécutent en tant que service Windows. Pour l'agent Zabbix 2, remplacez *agentd* par *agent2* dans les instructions ci-dessous. Vous pouvez exécuter une seule instance de l'agent Zabbix ou plusieurs instances de l'agent sur un hôte Microsoft Windows. Une seule instance peut utiliser le fichier de configuration par défaut `C:\zabbix_agentd.conf` ou un fichier de configuration spécifié dans la ligne de commande. En cas d'instances multiples, chacune des instances d'agent doit avoir son propre fichier de configuration (l'une des instances peut utiliser le fichier de configuration par défaut). Un exemple de fichier de configuration (`conf/zabbix_agentd.win.conf`) est disponible dans l'archive source de Zabbix. Voir les options du [fichier de configuration](/manual/appendix/config/zabbix_agentd_win) pour plus de détails sur la configuration de l'agent Windows Zabbix. #### Configuring and running Java gateway Configuration parameters of Zabbix Java gateway may be tuned in the file: /etc/zabbix/zabbix_java_gateway.conf For more details, see Zabbix Java gateway configuration [parameters](/manual/appendix/config/zabbix_java). To start Zabbix Java gateway: # service zabbix-java-gateway restart To automatically start Zabbix Java gateway on boot: RHEL 7 and later: # systemctl enable zabbix-java-gateway RHEL prior to 7: # chkconfig --level 12345 zabbix-java-gateway on #### Configuration et exécution de la passerelle Java Les paramètres de configuration de la passerelle Java Zabbix peuvent être personnalisés dans le fichier : /etc/zabbix/zabbix_java_gateway.conf Pour plus de détails, voir les [paramètres](/fr/manual/appendix/config/zabbix_java) de configuration de la passerelle Java Zabbix. Pour démarrer la passerelle Java Zabbix : # service zabbix-java-gateway restart Pour démarrer automatiquement la passerelle Java Zabbix au démarrage de l'OS : RHEL 7 et ultérieur : # systemctl enable zabbix-java-gateway RHEL avant la version 7 : # chkconfig --level 12345 zabbix-java-gateway on #### Configuring an operation To configure an operation, go to the *Operations* tab in [action](/manual/config/notifications/action) configuration. {width="600"} General operation attributes: |Parameter|Description| |--|-----------| |*Default operation step duration*|Duration of one operation step by default (60 seconds to 1 week).<br>For example, an hour-long step duration means that if an operation is carried out, an hour will pass before the next step.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 60s, 1m, 2h, 1d, since Zabbix 3.4.0.<br>[User macros](/manual/config/macros/user_macros) are supported, since Zabbix 3.4.0.| |*Operations*|Action operations (if any) are displayed, with these details:<br>**Steps** - escalation step(s) to which the operation is assigned<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Start in** - how long after an event the operation is performed<br>**Duration (sec)** - step duration is displayed. *Default* is displayed if the step uses default duration, and a time is displayed if custom duration is used.<br>**Action** - links for editing and removing an operation are displayed.| |*Recovery operations*|Action operations (if any) are displayed, with these details:<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Action** - links for editing and removing an operation are displayed.| |*Update operations*|Action operations (if any) are displayed, with these details:<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Action** - links for editing and removing an operation are displayed.| |*Pause operations for suppressed problems*|Mark this checkbox to delay the start of operations for the duration of a maintenance period. When operations are started, after the maintenance, all operations are performed including those for the events during the maintenance.<br>Note that this setting affects only problem escalations; recovery and update operations will not be affected.<br>If you unmark this checkbox, operations will be executed without delay even during a maintenance period.<br>This option is not available for *Service actions*.| |*Notify about canceled escalations*|Unmark this checkbox to disable notifications about canceled escalations (when host, item, trigger or action is disabled).| All mandatory input fields are marked with a red asterisk. To configure details of a new operation, click on  in the Operations block. To edit an existing operation, click on  next to the operation. A popup window will open where you can edit the operation step details. #### Configurer une opération Pour configurer une opération, accédez à l'onglet *Opérations* dans la configuration de l'[action](/manual/config/notifications/action). {width="600"} Attributs généraux d'opération : |Paramètre|Description| |--|-----------| |*Durée de l'étape d'opération par défaut*|Durée d'une étape d'opération par défaut (60 secondes à 1 semaine).<br>Par exemple, une durée d'étape d'une heure signifie que si une opération est effectuée, une heure s'écoulera avant que la étape suivante.<br>[Les suffixes temporels](/manual/appendix/suffixes) sont pris en charge, par exemple 60s, 1m, 2h, 1d, depuis Zabbix 3.4.0.<br>[Les macros utilisateur](/manual/config/macros/user_macros) sont supportées, depuis Zabbix 3.4.0.| |*Opérations*|Les opérations d'action (le cas échéant) sont affichées, avec ces détails :<br>**Étapes** : étape(s) d'escalade à laquelle l'opération est affectée<br>**Détails** : type d'opération et son destinataire/cible.<br>La liste des opérations affiche également le type de média (e-mail, SMS ou script) utilisé ainsi que le nom et le prénom (entre parenthèses après le nom d'utilisateur) d'un destinataire de la notification.<br>**Démarrer dans** - combien de temps après un événement l'opération est effectuée<br>**Durée** - la durée de l'étape est affichée. *Défaut* s'affiche si l'étape utilise une durée par défaut, et une heure s'affiche si une durée personnalisée est utilisée.<br>**Action** : des liens permettant de modifier et de supprimer une opération s'affichent.| |*Opérations de récupération*|Les opérations d'action (le cas échéant) sont affichées, avec ces détails :<br>**Détails** - type d'opération et son destinataire/cible.<br>La liste des opérations affiche également le type de média (e -mail, SMS ou script) utilisé ainsi que le nom et prénom (entre parenthèses après le nom d'utilisateur) d'un destinataire de la notification.<br>**Action** - les liens pour modifier et supprimer une opération sont affichés.| |*Opérations de mise à jour*|Les opérations d'action (le cas échéant) sont affichées, avec ces détails :<br>**Détails** - type d'opération et son destinataire/cible.<br>La liste des opérations affiche également le type de média (e -mail, SMS ou script) utilisé ainsi que le nom et prénom (entre parenthèses après le nom d'utilisateur) d'un destinataire de la notification.<br>**Action** - les liens pour modifier et supprimer une opération sont affichés.| |*Suspendre les opérations des problèmes supprimés*|Cochez cette case pour retarder le début des opérations pendant la durée d'une période de maintenance. Lorsque les opérations sont lancées, après la maintenance, toutes les opérations sont effectuées, y compris celles des événements pendant la maintenance.<br>Notez que ce paramètre n'affecte que les escalades de problèmes ; les opérations de récupération et de mise à jour ne seront pas affectées.<br>Si vous décochez cette case, les opérations seront exécutées sans délai même pendant une période de maintenance.<br>Cette option n'est pas disponible pour les *actions de service*.| |*Notifier les escalades annulées*|Décochez cette case pour désactiver les notifications sur les escalades annulées (lorsque l'hôte, l'élément, le déclencheur ou l'action est désactivé).| Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Pour configurer les détails d'une nouvelle opération, cliquez sur  dans le bloc Opérations. Pour modifier une opération existante, cliquez sur  à côté de l'opération. Une fenêtre contextuelle s'ouvrira dans laquelle vous pourrez modifier les détails de l'étape de l'opération. #### Configuring an update operation To configure an update operation go to the *Operations* tab in action [configuration](/manual/config/notifications/action).  To configure details of a new update operation, click on  in the Update operations block. To edit an existing operation, click on  next to the operation. A popup window will open where you can edit the operation step details. #### Configuration d'une opération de mise à jour Pour configurer une opération de mise à jour rendez-vous dans l'onglet *Opérations* dans la [configuration](/manual/config/notifications/action) de l'action.  Pour configurer les détails d'une nouvelle opération de mise à jour, cliquez sur  dans le bloc Opérations de mise à jour. Pour modifier une opération existante, cliquez sur  à côté de l'opération. Une fenêtre contextuelle s'ouvrira dans laquelle vous pourrez modifier les détails de l'étape de l'opération. #### Configuring authentication The **Authentication** tab allows you to configure scenario authentication options. A green dot next to the tab name indicates that some type of HTTP authentication is enabled.  Authentication parameters: |Parameter|Description| |--|--------| |*Authentication*|Authentication options.<br>**None** - no authentication used.<br>**Basic** - basic authentication is used.<br>**NTLM** - NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) authentication is used.<br>**Kerberos** - Kerberos authentication is used. See also: [Configuring Kerberos with Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - Digest authentication is used.<br>Selecting an authentication method will provide two additional fields for entering a user name and password.<br>User macros can be used in user and password fields.| |*SSL verify peer*|Mark the checkbox to verify the SSL certificate of the web server.<br>The server certificate will be automatically taken from system-wide certificate authority (CA) location. You can override the location of CA files using Zabbix server or proxy configuration parameter [SSLCALocation](/manual/appendix/config/zabbix_server).<br>This sets the [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL option.| |*SSL verify host*|Mark the checkbox to verify that the *Common Name* field or the *Subject Alternate Name* field of the web server certificate matches.<br>This sets the [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL option.| |*SSL certificate file*|Name of the SSL certificate file used for client authentication. The certificate file must be in PEM^1^ format. If the certificate file contains also the private key, leave the *SSL key file* field empty. If the key is encrypted, specify the password in *SSL key password* field. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL option.| |*SSL key file*|Name of the SSL private key file used for client authentication. The private key file must be in PEM^1^ format. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL option.| |*SSL key password*|SSL private key file password.<br>User macros can be used in this field.<br>This sets the [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL option.| ::: noteimportant \[1\] Zabbix supports certificate and private key files in PEM format only. In case you have your certificate and private key data in PKCS \#12 format file (usually with extension \*.p12 or \*.pfx) you may generate the PEM file from it using the following commands: openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes -out ssl-cert.key ::: ::: noteclassic Zabbix server picks up changes in certificates without a restart. ::: ::: noteclassic If you have client certificate and private key in a single file just specify it in a "SSL certificate file" field and leave "SSL key file" field empty. The certificate and key must still be in PEM format. Combining certificate and key is easy: cat client.crt client.key > client.pem ::: #### Configuration de l'authentification L'onglet **Authentification** vous permet de configurer les options d'authentification du scénario. Un point vert à côté du nom de l'onglet indique qu'un certain type d'authentification HTTP est activé.  Paramètres d'authentification : |Paramètre|Description| |--|--------| |*Authentification*|Options d'authentification.<br>**Aucun** - aucune authentification utilisée.<br>**Basique** - l'authentification de base est utilisée.<br>**NTLM** - l'authentification NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) est utilisée.<br>**Kerberos** : l'authentification Kerberos est utilisée. Voir aussi : [Configuration de Kerberos avec Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - L'authentification Digest est utilisée.<br>La sélection d'une méthode d'authentification fournira deux champs supplémentaires pour entrer un utilisateur nom et mot de passe.<br>Des macros utilisateur peuvent être utilisées dans les champs utilisateur et mot de passe.| |*Vérifier le pair SSL*|Cochez la case pour vérifier le certificat SSL du serveur Web.<br>Le certificat du serveur sera automatiquement extrait de l'emplacement de l'autorité de certification (CA) à l'échelle du système. Vous pouvez remplacer l'emplacement des fichiers CA à l'aide du serveur Zabbix ou du paramètre de configuration proxy [SSLCALocation](/manual/appendix/config/zabbix_server).<br>Cela définit l'option cURL [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html).| |*Vérifier l'hôte SSL*|Cochez la case pour vérifier que le champ *Common Name* ou le champ *Subject Alternate Name* du certificat de serveur Web correspond.<br>Cela définit l'option cURL [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html).| |*Fichier de certificat SSL*|Nom du fichier de certificat SSL utilisé pour l'authentification du client. Le fichier de certificat doit être au format PEM^1^. Si le fichier de certificat contient également la clé privée, laissez le champ *fichier de clé SSL* vide. Si la clé est cryptée, indiquez le mot de passe dans le champ *mot de passe de la clé SSL*. Le répertoire contenant ce fichier est spécifié par le paramètre de configuration du serveur Zabbix ou du proxy [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>Les macros `HOST.*` et les macros utilisateur peuvent être utilisées dans ce champ.<br> Cela définit l'option cURL [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html).| |*Fichier de clé SSL*|Nom du fichier de clé privée SSL utilisé pour l'authentification du client. Le fichier de clé privée doit être au format PEM^1^. Le répertoire contenant ce fichier est spécifié par le paramètre de configuration du serveur ou du proxy Zabbix [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>Les macros `HOST.*` et les macros utilisateur peuvent être utilisées dans ce champ.<br> Cela définit l'option cURL [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html).| |*Mot de passe de la clé SSL*|Mot de passe du fichier de clé privée SSL.<br>Des macros utilisateur peuvent être utilisées dans ce champ.<br>Cela définit l'option cURL [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html).| ::: noteimportant \[1\] Zabbix prend uniquement en charge les fichiers de certificat et de clé privée au format PEM. Si vous avez votre certificat et vos données de clé privée dans un fichier au format PKCS \#12 (généralement avec l'extension \*.p12 ou \*.pfx), vous pouvez générer le fichier PEM à partir de celui-ci à l'aide des commandes suivantes : openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes -out ssl-cert.key ::: ::: noteclassic Le serveur Zabbix récupère les modifications des certificats sans redémarrage. ::: ::: noteclassic Si vous avez un certificat client et une clé privée dans un seul fichier, spécifiez-le simplement dans un champ "Fichier de certificat SSL" et laissez le champ "Fichier de clé SSL" vide. Le certificat et la clé doivent toujours être au format PEM. Combiner certificat et clé est simple : cat client.crt client.key > client.pem ::: #### Configuring a web scenario To configure a web scenario: - Go to: *Configuration → Hosts* (or *Templates*) - Click on *Web* in the row of the host/template - Click on *Create scenario* to the right (or on the scenario name to edit an existing scenario) - Enter parameters of the scenario in the form The **Scenario** tab allows you to configure the general parameters of a web scenario.  All mandatory input fields are marked with a red asterisk. Scenario parameters: |Parameter|Description| |--|--------| |*Host*|Name of the host/template that the scenario belongs to.| |*Name*|Unique scenario name.| |*Update interval*|How often the scenario will be executed.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported. *Note* that if a user macro is used and its value is changed (e.g. 5m → 30s), the next check will be executed according to the previous value (farther in the future with the example values).| |*Attempts*|The number of attempts for executing web scenario steps. In case of network problems (timeout, no connectivity, etc) Zabbix can repeat executing a step several times. The figure set will equally affect each step of the scenario. Up to 10 attempts can be specified, default value is 1.<br>*Note*: Zabbix will not repeat a step because of a wrong response code or the mismatch of a required string.| |*Agent*|Select a client agent.<br>Zabbix will pretend to be the selected browser. This is useful when a website returns different content for different browsers.<br>User macros can be used in this field.| |*HTTP proxy*|You can specify an HTTP proxy to use, using the format `[protocol://][username[:password]@]proxy.example.com[:port]`.<br>This sets the [CURLOPT\_PROXY](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html) cURL option.<br>The optional `protocol://` prefix may be used to specify alternative proxy protocols (the protocol prefix support was added in cURL 7.21.7). With no protocol specified, the proxy will be treated as an HTTP proxy.<br>By default, 1080 port will be used.<br>If specified, the proxy will overwrite proxy related environment variables like http\_proxy, HTTPS\_PROXY. If not specified, the proxy will not overwrite proxy-related environment variables. The entered value is passed on "as is", no sanity checking takes place.<br>You may also enter a SOCKS proxy address. If you specify the wrong protocol, the connection will fail and the item will become unsupported.<br>*Note* that only simple authentication is supported with HTTP proxy.<br>User macros can be used in this field.| |*Variables*|Variables that may be used in scenario steps (URL, post variables).<br>They have the following format:<br>**{macro1}**=value1<br>**{macro2}**=value2<br>**{macro3}**=regex:<regular expression><br>For example:<br>{username}=Alexei<br>{password}=kj3h5kJ34bd<br>{hostid}=regex:hostid is (\[0-9\]+)<br>The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values. Note that variables with `regex:` need one step to get the value of the regular expression so the extracted value can only be applied to the step after.<br>If the value part starts with `regex:` then the part after it is treated as a regular expression that searches the web page and, if found, stores the match in the variable. At least one subgroup must be present so that the matched value can be extracted.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.<br>Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.| |*Headers*|HTTP Headers are used when performing a request. Default and custom headers can be used.<br>Headers will be assigned using default settings depending on the Agent type selected from a drop-down list on a scenario level, and will be applied to all the steps, unless they are custom defined on a step level.<br>**It should be noted that defining the header on a step level automatically discards all the previously defined headers, except for a default header that is assigned by selecting the 'User-Agent' from a drop-down list on a scenario level.**<br>However, even the 'User-Agent' default header can be overridden by specifying it on a step level.<br>To unset the header on a scenario level, the header should be named and attributed with no value on a step level.<br>Headers should be listed using the same syntax as they would appear in the HTTP protocol, optionally using some additional features supported by the [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL option.<br>For example:<br>Accept-Charset=utf-8<br>Accept-Language=en-US<br>Content-Type=application/xml; charset=utf-8<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Enabled*|The scenario is active if this box is checked, otherwise - disabled.| Note that when editing an existing scenario, two extra buttons are available in the form: | | | |--|--------| ||Create another scenario based on the properties of the existing one.| ||Delete history and trend data for the scenario. This will make the server perform the scenario immediately after deleting the data.| ::: notetip If *HTTP proxy* field is left empty, another way for using an HTTP proxy is to set proxy related environment variables. For HTTP checks - set the **http\_proxy** environment variable for the Zabbix server user. For example, `http_proxy=http://proxy_ip:proxy_port`. For HTTPS checks - set the **HTTPS\_PROXY** environment variable. For example, `HTTPS_PROXY=http://proxy_ip:proxy_port`. More details are available by running a shell command: *\# man curl*. ::: The **Steps** tab allows you to configure the web scenario steps. To add a web scenario step, click on *Add* in the *Steps* block. {width="600"} ::: noteclassic Secret [user macros](/manual/config/macros/user_macros#configuration) must not be used in URLs as they will resolve to "\*\*\*\*\*\*". ::: #### Configurer un scenario web Pour configurer un scenario web : - Allez dans : *Configuration → Hôtes* (or *Modèles*) - Cliquez sur *Web* dans la ligne de l'hôte/modèle - Cliquez sur *Créer un scénario web* à droite (ou sur le nom du scénario pour modifier un scénario existant) - Entrez les paramètres du scénario dans le formulaire L'onglet **Scénario** vous permet de configurer les paramètres généraux d'un scénario Web.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Paramètres de scénario : | Paramètre |Description| |---------|-----------| |* Hôte*|Nom de l'hôte/modèle auquel le scénario appartient.| |*Nom*|Nom unique du scénario.| |*Intervalle d'actualisation*|A quelle fréquence le scénario sera exécuté.<br>[Les suffixes de temps](/manual/appendix/suffixes) sont supportés, ex : 30s, 1m, 2h, 1d.<br>[Les macros utilisateurs](/manual/config/macros/user_macros) sont supportées. *A noter :* si une macro utilisateur est utilisée et que sa valeur change (e.g. 5m → 30s), la prochaine vérification sera exécutée selon la valeur précédente (plus tard dans le futur avec les valeurs d'exemple).| |* Tentatives*Nombre de tentatives d'exécution des étapes du scénario Web. En cas de problèmes réseau (timeout, absence de connectivité, etc.), Zabbix peut répéter plusieurs fois l'exécution d'une étape. Le chiffre positionné affectera également chaque étape du scénario. Vous pouvez spécifier jusqu'à 10 tentatives, la valeur par défaut est 1.<br>*A noter* : Zabbix ne répètera pas une étape en raison d'un code de réponse erroné ou d'une non-concordance d'une chaîne requise.| |*Agent*|Choix du client.<br>Zabbix fera semblant d'être le navigateur sélectionné. Ceci est utile lorsqu'un site Web renvoie un contenu différent pour différents navigateurs.<br>Les macros utilisateur peuvent être utilisées dans ce champ.| |*Proxy HTTP*|Vous pouvez spécifier un proxy HTTP à utiliser, en utilisant le format `[protocol://][username[:password]@]proxy.example.com[:port]`.<br>Cela définit l'option cURL [CURLOPT\_PROXY](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html).<br>Le préfixe facultatif `protocol://` peut être utilisé pour spécifier des protocoles proxy alternatifs (la prise en charge du préfixe de protocole a été ajoutée dans cURL 7.21.7). Sans protocole spécifié, le proxy sera traité comme un proxy HTTP.<br>Par défaut, le port 1080 sera utilisé.<br>Si spécifié, le proxy écrasera les variables d'environnement liées au proxy comme HTTP\_PROXY, HTTPS\_PROXY. S'il n'est pas spécifié, le proxy n'écrasera pas les variables d'environnement liées au proxy. La valeur saisie est transmise "telle quelle", aucune vérification de cohérence n'a lieu.<br>Vous pouvez également entrer une adresse proxy SOCKS. Si vous spécifiez le mauvais protocole, la connexion échouera et l'élément ne sera plus pris en charge.<br>*A noter* : seule l'authentification simple est prise en charge avec le proxy HTTP.<br>Les macros utilisateur peuvent être utilisées dans ce champ.| |* Variables*|Variables pouvant être utilisées dans les étapes du scénario (URL, variables post).<br>Elles ont le format suivant :<br>**{macro1}**=value1<br>**{macro2}**=value2<br>**{macro3}**=regex:<regular expression><br>Par exemple :<br>{username}=Alexei<br>{password}=kj3h5kJ34bd<br>{hostid}=regex:hostid is (\[0-9\]+)<br>Les macros peuvent ensuite être référencées dans les étapes sous la forme {username}, {password} et {hostid}. Zabbix les remplacera automatiquement par des valeurs réelles. Notez que les variables avec `regex:` ont besoin d'une étape pour obtenir la valeur de l'expression régulière afin que la valeur extraite ne puisse être appliquée qu'à l'étape suivante.<br>Si la partie valeur commence par `regex:` la partie après celle-ci est traitée comme une expression régulière qui recherche la page Web et, si elle est trouvée, stocke la correspondance dans la variable. Au moins un sous-groupe doit être présent pour que la valeur correspondante puisse être extraite. <br>Les macros utilisateur et les [macros](/manual/appendix/macros/supported_by_location) {HOST.\*} sont prises en charge.<br>Les variables sont automatiquement encodées en URL lorsqu'elles sont utilisées dans des champs de requête ou des données de formulaire pour des variables post, mais doivent être encodées manuellement lorsqu'elles sont utilisées en post brut ou directement dans l'URL.| |*En-têtes*|Les en-têtes HTTP personnalisés qui seront envoyés lors de l'exécution d'une requête.<br>Les en-têtes doivent être répertoriés en utilisant la même syntaxe qu'ils apparaîssent dans le protocole HTTP, en utilisant éventuellement certaines fonctionnalités supplémentaires prises en charge par l'option cURL [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL option.<br>Par exemple :<br>Accept-Charset=utf-8<br>Accept-Language=en-US<br>Content-Type=application/xml; charset=utf-8<br>Les macros utilisateur et les [macros](/manual/appendix/macros/supported_by_location) {HOST.\*} sont supportées.| |*Activé*|Le scénario est activé si cette case est cochée, sinon - désactivé.| Notez que lors de l'édition d'un scénario existant, deux boutons supplémentaires sont disponibles dans le formulaire : | | | |--|--------| ||Créer un autre scénario basé sur les propriétés d'un scénario existant.| ||Supprimer l'historique et les données de tendance du scénario. Cela obligera le serveur à exécuter le scénario immédiatement après la suppression des données.| ::: notetip Si le champs *HTTP proxy* est laissé vide, un autre moyen d'utiliser un proxy HTTP est de positionner les variables d'environnement liées au proxy. Pour les vérifications HTTP - positionnez la variable d'environnement **HTTP\_PROXY** pour l'utilisateur du serveur Zabbix. Par exemple, `HTTP_PROXY=http://proxy_ip:proxy_port`. Pour les vérifications HTTPS - positionnez la variable d'environnement **HTTPS\_PROXY** pour l'utilisateur du serveur Zabbix. Par exemple, `HTTPS_PROXY=http://proxy_ip:proxy_port`. Plus de détails sont disponibles en exécutant la commande : *\# man curl*. ::: L'onglet **Étapes** vous permet de configurer les étapes du scénario web. Pour ajouter une étape d'un scénario web, cliquez sur *Ajouter* dans le bloc *Étapes*. {width="600"} ::: noteclassic Les [macros utilisateur secrètes](/manual/config/macros/user_macros#configuration) ne doivent pas être utilisées dans les URL car elles seront résolue en "\*\*\*\*\*\*". ::: #### Configuring certificate on Zabbix server 1\. In order to verify peer certificates, Zabbix server must have access to file with their top-level self-signed root CA certificates. For example, if we expect certificates from two independent root CAs, we can put their certificates into file `/home/zabbix/zabbix_ca_file` like this: Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE ... -----BEGIN CERTIFICATE----- MIID2jCCAsKgAwIBAgIBATANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB .... 9wEzdN8uTrqoyU78gi12npLj08LegRKjb5hFTVmO -----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) .... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE .... -----BEGIN CERTIFICATE----- MIID3DCCAsSgAwIBAgIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQB ... vdGNYoSfvu41GQAR5Vj5FnRJRzv5XQOZ3B6894GY1zY= -----END CERTIFICATE----- 2\. Put Zabbix server certificate chain into file, for example, `/home/zabbix/zabbix_server.crt`: Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Zabbix server Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Digital Signature, Key Encipherment X509v3 Basic Constraints: CA:FALSE ... -----BEGIN CERTIFICATE----- MIIECDCCAvCgAwIBAgIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixk ... h02u1GHiy46GI+xfR3LsPwFKlkTaaLaL/6aaoQ== -----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: 2 (0x2) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE, pathlen:0 ... -----BEGIN CERTIFICATE----- MIID4TCCAsmgAwIBAgIBAjANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB ... dyCeWnvL7u5sd6ffo8iRny0QzbHKmQt/wUtcVIvWXdMIFJM0Hw== -----END CERTIFICATE----- Here the first is Zabbix server certificate, followed by intermediate CA certificate. 3\. Put Zabbix server private key into file, for example, `/home/zabbix/zabbix_server.key`: -----BEGIN PRIVATE KEY----- MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAAoIBAQC9tIXIJoVnNXDl ... IJLkhbybBYEf47MLhffWa7XvZTY= -----END PRIVATE KEY----- 4\. Edit TLS parameters in Zabbix server configuration file like this: TLSCAFile=/home/zabbix/zabbix_ca_file TLSCertFile=/home/zabbix/zabbix_server.crt TLSKeyFile=/home/zabbix/zabbix_server.key #### Configuration du certificat sur le serveur Zabbix 1\. Afin de vérifier les certificats homologues, le serveur Zabbix doit avoir accès aux fichiers avec leurs certificats d'autorité de certification racine auto-signés de niveau supérieur. Par exemple, si nous souhaitons des certificats de deux autorités de certification racine indépendantes, nous pouvons placer leurs certificats dans un fichier `/home/zabbix/zabbix_ca_file` ainsi : Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE ... -----BEGIN CERTIFICATE----- MIID2jCCAsKgAwIBAgIBATANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB .... 9wEzdN8uTrqoyU78gi12npLj08LegRKjb5hFTVmO -----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) .... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE .... -----BEGIN CERTIFICATE----- MIID3DCCAsSgAwIBAgIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQB ... vdGNYoSfvu41GQAR5Vj5FnRJRzv5XQOZ3B6894GY1zY= -----END CERTIFICATE----- 2\. Placer la chaîne de certificats du serveur Zabbix dans un fichier, par exemple, `/home/zabbix/zabbix_server.crt` : Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Zabbix server Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Digital Signature, Key Encipherment X509v3 Basic Constraints: CA:FALSE ... -----BEGIN CERTIFICATE----- MIIECDCCAvCgAwIBAgIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixk ... h02u1GHiy46GI+xfR3LsPwFKlkTaaLaL/6aaoQ== -----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: 2 (0x2) Signature Algorithm: sha1WithRSAEncryption Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA ... Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) ... X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE, pathlen:0 ... -----BEGIN CERTIFICATE----- MIID4TCCAsmgAwIBAgIBAjANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB ... dyCeWnvL7u5sd6ffo8iRny0QzbHKmQt/wUtcVIvWXdMIFJM0Hw== -----END CERTIFICATE----- Ici, le premier est le certificat du serveur Zabbix, suivi du certificat intermédiaire de l'autorité de certification. 3\. Placer la clé privée du serveur Zabbix dans un fichier, par exemple, `/home/zabbix/zabbix_server.key` : -----BEGIN PRIVATE KEY----- MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAAoIBAQC9tIXIJoVnNXDl ... IJLkhbybBYEf47MLhffWa7XvZTY= -----END PRIVATE KEY----- 4\. Modifier les paramètres TLS dans le fichier de configuration du serveur Zabbix comme suit : TLSCAFile=/home/zabbix/zabbix_ca_file TLSCertFile=/home/zabbix/zabbix_server.crt TLSKeyFile=/home/zabbix/zabbix_server.key #### Configuring JMX interfaces and items in Zabbix frontend With Java gateway running, server knowing where to find it and a Java application started with support for remote JMX monitoring, it is time to configure the interfaces and items in Zabbix GUI. #### Configuration des interfaces et des éléments JMX dans l'interface Zabbix Avec la passerelle Java en cours d'exécution, le serveur sachant où trouver la passerelle et une application Java démarrée avec la prise en charge de la surveillance JMX à distance, il est temps de configurer les interfaces et les éléments dans l'interface web de Zabbix. #### Configuring low-level discovery rules See the [low-level discovery](/manual/discovery/low_level_discovery) section of the manual. #### Configuration des règles de découverte de bas niveau Voir la section [découverte de bas niveau](/manual/discovery/low_level_discovery) du manuel. #### Configuring nested templates To link templates, you need to take an existing template or a new one, and then: - Open the [template configuration form](/manual/config/templates/template#creating-a-template) - Find the *Templates* field - Click *Select* to open the *Templates* popup window - In the popup window, choose required templates, then click *Select* to add the templates to the list - Click *Add* or *Update* in the template configuration form Thus, all entities of the parent template, as well as all entities of linked templates (such as items, triggers, graphs, etc.) will now appear in the template configuration, except for linked template dashboards, which will, nevertheless, be inherited by hosts. To unlink any of the linked templates, in the same form use the *Unlink* or *Unlink and clear* buttons and click *Update*. Choosing the *Unlink* option will simply remove the association with the linked template, while not removing all its entities (items, triggers, graphs, etc.). Choosing the *Unlink and clear* option will remove both the association with the linked template and all its entities (items, triggers, graphs, etc.). #### Configuration de modèles imbriqués Pour lier des modèles, vous devez prendre un modèle existant ou un nouveau, puis : - Ouvrir le [formulaire de configuration du modèle](/manual/config/templates/template#creating-a-template) - Trouver le champ *Modèles* - Cliquer sur *Sélectionner* pour ouvrir la fenêtre contextuelle *Modèles* - Dans la fenêtre contextuelle, choisir les modèles requis, puis cliquer sur *Sélectionner* pour ajouter les modèles à la liste - Cliquer sur *Ajouter* ou *Mettre à jour* dans le formulaire de configuration du modèle Ainsi, toutes les entités du modèle parent, ainsi que toutes les entités des modèles liés (tels que les éléments, les déclencheurs, les graphiques, etc.) apparaîtront désormais dans la configuration du modèle, à l'exception des tableaux de bord du modèle lié, qui seront néanmoins hérités. par les hôtes. Pour dissocier l'un des modèles liés, dans le même formulaire, utiliser les boutons *Dissocier* ou *Dissocier et effacer* et cliquer sur *Mettre à jour*. Choisir l'option *Dissocier* supprimera simplement l'association avec le modèle lié, sans supprimer toutes ses entités (éléments, déclencheurs, graphiques, etc.). Choisir l'option *Dissocier et effacer* supprimera à la fois l'association avec le modèle lié et toutes ses entités (éléments, déclencheurs, graphiques, etc.). ##### Configuring Perl trap receiver Requirements: Perl, Net-SNMP compiled with --enable-embedded-perl (done by default since Net-SNMP 5.4) A Perl trap receiver (look for misc/snmptrap/zabbix\_trap\_receiver.pl) can be used to pass traps to Zabbix server directly from snmptrapd. To configure it: - add the Perl script to the snmptrapd configuration file (snmptrapd.conf), e.g.: perl do "[FULL PATH TO PERL RECEIVER SCRIPT]"; - configure the receiver, e.g: $SNMPTrapperFile = '[TRAP FILE]'; $DateTimeFormat = '[DATE TIME FORMAT]'; ::: notetip If the script name is not quoted, snmptrapd will refuse to start up with messages, similar to these: Regexp modifiers "/l" and "/a" are mutually exclusive at (eval 2) line 1, at end of line Regexp modifier "/l" may not appear twice at (eval 2) line 1, at end of line ::: ##### Configuration du récepteur de traps Perl Pré-requis : Perl, Net-SNMP compilé avec --enable-embedded-perl (fait par défaut depuis Net-SNMP 5.4) Le récepteur de traps Perl (recherchez misc/snmptrap/zabbix\_trap\_receiver.pl) peut être utilisé pour transférer les traps au serveur Zabbix directement depuis snmptrapd. Pour le configurer : - ajouter le script perl au fichier de configuration snmptrapd (snmptrapd.conf), par exemple : perl do "[FULL PATH TO PERL RECEIVER SCRIPT]"; - configurer le récepteur, par exemple : $SNMPTrapperFile = '[TRAP FILE]'; $DateTimeFormat = '[DATE TIME FORMAT]'; ::: notetip Si le nom du script n'est pas entre quote, snmptrapd refusera de démarrer avec des messages similaires à ceux-ci : Regexp modifiers "/l" and "/a" are mutually exclusive at (eval 2) line 1, at end of line Regexp modifier "/l" may not appear twice at (eval 2) line 1, at end of line ::: #### Configuring PSK for server - active proxy communication (example) On the proxy, write the PSK value into a file, for example, `/home/zabbix/zabbix_proxy.psk`. The file must contain PSK in the first text string, for example: e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9 Set access rights to PSK file - it must be readable only by Zabbix user. Edit TLS parameters in proxy configuration file `zabbix_proxy.conf`, for example, set: TLSConnect=psk TLSPSKFile=/home/zabbix/zabbix_proxy.psk TLSPSKIdentity=PSK 002 The proxy will connect to server using PSK. PSK identity will be "PSK 002". (To minimize downtime see how to change connection type in [Connection encryption management](/manual/encryption#connection_encryption_management)). Configure PSK for this proxy in Zabbix frontend. Go to *Administration→Proxies*, select the proxy, go to "Encryption" tab. In "Connections from proxy" mark `PSK`. Paste into "PSK identity" field "PSK 002" and "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" into "PSK" field. Click "Update". Restart proxy. It will start using PSK-based encrypted connections to server. Check server and proxy logfiles for error messages. For a passive proxy the procedure is very similar. The only difference - set `TLSAccept=psk` in proxy configuration file and set "Connections to proxy" in Zabbix frontend to `PSK`. #### Configuration de PSK pour le serveur - communication d'un proxy actif (exemple) Sur le proxy, écrivez la valeur PSK dans un fichier, par exemple, `/home/zabbix/zabbix_proxy.psk`. Le fichier doit contenir le PSK dans la première chaîne de texte, par exemple : e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9 Définir les droits d’accès au fichier PSK - il ne doit être lisible que par l’utilisateur Zabbix. Modifier les paramètres TLS dans le fichier de configuration de proxy `zabbix_proxy.conf`, par exemple, définir : TLSConnect=psk TLSPSKFile=/home/zabbix/zabbix_proxy.psk TLSPSKIdentity=PSK 002 Le proxy se connecte au serveur en utilisant PSK. L'identité PSK sera "PSK 002". (Pour minimiser les temps d'interruption, modifier le type de connexion comme décrit dans [Gestion du chiffrement de la connexion](/manual/encryption#connection_encryption_management)). Configurer PSK pour ce proxy dans l'interface Zabbix. Aller dans *Administration → Proxies*, sélectionner le proxy et aller dans l'onglet "Chiffrement". Dans "Connexions du proxy", cocher `PSK`. Coller dans le champ "Identité PSK" "PSK 002" et "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" dans le champ "PSK". Cliquez sur "Actualiser". Redémarrer le proxy. Il commencera à utiliser des connexions au serveur chiffrées basées sur PSK. Vérifiez les fichiers journaux du serveur et du proxy à la recherche de messages d'erreur. Pour un proxy passif, la procédure est similaire. La seule différence est - définir `TLSAccept=psk` dans le fichier de configuration du proxy et définir "Connexions du proxy" dans l'interface Zabbix à `PSK`. #### Configuring server for use with Java gateway With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead. JavaGateway=192.168.3.14 JavaGatewayPort=10052 By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers. StartJavaPollers=5 Do not forget to restart server or proxy, once you are done with configuring them. #### Configuration du serveur pour utiliser la passerelle Java Avec la passerelle Java opérationnelle, vous devez indiquer au serveur Zabbix où trouver la passerelle Java Zabbix. Pour ce faire, indiquez les paramètres JavaGateway et JavaGatewayPort dans le [fichier de configuration du serveur](/fr/manual/appendix/config/zabbix_server). Si l'hôte sur lequel l'application JMX est en cours d'exécution est surveillé par le proxy Zabbix, spécifiez les paramètres de connexion dans le [fichier de configuration du proxy](/fr/manual/appendix/config/zabbix_proxy) à la place de celui du serveur. JavaGateway=192.168.3.14 JavaGatewayPort=10052 Par défaut, le serveur ne démarre aucun processus lié à la surveillance JMX. Toutefois, si vous souhaitez l’utiliser, vous devez spécifier le nombre d’instances prédéfinies de pollers Java. Vous faites cela de la même manière que vous spécifiez les pollers et les trappers. StartJavaPollers=5 N'oubliez pas de redémarrer le serveur ou le proxy, une fois que vous avez fini de les configurer. #### Configuring server for use with Java gateway With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead. JavaGateway=192.168.3.14 JavaGatewayPort=10052 By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers. StartJavaPollers=5 Do not forget to restart server or proxy, once you are done with configuring them. #### Configuration du serveur pour utiliser la passerelle Java Avec la passerelle Java opérationnelle, vous devez indiquer au serveur Zabbix où trouver la passerelle Java Zabbix. Pour ce faire, indiquez les paramètres JavaGateway et JavaGatewayPort dans le [fichier de configuration du serveur](/fr/manual/appendix/config/zabbix_server). Si l'hôte sur lequel l'application JMX est en cours d'exécution est surveillé par le proxy Zabbix, spécifiez les paramètres de connexion dans le [fichier de configuration du proxy](/fr/manual/appendix/config/zabbix_proxy) à la place de celui du serveur. JavaGateway=192.168.3.14 JavaGatewayPort=10052 Par défaut, le serveur ne démarre aucun processus lié à la surveillance JMX. Toutefois, si vous souhaitez l’utiliser, vous devez spécifier le nombre d’instances prédéfinies de pollers Java. Vous faites cela de la même manière que vous spécifiez les pollers et les trappers. StartJavaPollers=5 N'oubliez pas de redémarrer le serveur ou le proxy, une fois que vous avez fini de les configurer. #### Configuring server for use with Java gateway With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead. JavaGateway=192.168.3.14 JavaGatewayPort=10052 By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers. StartJavaPollers=5 Do not forget to restart server or proxy, once you are done with configuring them. #### Configuration du serveur pour utiliser la passerelle Java Avec la passerelle Java opérationnelle, vous devez indiquer au serveur Zabbix où trouver la passerelle Java Zabbix. Pour ce faire, indiquez les paramètres JavaGateway et JavaGatewayPort dans le [fichier de configuration du serveur](/manual/appendix/config/zabbix_server). Si l'hôte sur lequel l'application JMX est en cours d'exécution est surveillé par le proxy Zabbix, spécifiez les paramètres de connexion dans le [fichier de configuration du proxy](/manual/appendix/config/zabbix_proxy) à la place de celui du serveur. JavaGateway=192.168.3.14 JavaGatewayPort=10052 Par défaut, le serveur ne démarre aucun processus lié à la surveillance JMX. Toutefois, si vous souhaitez l’utiliser, vous devez spécifier le nombre d’instances prédéfinies de pollers Java. Vous faites cela de la même manière que vous spécifiez les pollers et les trappers. StartJavaPollers=5 N'oubliez pas de redémarrer le serveur ou le proxy, une fois que vous avez fini de les configurer. #### Configuring server for use with Java gateway With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead. JavaGateway=192.168.3.14 JavaGatewayPort=10052 By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers. StartJavaPollers=5 Do not forget to restart server or proxy, once you are done with configuring them. #### Configuration du serveur pour une utilisation avec la passerelle Java Avec la passerelle Java opérationnelle, vous devez indiquer au serveur Zabbix où trouver la passerelle Java Zabbix. Pour ce faire, indiquez les paramètres JavaGateway et JavaGatewayPort dans le [fichier de configuration du serveur](/fr/manual/appendix/config/zabbix_server). Si l'hôte sur lequel l'application JMX est en cours d'exécution est surveillé par le proxy Zabbix, spécifiez les paramètres de connexion dans le [fichier de configuration du proxy](/fr/manual/appendix/config/zabbix_proxy) à la place de celui du serveur. JavaGateway=192.168.3.14 JavaGatewayPort=10052 Par défaut, le serveur ne démarre aucun processus lié à la surveillanceJMX. Toutefois, si vous souhaitez l’utiliser, vous devez spécifier le nombre d’instances prédéfinies de pollers Java. Vous faites cela de la même manière que vous spécifiez les pollers et les trappers. StartJavaPollers=5 N'oubliez pas de redémarrer le serveur ou le proxy, une fois que vous avez fini de les configurer. #### Configuring SNMP monitoring To start monitoring a device through SNMP, the following steps have to be performed: #### Configuration de la surveillance SNMP Pour démarrer la surveillance d'un appareil via SNMP, les étapes suivantes doivent être effectuées : ##### Configuring SNMPTT At first, snmptrapd should be configured to use SNMPTT. ::: notetip For the best performance, SNMPTT should be configured as a daemon using **snmptthandler-embedded** to pass the traps to it. See instructions for [configuring SNMPTT](http://snmptt.sourceforge.net/docs/snmptt.shtml). ::: When SNMPTT is configured to receive the traps, configure `snmptt.ini`: 1. enable the use of the Perl module from the NET-SNMP package: net\_snmp\_perl\_enable = 1 2. log traps to the trap file which will be read by Zabbix: log_enable = 1 log_file = [TRAP FILE] 3. set the date-time format: date_time_format = %H:%M:%S %Y/%m/%d = [DATE TIME FORMAT] ::: notewarning The "net-snmp-perl" package has been removed in RHEL 8.0-8.2; re-added in RHEL 8.3. For more information, see the [known issues](/manual/installation/known_issues#snmp_traps). ::: Now format the traps for Zabbix to recognize them (edit snmptt.conf): 1. Each FORMAT statement should start with "ZBXTRAP \[address\]", where \[address\] will be compared to IP and DNS addresses of SNMP interfaces on Zabbix. E.g.: EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal FORMAT ZBXTRAP $aA Device reinitialized (coldStart) 2. See more about SNMP trap format below. ::: noteimportant Do not use unknown traps - Zabbix will not be able to recognize them. Unknown traps can be handled by defining a general event in snmptt.conf:\ EVENT general .\* "General event" Normal ::: ##### Configuration de SNMPTT Dans un premier temps, snmptrapd doit être configuré pour utiliser SNMPTT. ::: notetip Pour des performances optimales, SNMPTT doit être configuré en tant que démon à l'aide de **snmptthandler-embedded** pour lui transmettre les interruptions. Voir les instructions pour [configurer SNMPTT](http://snmptt.sourceforge.net/docs/snmptt.shtml). ::: Lorsque SNMPTT est configuré pour recevoir les traps, configurer `snmptt.ini` : 1. activer l'utilisation du module Perl du package NET-SNMP : net\_snmp\_perl\_enable = 1 2. logger les traps dans le fichier trap qui sera lu par Zabbix : log_enable = 1 log_file = [TRAP FILE] 3. définir le format date-heure : date_time_format = %H:%M:%S %Y/%m/%d = [DATE TIME FORMAT] ::: notewarning Le package "net-snmp-perl" a été supprimé dans RHEL 8.0-8.2 ; rajouté dans RHEL 8.3. Pour plus d'informations, consultez les [problèmes connus](/manual/installation/known_issues#snmp_traps). ::: Formater les traps pour que Zabbix les reconnaisse (éditer snmptt.conf): 1. Chaque instruction FORMAT doit commencer par "ZBXTRAP \[address\]", où \[address\] sera comparée aux adresses IP et DNS des interfaces SNMP sur Zabbix. Par exemple.: EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal FORMAT ZBXTRAP $aA Device reinitialized (coldStart) 2. En savoir plus sur le format d'interruption SNMP ci-dessous. ::: noteimportant N'utilisez pas de traps inconnus - Zabbix ne pourra pas les reconnaître. Les traps inconnues peuvent être gérés en définissant un événement général dans snmptt.conf:\ EVENT general .\* "General event" Normal ::: #### Configuring steps {width="600"} Step parameters: |Parameter|Description| |--|--------| |*Name*|Unique step name.| |*URL*|URL to connect to and retrieve data. For example:<br>https://www.example.com<br>http://www.example.com/download<br>Domain names can be specified in Unicode characters. They are automatically punycode-converted to ASCII when executing the web scenario step.<br>The *Parse* button can be used to separate optional query fields (like ?name=Admin&password=mypassword) from the URL, moving the attributes and values into *Query fields* for automatic URL-encoding.<br>Variables can be used in the URL, using the {macro} syntax. Variables can be URL-encoded manually using a {{macro}.urlencode()} syntax.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.<br>Limited to 2048 characters.| |*Query fields*|HTTP GET variables for the URL.<br>Specified as attribute and value pairs.<br>Values are URL-encoded automatically. Values from scenario variables, user macros or {HOST.\*} macros are resolved and then URL-encoded automatically. Using a {{macro}.urlencode()} syntax will double URL-encode them.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Post*|HTTP POST variables.<br>In **Form data** mode, specified as attribute and value pairs.<br>Values are URL-encoded automatically. Values from scenario variables, user macros or {HOST.\*} macros are resolved and then URL-encoded automatically.<br>In **Raw data** mode, attributes/values are displayed on a single line and concatenated with a **&** symbol.<br>Raw values can be URL-encoded/decoded manually using a {{macro}.urlencode()} or {{macro}.urldecode()} syntax.<br>For example: id=2345&userid={user}<br>If {user} is defined as a variable of the web scenario, it will be replaced by its value when the step is executed. If you wish to URL-encode the variable, substitute {user} with {{user}.urlencode()}.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Variables*|Step-level variables that may be used for GET and POST functions.<br>Specified as attribute and value pairs.<br>Step-level variables override scenario-level variables or variables from the previous step. However, the value of a step-level variable only affects the step after (and not the current step).<br>They have the following format:<br>**{macro}**=value<br>**{macro}**=regex:<regular expression><br>For more information see variable description on the [scenario](web_monitoring#configuring_a_web_scenario) level.<br>Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.| |*Headers*|Custom HTTP headers that will be sent when performing a request.<br>Specified as attribute and value pairs.<br>A header defined on a step level will be used for that particular step.<br>**It should be noted that defining the header on a step level automatically discards all the previously defined headers, except for a default header that is assigned by selecting the 'User-Agent' from a drop-down list on a scenario level.**<br>However, even the 'User-Agent' default header can be overridden by specifying it on a step level.<br>For example, assigning the name to a header, but setting no value will unset the default header on a scenario level.<br>User macros and {HOST.\*} macros are supported.<br>This sets the [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL option.<br>Specifying custom headers is supported *starting with Zabbix 2.4*.| |*Follow redirects*|Mark the checkbox to follow HTTP redirects.<br>This sets the [CURLOPT\_FOLLOWLOCATION](http://curl.haxx.se/libcurl/c/CURLOPT_FOLLOWLOCATION.html) cURL option.| |*Retrieve mode*|Select the retrieve mode:<br>**Body** - retrieve only body from the HTTP response<br>**Headers** - retrieve only headers from the HTTP response<br>**Body and headers** - retrieve body and headers from the HTTP response| |*Timeout*|Zabbix will not spend more than the set amount of time on processing the URL (from one second to maximum of 1 hour). Actually this parameter defines the maximum time for making connection to the URL and maximum time for performing an HTTP request. Therefore, Zabbix will not spend more than **2 x Timeout** seconds on the step.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 1h. [User macros](/manual/config/macros/user_macros) are supported.| |*Required string*|Required regular expression pattern.<br>Unless retrieved content (HTML) matches the required pattern the step will fail. If empty, no check on required string is performed.<br>For example:<br>Homepage of Zabbix<br>Welcome.\*admin<br>*Note*: Referencing [regular expressions](regular_expressions) created in the Zabbix frontend is not supported in this field.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Required status codes*|List of expected HTTP status codes. If Zabbix gets a code which is not in the list, the step will fail.<br>If empty, no check on status codes is performed.<br>For example: 200,201,210-299<br>User macros are supported.| ::: noteclassic Any changes in web scenario steps will only be saved when the whole scenario is saved. ::: See also a [real-life example](/manual/web_monitoring/example) of how web monitoring steps can be configured. #### Configuration des étapes {width="600"} Paramètres d'étape : |Paramètre|Description| |--|--------| |*Nom*|Nom unique de l'étape.| |*URL*|URL où se connecter et où récupérer les données. Par exemple :<br>https://www.example.com<br>http://www.example.com/download<br>Les noms de domaines peuvent être spécifiés en caractères Unicode. Ils sont automatiquement convertis en ASCII lors de l'exécution de l'étape du scénario web. <br>Le bouton *Analyser* peut être utilisé pour séparer les champs de requête facultatifs (comme ?name=Admin&password=mypassword) de l'URL, et ainsi placer les attributs et les valeurs dans le *Champs de requête* pour un encodage automatique d'URL.<br>Variables can be used in the URL, using the {macro} syntax. Les variables peuvent être utilisées dans l'URL, en utilisant la syntaxe {macro}. Les variables peuvent être encodée manuellement en utilisant la syntaxe {{macro}.urlencode()}.<br>Les macros utilisateurs et les [macros](/manual/appendix/macros/supported_by_location) {HOST.\*} sont supportées.<br>Limité à 2048 caractères.| |*Champs de requête*|Variables HTTP GET pour l'URL.<br>Spécifié comme paires attribut/valeur.<br>Les valeurs sont automatiquement encodées en URL. Les valeurs des variables de scénario, des macros utilisateur ou des macros {HOST.\*} sont résolues puis automatiquement codées en URL. L'utilisation d'une syntaxe {{macro}.urlencode()} doublera leur encodage URL.<br>Les macros utilisateurs et les [macros](/manual/appendix/macros/supported_by_location) {HOST.\*} sont supportées.| |*Post*|Variables HTTP POST.<br>Dans le mode **Données de formulaire**, spécifié comme paires attribut/valeur.<br>Les valeurs sont encodées automatiquement. Les valeurs issues des variables de scénario, les macros utilisateurs ou les macros {HOST.*} sont résolues et sont encodées automatiquement.<br>Dans le mode **Données brutes**, les paires attribut/valeur sont affichées sur une seule ligne et concaténées avec le symbole **&**.<br>Les valeurs brutes peuvent être encodées/décodées manuellement en utilisant une syntaxe {{macro}.urlencode()} ou {{macro}.urldecode()}.<br>Par exemple : id=2345&userid={user}<br>Si {user} est défini comme variable du scénario web, il sera remplacé par sa valeur lors de l'exécution de l'étape. Si vous souhaitez encoder la variable au format URL, il faut substituer {user} par {{user}.urlencode()}.<br>Les macros utilisateurs et les [macros](/manual/appendix/macros/supported_by_location) {HOST.*} sont supportées.| |*Variables*|Variables qui peuvent être utilisées pour les fonctions GET et POST dans l'étape.<br>Spécifié comme paires d'attribut/valeur.<br>Les variables d'étape remplacent les variables de scénario ou les variables de l'étape précédente. Néanmoins, la valeur d'une variable d'étape affecte uniquement l'étape suivante (et non pas l'étape actuelle).<br>Elles ont le format suivant :<br>**{macro}**=value<br>**{macro}**=regex:<regular expression><br>Pour plus d'informations, voir la description des variables au niveau du [scenario](web_monitoring#configuring_a_web_scenario).<br>Les variables sont automatiquement encodées au format URL quand elles sont utilisées dans le champs de requête ou dans les données de formulaire pour les variables post, mais doivent être encodées manuellement quand elles sont utilisées dans les données brutes ou directement dans l'URL.| |*En-têtes*|En-têtes HTTP personnalisés à envoyer lors de l'exécution d'une requête.<br>Spécifié sous forme de paires d'attributs et de valeurs.<br>Les en-têtes au niveau de l'étape remplaceront les en-têtes spécifiés pour le scénario.<br>Par exemple, la définition d'un attribut 'User-Agent' sans valeur supprimera la valeur User-Agent définie au niveau du scénario.<br>Les macros utilisateurs et les macros {HOST.*} sont supportées.<br>Cela défini l'option cURL [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html).<br>La spécification des en-têtes personnalisés est supportée *depuis Zabbix 2.4*.| |*Suivre les redirections*|Cochez la case pour suivre les redirections HTTP.<br>Cela défini l'option cURL [CURLOPT\_FOLLOWLOCATION](http://curl.haxx.se/libcurl/c/CURLOPT_FOLLOWLOCATION.html).| |*Mode de récupération*|Sélectionnez le mode de récupération :<br>**Corps** - récupérer uniquement le corps de la réponse HTTP<br>**En-têtes** - récupérer uniquement les en-têtes de la réponse HTTP<br>**Corps et en-têtes** - récupérer le corps et les en-têtes de la réponse HTTP| |* Expiration*|Zabbix ne passera pas plus de temps que prévu à traiter l’URL (maximum 1 heure). En réalité, ce paramètre définit le délai maximal de connexion à l'URL et le délai maximal d'exécution d'une requête HTTP. Par conséquent, Zabbix ne passera pas plus de **2xExpiration* secondes sur l’étape.<br>[Les suffixes temporels](/manual/appendix/suffixes) sont supportés, ex : 30s, 1m, 1h. Les [macros utilisateur](/manual/config/macros/user_macros) sont supportées.| |*Chaîne requise*|Modèle requis d'expression régulière.<br>À moins que le contenu récupéré (HTML) ne corresponde au modèle requis, l'étape échouera. Si vide, aucune vérification sur la chaîne n'est effectuée.<br>Par exemple :<br>Homepage of Zabbix<br>Welcome.\*admin<br>*A noter* : [Les expressions régulières](regular_expressions) créées dans l'interface Zabbix ne sont pas supportées dans ce champs.<br>Les macros utilisateur et les [macros](/manual/appendix/macros/supported_by_location) {HOST.*} sont supportées.| |*Code d'état requis*|Liste des codes d'état HTTP attendus. Si Zabbix obtient un code qui ne figure pas dans la liste, l'étape échouera.<br>S'il est vide, aucune vérification de code d'état n'est effectuée.<br>Par exemple : 200,201,210-299<br>Les macros utilisateur sont supportées.| ::: noteclassic Toute modification apportée aux étapes du scénario Web ne sera enregistrée que lorsque l'intégralité du scénario sera enregistré. ::: Voir aussi un [exemple concret](/manual/web_monitoring/example) de la configuration des étapes de surveillance Web. #### Configuring tags The **Tags** tab allows to define scenario-level [tags](/manual/config/tagging).  Tagging allows to filter web scenarios and web monitoring [items](/manual/web_monitoring/items). #### Configuration des tags L'onglet **Tags** permet de définir des [tags](/manual/config/tagging) au niveau du scénario.  Les tags permettent de filtrer les scénarios Web et les [éléments](/manual/web_monitoring/items) de surveillance Web. ##### Configuring Zabbix server/proxy To read the traps, Zabbix server or proxy must be configured to start the SNMP trapper process and point to the trap file that is being written by SNMPTT or a Bash/Perl trap receiver. To do that, edit the configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server) or [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)): StartSNMPTrapper=1 SNMPTrapperFile=[TRAP FILE] ::: notewarning If systemd parameter **[PrivateTmp](http://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=)** is used, this file is unlikely to work in */tmp*. ::: ##### Configuring Bash trap receiver Requirements: only snmptrapd. A Bash trap receiver [script](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh) can be used to pass traps to Zabbix server directly from snmptrapd. To configure it, add the `traphandle` option to snmptrapd configuration file (`snmptrapd.conf`), see [example](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/etc/snmp/snmptrapd.conf). ##### Configuration du serveur/proxy Zabbix Pour lire les traps, le serveur ou le proxy Zabbix doit être configuré pour démarrer le processus de trappeur SNMP et pointer vers le fichier de trap en cours d'écriture par SNMPTT ou un récepteur de trap Bash/Perl. Pour ce faire, modifiez le fichier de configuration ([zabbix\_server.conf](/manual/appendix/config/zabbix_server) ou [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)) : StartSNMPTrapper=1 SNMPTrapperFile=[TRAP FILE] ::: notewarning Si le paramètre systemd **[PrivateTmp](http://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=)** est utilisé, il est peu probable que ce fichier fonctionne dans */tmp* . ::: ##### Configuration du récepteur de trap Bash Pré-requis : uniquement snmptrapd. Un [script de récepteur de trap Bash](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh) peut être utilisé pour transmettre des traps au serveur Zabbix directement depuis snmptrapd. Pour le configurer, ajoutez l'option `traphandle` au fichier de configuration snmptrapd (`snmptrapd.conf`), voir l'[exemple](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine /conf/etc/snmp/snmptrapd.conf). ### Connection options for Oracle plugin Oracle plugin, supported for Zabbix agent 2, now allows to specify `as sysdba`, `as sysoper`, or `as sysasm` login option. The option can be appended either to the user item key parameter or to the plugin configuration parameter Plugins.Oracle.Sessions.<SessionName>.User in the format `user as sysdba` (login option is case-insensitive; must not contain a trailing space). ### Options de connexion pour le plug-in Oracle Le plugin Oracle, pris en charge pour l'agent Zabbix 2, permet désormais de spécifier l'option de connexion `as sysdba`, `as sysoper` ou `as sysasm`. L'option peut être ajoutée au paramètre clé de l'élément utilisateur ou au paramètre de configuration du plug-in Plugins.Oracle.Sessions.<SessionName>.User au format `user as sysdba` (l'option de connexion est insensible à la casse ; ne doit pas contenir de espace). ### Connection set up Zabbix supports two types of connect identifiers (connection methods): - Easy Connect - Net Service Name Connection configuration parameters for Zabbix server and Zabbix proxy can be set in the configuration files. Important parameters for the server and proxy are *DBHost*, *DBUser*, *DBName* and *DBPassword*. The same parameters are important for the frontend: *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*. Zabbix uses the following connection string syntax: {DBUser/DBPassword[@<connect_identifier>]} <connect\_identifier> can be specified either in the form of "Net Service Name" or "Easy Connect". @[[//]Host[:Port]/<service_name> | <net_service_name>] ### Etablissement de la connexion Zabbix prend en charge deux types d'identifiants de connexion (méthodes de connexion) : - Easy Connect - Net Service Name Les paramètres de configuration de connexion pour le serveur Zabbix et le proxy Zabbix peuvent être définis dans les fichiers de configuration. Les paramètres importants pour le serveur et le proxy sont *DBHost*, *DBUser*, *DBName* et *DBPassword*. Les mêmes paramètres sont importants pour l'interface Web : *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*. Zabbix utilise la syntaxe de chaîne de connexion suivante : {DBUser/DBPassword[@<connect_identifier>]} <connect\_identifier> peut être spécifié sous la forme "Net Nom du service" ou sous la forme "Easy Connect". @[[//]Host[:Port]/<service_name> | <net_service_name>] #### Copy an LLD rule to multiple hosts Copy an LLD rule to two hosts. Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.copy", "params": { "discoveryids": [ "27426" ], "hostids": [ "10196", "10197" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` #### Copier une règle de découverte bas niveau sur plusieurs hôtes Copier une règle de découverte bas niveau sur deux hôtes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.copy", "params": { "discoveryids": [ "27426" ], "hostids": [ "10196", "10197" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` #### Copying/pasting pages Dashboard pages can be copied and pasted, allowing to create a new page with the properties of an existing one. They can be pasted from the same dashboard or a different dashboard. To paste an existing page to the dashboard, first copy it, using the [page menu](#page_menu):  To paste the copied page: - Make sure the dashboard is in the [editing mode](#viewing_and_editing_a_dashboard) - Click on the arrow next to the *Add* button and select the *Paste page* option #### Copier/coller des pages Les pages du tableau de bord peuvent être copiées et collées, ce qui permet de créer une nouvelle page avec les propriétés d'une page existante. Ils peuvent être collés à partir du même tableau de bord ou d'un tableau de bord différent. Pour coller une page existante dans le tableau de bord, copiez-la d'abord à l'aide du [menu de la page](#page_menu) :  To paste the copied page : - Assurez-vous que le tableau de bord est en [mode édition](#viewing_and_editing_a_dashboard) - Cliquez sur la flèche à côté du bouton *Ajouter* et sélectionnez l'option *Coller la page* #### Copying/pasting widgets Dashboard widgets can be copied and pasted, allowing to create a new widget with the properties of an existing one. They can be copy-pasted within the same dashboard, or between dashboards opened in different tabs. A widget can be copied using the [widget menu](#widget_menu). To paste the widget: - click on the arrow next to the *Add* button and selecting the *Paste widget* option, when editing the dashboard - use the *Paste widget* option when adding a new widget by selecting some area in the dashboard (a widget must be copied first for the paste option to become available) A copied widget can be used to paste over an existing widget using the *Paste* option in the [widget menu](#widget_menu). #### Copier/coller des widgets Les widgets du tableau de bord peuvent être copiés et collés, ce qui permet de créer un nouveau widget avec les propriétés d'un widget existant. Ils peuvent être copiés-collés dans le même tableau de bord, ou entre des tableaux de bord ouverts dans différents onglets. Un widget peut être copié à l'aide du [menu widget](#widget_menu). Pour coller le widget : - cliquer sur la flèche à côté du bouton *Ajouter* et sélectionnez l'option *Coller le widget*, lors de l'édition du tableau de bord - utiliser l'option *Coller le widget* lors de l'ajout d'un nouveau widget en sélectionnant une zone dans le tableau de bord (un widget doit d'abord être copié pour que l'option de collage devienne disponible) Un widget copié peut être utilisé pour coller sur un widget existant en utilisant l'option *Coller* dans le [menu du widget](#widget_menu). ##### Copying PHP files Zabbix frontend is written in PHP, so to run it a PHP supported webserver is needed. Installation is done by simply copying the PHP files from the ui directory to the webserver HTML documents directory. Common locations of HTML documents directories for Apache web servers include: - /usr/local/apache2/htdocs (default directory when installing Apache from source) - /srv/www/htdocs (OpenSUSE, SLES) - /var/www/html (Debian, Ubuntu, Fedora, RHEL) It is suggested to use a subdirectory instead of the HTML root. To create a subdirectory and copy Zabbix frontend files into it, execute the following commands, replacing the actual directory: mkdir <htdocs>/zabbix cd ui cp -a . <htdocs>/zabbix If planning to use any other language than English, see [Installation of additional frontend languages](/manual/appendix/install/locales) for instructions. ##### Copier les fichiers PHP L'interface Zabbix est écrite en PHP, donc pour l'exécuter, un serveur web qui supporte PHP est nécessaire. L'installation se fait simplement en copiant les fichiers PHP depuis frontends/php vers le répertoire HTML du serveur web. Les emplacements communs des répertoires HTML pour les serveurs Web Apache incluent : - /usr/local/apache2/htdocs (répertoire par défaut lors de l'installation d'Apache à partir des sources) - /srv/www/htdocs (OpenSUSE, SLES) - /var/www/html (Debian, Ubuntu, Fedora, RHEL) Il est suggéré d'utiliser un sous-répertoire à la place de la racine HTML. Pour créer un sous-répertoire et y copier des fichiers frontaux Zabbix, exécutez les commandes suivantes en remplaçant le répertoire actuel : mkdir <htdocs>/zabbix cd ui cp -a . <htdocs>/zabbix Si vous prévoyez d'utiliser une autre langue que l'anglais, consultez [Installation de langues frontales supplémentaires](/manual/appendix/install/locales) pour obtenir des instructions. ### Copyright notice Zabbix documentation is NOT distributed under a GPL license. Use of Zabbix documentation is subject to the following terms: You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how Zabbix disseminates it (that is, electronically for download on a Zabbix web site) or on a USB or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Zabbix. Zabbix reserves any and all rights to this documentation not expressly granted above. ### Copyright La documentation Zabbix n'est PAS distribuée sous licence GPL. L'utilisation de la documentation Zabbix est soumise aux conditions suivantes : Vous pouvez créer une copie imprimée de cette documentation uniquement pour votre usage personnel. La conversion vers d'autres formats est autorisée tant que le contenu réel n'est pas modifié ou modifié de quelque manière que ce soit. Vous ne devez pas publier ou distribuer cette documentation sous quelque forme ou sur quelque support que ce soit, sauf si vous distribuez la documentation d'une manière similaire à la façon dont Zabbix la diffuse (c'est-à-dire, par voie électronique pour téléchargement sur un site Web Zabbix) ou sur une clé USB ou support similaire, à condition toutefois que la documentation soit diffusée avec le logiciel sur le même support. Toute autre utilisation, telle que toute diffusion de copies imprimées ou utilisation de cette documentation, en tout ou en partie, dans une autre publication, nécessite l'accord écrit préalable d'un représentant autorisé de Zabbix. Zabbix se réserve tous les droits sur cette documentation non expressément accordés ci-dessus. # correlation.create # correlation.create # correlation.delete # correlation.delete #### Correlation filter condition The correlation filter condition object defines a specific condition that must be checked before running the correlation operations. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>0 - old event tag;<br>1 - new event tag;<br>2 - new event host group;<br>3 - event tag pair;<br>4 - old event tag value;<br>5 - new event tag value.| |tag|string|Event tag (old or new). Required when type of condition is: 0, 1, 4, 5.| |groupid|string|Host group ID. Required when type of condition is: 2.| |oldtag|string|Old event tag. Required when type of condition is: 3.| |newtag|string|Old event tag. Required when type of condition is: 3.| |value|string|Event tag (old or new) value. Required when type of condition is: 4, 5.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Required when type of condition is: 2, 4, 5.| ::: notetip To better understand how to use filters with various types of expressions, see examples on the [correlation.get](get#retrieve_correlations) and [correlation.create](create#using_a_custom_expression_filter) method pages. ::: The following operators and values are supported for each condition type. |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |2|Host group|=, <>|Host group ID.| |4|Old event tag value|=, <>, like, not like|string| |5|New event tag value|=, <>, like, not like|string| #### Condition du filtre de corrélation L'objet de condition de filtre de corrélation définit une condition spécifique qui doit être vérifiée avant d'exécuter les opérations de corrélation. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(obligatoire)|integer|Type de condition.<br><br>Valeurs possibles :<br>0 - ancien tag d'événement ;<br>1 - nouveau tag d'événement ;<br>2 - nouveau groupe d'hôtes de l'événement ;<br>3 - paire de tag d'événement ;<br>4 - ancienne valeur de tag d'événement ;<br>5 - nouvelle valeur de tag d'événement.| |tag|string|Tag d'événement (ancienne ou nouvelle). Requis lorsque le type de condition est : 0, 1, 4, 5.| |groupid|string|ID du groupe d'hôtes. Requis lorsque le type de condition est : 2.| |oldtag|string|Ancien tag d'événement. Requis lorsque le type de condition est : 3.| |newtag|string|Nouveau tag d'événement. Requis lorsque le type de condition est : 3.| |value|string|Valeur du tag d'événement (ancien ou nouveau). Requis lorsque le type de condition est : 4, 5.| |formulaid|string|ID unique arbitraire utilisé pour référencer la condition à partir d'une expression personnalisée. Ne peut contenir que des lettres majuscules. L'ID doit être défini par l'utilisateur lors de la modification des conditions de filtrage, mais sera généré de nouveau lors d'une demande ultérieure.| |operator|integer|Opérateur de condition.<br><br>Requis lorsque le type de condition est : 2, 4, 5.| ::: notetip Pour mieux comprendre comment utiliser des filtres avec différents types d’expressions, voir des exemples sur les pages des méthodes [correlation.get](get#retrieve_correlations) et [correlation.create](create#using_a_custom_expression_filter). ::: Les opérateurs et les valeurs suivants sont pris en charge pour chaque type de condition. |Condition|Nom de la Condition|Opérateurs pris en charge|Valeur attendue| |---------|--------------|-------------------|--------------| |2|Groupe d'hôtes|=, <>|Host group ID.| |4|Ancienne valeur de tag d'événement|=, <>, like, not like|string| |5|Nouvelle valeur de tag d'événement |=, <>, like, not like|string| ### Correlation filter The correlation filter object defines a set of conditions that must be met to perform the configured correlation operations. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.| ### Filtre de Corrélation L'objet filtre de corrélation définit un ensemble de conditions à respecter pour effectuer les opérations de corrélation configurées. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**evaltype**<br>(obligatoire)|integer|Méthode d'évaluation de la condition du filtre.<br><br>Valeurs possibles :<br>0 - et/ou ;<br>1 - et ;<br>2 - ou ;<br>3 - expression personnalisée.| |**conditions**<br>(obligatoire)|array|Ensemble de conditions de filtre à utiliser pour filtrer les résultats.| |eval\_formula|string|*(lecture seule)* Expression générée qui sera utilisée pour évaluer les conditions de filtrage. L'expression contient des ID qui référencent des conditions de filtrage spécifiques par son `formulaid`. La valeur de `eval_formula` est égale à la valeur de `formula` pour les filtres avec une expression personnalisée.| |formula|string|Expression définie par l'utilisateur à utiliser pour évaluer les conditions des filtres avec une expression personnalisée. L'expression doit contenir des IDs qui référencent des conditions de filtrage spécifiques par son `formulaid`. Les ID utilisés dans l'expression doivent correspondre exactement à ceux définis dans les conditions de filtrage : aucune condition ne peut rester inutilisée ou omise.<br><br>Obligatoire pour les filtres d'expression personnalisés.| # correlation.get # correlation.get ### Correlation operation The correlation operation object defines an operation that will be performed when a correlation is executed. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - close old events;<br>1 - close new event.| ### Opération de Corrélation L'objet opération de corrélation définit une opération qui sera effectuée lorsqu'une corrélation est exécutée. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(obligatoire)|integer|Type d'opération.<br><br>Valeurs possibles :<br>0 - fermer les anciens évènements ;<br>1 - fermer le nouvel évènement.| ### Correlation The correlation object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |correlationid|string|*(readonly)* ID of the correlation.| |**name**<br>(required)|string|Name of the correlation.| |description|string|Description of the correlation.| |status|integer|Whether the correlation is enabled or disabled.<br><br>Possible values are:<br>0 - *(default)* enabled;<br>1 - disabled.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Corrélation L'objet corrélation a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |correlationid|string|*(lecture seule)* ID de la corrélation.| |**name**<br>(obligatoire)|string|Nom de la corrélation.| |description|string|Description de la corrélation.| |status|integer|Indique si la corrélation est activée ou désactivée.<br><br>Valeurs possibles :<br>0 - *(par défaut)* activée ;<br>1 - désactivée.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # correlation.update # correlation.update ##### Counting of threads in `proc.mem[]` and `proc.num[]` items Linux kernel threads are counted by `proc.num[]` item but do not report memory in `proc.mem[]` item. For example: $ ps -ef | grep kthreadd root 2 0 0 09:51 ? 00:00:00 [kthreadd] $ zabbix_get -s localhost -k 'proc.num[kthreadd]' 1 $ zabbix_get -s localhost -k 'proc.mem[kthreadd]' ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory. But what happens if there is a user process with the same name as a kernel thread ? Then it could look like this: $ ps -ef | grep kthreadd root 2 0 0 09:51 ? 00:00:00 [kthreadd] zabbix 9611 6133 0 17:58 pts/1 00:00:00 ./kthreadd $ zabbix_get -s localhost -k 'proc.num[kthreadd]' 2 $ zabbix_get -s localhost -k 'proc.mem[kthreadd]' 4157440 `proc.num[]` counted both the kernel thread and the user process. `proc.mem[]` reports memory for the user process only and counts the kernel thread memory as if it was 0. This is different from the case above when ZBX\_NOTSUPPORTED was reported. Be careful when using `proc.mem[]` and `proc.num[]` items if the program name happens to match one of the thread. Before putting parameters into `proc.mem[]` and `proc.num[]` items, you may want to test the parameters using `proc.num[]` item and `ps` command. ##### Comptage des threads dans les éléments `proc.mem[]` et `proc.num[]` Les threads du noyau Linux sont comptés par l'élément `proc.num[]` mais ne signalent pas la mémoire dans l'élément `proc.mem[]`. Par exemple : $ ps -ef | grep kthreadd root 2 0 0 09:51 ? 00:00:00 [kthreadd] $ zabbix_get -s localhost -k 'proc.num[kthreadd]' 1 $ zabbix_get -s localhost -k 'proc.mem[kthreadd]' ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory. Mais que se passe-t-il si un processus utilisateur porte le même nom qu'un thread du noyau ? Alors cela pourrait ressembler à ceci : $ ps -ef | grep kthreadd root 2 0 0 09:51 ? 00:00:00 [kthreadd] zabbix 9611 6133 0 17:58 pts/1 00:00:00 ./kthreadd $ zabbix_get -s localhost -k 'proc.num[kthreadd]' 2 $ zabbix_get -s localhost -k 'proc.mem[kthreadd]' 4157440 `proc.num[]` compte à la fois le thread du noyau et le processus utilisateur. `proc.mem[]` rapporte la mémoire pour le processus utilisateur uniquement et compte la mémoire du thread du noyau comme si elle était à 0. Cela est différent du cas ci-dessus lorsque ZBX\_NOTSUPPORTED a été signalé. Soyez prudent lorsque vous utilisez les éléments `proc.mem[]` et `proc.num[]` si le nom du programme correspond à l'un des threads. Avant de mettre des paramètres dans les éléments `proc.mem[]` et `proc.num[]`, vous pouvez les tester à l'aide de l'élément `proc.num[]` et de la commande `ps`. **CPU** Zabbix and especially Zabbix database may require significant CPU resources depending on number of monitored parameters and chosen database engine. **CPU** Zabbix et en particulier la base de données Zabbix peuvent nécessiter des ressources CPU importantes en fonction du nombre de paramètres surveillés et du moteur de base de données choisi. #### Create a custom script Create a custom script that will reboot a server. The script will require write access to the host and will display a configuration message before running in the frontend. Request: ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "Reboot server", "command": "reboot server 1", "confirmation": "Are you sure you would like to reboot the server?", "scope": 2, "type": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "4" ] }, "id": 1 } ``` #### Créer un script personnalisé Créez un script personnalisé qui redémarrera un serveur. Le script nécessitera un accès en écriture à l'hôte et affichera un message de configuration avant de s'exécuter dans le frontend. Requête : ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "Reboot server", "command": "reboot server 1", "confirmation": "Are you sure you would like to reboot the server?", "scope": 2, "type": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "4" ] }, "id": 1 } ``` #### Create a discovery action Create a discovery action that will link discovered hosts to template "10001". Request: ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Discovery action", "eventsource": 1, "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 21, "operator": 0, "value": "1" }, { "conditiontype": 10, "operator": 0, "value": "2" } ] }, "operations": [ { "operationtype": 6, "optemplate": [ { "templateid": "10001" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "actionids": [ "18" ] }, "id": 1 } ``` #### Créer une action de découverte Créer une action qui liera les hôtes découverts au modèle "10001". Requête : ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Discovery action", "eventsource": 1, "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 21, "operator": 0, "value": "1" }, { "conditiontype": 10, "operator": 0, "value": "2" } ] }, "operations": [ { "operationtype": 6, "optemplate": [ { "templateid": "10001" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "actionids": [ "18" ] }, "id": 1 } ``` #### Create a discovery action Create an action that will link discovered hosts to template "10091". Request: ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Discovery action", "eventsource": 1, "status": 0, "esc_period": "0s", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 21, "value": "1" }, { "conditiontype": 10, "value": "2" } ] }, "operations": [ { "esc_step_from": 1, "esc_period": "0s", "optemplate": [ { "templateid": "10091" } ], "operationtype": 6, "esc_step_to": 1 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "18" ] }, "id": 1 } ``` #### Création d'une action de découverte Créer une action qui liera les hôtes découverts au modèle "10091". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Discovery action", "eventsource": 1, "status": 0, "esc_period": "0s", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 21, "value": "1" }, { "conditiontype": 10, "value": "2" } ] }, "operations": [ { "esc_step_from": 1, "esc_period": "0s", "optemplate": [ { "templateid": "10091" } ], "operationtype": 6, "esc_step_to": 1 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "18" ] }, "id": 1 } ``` #### Create a discovery rule Create a discovery rule to find machines running the Zabbix agent in the local network. The rule must use a single Zabbix agent check on port 10050. Request: ```json { "jsonrpc": "2.0", "method": "drule.create", "params": { "name": "Zabbix agent discovery", "iprange": "192.168.1.1-255", "dchecks": [ { "type": "9", "key_": "system.uname", "ports": "10050", "uniq": "0" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "druleids": [ "6" ] }, "id": 1 } ``` #### Création d'une règle de découverte Créez une règle de découverte permettant de rechercher les machines exécutant l'agent Zabbix sur le réseau local. La règle doit utiliser un seul test de découverte d'agent Zabbix sur le port 10050. Requête : ```json { "jsonrpc": "2.0", "method": "drule.create", "params": { "name": "Zabbix agent discovery", "iprange": "192.168.1.1-255", "dchecks": [ { "type": "9", "key_": "system.uname", "ports": "10050", "uniq": "0" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "druleids": [ "6" ] }, "id": 1 } ``` #### Create agent autoregistration rule Add a host to host group "Linux servers" when host name contains "SRV" or metadata contains "AlmaLinux". Request: ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Register Linux servers", "eventsource": "2", "status": "0", "filter": { "evaltype": "2", "conditions": [ { "conditiontype": "22", "operator": "2", "value": "SRV" }, { "conditiontype": "24", "operator": "2", "value": "AlmaLinux" } ] }, "operations": [ { "operationtype": "4", "opgroup": [ { "groupid": "2" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "actionids": [ 19 ] }, "id": 1 } ``` #### Créer une règle d'enregistrement automatique des agents Ajoutez un hôte au groupe d'hôtes "Linux servers" lorsque le nom d'hôte contient "SRV" ou que les métadonnées contiennent "AlmaLinux". Requête : ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Register Linux servers", "eventsource": "2", "status": "0", "filter": { "evaltype": "2", "conditions": [ { "conditiontype": "22", "operator": "2", "value": "SRV" }, { "conditiontype": "24", "operator": "2", "value": "AlmaLinux" } ] }, "operations": [ { "operationtype": "4", "opgroup": [ { "groupid": "2" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "actionids": [ 19 ] }, "id": 1 } ``` #### Create agent autoregistration rule Add a host to host group "Linux servers" when host name contains "SRV" or metadata contains "CentOS". Request: ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Register Linux servers", "eventsource": "2", "status": "0", "filter": { "evaltype": "2", "formula": "A or B", "conditions": [ { "conditiontype": "22", "operator": "2", "value": "SRV", "value2": "", "formulaid": "B" }, { "conditiontype": "24", "operator": "2", "value": "CentOS", "value2": "", "formulaid": "A" } ] }, "operations": [ { "actionid": "9", "operationtype": "4", "esc_period": "0", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opgroup": [ { "operationid": "16", "groupid": "2" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ 19 ] }, "id": 1 } ``` #### Créer une règle d'enregistrement automatique d'agent Ajouter un hôte au groupe d'hôtes "Linux servers" lorsque son nom contient "SRV" ou que les métadonnées contiennent "CentOS". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Register Linux servers", "eventsource": "2", "status": "0", "filter": { "evaltype": "2", "formula": "A or B", "conditions": [ { "conditiontype": "22", "operator": "2", "value": "SRV", "value2": "", "formulaid": "B" }, { "conditiontype": "24", "operator": "2", "value": "CentOS", "value2": "", "formulaid": "A" } ] }, "operations": [ { "actionid": "9", "operationtype": "4", "esc_period": "0", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opgroup": [ { "operationid": "16", "groupid": "2" } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ 19 ] }, "id": 1 } ``` #### Create a host map Create a map with two host elements and a link between them. Note the use of temporary "selementid1" and "selementid2" values in the map link object to refer to map elements. Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Host map", "width": 600, "height": 600, "selements": [ { "selementid": "1", "elements": [ {"hostid": "1033"} ], "elementtype": 0, "iconid_off": "2" }, { "selementid": "2", "elements": [ {"hostid": "1037"} ], "elementtype": 0, "iconid_off": "2" } ], "links": [ { "selementid1": "1", "selementid2": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 1 } ``` #### Créer une carte d'hôte Créer une carte avec deux éléments hôtes et un lien entre eux. A noter : l'utilisation de valeurs temporaires "selementid1" et "selementid2" dans l'objet de lien de carte pour faire référence à des éléments de carte. Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Host map", "width": 600, "height": 600, "selements": [ { "selementid": "1", "elements": [ {"hostid": "1033"} ], "elementtype": 0, "iconid_off": "2" }, { "selementid": "2", "elements": [ {"hostid": "1037"} ], "elementtype": 0, "iconid_off": "2" } ], "links": [ { "selementid1": "1", "selementid2": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 1 } ``` #### Create an active proxy Create an action proxy "Active proxy" and assign a host to be monitored by it. Request: ```json { "jsonrpc": "2.0", "method": "proxy.create", "params": { "host": "Active proxy", "status": "5", "hosts": [ { "hostid": "10279" } ] }, "auth": "ab9638041ec6922cb14b07982b268f47", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10280" ] }, "id": 1 } ``` #### Création d'un proxy actif Créez un proxy actif "Active proxy" et lui assigner un hôte à surveiller. Requête : ```json { "jsonrpc": "2.0", "method": "proxy.create", "params": { "host": "Active proxy", "status": "5", "hosts": [ { "hostid": "10279" } ] }, "auth": "ab9638041ec6922cb14b07982b268f47", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10280" ] }, "id": 1 } ``` #### Create an empty map Create a map with no elements. Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map", "width": 600, "height": 600 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "8" ] }, "id": 1 } ``` #### Créer une carte vide Créer une carte sans élément. Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map", "width": 600, "height": 600 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "8" ] }, "id": 1 } ``` #### Create a new event tag correlation Create a correlation using evaluation method `AND/OR` with one condition and one operation. By default the correlation will be enabled. Request: ``` {.java} { "jsonrpc": "2.0", "method": "correlation.create", "params": { "name": "new event tag correlation", "filter": { "evaltype": 0, "conditions": [ { "type": 1, "tag": "ok" } ] }, "operations": [ { "type": 0 } ] }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Créer un nouveau tag d'événement de corrélation Créez une corrélation à l'aide de la méthode d'évaluation "AND/OR" avec une condition et une opération. Par défaut, la corrélation sera activée. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "correlation.create", "params": { "name": "new event tag correlation", "filter": { "evaltype": 0, "conditions": [ { "type": 1, "tag": "ok" } ] }, "operations": [ { "type": 0 } ] }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Create a new interface Create a secondary IP agent interface on host "30052." Request: ```json { "jsonrpc": "2.0", "method": "hostinterface.create", "params": { "hostid": "30052", "main": "0", "type": "1", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "10050", }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "interfaceids": [ "30062" ] }, "id": 1 } ``` #### Création d'une interface Créer une interface d'agent IP secondaire sur l'hôte "30052". Requête : ```json { "jsonrpc": "2.0", "method": "hostinterface.create", "params": { "hostid": "30052", "main": "0", "type": "1", "useip": "1" "ip": "127.0.0.1", "dns": "", "port": "10050", }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "interfaceids": [ "30062" ] }, "id": 1 } ``` #### Create an icon map Create an icon map to display hosts of different types. Request: ```json { "jsonrpc": "2.0", "method": "iconmap.create", "params": { "name": "Type icons", "default_iconid": "2", "mappings": [ { "inventory_link": 1, "expression": "server", "iconid": "3" }, { "inventory_link": 1, "expression": "switch", "iconid": "4" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "iconmapids": [ "2" ] }, "id": 1 } ``` #### Créer une carte d'icônes Créez une carte d'icônes pour afficher les hôtes de différents types. Requête : ```json { "jsonrpc": "2.0", "method": "iconmap.create", "params": { "name": "Type icons", "default_iconid": "2", "mappings": [ { "inventory_link": 1, "expression": "server", "iconid": "3" }, { "inventory_link": 1, "expression": "switch", "iconid": "4" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "iconmapids": [ "2" ] }, "id": 1 } ``` #### Create an image Create a cloud icon. Request: ```json { "jsonrpc": "2.0", "method": "image.create", "params": { "imagetype": 1, "name": "Cloud_(24)", "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII=" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "imageids": [ "188" ] }, "id": 1 } ``` #### Créer une image Créez une icône de nuage. Requête : ```json { "jsonrpc": "2.0", "method": "image.create", "params": { "imagetype": 1, "name": "Cloud_(24)", "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII=" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "imageids": [ "188" ] }, "id": 1 } ``` #### Create an interface with SNMP details Request: ```json { "jsonrpc": "2.0", "method": "hostinterface.create", "params": { "hostid": "10456", "main": "0", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "1601", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "interfaceids": [ "30063" ] }, "id": 1 } ``` #### Créer une interface avec des détails SNMP Requête : ```json { "jsonrpc": "2.0", "method": "hostinterface.create", "params": { "hostid": "10456", "main": "0", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "1601", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "interfaceids": [ "30063" ] }, "id": 1 } ``` Create another child service of Zabbix cluster with name "Zabbix server node 2". Set the Problem tags as: - Name: component - Operation: Equals - Value: HA node 2 Switch to the *Tags* tab and add a service tag: `Zabbix server:node 2`. Save the new service. Créez un autre service enfant du cluster Zabbix avec le nom "Zabbix server node 2". Définissez les tags de problème comme : - Name: component - Operation: Equals - Value: HA node 2 Basculez vers l'onglet *Tags* et ajoutez un tag de service : `Zabbix server:node 2`. Enregistrez le nouveau service. #### Create an SSH script Create an SSH script with public key authentication that can be executed on a host and has a context menu. Request: ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "SSH script", "command": "my script command", "type": 2, "username": "John", "publickey": "pub.key", "privatekey": "priv.key", "password": "secret", "port": "12345", "scope": 2, "menu_path": "All scripts/SSH", "usrgrpid": "7", "groupid": "4" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "5" ] }, "id": 1 } ``` #### Créer un script SSH Créez un script SSH avec une authentification par clé publique pouvant être exécuté sur un hôte et doté d'un menu contextuel. Requête : ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "SSH script", "command": "my script command", "type": 2, "username": "John", "publickey": "pub.key", "privatekey": "priv.key", "password": "secret", "port": "12345", "scope": 2, "menu_path": "All scripts/SSH", "usrgrpid": "7", "groupid": "4" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "5" ] }, "id": 1 } ``` #### Create a passive proxy Create a passive proxy "Passive proxy" and assign two hosts to be monitored by it. Request: ```json { "jsonrpc": "2.0", "method": "proxy.create", "params": { "host": "Passive proxy", "status": "6", "interface": { "ip": "127.0.0.1", "dns": "", "useip": "1", "port": "10051" }, "hosts": [ { "hostid": "10192" }, { "hostid": "10139" } ] }, "auth": "ab9638041ec6922cb14b07982b268f47", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10284" ] }, "id": 1 } ``` #### Création d'un proxy passif Créez un proxy actif "Passive proxy" et lui assigner deux hôtes à surveiller. Requête : ```json { "jsonrpc": "2.0", "method": "proxy.create", "params": { "host": "Passive proxy", "status": "6", "interface": { "ip": "127.0.0.1", "dns": "", "useip": "1", "port": "10051" }, "hosts": [ { "hostid": "10192" }, { "hostid": "10139" } ] }, "auth": "ab9638041ec6922cb14b07982b268f47", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "proxyids": [ "10284" ] }, "id": 1 } ``` #### Create a token Create an enabled token that never expires and authenticates user of ID 2. Request: ```json { "jsonrpc": "2.0", "method": "token.create", "params": { "name": "Your token", "userid": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "188" ] }, "id": 1 } ``` Create a disabled token that expires at January 21st, 2021. This token will authenticate current user. Request: ```json { "jsonrpc": "2.0", "method": "token.create", "params": { "name": "Your token", "status": "1", "expires_at": "1611238072" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "189" ] }, "id": 1 } ``` #### Créer un token Créez un token activé qui n'expire jamais et authentifie l'utilisateur d'ID 2. Requête : ```json { "jsonrpc": "2.0", "method": "token.create", "params": { "name": "Your token", "userid": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "188" ] }, "id": 1 } ``` Créez un token désactivé qui expire le 21 janvier 2021. Ce token authentifiera l'utilisateur actuel. Requête : ```json { "jsonrpc": "2.0", "method": "token.create", "params": { "name": "Your token", "status": "1", "expires_at": "1611238072" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "189" ] }, "id": 1 } ``` #### Create a trigger action Create an action that will be run when a trigger from host "10084" that has the word "memory" in its name goes into problem state. The action must first send a message to all users in user group "7". If the event is not resolved in 4 minutes, it will run script "3" on all hosts in group "2". On trigger recovery it will notify all users who received any messages regarding the problem before. On trigger update, message with custom subject and body will be sent to all who left acknowledgments and comments via all media types. Request: ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Trigger action", "eventsource": 0, "status": 0, "esc_period": "2m", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 1, "operator": 0, "value": "10084" }, { "conditiontype": 3, "operator": 2, "value": "memory" } ] }, "operations": [ { "operationtype": 0, "esc_period": "0s", "esc_step_from": 1, "esc_step_to": 2, "evaltype": 0, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage": { "default_msg": 1, "mediatypeid": "1" } }, { "operationtype": 1, "esc_step_from": 3, "esc_step_to": 4, "evaltype": 0, "opconditions": [ { "conditiontype": 14, "operator": 0, "value": "0" } ], "opcommand_grp": [ { "groupid": "2" } ], "opcommand": { "scriptid": "3" } } ], "recovery_operations": [ { "operationtype": "11", "opmessage": { "default_msg": 1 } } ], "update_operations": [ { "operationtype": "12", "opmessage": { "default_msg": 0, "message": "Custom update operation message body", "subject": "Custom update operation message subject" } } ], "pause_suppressed": "0", "notify_if_canceled": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "17" ] }, "id": 1 } ``` #### Créer une action de déclenchement Créer une action à exécuter lorsqu'un déclencheur de l'hôte "10084" contenant le mot clé "memory" dans son nom passe à l'état problématique. L'action doit d'abord envoyer un message à tous les utilisateurs du groupe d'utilisateurs "7". Si l'événement n'est pas résolu dans les 4 minutes, le script "3" sera exécuté sur tous les hôtes du groupe "2". Lors du retour à la normale du déclencheur, il avertira tous les utilisateurs ayant reçu auparavant des messages concernant le problème. Lors de la mise à jour du déclencheur, un message avec un sujet et un corps personnalisés sera envoyé à tous ceux qui ont laissé des acquittements et des commentaires via tous les types de support. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Trigger action", "eventsource": 0, "status": 0, "esc_period": "2m", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 1, "operator": 0, "value": "10084" }, { "conditiontype": 3, "operator": 2, "value": "memory" } ] }, "operations": [ { "operationtype": 0, "esc_period": "0s", "esc_step_from": 1, "esc_step_to": 2, "evaltype": 0, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage": { "default_msg": 1, "mediatypeid": "1" } }, { "operationtype": 1, "esc_step_from": 3, "esc_step_to": 4, "evaltype": 0, "opconditions": [ { "conditiontype": 14, "operator": 0, "value": "0" } ], "opcommand_grp": [ { "groupid": "2" } ], "opcommand": { "scriptid": "3" } } ], "recovery_operations": [ { "operationtype": "11", "opmessage": { "default_msg": 1 } } ], "update_operations": [ { "operationtype": "12", "opmessage": { "default_msg": 0, "message": "Custom update operation message body", "subject": "Custom update operation message subject" } } ], "pause_suppressed": "0", "notify_if_canceled": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "17" ] }, "id": 1 } ``` #### Create a trigger action Create a trigger action that will begin once a trigger (with the word "memory" in its name) from host "10084" goes into a PROBLEM state. The action will have 4 configured operations. The first and immediate operation will send a message to all users in user group "7" via media type "1". If the event is not resolved in 30 minutes, the second operation will run [script](/manual/web_interface/frontend_sections/administration/scripts#configuring-a-global-script) "5" (script with scope "Action operation") on all hosts in group "2". If the event is resolved, a recovery operation will notify all users who received any messages regarding the problem. If the event is updated, an acknowledge/update operation will notify (with a custom subject and message) all users who received any messages regarding the problem. Request: ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Trigger action", "eventsource": 0, "esc_period": "30m", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 1, "operator": 0, "value": "10084" }, { "conditiontype": 3, "operator": 2, "value": "memory" } ] }, "operations": [ { "operationtype": 0, "esc_step_from": 1, "esc_step_to": 1, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage": { "default_msg": 1, "mediatypeid": "1" } }, { "operationtype": 1, "esc_step_from": 2, "esc_step_to": 2, "opconditions": [ { "conditiontype": 14, "operator": 0, "value": "0" } ], "opcommand_grp": [ { "groupid": "2" } ], "opcommand": { "scriptid": "5" } } ], "recovery_operations": [ { "operationtype": "11", "opmessage": { "default_msg": 1 } } ], "update_operations": [ { "operationtype": "12", "opmessage": { "default_msg": 0, "message": "Custom update operation message body", "subject": "Custom update operation message subject" } } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "actionids": [ "17" ] }, "id": 1 } ``` #### Créer une action de déclenchement Créez une action de déclencheur qui commencera une fois qu'un déclencheur (avec le mot "mémoire" dans son nom) de l'hôte "10084" passera à l'état PROBLÈME. L'action aura 4 opérations configurées. La première opération immédiate enverra un message à tous les utilisateurs du groupe d'utilisateurs "7" via le type de média "1". Si l'événement n'est pas résolu en 30 minutes, la deuxième opération s'exécutera [script](/manual/web_interface/frontend_sections/administration/scripts#configuration-dun-script-global) "5" (script avec la portée "Action operation") sur tous les hôtes du groupe "2". Si l'événement est résolu, une opération de récupération informera tous les utilisateurs qui ont reçu des messages concernant le problème. Si l'événement est mis à jour, une opération d'accusé de réception/de mise à jour notifiera (avec un objet et un message personnalisés) tous les utilisateurs qui ont reçu des messages concernant le problème. Requête : ```json { "jsonrpc": "2.0", "method": "action.create", "params": { "name": "Trigger action", "eventsource": 0, "esc_period": "30m", "filter": { "evaltype": 0, "conditions": [ { "conditiontype": 1, "operator": 0, "value": "10084" }, { "conditiontype": 3, "operator": 2, "value": "memory" } ] }, "operations": [ { "operationtype": 0, "esc_step_from": 1, "esc_step_to": 1, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage": { "default_msg": 1, "mediatypeid": "1" } }, { "operationtype": 1, "esc_step_from": 2, "esc_step_to": 2, "opconditions": [ { "conditiontype": 14, "operator": 0, "value": "0" } ], "opcommand_grp": [ { "groupid": "2" } ], "opcommand": { "scriptid": "5" } } ], "recovery_operations": [ { "operationtype": "11", "opmessage": { "default_msg": 1 } } ], "update_operations": [ { "operationtype": "12", "opmessage": { "default_msg": 0, "message": "Custom update operation message body", "subject": "Custom update operation message subject" } } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "actionids": [ "17" ] }, "id": 1 } ``` #### Create a trigger map Create a map with trigger element, which contains two triggers. Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Trigger map", "width": 600, "height": 600, "selements": [ { "elements": [ {"triggerid": "12345"}, {"triggerid": "67890"} ], "elementtype": 2, "iconid_off": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "10" ] }, "id": 1 } ``` #### Créer une carte de déclencheurs Créer une carte avec un élément déclencheur, qui contient deux déclencheurs. Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Trigger map", "width": 600, "height": 600, "selements": [ { "elements": [ {"triggerid": "12345"}, {"triggerid": "67890"} ], "elementtype": 2, "iconid_off": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "10" ] }, "id": 1 } ``` #### Create a webhook script Create a webhook script that sends HTTP request to external service. Request: ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "Webhook script", "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}", "type": 5, "timeout": "40s", "parameters": [ { "name": "token", "value": "{$WEBHOOK.TOKEN}" }, { "name": "host", "value": "{HOST.HOST}" }, { "name": "v", "value": "2.2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "3" ] }, "id": 1 } ``` #### Créer un script de webhook Créez un script de webhook qui envoie une requête HTTP à un service externe. Requête : ```json { "jsonrpc": "2.0", "method": "script.create", "params": { "name": "Webhook script", "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}", "type": 5, "timeout": "40s", "parameters": [ { "name": "token", "value": "{$WEBHOOK.TOKEN}" }, { "name": "host", "value": "{HOST.HOST}" }, { "name": "v", "value": "2.2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "scriptids": [ "3" ] }, "id": 1 } ``` #### Create HTTP agent item Create POST request method item with JSON response preprocessing. Request: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "url": "http://127.0.0.1/http.php", "query_fields": [ { "mode": "json" }, { "min": "10" }, { "max": "100" } ], "interfaceid": "1", "type": 19, "hostid": "10254", "delay": "5s", "key_": "json", "name": "HTTP agent example JSON", "value_type": 0, "output_format": 1, "preprocessing": [ { "type": 12, "params": "$.random", "error_handler": 0, "error_handler_params": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Créer un élément d'agent HTTP Créez un élément de méthode de requête POST avec le prétraitement de la réponse JSON. Requête : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "url": "http://127.0.0.1/http.php", "query_fields": [ { "mode": "json" }, { "min": "10" }, { "max": "100" } ], "interfaceid": "1", "type": 19, "hostid": "10254", "delay": "5s", "key_": "json", "name": "HTTP agent example JSON", "value_type": 0, "output_format": 1, "preprocessing": [ { "type": 12, "params": "$.random", "error_handler": 0, "error_handler_params": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Create HTTP agent item prototype Create item prototype with URL using user macro, query fields and custom headers. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "type": "19", "hostid": "10254", "ruleid": "28256", "interfaceid": "2", "name": "api item prototype example", "key_": "api_http_item", "value_type": 3, "url": "{$URL_PROTOTYPE}", "query_fields": [ { "min": "10" }, { "max": "100" } ], "headers": { "X-Source": "api" }, "delay": "35" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "28305" ] }, "id": 1 } ``` #### Créer un prototype d'élément d'agent HTTP Créez un prototype d'élément avec une URL à l'aide d'une macro utilisateur, de champs de requête et d'en-têtes personnalisés. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "type": "19", "hostid": "10254", "ruleid": "28256", "interfaceid": "2", "name": "api item prototype example", "key_": "api_http_item", "value_type": 3, "url": "{$URL_PROTOTYPE}", "query_fields": [ { "min": "10" }, { "max": "100" } ], "headers": { "X-Source": "api" }, "delay": "35" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "28305" ] }, "id": 1 } ``` #### Create script item Create a simple data collection using a script item. Request: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Script example", "key_": "custom.script.item", "hostid": "12345", "type": 21, "value_type": 4, "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));", "parameters": [ { "name": "host", "value": "{HOST.CONN}" } ], "timeout": "6s", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Créer un élément de script Créez une collection de données simple à l'aide d'un élément de script. Requête : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Script example", "key_": "custom.script.item", "hostid": "12345", "type": 21, "value_type": 4, "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));", "parameters": [ { "name": "host", "value": "{HOST.CONN}" } ], "timeout": "6s", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Create script item prototype Create a simple data collection using a script item prototype. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "name": "Script example", "key_": "custom.script.itemprototype", "hostid": "12345", "type": 21, "value_type": 4, "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));", "parameters": [ { "name": "host", "value": "{HOST.CONN}" } ], "timeout": "6s", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Créer un prototype d'élément de script Créez une collection de données simple à l'aide d'un prototype d'élément de script. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "name": "Script example", "key_": "custom.script.itemprototype", "hostid": "12345", "type": 21, "value_type": 4, "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));", "parameters": [ { "name": "host", "value": "{HOST.CONN}" } ], "timeout": "6s", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "23865" ] }, "id": 3 } ``` #### Creating a dashboard Create a dashboard named "My dashboard" with one Problems widget with tags and using two types of sharing (user group and user) on a single dashboard page. Request: ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.create", "params": { "name": "My dashboard", "display_period": 30, "auto_start": 1, "pages": [ { "widgets": [ { "type": "problems", "x": 0, "y": 0, "width": 12, "height": 5, "view_mode": 0, "fields": [ { "type": 1, "name": "tags.tag.0", "value": "service" }, { "type": 0, "name": "tags.operator.0", "value": 1 }, { "type": 1, "name": "tags.value.0", "value": "zabbix_server" } ] } ] } ], "userGroups": [ { "usrgrpid": "7", "permission": 2 } ], "users": [ { "userid": "4", "permission": 3 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 1 } ``` #### Création d'un tableau de bord Créer un tableau de bord nommé "My dashboard" avec un widget Problèmes avec des tags et utilisant deux type de partages (utilisateur et groupe d'utilisateurs) sur une page de tableau de bord seule. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.create", "params": { "name": "My dashboard", "display_period": 30, "auto_start": 1, "pages": [ { "widgets": [ { "type": "problems", "x": 0, "y": 0, "width": 12, "height": 5, "view_mode": 0, "fields": [ { "type": 1, "name": "tags.tag.0", "value": "service" }, { "type": 0, "name": "tags.operator.0", "value": 1 }, { "type": 1, "name": "tags.value.0", "value": "zabbix_server" } ] } ] } ], "userGroups": [ { "usrgrpid": "7", "permission": 2 } ], "users": [ { "userid": "4", "permission": 3 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 1 } ``` #### Creating a dashboard It is possible to create a new dashboard in two ways: - Click on *Create dashboard*, when viewing all dashboards - Select *Create new* from the action menu, when viewing a single dashboard You will be first asked to enter general dashboard parameters:  |Parameter|Description| |--|--------| |*Owner*|Select system user that will be the dashboard owner.| |*Name*|Enter dashboard name.| |*Default page display period*|Select period for how long a dashboard page is displayed before rotating to the next page in a [slideshow](#creating_a_slideshow).| |*Start slideshow automatically*|Mark this checkbox to run a slideshow automatically one more than one dashboard page exists.| When you click on *Apply*, an empty dashboard is opened: {width="600"} To populate the dashboard, you can add widgets and pages. Click on the *Save changes* button to save the dashboard. If you click on *Cancel*, the dashboard will not be created. #### Création d'un tableau de bord Il est possible de créer un nouveau tableau de bord de deux manières : - Cliquez sur *Créer un tableau de bord*, lors de l'affichage de tous les tableaux de bord - Sélectionnez *Créer un nouveau* dans le menu d'action, lors de l'affichage d'un seul tableau de bord Il vous sera d'abord demandé de saisir les paramètres généraux du tableau de bord :  |Paramètre|Description| |--|--------| |*Propriétaire*|Sélectionner l'utilisateur système qui sera le propriétaire du tableau de bord.| |*Nom*|Saisir le nom du tableau de bord.| |*Période d'affichage de la page par défaut*|Sélectionner la durée d'affichage d'une page de tableau de bord avant de passer à la page suivante dans un [diaporama](#creating_a_slideshow).| |*Démarrer le diaporama automatiquement*|Cocher cette case pour exécuter un diaporama automatiquement si plusieurs pages de tableau de bord existent.| Lorsque vous cliquez sur *Appliquer*, un tableau de bord vide s'ouvre : {width="600"} Pour remplir le tableau de bord, vous pouvez ajouter des widgets et des pages. Cliquez sur le bouton *Sauvegarder les modifications* pour enregistrer le tableau de bord. Si vous cliquez sur *Annuler*, le tableau de bord ne sera pas créé. #### Creating a global macro Create a global macro "{$SNMP\_COMMUNITY}" with value "public". Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.createglobal", "params": { "macro": "{$SNMP_COMMUNITY}", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "6" ] }, "id": 1 } ``` #### Créer une macro globale Créer une macro globale "{$SNMP\_COMMUNITY}" avec pour valeur "public". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.createglobal", "params": { "macro": "{$SNMP_COMMUNITY}", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "6" ] }, "id": 1 } ``` #### Creating a graph Create a graph with two items. Request: ``` {.java} { "jsonrpc": "2.0", "method": "graph.create", "params": { "name": "MySQL bandwidth", "width": 900, "height": 200, "gitems": [ { "itemid": "22828", "color": "00AA00" }, { "itemid": "22829", "color": "3333FF" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652" ] }, "id": 1 } ``` #### Création d'un graphique Créer un graphique avec deux éléments. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "graph.create", "params": { "name": "MySQL bandwidth", "width": 900, "height": 200, "gitems": [ { "itemid": "22828", "color": "00AA00" }, { "itemid": "22829", "color": "3333FF" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652" ] }, "id": 1 } ``` #### Creating a graph prototype Create a graph prototype with two items. Request: ``` {.java} { "jsonrpc": "2.0", "method": "graphprototype.create", "params": { "name": "Disk space usage {#FSNAME}", "width": 900, "height": 200, "gitems": [ { "itemid": "22828", "color": "00AA00" }, { "itemid": "22829", "color": "3333FF" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652" ] }, "id": 1 } ``` #### Création d'un prototype de graphe Créez un prototype de graphique avec deux éléments. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "graphprototype.create", "params": { "name": "Disk space usage {#FSNAME}", "width": 900, "height": 200, "gitems": [ { "itemid": "22828", "color": "00AA00" }, { "itemid": "22829", "color": "3333FF" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652" ] }, "id": 1 } ``` #### Creating a host Create a host called "Linux server" with an IP interface and tags, add it to a group, link a template to it and set the MAC addresses in the host inventory. Request: ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "Linux server", "interfaces": [ { "type": 1, "main": 1, "useip": 1, "ip": "192.168.3.1", "dns": "", "port": "10050" } ], "groups": [ { "groupid": "50" } ], "tags": [ { "tag": "Host name", "value": "Linux server" } ], "templates": [ { "templateid": "20045" } ], "macros": [ { "macro": "{$USER_ID}", "value": "123321" }, { "macro": "{$USER_LOCATION}", "value": "0:0:0", "description": "latitude, longitude and altitude coordinates" } ], "inventory_mode": 0, "inventory": { "macaddress_a": "01234", "macaddress_b": "56768" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "107819" ] }, "id": 1 } ``` #### Création d'un hôte Créez un hôte appelé "Linux server" avec une interface IP et des tags, ajoutez-le à un groupe, liez-la à un modèle et définissez les adresses MAC dans l'inventaire des hôtes. Requête : ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "Linux server", "interfaces": [ { "type": 1, "main": 1, "useip": 1, "ip": "192.168.3.1", "dns": "", "port": "10050" } ], "groups": [ { "groupid": "50" } ], "tags": [ { "tag": "Host name", "value": "Linux server" } ], "templates": [ { "templateid": "20045" } ], "macros": [ { "macro": "{$USER_ID}", "value": "123321" }, { "macro": "{$USER_LOCATION}", "value": "0:0:0", "description": "latitude, longitude and altitude coordinates" } ], "inventory_mode": 0, "inventory": { "macaddress_a": "01234", "macaddress_b": "56768" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "107819" ] }, "id": 1 } ``` #### Creating a host group Create a host group called "Linux servers". Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.create", "params": { "name": "Linux servers" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "107819" ] }, "id": 1 } ``` #### Création d'un groupe d'hôtes Créer un groupe d'hôtes appelé "Linux servers". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.create", "params": { "name": "Linux servers" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "107819" ] }, "id": 1 } ``` #### Creating a host group ::: noteimportant Only Super Admin users can create host groups. ::: To create a host group in Zabbix frontend, do the following: - Go to: *Configuration → Host groups* - Click on *Create Group* in the upper right corner of the screen - Enter parameters of the group in the form  All mandatory input fields are marked with a red asterisk. |Parameter|Description| |---------|-----------| |*Group name*|Enter a unique host group name.<br>To create a nested host group, use the '/' forward slash separator, for example `Europe/Latvia/Riga/Zabbix servers`. You can create this group even if none of the three parent host groups (`Europe/Latvia/Riga`) exist. In this case creating these parent host groups is up to the user; they will not be created automatically.<br>Leading and trailing slashes, several slashes in a row are not allowed. Escaping of '/' is not supported.<br>Nested representation of host groups is supported since Zabbix 3.2.0.| |*Apply permissions and tag filters to all subgroups*|Checkbox is available to Super Admin users only and only when editing an existing host group.<br>Mark this checkbox and click on *Update* to apply the same level of permissions/tag filters to all nested host groups. For user groups that may have had differing [permissions](/manual/config/users_and_usergroups/usergroup#configuration) assigned to nested host groups, the permission level of the parent host group will be enforced on the nested groups.<br>This is a one-time option that is not saved in the database.<br>This option is supported since Zabbix 3.4.0.| **Permissions to nested host groups** - When creating a child host group to an existing parent host group, [user group](/manual/config/users_and_usergroups/usergroup) permissions to the child are inherited from the parent (for example, when creating `Riga/Zabbix servers` if `Riga` already exists) - When creating a parent host group to an existing child host group, no permissions to the parent are set (for example, when creating `Riga` if `Riga/Zabbix servers` already exists) #### Création d'un groupe d'hôtes ::: noteimportant Seuls les utilisateurs Super Admin peuvent créer des groupes d'hôtes. ::: Pour créer un groupe d'hôtes dans l'interface Zabbix, procédez de la manière suivante : - Allez dans : *Configuration → Groupes d'hôtes* - Cliquez sur *Créer un groupe* dans le coin supérieur droit de l'écran - Saisir les paramètres du groupe dans le formulaire  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. |Paramètre|Description| |---------|-----------| |*Nom du groupe*|Entrez un nom de groupe d'hôtes unique.<br>Pour créer un groupe d'hôtes imbriqué, utilisez le séparateur de barre oblique '/', par exemple `Europe/Lettonie/Riga/Zabbix`. Vous pouvez créer ce groupe même si aucun des trois groupes d'hôtes parents (`Europe/Lettonie/Riga`) n'existe. Dans ce cas, la création de ces groupes d'hôtes parents appartient à l'utilisateur ; ils ne seront pas créés automatiquement.<br>Les barres obliques de début et de fin, et plusieurs barres obliques consécutives ne sont pas autorisées. L'échappement de '/' n'est pas pris en charge.<br>La représentation imbriquée des groupes d'hôtes est prise en charge depuis Zabbix 3.2.0.| |*Appliquer les autorisations et les filtres de tags à tous les sous-groupes*|La case à cocher est disponible uniquement pour les utilisateurs super administrateurs et uniquement lors de la modification d'un groupe d'hôtes existant.<br>Cochez cette case et cliquez sur *Mettre à jour* pour appliquer le même niveau d'autorisations/filtres de tags à tous les groupes d'hôtes imbriqués. Pour les groupes d'utilisateurs qui peuvent avoir des [autorisations](/manual/config/users_and_usergroups/usergroup#configuration) différentes attribuées aux groupes d'hôtes imbriqués, le niveau d'autorisation du groupe d'hôtes parent sera appliqué sur les groupes imbriqués.<br>Ceci est une option unique qui n'est pas enregistrée dans la base de données.<br>Cette option est prise en charge depuis Zabbix 3.4.0.| **Autorisations pour les groupes d'hôtes imbriqués** - Lors de la création d'un groupe d'hôtes enfant sur un groupe d'hôtes parent existant, les autorisations du [groupe d'utilisateurs](/manual/config/users_and_usergroups/usergroup) sur l'enfant sont héritées du parent (par exemple, lors de la création de `serveurs Riga/Zabbix` si `Riga` existe déjà) - Lors de la création d'un groupe d'hôtes parent pour un groupe d'hôtes enfant existant, aucune autorisation pour le parent n'est définie (par exemple, lors de la création de `Riga` si `Riga/Zabbix servers` existe déjà) #### Creating a host inventory item Create a Zabbix agent item to populate the host's "OS" inventory field. Request: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "uname", "key_": "system.uname", "hostid": "30021", "type": 0, "interfaceid": "30007", "value_type": 1, "delay": "10s", "inventory_link": 5 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "24759" ] }, "id": 1 } ``` #### Création d'un élément d'inventaire d'hôte Créez un élément d'agent Zabbix pour remplir le champ d'inventaire "OS" de l'hôte. Requête : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "uname", "key_": "system.uname", "hostid": "30021", "type": 0, "interfaceid": "30007", "value_type": 1, "delay": "10s", "inventory_link": 5 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "24759" ] }, "id": 1 } ``` #### Creating a host macro Create a host macro "{$SNMP\_COMMUNITY}" with the value "public" on host "10198". Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.create", "params": { "hostid": "10198", "macro": "{$SNMP_COMMUNITY}", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "11" ] }, "id": 1 } ``` #### Création d'une macro d'hôte Créez une macro d'hôte "{$SNMP\_COMMUNITY}" avec la valeur "public" sur l'hôte "10198". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.create", "params": { "hostid": "10198", "macro": "{$SNMP_COMMUNITY}", "value": "public" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "11" ] }, "id": 1 } ``` #### Creating a host prototype Create a host prototype "{\#VM.NAME}" on LLD rule "23542" with a group prototype "{\#HV.NAME}", tag pair "Datacenter": "{\#DATACENTER.NAME}" and custom SNMPv2 interface 127.0.0.1:161 with community {$SNMP\_COMMUNITY}. Link it to host group "2". Request: ```json { "jsonrpc": "2.0", "method": "hostprototype.create", "params": { "host": "{#VM.NAME}", "ruleid": "23542", "custom_interfaces": "1", "groupLinks": [ { "groupid": "2" } ], "groupPrototypes": [ { "name": "{#HV.NAME}" } ], "tags": [ { "tag": "Datacenter", "value": "{#DATACENTER.NAME}" } ], "interfaces": [ { "main": "1", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10103" ] }, "id": 1 } ``` #### Création d'un prototype d'hôte Créez un prototype d'hôte "{\#VM.NAME}" sur la règle LLD "23542" avec un prototype de groupe "{\#HV.NAME}", une paire de tag "Datacenter": "\#DATACENTER.NAME}" et une interface SNMPv2 personnalisée 127.0.0.1:161 avec la communauté {$SNMP\_COMMUNITY}. Liez-le au groupe d'hôtes "2". Requête : ```json { "jsonrpc": "2.0", "method": "hostprototype.create", "params": { "host": "{#VM.NAME}", "ruleid": "23542", "custom_interfaces": "1", "groupLinks": [ { "groupid": "2" } ], "groupPrototypes": [ { "name": "{#HV.NAME}" } ], "tags": [ { "tag": "Datacenter", "value": "{#DATACENTER.NAME}" } ], "interfaces": [ { "main": "1", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10103" ] }, "id": 1 } ``` #### Creating a host with SNMP interface Create a host called "SNMP host" with an SNMPv3 interface with details. Request: ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "SNMP host", "interfaces": [ { "type": 2, "main": 1, "useip": 1, "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": 3, "bulk": 0, "securityname": "mysecurityname", "contextname": "", "securitylevel": 1 } } ], "groups": [ { "groupid": "4" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10658" ] }, "id": 1 } ``` #### Création d'un hôte avec interface SNMP Créez un hôte appelé "hôte SNMP" avec une interface SNMPv3 avec des détails. Requête : ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "SNMP host", "interfaces": [ { "type": 2, "main": 1, "useip": 1, "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": 3, "bulk": 0, "securityname": "mysecurityname", "contextname": "", "securitylevel": 1 } } ], "groups": [ { "groupid": "4" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10658" ] }, "id": 1 } ``` #### Creating a maintenance Create a maintenance with data collection for host group with ID "2" and with problem tags **service:mysqld** and **error**. It must be active from 22.01.2013 till 22.01.2014, come in effect each Sunday at 18:00 and last for one hour. Request: ```json { "jsonrpc": "2.0", "method": "maintenance.create", "params": { "name": "Sunday maintenance", "active_since": 1358844540, "active_till": 1390466940, "tags_evaltype": 0, "groups": [ {"groupid": "2"} ], "timeperiods": [ { "period": 3600, "timeperiod_type": 3, "start_time": 64800, "every": 1, "dayofweek": 64 } ], "tags": [ { "tag": "service", "operator": "0", "value": "mysqld" }, { "tag": "error", "operator": "2", "value": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3" ] }, "id": 1 } ``` #### Création d'une maintenance Créez une maintenance avec collecte de données pour le groupe d'hôtes avec l'ID "2" et avec les tags de problème **service:mysqld** et **error**. Il doit être actif du 22.01.2013 au 22.01.2014, entrer en vigueur chaque dimanche à 18h00 et durer une heure. Requête : ```json { "jsonrpc": "2.0", "method": "maintenance.create", "params": { "name": "Sunday maintenance", "active_since": 1358844540, "active_till": 1390466940, "tags_evaltype": 0, "groups": [ {"groupid": "2"} ], "timeperiods": [ { "period": 3600, "timeperiod_type": 3, "start_time": 64800, "every": 1, "dayofweek": 64 } ], "tags": [ { "tag": "service", "operator": "0", "value": "mysqld" }, { "tag": "error", "operator": "2", "value": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3" ] }, "id": 1 } ``` #### Creating an e-mail media type Create a new e-mail media type with a custom SMTP port and message templates. Request: ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "0", "name": "E-mail", "smtp_server": "mail.example.com", "smtp_helo": "example.com", "smtp_email": "zabbix@example.com", "smtp_port": "587", "content_type": "1", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "Problem: {EVENT.NAME}", "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" started at {EVENT.TIME}." }, { "eventsource": "0", "recovery": "1", "subject": "Resolved in {EVENT.DURATION}: {EVENT.NAME}", "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}." }, { "eventsource": "0", "recovery": "2", "subject": "Updated problem in {EVENT.AGE}: {EVENT.NAME}", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}." } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "7" ] }, "id": 1 } ``` #### Création d'un type de support email Créez un nouveau type de support email avec un port SMTP personnalisé et des modèles de message. Requête : ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "0", "name": "E-mail", "smtp_server": "mail.example.com", "smtp_helo": "example.com", "smtp_email": "zabbix@example.com", "smtp_port": "587", "content_type": "1", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "Problem: {EVENT.NAME}", "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" started at {EVENT.TIME}." }, { "eventsource": "0", "recovery": "1", "subject": "Resolved in {EVENT.DURATION}: {EVENT.NAME}", "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}." }, { "eventsource": "0", "recovery": "2", "subject": "Updated problem in {EVENT.AGE}: {EVENT.NAME}", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}." } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "7" ] }, "id": 1 } ``` #### Creating a new global regular expression. Request: ```json { "jsonrpc": "2.0", "method": "regexp.create", "params": { "name": "Storage devices for SNMP discovery", "test_string": "/boot", "expressions": [ { "expression": "^(Physical memory|Virtual memory|Memory buffers|Cached memory|Swap space)$", "expression_type": "4", "case_sensitive": "1" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "regexpids": [ "16" ] }, "id": 1 } ``` #### Création d'une nouvelle expression régulière globale. Requête : ```json { "jsonrpc": "2.0", "method": "regexp.create", "params": { "name": "Storage devices for SNMP discovery", "test_string": "/boot", "expressions": [ { "expression": "^(Physical memory|Virtual memory|Memory buffers|Cached memory|Swap space)$", "expression_type": "4", "case_sensitive": "1" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "regexpids": [ "16" ] }, "id": 1 } ``` #### Creating a new item Let's create a new [item](/manual/api/reference/item/object) on "Zabbix server" using the data we've obtained from the previous `host.get` request. This can be done by using the [item.create](/manual/api/reference/item/create) method: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Free disk space on /home/joe/", "key_": "vfs.fs.size[/home/joe/,free]", "hostid": "10084", "type": 0, "value_type": 3, "interfaceid": "1", "delay": 30 }, "auth": "0424bd59b807674191e7d77572075f33", "id": 3 } ``` A successful response will contain the ID of the newly created item, which can be used to reference the item in the following requests: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "24759" ] }, "id": 3 } ``` ::: notetip The `item.create` method as well as other create methods can also accept arrays of objects and create multiple items with one API call. ::: #### Création d'un nouvel élément Créons un nouvel [élément](/manual/api/reference/item/object) sur l'hôte "Zabbix server" en utilisant les données que nous avons obtenues de la précédente requête `host.get`. Cela peut être fait en utilisant la méthode [item.create](/manual/api/reference/item/create) : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Free disk space on /home/joe/", "key_": "vfs.fs.size[/home/joe/,free]", "hostid": "10084", "type": 0, "value_type": 3, "interfaceid": "1", "delay": 30 }, "auth": "0424bd59b807674191e7d77572075f33", "id": 3 } ``` Une réponse réussie contiendra l'ID du nouvel élément créé, qui peut être utilisé pour référencer l'élément dans les demandes suivantes : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "24759" ] }, "id": 3 } ``` ::: notetip La méthode `item.create` ainsi que d'autres méthodes de création peuvent également accepter des tableaux d'objets et créer plusieurs éléments avec un seul appel d'API. ::: #### Creating an item prototype with preprocessing Create an item using change per second and a custom multiplier as a second step. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "name": "Incoming network traffic on {#IFNAME}", "key_": "net.if.in[{#IFNAME}]", "hostid": "10001", "ruleid": "27665", "type": 0, "value_type": 3, "delay": "60s", "units": "bps", "interfaceid": "1155", "preprocessing": [ { "type": 10, "params": "", "error_handler": 0, "error_handler_params": "" }, { "type": 1, "params": "8", "error_handler": 2, "error_handler_params": "10" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44211" ] }, "id": 1 } ``` #### Création d'un prototype d'élément avec prétraitement Créez un élément en utilisant le changement par seconde et un multiplicateur personnalisé comme deuxième étape. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "name": "Incoming network traffic on {#IFNAME}", "key_": "net.if.in[{#IFNAME}]", "hostid": "10001", "ruleid": "27665", "type": 0, "value_type": 3, "delay": "60s", "units": "bps", "interfaceid": "1155", "preprocessing": [ { "type": 10, "params": "", "error_handler": 0, "error_handler_params": "" }, { "type": 1, "params": "8", "error_handler": 2, "error_handler_params": "10" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44211" ] }, "id": 1 } ``` #### Creating an item with preprocessing Create an item using custom multiplier. Request: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Device uptime", "key_": "sysUpTime", "hostid": "11312", "type": 4, "snmp_oid": "SNMPv2-MIB::sysUpTime.0", "value_type": 1, "delay": "60s", "units": "uptime", "interfaceid": "1156", "preprocessing": [ { "type": 1, "params": "0.01", "error_handler": 1, "error_handler_params": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44210" ] }, "id": 1 } ``` #### Création d'un élément avec prétraitement Créez un élément à l'aide d'un multiplicateur personnalisé. Requête : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "name": "Device uptime", "key_": "sysUpTime", "hostid": "11312", "type": 4, "snmp_oid": "SNMPv2-MIB::sysUpTime.0", "value_type": 1, "delay": "60s", "units": "uptime", "interfaceid": "1156", "preprocessing": [ { "type": 1, "params": "0.01", "error_handler": 1, "error_handler_params": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44210" ] }, "id": 1 } ``` #### Creating an LLD rule Create a Zabbix agent LLD rule to discover mounted file systems. Discovered items will be updated every 30 seconds. Request: ```json { "jsonrpc": "2.0", "method": "discoveryrule.create", "params": { "name": "Mounted filesystem discovery", "key_": "vfs.fs.discovery", "hostid": "10197", "type": 0, "interfaceid": "112", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "27665" ] }, "id": 1 } ``` #### Création d'une règle de découverte bas niveau Créer une règle de découverte bas niveau pour découvrir les systèmes de fichiers montés. Les objets découverts seront mis à jour toutes les 30 secondes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.create", "params": { "name": "Mounted filesystem discovery", "key_": "vfs.fs.discovery", "hostid": "10197", "type": "0", "interfaceid": "112", "delay": "30s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "27665" ] }, "id": 1 } ``` #### Creating an SLA Instruct to create an SLA entry for: * tracking uptime for SQL-engine related services; * custom schedule of all weekdays excluding last hour on Saturday; * an effective date of the last day of the year 2022; * with 1 hour and 15 minutes long planned downtime starting at midnight on the 4th of July; * SLA weekly report calculation will be on; * the minimum acceptable SLO will be 99.9995%. #### Création d'un SLA Lancer la création d'une entrée SLA  : * pour suivre de la disponibilité des services liés au moteur SQL ; * avec horaire personnalisé tous les jours de la semaine à l'exception de la dernière heure du samedi ; * avec une date effective au dernier jour de l'année 2022 ; * avec 1 heure et 15 minutes d'arrêt planifié à partir de minuit le 4 juillet ; * le calcul du rapport hebdomadaire SLA sera activé ; * le SLO minimum acceptable sera de 99,9995 %. #### Creating a role Create a role with type "User" and denied access to two UI elements. Request: ```json { "jsonrpc": "2.0", "method": "role.create", "params": { "name": "Operator", "type": "1", "rules": { "ui": [ { "name": "monitoring.hosts", "status": "0" }, { "name": "monitoring.maps", "status": "0" } ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` #### Création d'un rôle Créez un rôle avec le type "Utilisateur" et refusez l'accès à deux éléments de l'interface utilisateur. Requête : ```json { "jsonrpc": "2.0", "method": "role.create", "params": { "name": "Operator", "type": "1", "rules": { "ui": [ { "name": "monitoring.hosts", "status": "0" }, { "name": "monitoring.maps", "status": "0" } ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` #### Creating a scheduled report Create a weekly report that will be prepared for the previous week every Monday-Friday at 12:00 from 2021-04-01 to 2021-08-31. Request: ```json { "jsonrpc": "2.0", "method": "report.create", "params": { "userid": "1", "name": "Weekly report", "dashboardid": "1", "period": "1", "cycle": "1", "start_time": "43200", "weekdays": "31", "active_since": "2021-04-01", "active_till": "2021-08-31", "subject": "Weekly report", "message": "Report accompanying text", "status": "1", "description": "Report description", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" }, { "userid": "2", "access_userid": "0", "exclude": "1" } ], "user_groups": [ { "usrgrpid": "7", "access_userid": "0" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "reportids": [ "1" ] }, "id": 1 } ``` #### Création d'un rapport planifié Créez un rapport hebdomadaire qui sera préparé pour la semaine précédente tous les lundis-vendredis à 12h00 du 2021-04-01 au 2021-08-31. Requête : ```json { "jsonrpc": "2.0", "method": "report.create", "params": { "userid": "1", "name": "Weekly report", "dashboardid": "1", "period": "1", "cycle": "1", "start_time": "43200", "weekdays": "31", "active_since": "2021-04-01", "active_till": "2021-08-31", "subject": "Weekly report", "message": "Report accompanying text", "status": "1", "description": "Report description", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" }, { "userid": "2", "access_userid": "0", "exclude": "1" } ], "user_groups": [ { "usrgrpid": "7", "access_userid": "0" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "reportids": [ "1" ] }, "id": 1 } ``` #### Creating a script media type Create a new script media type with a custom value for the number of attempts and the interval between them. Request: ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "1", "name": "Push notifications", "exec_path": "push-notification.sh", "exec_params": "{ALERT.SENDTO}\n{ALERT.SUBJECT}\n{ALERT.MESSAGE}\n", "maxattempts": "5", "attempt_interval": "11s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "8" ] }, "id": 1 } ``` #### Création d'un type de média de script Créez un nouveau type de média de script avec une valeur personnalisée pour le nombre de tentatives et l'intervalle entre elles. Requête : ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "1", "name": "Push notifications", "exec_path": "push-notification.sh", "exec_params": "{ALERT.SENDTO}\n{ALERT.SUBJECT}\n{ALERT.MESSAGE}\n", "maxattempts": "5", "attempt_interval": "11s" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "8" ] }, "id": 1 } ``` #### Creating a service Create a service that will be switched to problem state, if at least one child has a problem. Request: ```json { "jsonrpc": "2.0", "method": "service.create", "params": { "name": "Server 1", "algorithm": 1, "sortorder": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "serviceids": [ "5" ] }, "id": 1 } ``` #### Création d'un service Créez un service qui passera à l'état de problème, si au moins un enfant a un problème. Requête : ```json { "jsonrpc": "2.0", "method": "service.create", "params": { "name": "Server 1", "algorithm": 1, "sortorder": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "serviceids": [ "5" ] }, "id": 1 } ``` #### Creating a slideshow A slideshow will run automatically if the dashboard contains two or more pages (see [Adding pages](#adding_pages)) and if one of the following is true: - The *Start slideshow automatically* option is marked in dashboard properties - The dashboard URL contains a `slideshow=1` parameter The pages rotate according to the intervals given in the properties of the dashboard and individual pages. Click on: - *Stop slideshow* - to stop the slideshow - *Start slideshow* - to start the slideshow  Slideshow-related controls are also available in [kiosk mode](#viewing_and_editing_a_dashboard) (where only the page content is shown): -  - stop slideshow -  - start slideshow -  - go back one page -  - go to the next page #### Création d'un diaporama Un diaporama s'exécutera automatiquement si le tableau de bord contient deux pages ou plus (voir [Ajouter des pages](#adding_pages)) et si l'une des conditions suivantes est vraie : - L'option *Démarrer le diaporama automatiquement* est marquée dans les propriétés du tableau de bord - L'URL du tableau de bord contient un paramètre `slideshow=1` Les pages tournent selon les intervalles indiqués dans les propriétés du tableau de bord et des pages individuelles. Cliquer sur : - *Arrêter le diaporama* - pour arrêter le diaporama - *Démarrer le diaporama* - pour démarrer le diaporama  Les commandes liées au diaporama sont également disponibles en [mode kiosque](#viewing_and_editing_a_dashboard) (où seul le contenu de la page est affiché) : -  - arrêter le diaporama -  - démarrer le diaporama -  - revenir en arrière d'une page -  - aller à la page suivante #### Creating a task Create a task `check now` for two items. One is an item, the other is a low-level discovery rule. Request: ```json { "jsonrpc": "2.0", "method": "task.create", "params": [ { "type": 6, "request": { "itemid": "10092" } }, { "type": "6", "request": { "itemid": "10093" } } ], "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "taskids": [ "1", "2" ] }, "id": 1 } ``` Create a task `diagnostic information` task. Request: ```json { "jsonrpc": "2.0", "method": "task.create", "params": [ { "type": 1, "request": { "alerting": { "stats": [ "alerts" ], "top": { "media.alerts": 10 } }, "lld": { "stats": "extend", "top": { "values": 5 } } }, "proxy_hostid": 0 } ], "auth": "700ca65537074ec963db7efabda78259", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "taskids": [ "3" ] }, "id": 2 } ``` #### Création d'une tâche Créez une tâche "vérifier maintenant" pour deux éléments. L'un est un élément, l'autre est une règle de découverte de bas niveau. Requête : ```json { "jsonrpc": "2.0", "method": "task.create", "params": [ { "type": 6, "request": { "itemid": "10092" } }, { "type": "6", "request": { "itemid": "10093" } } ], "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "taskids": [ "1", "2" ] }, "id": 1 } ``` Créez une tâche "informations de diagnostic". Requête : ```json { "jsonrpc": "2.0", "method": "task.create", "params": [ { "type": 1, "request": { "alerting": { "stats": [ "alerts" ], "top": { "media.alerts": 10 } }, "lld": { "stats": "extend", "top": { "values": 5 } } }, "proxy_hostid": 0 } ], "auth": "700ca65537074ec963db7efabda78259", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "taskids": [ "3" ] }, "id": 2 } ``` #### Creating a template Create a template with tags and link two templates to this template. Request: ```json { "jsonrpc": "2.0", "method": "template.create", "params": { "host": "Linux template", "groups": { "groupid": 1 }, "templates": [ { "templateid": "11115" }, { "templateid": "11116" } ], "tags": [ { "tag": "Host name", "value": "{HOST.NAME}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "11117" ] }, "id": 1 } ``` #### Création d'un modèle Créez un modèle avec des tags et liez deux modèles à ce modèle. Requête : ```json { "jsonrpc": "2.0", "method": "template.create", "params": { "host": "Linux template", "groups": { "groupid": 1 }, "templates": [ { "templateid": "11115" }, { "templateid": "11116" } ], "tags": [ { "tag": "Host name", "value": "{HOST.NAME}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "11117" ] }, "id": 1 } ``` #### Creating a template dashboard Create a template dashboard named “Graphs” with one Graph widget on a single dashboard page. Request: ```json { "jsonrpc": "2.0", "method": "templatedashboard.create", "params": { "templateid": "10318", "name": "Graphs", "pages": [ { "widgets": [ { "type": "graph", "x": 0, "y": 0, "width": 12, "height": 5, "view_mode": 0, "fields": [ { "type": 6, "name": "graphid", "value": "1123" } ] } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "dashboardids": [ "32" ] }, "id": 1 } ``` #### Création d'un modèle de tableau de bord Créez un modèle de tableau de bord nommé "Graphs" avec un widget Graphique sur une seule page de tableau de bord. Requête : ```json { "jsonrpc": "2.0", "method": "templatedashboard.create", "params": { "templateid": "10318", "name": "Graphs", "pages": [ { "widgets": [ { "type": "graph", "x": 0, "y": 0, "width": 12, "height": 5, "view_mode": 0, "fields": [ { "type": 6, "name": "graphid", "value": "1123" } ] } ] } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "dashboardids": [ "32" ] }, "id": 1 } ``` #### Creating a template To create a template, do the following: - Go to *Configuration → Templates* - Click on *Create template* - Edit template attributes The **Templates** tab contains general template attributes.  All mandatory input fields are marked with a red asterisk. Template attributes: |Parameter|Description| |--|--------| |*Template name*|Unique template name. Alphanumerics, spaces, dots, dashes, and underscores are allowed. However, leading and trailing spaces are disallowed.| |*Visible name*|If you set this name, it will be the one visible in lists, maps, etc.| |*Templates*|Link one or more "nested" templates to this template. All entities (items, triggers, graphs, etc.) will be inherited from the linked templates.<br>To link a new template, start typing the template name in the *Link new templates* field. A list of matching templates will appear; scroll down to select. Alternatively, you may click on *Select* next to the field and select templates from the list in a popup window. The templates that are selected in the *Link new templates* field will be linked to the template when the template configuration form is saved or updated.<br>To unlink a template, use one of the two options in the *Linked templates* block:<br>*Unlink* - unlink the template, but preserve its items, triggers, and graphs<br>*Unlink and clear* - unlink the template and remove all its items, triggers, and graphs| |*Groups*|Host/template groups the template belongs to.| |*Description*|Enter the template description.| The **Tags** tab allows you to define template-level [tags](/manual/config/tagging). All problems of hosts linked to this template will be tagged with the values entered here.  User macros, {INVENTORY.\*} macros, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros are supported in tags. The **Macros** tab allows you to define template-level [user macros](/manual/config/macros/user_macros) as a name-value pairs. Note that macro values can be kept as plain text, secret text, or Vault secret. Adding a description is also supported.  You may also view here macros from linked templates and global macros if you select the *Inherited and template macros* option. That is where all defined user macros for the template are displayed with the value they resolve to as well as their origin.  For convenience, links to respective templates and global macro configuration are provided. It is also possible to edit a nested template/global macro on the template level, effectively creating a copy of the macro on the template. The **Value mapping** tab allows to configure human-friendly representation of item data in [value mappings](/manual/config/items/mapping). Buttons: | | | |--|--------| ||Add the template. The added template should appear in the list.| ||Update the properties of an existing template.| ||Create another template based on the properties of the current template, including the entities (items, triggers, etc) inherited from linked templates.| ||Create another template based on the properties of the current template, including the entities (items, triggers, etc) both inherited from linked templates and directly attached to the current template.| ||Delete the template; entities of the template (items, triggers, etc) remain with the linked hosts.| ||Delete the template and all its entities from linked hosts.| ||Cancel the editing of template properties.| With a template created, it is time to add some entities to it. ::: noteimportant Items have to be added to a template first. Triggers and graphs cannot be added without the corresponding item. ::: #### Création d'un modèle Pour créer un modèle, procédez comme suit : - Allez dans *Configuration → Modèles* - Cliquez sur *Créer un modèle* - Modifiez les attributs du modèle L'onglet **Modèles** contient les attributs généraux des modèles.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Attributs du modèle : |Paramètre|Description| |--|--------| |*Nom du modèle*|Nom de modèle unique. Les caractères alphanumériques, les espaces, les points, les tirets et les traits de soulignement sont autorisés. Cependant, les espaces de début et de fin ne sont pas autorisés.| |*Nom visible*|Si vous définissez ce nom, ce sera celui visible dans les listes, cartes, etc.| |*Modèles*|Liez un ou plusieurs modèles "imbriqués" à ce modèle. Toutes les entités (éléments, déclencheurs, graphiques, etc.) seront héritées des modèles liés.<br>Pour lier un nouveau modèle, commencez à saisir le nom du modèle dans le champ *Lier de nouveaux modèles*. Une liste de modèles correspondants apparaîtra ; faites défiler vers le bas pour sélectionner. Vous pouvez également cliquer sur *Sélectionner* à côté du champ et sélectionner des modèles dans la liste dans une fenêtre contextuelle. Les modèles sélectionnés dans le champ *Lier de nouveaux modèles* seront liés au modèle lors de l'enregistrement ou de la mise à jour du formulaire de configuration du modèle.<br>Pour dissocier un modèle, utilisez l'une des deux options du bloc *Modèles liés* :<br>*Dissocier* - dissocier le modèle, mais conserver ses éléments, déclencheurs et graphiques<br>*Dissocier et effacer* - dissocier le modèle et supprimer tous ses éléments, déclencheurs et graphiques| |*Groupes*|Groupes d'hôtes/de modèles auxquels appartient le modèle.| |*Description*|Entrez la description du modèle.| L'onglet **Tags** vous permet de définir des [tags](/manual/config/tagging) au niveau du modèle. Tous les problèmes des hôtes liés à ce modèle seront marqués avec les valeurs saisies ici.  Les macros utilisateur, les macros {INVENTORY.\*}, les macros {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} et {HOST.ID} sont pris en charge dans les tags. L'onglet **Macros** vous permet de définir des [macros utilisateur](/manual/config/macros/user_macros) au niveau du modèle sous forme de paires nom-valeur. Notez que les valeurs de macro peuvent être conservées sous forme de texte brut, de texte secret ou de secret de coffre-fort. L'ajout d'une description est également pris en charge.  Vous pouvez également afficher ici les macros des modèles liés et les macros globales si vous sélectionnez l'option *Macros héritées et du modèle*. C'est là que toutes les macros utilisateur définies pour le modèle sont affichées avec la valeur à laquelle elles se résolvent ainsi que leur origine.  Pour plus de commodité, des liens vers les modèles respectifs et la configuration globale des macros sont fournis. Il est également possible de modifier un modèle imbriqué/une macro globale au niveau du modèle, créant ainsi une copie de la macro sur le modèle. L'onglet **Table de correspondance** permet de configurer une représentation conviviale des données d'éléments dans [tables de correspondance](/manual/config/items/mapping). Boutons : | | | |--|--------| ||Ajouter le modèle. Le modèle ajouté doit apparaître dans la liste.| ||Mettre à jour les propriétés d'un modèle existant.| ||Créer un autre modèle basé sur les propriétés du modèle actuel, y compris les entités (éléments, déclencheurs, etc.) héritées des modèles liés.| ||Créer un autre modèle basé sur les propriétés du modèle actuel, y compris les entités (éléments, déclencheurs, etc.) héritées des modèles liés et directement attachées au modèle actuel.| ||Supprimer le modèle ; les entités du modèle (éléments, déclencheurs, etc.) restent avec les hôtes liés.| ||Supprimer le modèle et toutes ses entités des hôtes liés.| ||Annuler la modification des propriétés du modèle.| Une fois le modèle créé, il est temps d'y ajouter des entités. ::: noteimportant Les éléments doivent d'abord être ajoutés à un modèle. Les déclencheurs et les graphiques ne peuvent pas être ajoutés sans l'élément correspondant. ::: #### Creating a trigger Create a trigger with a single trigger dependency. Request: ```json { "jsonrpc": "2.0", "method": "trigger.create", "params": [ { "description": "Processor load is too high on {HOST.NAME}", "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5", "dependencies": [ { "triggerid": "17367" } ] }, { "description": "Service status", "expression": "length(last(/Linux server/log[/var/log/system,Service .* has stopped]))<>0", "dependencies": [ { "triggerid": "17368" } ], "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17369", "17370" ] }, "id": 1 } ``` #### Création d'un déclencheur Créez un déclencheur avec une seule dépendance de déclencheur. Requête : ```json { "jsonrpc": "2.0", "method": "trigger.create", "params": [ { "description": "Processor load is too high on {HOST.NAME}", "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5", "dependencies": [ { "triggerid": "17367" } ] }, { "description": "Service status", "expression": "length(last(/Linux server/log[/var/log/system,Service .* has stopped]))<>0", "dependencies": [ { "triggerid": "17368" } ], "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17369", "17370" ] }, "id": 1 } ``` #### Creating a trigger prototype Create a trigger prototype to detect when a file system has less than 20% free disk space. Request: ```json { "jsonrpc": "2.0", "method": "triggerprototype.create", "params": { "description": "Free disk space is less than 20% on volume {#FSNAME}", "expression": "last(/Zabbix server/vfs.fs.size[{#FSNAME},pfree])<20", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17372" ] }, "id": 1 } ``` #### Création d'un prototype de déclencheur Créez un prototype de déclencheur pour détecter lorsqu'un système de fichiers dispose de moins de 20 % d'espace disque libre. Requête : ```json { "jsonrpc": "2.0", "method": "triggerprototype.create", "params": { "description": "Free disk space is less than 20% on volume {#FSNAME}", "expression": "last(/Zabbix server/vfs.fs.size[{#FSNAME},pfree])<20", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17372" ] }, "id": 1 } ``` #### Creating a user Create a new user, add him to a user group and create a new media for him. Request: ```json { "jsonrpc": "2.0", "method": "user.create", "params": { "username": "John", "passwd": "Doe123", "roleid": "5", "usrgrps": [ { "usrgrpid": "7" } ], "medias": [ { "mediatypeid": "1", "sendto": [ "support@company.com" ], "active": 0, "severity": 63, "period": "1-7,00:00-24:00" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "userids": [ "12" ] }, "id": 1 } ``` #### Création d'un utilisateur Créez un nouvel utilisateur, ajoutez-le à un groupe d'utilisateurs et créez un nouveau média pour lui. Requête : ```json { "jsonrpc": "2.0", "method": "user.create", "params": { "username": "John", "passwd": "Doe123", "roleid": "5", "usrgrps": [ { "usrgrpid": "7" } ], "medias": [ { "mediatypeid": "1", "sendto": [ "support@company.com" ], "active": 0, "severity": 63, "period": "1-7,00:00-24:00" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "userids": [ "12" ] }, "id": 1 } ``` #### Creating a user group Create a user group, which denies access to host group "2", and add a user to it. Request: ``` {.java} { "jsonrpc": "2.0", "method": "usergroup.create", "params": { "name": "Operation managers", "rights": { "permission": 0, "id": "2" }, "users": [ {"userid": "12"} ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "usrgrpids": [ "20" ] }, "id": 1 } ``` #### Création d'un groupe d'utilisateurs Créez un groupe d'utilisateurs qui refuse l'accès au groupe d'hôtes "2" et ajoutez-y un utilisateur. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usergroup.create", "params": { "name": "Operation managers", "rights": { "permission": 0, "id": "2" }, "users": [ {"userid": "12"} ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "usrgrpids": [ "20" ] }, "id": 1 } ``` #### Creating a value map Create one value map with two mappings. Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.create", "params": { "hostid": "50009", "name": "Service state", "mappings": [ { "type": "1", "value": "1", "newvalue": "Up" }, { "type": "5", "newvalue": "Down" } ] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "1" ] }, "id": 1 } ``` #### Création d'une carte de valeurs Créez une carte de valeurs avec deux correspondances. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.create", "params": { "hostid": "50009", "name": "Service state", "mappings": [ { "type": "1", "value": "1", "newvalue": "Up" }, { "type": "5", "newvalue": "Down" } ] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "1" ] }, "id": 1 } ``` #### Creating a webhook media type Create a new webhook media type. Request: ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "4", "name": "Webhook", "script": "var Webhook = {\r\n token: null,\r\n to: null,\r\n subject: null,\r\n message: null,\r\n\r\n sendMessage: function() {\r\n // some logic\r\n }\r\n}", "parameters": [ { "name": "Message", "value": "{ALERT.MESSAGE}" }, { "name": "Subject", "value": "{ALERT.SUBJECT}" }, { "name": "To", "value": "{ALERT.SENDTO}" }, { "name": "Token", "value": "<Token>" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "9" ] }, "id": 1 } ``` #### Création d'un type de média webhook Créez un nouveau type de média webhook. Requête : ```json { "jsonrpc": "2.0", "method": "mediatype.create", "params": { "type": "4", "name": "Webhook", "script": "var Webhook = {\r\n token: null,\r\n to: null,\r\n subject: null,\r\n message: null,\r\n\r\n sendMessage: function() {\r\n // some logic\r\n }\r\n}", "parameters": [ { "name": "Message", "value": "{ALERT.MESSAGE}" }, { "name": "Subject", "value": "{ALERT.SUBJECT}" }, { "name": "To", "value": "{ALERT.SENDTO}" }, { "name": "Token", "value": "<Token>" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "9" ] }, "id": 1 } ``` #### Creating a web scenario Create a web scenario to monitor the company home page. The scenario will have two steps, to check the home page and the "About" page and make sure they return the HTTP status code 200. Request: ```json { "jsonrpc": "2.0", "method": "httptest.create", "params": { "name": "Homepage check", "hostid": "10085", "steps": [ { "name": "Homepage", "url": "http://example.com", "status_codes": "200", "no": 1 }, { "name": "Homepage / About", "url": "http://example.com/about", "status_codes": "200", "no": 2 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "httptestids": [ "5" ] }, "id": 1 } ``` #### Création d'un scénario Web Créez un scénario Web pour surveiller la page d'accueil d'une société. Le scénario comportera deux étapes : vérifier la page d’accueil et la page "About" et s’assurer qu’elles renvoient le code d’état HTTP 200. Requête : ```json { "jsonrpc": "2.0", "method": "httptest.create", "params": { "name": "Homepage check", "hostid": "10085", "steps": [ { "name": "Homepage", "url": "http://mycompany.com", "status_codes": "200", "no": 1 }, { "name": "Homepage / About", "url": "http://mycompany.com/about", "status_codes": "200", "no": 2 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "httptestids": [ "5" ] }, "id": 1 } ``` ### Creating custom LLD rules It is also possible to create a completely custom LLD rule, discovering any type of entities - for example, databases on a database server. To do so, a custom item should be created that returns JSON, specifying found objects and optionally - some properties of them. The amount of macros per entity is not limited - while the built-in discovery rules return either one or two macros (for example, two for filesystem discovery), it is possible to return more. The required JSON format is best illustrated with an example. Suppose we are running an old Zabbix 1.8 agent (one that does not support "vfs.fs.discovery"), but we still need to discover file systems. Here is a simple Perl script for Linux that discovers mounted file systems and outputs JSON, which includes both file system name and type. One way to use it would be as a UserParameter with key "vfs.fs.discovery\_perl": ``` {.perl} #!/usr/bin/perl $first = 1; print "[\n"; for (`cat /proc/mounts`) { ($fsname, $fstype) = m/\S+ (\S+) (\S+)/; print "\t,\n" if not $first; $first = 0; print "\t{\n"; print "\t\t\"{#FSNAME}\":\"$fsname\",\n"; print "\t\t\"{#FSTYPE}\":\"$fstype\"\n"; print "\t}\n"; } print "]\n"; ``` ::: noteimportant Allowed symbols for LLD macro names are **0-9** , **A-Z** , **\_** , **.**\ \ Lowercase letters are not supported in the names. ::: An example of its output (reformatted for clarity) is shown below. JSON for custom discovery checks has to follow the same format. ``` {.javascript} [ { "{#FSNAME}":"/", "{#FSTYPE}":"rootfs" }, { "{#FSNAME}":"/sys", "{#FSTYPE}":"sysfs" }, { "{#FSNAME}":"/proc", "{#FSTYPE}":"proc" }, { "{#FSNAME}":"/dev", "{#FSTYPE}":"devtmpfs" }, { "{#FSNAME}":"/dev/pts", "{#FSTYPE}":"devpts" }, { "{#FSNAME}":"/lib/init/rw", "{#FSTYPE}":"tmpfs" }, { "{#FSNAME}":"/dev/shm", "{#FSTYPE}":"tmpfs" }, { "{#FSNAME}":"/home", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/tmp", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/usr", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/var", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/sys/fs/fuse/connections", "{#FSTYPE}":"fusectl" } ] ``` In previous example it is required that the keys match the LLD macro names used in prototypes, the alternative is to extract LLD macro values using JSONPath `{#FSNAME}` → `$.fsname` and `{#FSTYPE}` → `$.fstype`, thus making such script possible: ``` {.perl} #!/usr/bin/perl $first = 1; print "[\n"; for (`cat /proc/mounts`) { ($fsname, $fstype) = m/\S+ (\S+) (\S+)/; print "\t,\n" if not $first; $first = 0; print "\t{\n"; print "\t\t\"fsname\":\"$fsname\",\n"; print "\t\t\"fstype\":\"$fstype\"\n"; print "\t}\n"; } print "]\n"; ``` An example of its output (reformatted for clarity) is shown below. JSON for custom discovery checks has to follow the same format. ``` {.javascript} [ { "fsname":"/", "fstype":"rootfs" }, { "fsname":"/sys", "fstype":"sysfs" }, { "fsname":"/proc", "fstype":"proc" }, { "fsname":"/dev", "fstype":"devtmpfs" }, { "fsname":"/dev/pts", "fstype":"devpts" }, { "fsname":"/lib/init/rw", "fstype":"tmpfs" }, { "fsname":"/dev/shm", "fstype":"tmpfs" }, { "fsname":"/home", "fstype":"ext3" }, { "fsname":"/tmp", "fstype":"ext3" }, { "fsname":"/usr", "fstype":"ext3" }, { "fsname":"/var", "fstype":"ext3" }, { "fsname":"/sys/fs/fuse/connections", "fstype":"fusectl" } ] ``` Then, in the discovery rule's "Filter" field, we could specify "{\#FSTYPE}" as a macro and "rootfs|ext3" as a regular expression. ::: noteclassic You don't have to use macro names FSNAME/FSTYPE with custom LLD rules, you are free to use whatever names you like. In case JSONPath is used then LLD row will be an array element that can be an object, but it can be also another array or a value. ::: Note that, if using a user parameter, the return value is limited to 512 KB. For more details, see [data limits for LLD return values](/manual/discovery/low_level_discovery/notes#data_limits_for_return_values). ### Création de règles LLD personnalisées Il est également possible de créer une règle LLD entièrement personnalisée, découvrant tout type d'entités - par exemple, des bases de données sur un serveur de base de données. Pour ce faire, un élément personnalisé doit être créé qui renvoie JSON, en spécifiant les objets trouvés et éventuellement - certaines de leurs propriétés. Le nombre de macros par entité n'est pas limité - alors que les règles de découverte intégrées renvoient une ou deux macros (par exemple, deux pour la découverte du système de fichiers), il est possible d'en renvoyer davantage. Le format JSON requis est mieux illustré par un exemple. Supposons que nous exécutons un ancien agent Zabbix 1.8 (qui ne prend pas en charge "vfs.fs.discovery"), mais que nous devons encore découvrir les systèmes de fichiers. Voici un script Perl simple pour Linux qui découvre les systèmes de fichiers montés et génère JSON, qui inclut à la fois le nom et le type du système de fichiers. Une façon de l'utiliser serait en tant que UserParameter avec la clé "vfs.fs.discovery\_perl": ``` {.perl} #!/usr/bin/perl $first = 1; print "[\n"; for (`cat /proc/mounts`) { ($fsname, $fstype) = m/\S+ (\S+) (\S+)/; print "\t,\n" if not $first; $first = 0; print "\t{\n"; print "\t\t\"{#FSNAME}\":\"$fsname\",\n"; print "\t\t\"{#FSTYPE}\":\"$fstype\"\n"; print "\t}\n"; } print "]\n"; ``` ::: noteimportant Les symboles autorisés pour les noms de macro LLD sont **0-9** , **A-Z** , **\_** , **.**\ \ Les lettres minuscules ne sont pas prises en charge dans les noms. ::: Un exemple de sa sortie (reformaté pour plus de clarté) est présenté ci-dessous. Le JSON pour les vérifications de découverte personnalisées doit suivre le même format. ``` {.javascript} [ { "{#FSNAME}":"/", "{#FSTYPE}":"rootfs" }, { "{#FSNAME}":"/sys", "{#FSTYPE}":"sysfs" }, { "{#FSNAME}":"/proc", "{#FSTYPE}":"proc" }, { "{#FSNAME}":"/dev", "{#FSTYPE}":"devtmpfs" }, { "{#FSNAME}":"/dev/pts", "{#FSTYPE}":"devpts" }, { "{#FSNAME}":"/lib/init/rw", "{#FSTYPE}":"tmpfs" }, { "{#FSNAME}":"/dev/shm", "{#FSTYPE}":"tmpfs" }, { "{#FSNAME}":"/home", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/tmp", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/usr", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/var", "{#FSTYPE}":"ext3" }, { "{#FSNAME}":"/sys/fs/fuse/connections", "{#FSTYPE}":"fusectl" } ] ``` Dans l'exemple précédent, il est nécessaire que les clés correspondent aux noms de macro LLD utilisés dans les prototypes, l'alternative consiste à extraire les valeurs de macro LLD à l'aide de JSONPath `{#FSNAME}` → `$.fsname` et `{#FSTYPE}` → `$.fstype`, rendant ainsi possible un tel script: ``` {.perl} #!/usr/bin/perl $first = 1; print "[\n"; for (`cat /proc/mounts`) { ($fsname, $fstype) = m/\S+ (\S+) (\S+)/; print "\t,\n" if not $first; $first = 0; print "\t{\n"; print "\t\t\"fsname\":\"$fsname\",\n"; print "\t\t\"fstype\":\"$fstype\"\n"; print "\t}\n"; } print "]\n"; ``` Un exemple de sa sortie (reformaté pour plus de clarté) est présenté ci-dessous. Le JSON pour les vérifications de découverte personnalisées doit suivre le même format. ``` {.javascript} [ { "fsname":"/", "fstype":"rootfs" }, { "fsname":"/sys", "fstype":"sysfs" }, { "fsname":"/proc", "fstype":"proc" }, { "fsname":"/dev", "fstype":"devtmpfs" }, { "fsname":"/dev/pts", "fstype":"devpts" }, { "fsname":"/lib/init/rw", "fstype":"tmpfs" }, { "fsname":"/dev/shm", "fstype":"tmpfs" }, { "fsname":"/home", "fstype":"ext3" }, { "fsname":"/tmp", "fstype":"ext3" }, { "fsname":"/usr", "fstype":"ext3" }, { "fsname":"/var", "fstype":"ext3" }, { "fsname":"/sys/fs/fuse/connections", "fstype":"fusectl" } ] ``` Ensuite, dans le champ "Filtre" de la règle de découverte, nous pourrions spécifier "{\#FSTYPE}" comme macro et "rootfs|ext3" comme expression régulière. ::: noteclassic Vous n'êtes pas obligé d'utiliser les noms de macro FSNAME/FSTYPE avec des règles LLD personnalisées, vous êtes libre d'utiliser les noms que vous souhaitez. Dans le cas où JSONPath est utilisé, la ligne LLD sera un élément de tableau qui peut être un objet, mais il peut également s'agir d'un autre tableau ou d'une valeur. ::: Notez que, si vous utilisez un paramètre utilisateur, la valeur de retour est limitée à 512 Ko. Pour plus de détails, voir les [limites de données pour les valeurs de retour LLD](/manual/discovery/low_level_discovery/notes#data_limits_for_return_values). ##### Creating database [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy. Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name. ##### Création de la base de données [Créez](/manual/appendix/install/db_scripts) une base de données distincte pour le proxy Zabbix. Le serveur Zabbix et le proxy Zabbix ne peuvent pas utiliser la même base de données. S'ils sont installés sur le même hôte, la base de données proxy doit avoir un nom différent. ##### Creating database [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy. Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name. ##### Création des base de données [Créez](/manual/appendix/install/db_scripts) une base de données distincte pour le proxy Zabbix. Le serveur Zabbix et le proxy Zabbix ne peuvent pas utiliser la même base de données. S'ils sont installés sur le même hôte, la base de données proxy doit avoir un nom différent. ##### Creating database [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy. Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name. ##### Création des base de données [Créez](/manual/appendix/install/db_scripts) une base de données distincte pour le proxy Zabbix. Le serveur Zabbix et le proxy Zabbix ne peuvent pas utiliser la même base de données. S'ils sont installés sur le même hôte, la base de données proxy doit avoir un nom différent. #### Creating database For Zabbix [server](/manual/concepts/server) and [proxy](/manual/concepts/proxy) daemons a database is required. It is not needed to run Zabbix [agent](/manual/concepts/agent). ::: notewarning Separate databases are needed for Zabbix server and Zabbix proxy; they cannot use the same database. Therefore, if they are installed on the same host, their databases must be created with different names! ::: Create the database using the provided instructions for [MySQL](/manual/appendix/install/db_scripts#mysql) or [PostgreSQL](/manual/appendix/install/db_scripts#postgresql). #### Création de base de données Pour les démons [serveur](/manual/concepts/server) et [proxy](/manual/concepts/proxy) Zabbix une base de données est requise. Il n'est pas nécessaire d'exécuter l'[agent](/manual/concepts/agent) Zabbix. ::: notewarning Des bases de données distinctes sont nécessaires pour le serveur Zabbix et le proxy Zabbix ; ils ne peuvent pas utiliser la même base de données. Par conséquent, s'ils sont installés sur le même hôte, leurs bases de données doivent être créées avec des noms différents ! ::: Créez la base de données en suivant les instructions fournies pour [MySQL](/manual/appendix/install/db_scripts#mysql) ou [PostgreSQL](/manual/appendix/install/db_scripts#postgresql). #### Creating dependent item Create a dependent item for the master item with ID 24759. Only dependencies on the same host are allowed, therefore master and the dependent item should have the same hostid. Request: ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "hostid": "30074", "name": "Dependent test item", "key_": "dependent.item", "type": 18, "master_itemid": "24759", "value_type": 2 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44211" ] }, "id": 1 } ``` #### Création d'un élément dépendant Créez un élément dépendant pour l'élément principal avec l'ID 24759. Seules les dépendances sur le même hôte sont autorisées. Par conséquent, l'élément principal et l'élément dépendant doivent avoir le même hostid. Requête : ```json { "jsonrpc": "2.0", "method": "item.create", "params": { "hostid": "30074", "name": "Dependent test item", "key_": "dependent.item", "type": 18, "master_itemid": "24759", "value_type": 2 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44211" ] }, "id": 1 } ``` #### Creating dependent item prototype Create Dependent item prototype for Master item prototype with ID 44211. Only dependencies on same host (template/discovery rule) are allowed, therefore Master and Dependent item should have same hostid and ruleid. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "hostid": "10001", "ruleid": "27665", "name": "Dependent test item prototype", "key_": "dependent.prototype", "type": 18, "master_itemid": "44211", "value_type": 3 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44212" ] }, "id": 1 } ``` #### Création d'un prototype d'élément dépendant Créez un prototype d'élément dépendant pour le prototype d'élément principal avec l'ID 44211. Seules les dépendances sur le même hôte (modèle/règle de découverte) sont autorisées. Par conséquent, l'élément principal et l'élément dépendant doivent avoir les mêmes ID d'hôte et ID de règle. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.create", "params": { "hostid": "10001", "ruleid": "27665", "name": "Dependent test item prototype", "key_": "dependent.prototype", "type": 18, "master_itemid": "44211", "value_type": 3 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "44212" ] }, "id": 1 } ``` #### Creating interfaces Create an interface on two hosts. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.massadd", "params": { "hosts": [ { "hostid": "30050" }, { "hostid": "30052" } ], "interfaces": { "dns": "", "ip": "127.0.0.1", "main": 0, "port": "10050", "type": 1, "useip": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30069", "30070" ] }, "id": 1 } ``` #### Création d'interfaces Créez une interface sur deux hôtes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.massadd", "params": { "hosts": [ { "hostid": "30050" }, { "hostid": "30052" } ], "interfaces": { "dns": "", "ip": "127.0.0.1", "main": 0, "port": "10050", "type": 1, "useip": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30069", "30070" ] }, "id": 1 } ``` #### Creating multiple triggers So if create methods accept arrays, we can add multiple [triggers](/manual/api/reference/trigger/object) like so: ```json { "jsonrpc": "2.0", "method": "trigger.create", "params": [ { "description": "Processor load is too high on {HOST.NAME}", "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5", }, { "description": "Too many processes on {HOST.NAME}", "expression": "avg(/Linux server/proc.num[],5m)>300", } ], "auth": "0424bd59b807674191e7d77572075f33", "id": 4 } ``` A successful response will contain the IDs of the newly created triggers: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17369", "17370" ] }, "id": 4 } ``` #### Création de plusieurs déclencheurs Donc, si les méthodes create acceptent les tableaux, nous pouvons ajouter plusieurs [déclencheurs](/manual/api/reference/trigger/object) comme ceci : ```json { "jsonrpc": "2.0", "method": "trigger.create", "params": [ { "description": "Processor load is too high on {HOST.NAME}", "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5", }, { "description": "Too many processes on {HOST.NAME}", "expression": "avg(/Linux server/proc.num[],5m)>300", } ], "auth": "0424bd59b807674191e7d77572075f33", "id": 4 } ``` Une réponse réussie contiendra les identifiants des déclencheurs nouvellement créés : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17369", "17370" ] }, "id": 4 } ``` ### Critical ### Critique #### CRL expired or expires during server operation [*OpenSSL*]{.underline}, in server log: - before expiration: ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\ SSL routines:ssl3_get_server_certificate:certificate verify failed:\ TLS write fatal alert "certificate revoked" - after expiration: ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\ SSL routines:ssl3_get_server_certificate:certificate verify failed:\ TLS write fatal alert "certificate expired" The point here is that with valid CRL a revoked certificate is reported as "certificate revoked". When CRL expires the error message changes to "certificate expired" which is quite misleading. [*GnuTLS*]{.underline}, in server log: - before and after expiration the same: ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked. #### La CRL a expiré ou expire pendant le fonctionnement du serveur [*OpenSSL*]{.underline}, dans le journal du serveur : - avant expiration : ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\ SSL routines:ssl3_get_server_certificate:certificate verify failed:\ TLS write fatal alert "certificate revoked" - après expiration : ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\ SSL routines:ssl3_get_server_certificate:certificate verify failed:\ TLS write fatal alert "certificate expired" Le point ici est qu'avec une CRL valide, un certificat révoqué est signalé comme "certificat révoqué". Lorsque la CRL expire, le message d'erreur devient "certificat expiré", ce qui est assez trompeur. [*GnuTLS*]{.underline}, dans le journal du serveur : - avant et après expiration : ```{=html} <!-- --> ``` cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\ invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked. ### Cryptography ### Cryptographie ### Custom interface details The details object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**version**<br>(required)|integer|SNMP interface version.<br><br>Possible values are:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|integer|Whether to use bulk SNMP requests.<br><br>Possible values are:<br>0 - don't use bulk requests;<br>1 - *(default)* - use bulk requests.| |community|string|SNMP community. Used only by SNMPv1 and SNMPv2 interfaces.| |securityname|string|SNMPv3 security name. Used only by SNMPv3 interfaces.| |securitylevel|integer|SNMPv3 security level. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |authpassphrase|string|SNMPv3 authentication passphrase. Used only by SNMPv3 interfaces.| |privpassphrase|string|SNMPv3 privacy passphrase. Used only by SNMPv3 interfaces.| |authprotocol|integer|SNMPv3 authentication protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |privprotocol|integer|SNMPv3 privacy protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |contextname|string|SNMPv3 context name. Used only by SNMPv3 interfaces.| ### Détails de l'interface personnalisée L'objet détails a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**version**<br>(obligatoire)|integer|Version de l'interface SNMP.<br><br>Les valeurs possibles sont :<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|integer|Indique s'il faut utiliser les requêtes SNMP en masse.<br><br>Les valeurs possibles sont :<br>0 - ne pas utiliser les requêtes en masse ;<br>1 - *(par défaut)* - utiliser les requêtes en masse.| |community|string|Communauté SNMP. Utilisé uniquement par les interfaces SNMPv1 et SNMPv2.| |securityname|string|Nom de sécurité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |securitylevel|integer|Niveau de sécurité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - *(par défaut)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |authpassphrase|string|Mot de passe d'authentification SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |privpassphrase|string|Phrase secrète de confidentialité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |authprotocol|integer|Protocole d'authentification SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - *(par défaut)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |privprotocol|integer|Protocole de confidentialité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - *(par défaut)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |contextname|string|Nom de contexte SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| #### Custom script limit Available custom script length depends on the database used: | | | | |---|---|---| |*Database*|*Limit in characters*|*Limit in bytes*| |**MySQL**|65535|65535| |**Oracle Database**|2048|4000| |**PostgreSQL**|65535|not limited| |**SQLite (only Zabbix proxy)**|65535|not limited| #### Limite de script personnalisé La longueur de script personnalisé disponible dépend de la base de données utilisée : | | | | |---|---|---| |*Base de données*|*Limite en caractères*|*Limite en octets*| |**MySQL**|65535|65535| |**Base de données Oracle**|2048|4000| |**PostgreSQL**|65535|non limité| |**SQLite (proxy Zabbix uniquement)**|65535|non limité| # dashboard.create # dashboard.create # dashboard.delete # dashboard.delete # dashboard.get # dashboard.get ### Dashboard page The dashboard page object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboard\_pageid|string|*(readonly)* ID of the dashboard page.| |name|string|Dashboard page name.<br><br>Default: empty string.| |display\_period|integer|Dashboard page display period (in seconds).<br><br>Possible values: 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 0 (will use the default page display period).| |widgets|array|Array of the [dashboard widget](object#dashboard_widget) objects.| ### Page de tableau de bord L'objet page de tableau de bord a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |dashboard\_pageid|string|*(lecture seule)* ID de la page du tableau de bord.| |name|string|Nom de la page du tableau de bord.<br><br>Par défaut : chaîne vide.| |display\_period|integer|Période d'affichage de la page du tableau de bord (en secondes).<br><br>Valeurs possibles : 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>Par défaut : 0 (utilisera la période d'affichage de la page par défaut).| |widgets|array|Tableau des objets [widget de tableau de bord](object#dashboard_widget).| #### Dashboards Manage dashboards and make scheduled reports based on them. [Dashboard API](/manual/api/reference/dashboard) | [Template dashboard API](/manual/api/reference/templatedashboard) | [Report API](/manual/api/reference/report) #### Tableaux de bord Gérez les tableaux de bord et créez des rapports planifiés basés sur ces tableaux de bord. [API Tableau de bord](/manual/api/reference/dashboard) | [API Modèle de tableau de bord](/manual/api/reference/templatedashboard) | [API Report](/manual/api/reference/report) ### Dashboard The dashboard object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboardid|string|*(readonly)* ID of the dashboard.| |**name**<br>(required)|string|Name of the dashboard.| |userid|string|Dashboard owner user ID.| |private|integer|Type of dashboard sharing.<br><br>Possible values:<br>0 - public dashboard;<br>1 - *(default)* private dashboard.| |display\_period|integer|Default page display period (in seconds).<br><br>Possible values: 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 30.| |auto\_start|integer|Auto start slideshow.<br><br>Possible values:<br>0 - do not auto start slideshow;<br>1 - *(default)* auto start slideshow.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Tableau de bord L'objet dashboard a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboardid|string|*(lecture seule)* ID du tableau de bord.| |**name**<br>(obligatoire)|string|Nom du tableau de bord.| |userid|string|ID utilisateur du propriétaire du tableau de bord.| |private|integer|Type de partage du tableau de bord.<br><br>Valeurs possibles :<br>0 - tableau de bord public ;<br>1 - *(par défaut)* tableau de bord privé.| |display\_period|integer|Période d'affichage par défaut de la page (en secondes).<br><br>Valeurs possibles : 10, 30, 60, 120, 600, 1800, 3600.<br><br>Par défaut : 30.| |auto\_start|integer|Démarrage automatique du diaporama.<br><br>Valeurs possibles : <br>0 - ne démarre pas automatiquement le diaporama ;<br>1 - *(par défaut)* démarrage automatique du diaporama.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # dashboard.update # dashboard.update ### Dashboard user group List of dashboard permissions based on user groups. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;| ### Groupe d'utilisateurs du tableau de bord Liste des autorisations du tableau de bord en fonction des groupes d'utilisateurs. L'objet a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>(obligatoire)|string|ID du groupe d'utilisateurs.| |**permission**<br>(obligatoire)|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>2 - lecture seule ;<br>3 - lecture-écriture.| ### Dashboard user List of dashboard permissions based on users. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;| ### Utilisateur du tableau de bord Liste des autorisations du tableau de bord en fonction des utilisateurs. L'objet a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**userid**<br>(obligatoire)|string|ID de l'utilisateur.| |**permission**<br>(obligatoire)|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>2 - lecture seule ;<br>3 - lecture-écriture.| ### Dashboard widget field The dashboard widget field object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of the widget field.<br><br>Possible values:<br>0 - Integer;<br>1 - String;<br>2 - Host group;<br>3 - Host;<br>4 - Item;<br>5 - Item prototype;<br>6 - Graph;<br>7 - Graph prototype;<br>8 - Map;<br>9 - Service;<br>10 - SLA.| |**name**<br>(required)|string|Widget field name.<br><br>Possible values: see [Dashboard widget fields](/manual/api/reference/dashboard/widget_fields).| |**value**<br>(required)|mixed|Widget field value depending on the type.<br><br>Possible values: see [Dashboard widget fields](/manual/api/reference/dashboard/widget_fields).| ### Champ de widget de tableau de bord L'objet champ de widget de tableau de bord a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(obligatoire)|integer|Type de champ de widget.<br><br>Valeurs possibles :<br>0 - Entier ;<br>1 - Chaîne ;<br>2 - Groupe d'hôtes ;<br>3 - Hôte ;<br>4 - Élément ;<br>6 - Graphique ;<br>8 - Carte.| |**name**|string|Nom du champ du widget.<br><br>Valeurs possibles : voir [Champs des widget de tableau de bord](/manual/api/reference/dashboard/widget_fields).| |**value**<br>(obligatoire)|mixed|Valeur du champ du widget en fonction du type.<br><br>Valeurs possibles : voir [Champs des widget de tableau de bord](/manual/api/reference/dashboard/widget_fields).| #### Database engine This is probably the most important part of Zabbix tuning. Zabbix heavily depends on the availability and performance of database engine. - use fastest database engine, i.e. MySQL or PostgreSQL - use stable release of a database engine - rebuild MySQL or PostgreSQL from sources to get maximum performance - follow performance tuning instructions taken from MySQL or PostgreSQL documentation - for MySQL, use InnoDB table structure - ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU power. - tuning the database server for the best performance is highly recommended. - keep database tables on different hard disks - 'history', 'history\_str, 'items' 'functions', triggers', and 'trends' are most heavily used tables. - for large installations keeping MySQL temporary files in tmpfs is: - MySQL >= 5.5: not recommended ([MySQL bug \#58421](https://bugs.mysql.com/bug.php?id=58421)) - MySQL < 5.5: recommended #### Moteur de base de données C’est probablement la partie la plus importante du réglage de Zabbix. Zabbix dépend fortement de la disponibilité et des performances du moteur de base de données. - utiliser le moteur de base de données le plus rapide, à savoir MySQL ou PostgreSQL - utiliser la version stable d'un moteur de base de données - reconstruisez MySQL ou PostgreSQL à partir de sources pour obtenir des performances maximales - suivez les instructions de réglage des performances extraites de la documentation MySQL ou PostgreSQL - pour MySQL, utilisez une structure de table InnoDB - ZABBIX fonctionne au moins 1.5 fois plus vite (comparé à MyISAM) si InnoDB est utilisé. Ceci est dû au parallélisme accru. Cependant, InnoDB nécessite plus de puissance au niveau du CPU. - il est vivement recommandé d’optimiser le serveur de base de données pour obtenir les meilleures performances. - conserver les tables de base de données sur différents disques durs - 'history', 'history\_str, 'items' 'functions', triggers', et 'trends' sont les tables les plus utilisées. - pour les grandes installations, conserver les fichiers temporaires MySQL dans tmpfs est : - MySQL >= 5.5: non recommandé ([bug MySQL \#58421](https://bugs.mysql.com/bug.php?id=58421)) - MySQL < 5.5: recommandé ##### Database management system |Software|Supported versions|Comments| |--|--|------| |*MySQL/Percona*|8.0.X|Required if MySQL (or Percona) is used as Zabbix backend database. InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*MariaDB*|10.5.00-10.8.X|InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.<br>MariaDB 10.7 is supported since Zabbix 6.0.6, 10.8 since Zabbix 6.0.7.| |*Oracle*|19c - 21c|Required if Oracle is used as Zabbix backend database.| |*PostgreSQL*|13.0 - 14.X|Required if PostgreSQL is used as Zabbix backend database.| |*TimescaleDB* for PostgreSQL|2.0.1-2.6|Required if TimescaleDB is used as a PostgreSQL database extension. Make sure to install TimescaleDB Community Edition, which supports compression.| |*SQLite*|3.3.5-3.34.X|SQLite is only supported with Zabbix proxies. Required if SQLite is used as Zabbix proxy database.| ::: noteclassic Although Zabbix can work with databases available in the operating systems, for the best experience, we recommend using databases installed from the official database developer repositories. ::: ##### Système de gestion de base de données |Logiciel|Versions supportées|Commentaires| |--|--|------| |*MySQL/Percona*|8.0.X|Requis si MySQL (ou Percona) est utilisé comme base de données backend Zabbix. Le moteur InnoDB est requis. Nous vous recommandons d'utiliser la bibliothèque [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) pour créer un serveur/proxy.| |*MariaDB*|10.5.00-10.8.X|Le moteur InnoDB est requis. Nous vous recommandons d'utiliser la bibliothèque [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) pour créer un serveur/proxy.<br>MariaDB 10.7 est pris en charge depuis Zabbix 6.0.6, 10.8 depuis Zabbix 6.0.7.| |*Oracle*|19c - 21c|Obligatoire si Oracle est utilisé comme base de données backend Zabbix.| |*PostgreSQL*|13.0 - 14.X|Obligatoire si PostgreSQL est utilisé comme base de données backend Zabbix.| |*TimescaleDB* for PostgreSQL|2.0.1-2.6|Obligatoire si TimescaleDB est utilisé comme extension de base de données PostgreSQL. Assurez-vous d'installer TimescaleDB Community Edition, qui prend en charge la compression.| |*SQLite*|3.3.5-3.34.X|SQLite n'est pris en charge qu'avec les proxys Zabbix. Requis si SQLite est utilisé comme base de données proxy Zabbix.| ::: noteclassic Bien que Zabbix puisse fonctionner avec les bases de données disponibles dans les systèmes d'exploitation, pour une expérience optimale, nous vous recommandons d'utiliser les bases de données installées à partir des référentiels officiels des développeurs de bases de données. ::: #### Database size Zabbix configuration data require a fixed amount of disk space and do not grow much. Zabbix database size mainly depends on these variables, which define the amount of stored historical data: - Number of processed values per second This is the average number of new values Zabbix server receives every second. For example, if we have 3000 items for monitoring with a refresh rate of 60 seconds, the number of values per second is calculated as 3000/60 = **50**. It means that 50 new values are added to Zabbix database every second. - Housekeeper settings for history Zabbix keeps values for a fixed period of time, normally several weeks or months. Each new value requires a certain amount of disk space for data and index. So, if we would like to keep 30 days of history and we receive 50 values per second, the total number of values will be around (**30**\*24\*3600)\* **50** = 129.600.000, or about 130M of values. Depending on the database engine used, type of received values (floats, integers, strings, log files, etc), the disk space for keeping a single value may vary from 40 bytes to hundreds of bytes. Normally it is around 90 bytes per value for numeric items^**2**^. In our case, it means that 130M of values will require 130M \* 90 bytes = **10.9GB** of disk space. ::: noteclassic The size of text/log item values is impossible to predict exactly, but you may expect around 500 bytes per value. ::: - Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table **trends**. The data is used for trending and long period graphs. The one hour period can not be customized. Zabbix database, depending on the database type, requires about 90 bytes per each total. Suppose we would like to keep trend data for 5 years. Values for 3000 items will require 3000\*24\*365\* **90** = **2.2GB** per year, or **11GB** for 5 years. - Housekeeper settings for events Each Zabbix event requires approximately 250 bytes of disk space^**1**^. It is hard to estimate the number of events generated by Zabbix daily. In the worst-case scenario, we may assume that Zabbix generates one event per second. For each recovered event, an event\_recovery record is created. Normally most of the events will be recovered so we can assume one event\_recovery record per event. That means additional 80 bytes per event. Optionally events can have tags, each tag record requiring approximately 100 bytes of disk space^**1**^. The number of tags per event (\#tags) depends on configuration. So each will need an additional \#tags \* 100 bytes of disk space. It means that if we want to keep 3 years of events, this would require 3\*365\*24\*3600\* (250+80+\#tags\*100) = **\~30GB**+\#tags\*100B disk space^**2**^. ::: noteclassic ^**1**^ More when having non-ASCII event names, tags and values. ^**2**^ The size approximations are based on MySQL and might be different for other databases. ::: The table contains formulas that can be used to calculate the disk space required for Zabbix system: |Parameter|Formula for required disk space (in bytes)| |---------|------------------------------------------| |*Zabbix configuration*|Fixed size. Normally 10MB or less.| |*History*|days\*(items/refresh rate)\*24\*3600\*bytes<br>items : number of items<br>days : number of days to keep history<br>refresh rate : average refresh rate of items<br>bytes : number of bytes required to keep single value, depends on database engine, normally \~90 bytes.| |*Trends*|days\*(items/3600)\*24\*3600\*bytes<br>items : number of items<br>days : number of days to keep history<br>bytes : number of bytes required to keep single trend, depends on the database engine, normally \~90 bytes.| |*Events*|days\*events\*24\*3600\*bytes<br>events : number of event per second. One (1) event per second in worst-case scenario.<br>days : number of days to keep history<br>bytes : number of bytes required to keep single trend, depends on the database engine, normally \~330 + average number of tags per event \* 100 bytes.| So, the total required disk space can be calculated as:\ **Configuration + History + Trends + Events**\ The disk space will NOT be used immediately after Zabbix installation. Database size will grow then it will stop growing at some point, which depends on housekeeper settings. #### Taille de la base de données Les données de configuration de Zabbix nécessitent une quantité fixe d'espace disque et qui ne grandit pas beaucoup. La taille de la base de données Zabbix dépend principalement de ces variables, qui définissent la quantité de données historiques stockées : - Nombre de valeurs traitées par seconde Il s'agit du nombre moyen de nouvelles valeurs que le serveur Zabbix reçoit chaque seconde. Par exemple, si nous avons 3000 éléments à surveiller avec une cadence de rafraîchissementde à 60 secondes, le nombre de valeurs par seconde est calculé comme 3000/60 = **50**. Cela signifie que 50 nouvelles valeurs sont ajoutées à la base de données Zabbix chaque seconde. - Paramètres de Nettoyage de l'historique Zabbix conserve les valeurs pendant une période de temps fixe, normalement plusieurs semaines ou mois. Chaque nouvelle valeur nécessite une certaine quantité d'espace disque pour les données et l'index. Donc, si nous souhaitons conserver 30 jours d'historique et que nous recevons 50 valeurs par seconde, le nombre total de valeurs sera d'environ (**30**\*24\*3600)\* **50** = 129 600 000, soit environ 130 millions de valeurs. Selon le moteur de base de données utilisé, le type de valeurs reçues (flottants, entiers, chaînes, fichiers journaux, etc.), l'espace disque pour conserver une seule valeur peut varier de 40 octets à des centaines d'octets. Normalement c'est autour 90 octets par valeur pour les éléments numériques ^**2**^. Dans notre cas, cela signifie que 130 M de valeurs nécessiteront 130 M \* 90 octets = **10,9 Go** d'espace disque. ::: noteclassique La taille des valeurs des éléments de texte/journal est impossible à prévoir exactement, mais vous pouvez vous attendre à environ 500 octets par valeur. ::: - Paramètres de Nettoyage des tendances Zabbix conserve un ensemble de valeurs max/min/moy/count d'une heure pour chaque élément dans le tableau **tendances**. Les données sont utilisées pour les tendances et les graphiques de longues périodes. La période d'une heure ne peut pas être personnalisée. La base de données Zabbix, selon le type de base de données, nécessite environ 90 octets pour chaque total. Supposons que nous souhaitions conserver les données de tendance pendant 5 ans. Les valeurs pour 3 000 éléments nécessiteront 3 000\*24\*365\* **90** = **2,2 Go** par an, ou **11 Go** pendant 5 ans. - Paramètres de Nettoyage des évènements Chaque événement Zabbix nécessite environ 250 octets d'espace disque ^**1**^. Il est difficile d'estimer le nombre d'événements générés quotidiennement par Zabbix. Dans le pire des cas, nous pouvons supposer que Zabbix génère un événement par seconde. Pour chaque événement récupéré, un enregistrement event\_recovery est créé. Normalement la plupart des événements seront récupérés afin que nous puissions en supposer un enregistrement event\_recovery par événement. Cela signifie 80 octets supplémentaires par événement. Eventuellement, les événements peuvent avoir des tags, chaque enregistrement de tag nécessitant environ 100 octets d'espace disque ^**1**^. Le nombre de tags par événement (\#tags) dépend de la configuration. Donc, chaque évènement aura besoin de \#tags \* 100 octets supplémentaires d'espace disque. Cela signifie que si l'on veut conserver 3 ans d'événements, cela nécessiterait un espace disque de 3\*365\*24\*3600\* (250+80+\#tags\*100) = **\~30GB**+\#tags\*100B^**2**^. ::: noteclassique ^**1**^ Plus avec des noms d'événements, des balises et des valeurs. ^**2**^ Les approximations de taille sont basées sur MySQL et peuvent être différent pour les autres bases de données. ::: Le tableau contient des formules qui peuvent être utilisées pour calculer l'espace disque requis pour le système Zabbix : |Paramètre|Formule pour l'espace disque requis (en octets)| |---------|---------------------------------------------------- ---| |*Configuration Zabbix*|Taille fixe. Normalement 10 Mo ou moins.| |*Historique*|jours\*(éléments/taux de rafraîchissement)\*24\*3600\*octets<br>éléments : nombre d'éléments<br>jours : nombre de jours pour conserver l'historique<br>taux de rafraîchissement : rafraîchissement moyen taux d'éléments<br>octets : nombre d'octets requis pour conserver une valeur unique, dépend du moteur de base de données, normalement \~90 octets.| |*Tendances*|jours\*(éléments/3600)\*24\*3600\*octets<br>éléments: nombre d'éléments<br>jours : nombre de jours pour conserver l'historique<br>octets : nombre d'octets requis pour conserver une seule tendance, dépend du moteur de base de données, normalement \~90 octets.| |*Events*|days\*events\*24\*3600\*bytes<br>events : nombre d'événements par seconde. Un (1) événement par seconde dans le pire des cas.<br>jours : nombre de jours pour conserver l'historique<br>octets : nombre d'octets requis pour conserver une seule tendance, dépend du moteur de base de données, normalement \~330 + moyenne nombre de balises par événement \* 100 octets.| Ainsi, l'espace disque total requis peut être calculé comme suit :\ **Configuration + Historique + Tendances + Événements**\ L'espace disque ne sera PAS utilisé immédiatement après l'installation de Zabbix. La taille de la base de données augmentera puis cessera de croître à un moment donné, ce qui dépend des paramètres de Nettoyage. ### Databases To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance. Starting from Zabbix 6.0, the following [database](/manual/installation/requirements#software) versions are officially supported: - *MySQL/Percona* 8.0.X - *MariaDB* 10.5.X - 10.6.X - *PostgreSQL* 13.X - 14.X - *Oracle* 19c - 21c - *TimescaleDB* 2.0.1-2.3 - *SQLite* 3.3.5-3.34.X By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the [server](/manual/appendix/config/zabbix_server) or [proxy](/manual/appendix/config/zabbix_proxy). ### Bases de données Pour créer l'expérience utilisateur optimale et assurer la meilleure performance de Zabbix dans divers environnements de production, le support de certaines anciennes versions de bases de données a été supprimé. Cela s'applique principalement aux versions de base de données qui approchent de leur fin de vie et aux versions avec des problèmes non résolus qui peuvent interférer avec les performances normales. À partir de Zabbix 6.0, les [base de données](/manual/installation/requirements#software) suivantes sont officiellement prises en charge : - *MySQL/Percona* 8.0.X - *MariaDB* 10.5.X - 10.6.X - *PostgreSQL* 13.X - 14.X - *Oracle* 19c - 21c - *TimescaleDB* 2.0.1-2.3 - *SQLite* 3.3.5-3.34.X Par défaut, le serveur et le proxy Zabbix ne démarreront pas si une version no supportée de base de données est détectée. Il est maintenant possible, mais pas recommandé, de désactiver la vérification de la version de la base de données en modifiant le paramètre de configuration AllowUnsupportedDBVersions pour le [serveur](/manual/appendix/config/zabbix_server) ou le [proxy](/manual/appendix/config/zabbix_proxy). ##### Databases To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance. Starting from Zabbix 6.0, the following [database](/manual/installation/requirements#Software) versions are officially supported: - *MySQL/Percona* 8.0.X - *MariaDB* 10.5.X - 10.6.X - *PostgreSQL* 13.X - *Oracle* 19c - 21c - *TimescaleDB* 2.0.1-2.3 - *SQLite* 3.3.5-3.34.X By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the [server](/manual/appendix/config/zabbix_server) or [proxy](/manual/appendix/config/zabbix_proxy). ##### Databases Pour créer une expérience utilisateur optimale et garantir les meilleures performances de Zabbix dans divers environnements de production, la prise en charge de certaines anciennes versions de bases de données a été abandonnée. Cela s'applique principalement aux versions de base de données qui approchent de leur fin de vie et aux versions présentant des problèmes non résolus susceptibles d'interférer avec les performances normales. À partir de Zabbix 6.0, les versions de [base de données](/manual/installation/requirements#Software) suivantes sont officiellement prises en charge : - *MySQL/Percona* 8.0.X - *MariaDB* 10.5.X - 10.6.X - *PostgreSQL* 13.X - *Oracle* 19c - 21c - *TimescaleDB* 2.0.1-2.3 - *SQLite* 3.3.5-3.34.X Par défaut, le serveur et le proxy Zabbix ne démarreront pas si une version de base de données non prise en charge est détectée. Il est désormais possible, bien que non recommandé, de désactiver la vérification de la version de la base de données en modifiant le paramètre de configuration AllowUnsupportedDBVersions pour le [serveur](/manual/appendix/config/zabbix_server) ou le [proxy](/manual/appendix/config/zabbix_proxy). ##### Database storage All configuration information as well as the data gathered by Zabbix is stored in a database. ##### Stockage des données Toutes les informations de configuration ainsi que les données collectées par Zabbix sont stockées dans une base de données. #### Data flow In addition it is important to take a step back and have a look at the overall data flow within Zabbix. In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on *Server X* you must first create a host entry for *Server X* followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup. #### Flux de données En outre, il est important de prendre du recul et de jeter un coup d'œil au flux de données global au sein de Zabbix. Pour créer un élément qui rassemble des données, vous devez d'abord créer un hôte. En passant à l'autre extrémité du spectre Zabbix, vous devez d'abord avoir un élément pour créer un déclencheur. Vous devez avoir un déclencheur pour créer une action. Ainsi, si vous voulez recevoir une alerte quand votre charge CPU est trop élevée sur le *Serveur X*, vous devez d'abord créer une entrée hôte pour le *Serveur X* suivi d'un élément pour surveiller son CPU, puis un déclencheur qui s'activera si le CPU est trop chargé, suivi par une action qui vous envoie un email. Bien que cela puisse sembler beaucoup d’étapes, avec l'utilisation des modèles, ce n'est pas vraiment le cas. Cependant, grâce à cette conception, il est possible de créer une configuration très flexible. ### DB schema update A new column *name_upper* has been added to the database table **items**. The column contains a capitalized version of the item name or the LLD rule name. This change has been implemented to allow the use of the index with case-insensitive search for API query [optimization](#optimized-api-queries). ### Mise à jour du schéma de la BDD Une nouvelle colonne *name_upper* a été ajouté à la table **items** de la base de données. La colonne contient une version en majuscules du nom de l'élément ou du nom de la règle LLD. Ce changement a été implémentée pour permettre l'utilisation de l'index avec une recherche insensible à la casse pour la requête API [optimisées](#optimized-api-queries). # dcheck.get # dcheck.get ### Debian/Ubuntu Open the `/etc/apt/sources.list.d/zabbix.list` and uncomment "Zabbix unstable repository". # Zabbix unstable repository deb https://repo.zabbix.com/zabbix/5.5/debian bullseye main deb-src https://repo.zabbix.com/zabbix/5.5/debian bullseye main ### Debian/Ubuntu Ouvrez le fichier `/etc/apt/sources.list.d/zabbix.list` et décommentez "Zabbix unstable repository". # Zabbix unstable repository deb https://repo.zabbix.com/zabbix/5.5/debian bullseye main deb-src https://repo.zabbix.com/zabbix/5.5/debian bullseye main ### Debug Debug information of executed webhook script. The debug object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |logs|array|Array of [log entries](/manual/api/reference/script/object#Log entry).| |ms|string|Script execution duration in milliseconds.| ### Debug Informations de debug du script Webhook exécuté. L'objet de debug a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |logs|array|Tableau de [entrées de journal](/manual/api/reference/script/object#Log entry).| |ms|string|Durée d'exécution du script en millisecondes.| #### Debugging Java gateway In case there are any problems with Java gateway or an error message that you see about an item in the frontend is not descriptive enough, you might wish to take a look at Java gateway log file. By default, Java gateway logs its activities into /tmp/zabbix\_java.log file with log level "info". Sometimes that information is not enough and there is a need for information at log level "debug". In order to increase logging level, modify file lib/logback.xml and change the level attribute of <root> tag to "debug": <root level="debug"> <appender-ref ref="FILE" /> </root> Note that unlike Zabbix server or Zabbix proxy, there is no need to restart Zabbix Java gateway after changing logback.xml file - changes in logback.xml will be picked up automatically. When you are done with debugging, you can return the logging level to "info". If you wish to log to a different file or a completely different medium like database, adjust logback.xml file to meet your needs. See [Logback Manual](http://logback.qos.ch/manual/) for more details. Sometimes for debugging purposes it is useful to start Java gateway as a console application rather than a daemon. To do that, comment out PID\_FILE variable in settings.sh. If PID\_FILE is omitted, startup.sh script starts Java gateway as a console application and makes Logback use lib/logback-console.xml file instead, which not only logs to console, but has logging level "debug" enabled as well. Finally, note that since Java gateway uses SLF4J for logging, you can replace Logback with the framework of your choice by placing an appropriate JAR file in lib directory. See [SLF4J Manual](http://www.slf4j.org/manual.html) for more details. #### Débogage de la passerelle Java Au cas où il y aurait un problème avec la passerelle Java ou si un message d'erreur que vous voyez à propos d'un élément dans l'interface n'est pas assez descriptif, vous voudrez peut-être jeter un coup d'œil au fichier journal de la passerelle Java. Par défaut, la passerelle Java consigne ses activités dans le fichier /tmp/zabbix\_java.log avec le niveau de journalisation "info". Parfois, ces informations ne suffisent pas et il est nécessaire de disposer d'informations de niveau "debug". Pour augmenter le niveau de journalisation, modifiez le fichier lib/logback.xml et modifiez l'attribut de niveau du tag <root> en "debug" : <root level="debug"> <appender-ref ref="FILE" /> </root> Notez que contrairement au serveur Zabbix ou au proxy Zabbix, il n’est pas nécessaire de redémarrer la passerelle Java Zabbix après la modification du fichier logback.xml. Les modifications apportées dans logback.xml sont automatiquement prises en compte. Lorsque vous avez terminé le débogage, vous pouvez rétablir le niveau de journalisation sur "info". Si vous souhaitez vous connecter à un autre fichier ou à un support complètement différent, tel que base de données, ajustez le fichier logback.xml en fonction de vos besoins. Voir le [manuel de Logback](http://logback.qos.ch/manual/) pour plus de détails. Parfois, à des fins de débogage, il est utile de démarrer la passerelle Java en tant qu’application console plutôt qu’un démon. Pour cela, commentez la variable PID\_FILE dans settings.sh. Si PID\_FILE est omis, le script startup.sh démarre la passerelle Java en tant qu'application console et oblige Logback à utiliser à la place le fichier lib/logback-console.xml, qui non seulement renvoie ses logs à la console, mais dispose également du niveau de journalisation "debug". Enfin, notez que, puisque la passerelle Java utilise SLF4J pour la journalisation, vous pouvez remplacer Logback par la structure de votre choix en plaçant un fichier JAR approprié dans le répertoire lib. Voir le [manuel de SLF4J](http://www.slf4j.org/manual.html) pour plus de détails. #### Debugging Java gateway Zabbix Java gateway log file is: /var/log/zabbix/zabbix_java_gateway.log If you like to increase the logging, edit the file: /etc/zabbix/zabbix_java_gateway_logback.xml and change `level="info"` to "debug" or even "trace" (for deep troubleshooting): <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> #### Déboggage de la passerelle Java Le fichier journal de la passerelle Java Zabbix est : /var/log/zabbix/zabbix_java_gateway.log Si vous souhaitez augmenter le niveau de journalisation, éditez le fichier : /etc/zabbix/zabbix_java_gateway_logback.xml et modifiez `level="info"` en "debug" ou encore "trace" (pour un dépannage en profondeur) : <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> #### Debugging Java gateway Zabbix Java gateway log file is: /var/log/zabbix/zabbix_java_gateway.log If you like to increase the logging, edit the file: /etc/zabbix/zabbix_java_gateway_logback.xml and change `level="info"` to "debug" or even "trace" (for deep troubleshooting): <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> #### Déboggage de la passerelle Java Le fichier journal de la passerelle Java Zabbix est : /var/log/zabbix/zabbix_java_gateway.log Si vous souhaitez augmenter le niveau de journalisation, éditez le fichier : /etc/zabbix/zabbix_java_gateway_logback.xml et modifiez `level="info"` en "debug" ou encore "trace" (pour un dépannage en profondeur) : <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> #### Debugging Java gateway Zabbix Java gateway log file is: /var/log/zabbix/zabbix_java_gateway.log If you like to increase the logging, edit the file: /etc/zabbix/zabbix_java_gateway_logback.xml and change `level="info"` to "debug" or even "trace" (for deep troubleshooting): <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> #### Déboggage de la passerelle Java Le fichier journal de la passerelle Java Zabbix est : /var/log/zabbix/zabbix_java_gateway.log Si vous souhaitez augmenter le niveau de journalisation, éditez le fichier : /etc/zabbix/zabbix_java_gateway_logback.xml et modifiez `level="info"` en "debug" ou encore "trace" (pour un dépannage en profondeur) : <configuration scan="true" scanPeriod="15 seconds"> [...] <root level="info"> <appender-ref ref="FILE" /> </root> </configuration> ### Default authentication By default, Zabbix uses internal Zabbix authentication for all users. It is possible to change the default method to [LDAP](#ldap_authentication) system-wide or enable LDAP authentication only for specific user groups. To set LDAP as default authentication method for all users, navigate to the *LDAP* tab and configure authentication parameters, then return to the *Authentication* tab and switch *Default authentication* selector to LDAP. Note that the authentication method can be fine-tuned on the [user group](/manual/config/users_and_usergroups/usergroup) level. Even if LDAP authentication is set globally, some user groups can still be authenticated by Zabbix. These groups must have [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) set to Internal. Vice versa, if internal authentication is used globally, LDAP authentication details can be specified and used for specific user groups whose [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) is set to LDAP. If a user is included into at least one user group with LDAP authentication, this user will not be able to use internal authentication method. [HTTP](#http_authentication) and [SAML 2.0](#saml_authentication) authentication methods can be used in addition to the default authentication method. ### Authentification par défaut Par défaut, Zabbix utilise l'authentification interne Zabbix pour tous les utilisateurs. Il est possible de changer la méthode par défaut en [LDAP](#ldap_authentication) à l'échelle du système ou d'activer l'authentification LDAP uniquement pour des groupes d'utilisateurs spécifiques. Pour définir LDAP comme méthode d'authentification par défaut pour tous les utilisateurs, accédez à l'onglet *LDAP* et configurez les paramètres d'authentification, puis revenez à l'onglet *Authentification* et basculez le sélecteur *Authentification par défaut* sur LDAP. Notez que la méthode d'authentification peut être affinée au niveau [groupe d'utilisateurs](/manual/config/users_and_usergroups/usergroup). Même si l'authentification LDAP est définie globalement, certains groupes d'utilisateurs peuvent toujours être authentifiés par Zabbix. Ces groupes doivent avoir un [accès frontal](/manual/config/users_and_usergroups/usergroup#configuration) défini sur Interne. Inversement, si l'authentification interne est utilisée globalement, les détails d'authentification LDAP peuvent être spécifiés et utilisés pour des groupes d'utilisateurs spécifiques dont l'[accès frontal](/manual/config/users_and_usergroups/usergroup#configuration) est défini sur LDAP. Si un utilisateur est inclus dans au moins un groupe d'utilisateurs avec authentification LDAP, cet utilisateur ne pourra pas utiliser la méthode d'authentification interne. Les méthodes d'authentification [HTTP](#http_authentication) et [SAML 2.0](#saml_authentication) peuvent être utilisées en plus de la méthode d'authentification par défaut. #### Default port numbers The following list of open ports per component is applicable for default configuration: |Zabbix component|Port number|Protocol|Type of connection| |-------|-------|-------|-------| |Zabbix agent|10050|TCP|on demand| |Zabbix agent 2|10050|TCP|on demand| |Zabbix server|10051|TCP|on demand| |Zabbix proxy|10051|TCP|on demand| |Zabbix Java gateway|10052|TCP|on demand| |Zabbix web service|10053|TCP|on demand| |Zabbix frontend|80|HTTP|on demand| |^|443|HTTPS|on demand| |Zabbix trapper|10051 |TCP| on demand| ::: noteclassic The port numbers should be open in firewall to enable Zabbix communications. Outgoing TCP connections usually do not require explicit firewall settings. ::: #### Numéros de port par défaut La liste suivante de ports ouverts par composant s'applique à la configuration par défaut : |Composant Zabbix|Numéro de port|Protocole|Type de connexion| |-------|-------|-------|-------| |Agent Zabbix|10050|TCP|à la demande| |Agent Zabbix 2|10050|TCP|à la demande| |Serveur Zabbix|10051|TCP|à la demande| |Proxy Zabbix|10051|TCP|à la demande| |Passerelle Java Zabbix|10052|TCP|à la demande| |Service web Zabbix|10053|TCP|sur demande| |Interface Zabbix|80|HTTP|à la demande| |^|443|HTTPS|à la demande| |Trapper Zabbix|10051 |TCP|à la demande | ::: noteclassic Les numéros de port doivent être ouverts dans le pare-feu pour permettre les communications Zabbix. Les connexions TCP sortantes ne nécessitent généralement pas de paramètres de pare-feu explicites. ::: #### Default port numbers The following table lists default port numbers that Zabbix components listen on: |Zabbix component|Port number|Protocol|Type of connection| |-------|-------|-------|-------| |Zabbix agent|10050|TCP|on demand| |Zabbix agent 2|10050|TCP|on demand| |Zabbix server|10051|TCP|on demand| |Zabbix proxy|10051|TCP|on demand| |Zabbix Java gateway|10052|TCP|on demand| |Zabbix web service|10053|TCP|on demand| #### Numéros de port par défaut Le tableau suivant répertorie les numéros de port par défaut sur lesquels les composants Zabbix écoutent : |Composant Zabbix|Numéro de port|Protocole|Type de connexion| |-------|-------|-------|-------| |Agent Zabbix|10050|TCP|sur demande| |Agent Zabbix 2|10050|TCP|sur demande| |Serveur Zabbix|10051|TCP|à la demande| |Proxy Zabbix|10051|TCP|à la demande| |Passerelle Java Zabbix|10052|TCP|à la demande| |Service web Zabbix|10053|TCP|sur demande| #### Default user roles By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions: - Admin role - Guest role - Super admin role - User role {width="600"} ::: noteclassic Default *Super admin role* cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix. ::: Zabbix users with type Super admins and proper permissions can modify or delete existing roles or create new custom roles. To create a new role, click on the *Create user role* button at the top right corner. To update an existing role, press on the role name to open the configuration form.  Available permission options along with default permission sets for pre-configured user roles in Zabbix are described below. | | | | | | | | |-|----------|--------------------------------------|----|----|----|----| |**Parameter**|<|**Description**|**Default user roles**|<|<|<| | |<|<|*Super admin role*|*Admin role*|*User role*|*Guest role*| |User type|<|Selected user type determines the list of available permissions.<br>Upon selecting a user type, all available permissions for this user type are granted by default.<br>Uncheck the checkbox(es) to revoke certain permissions for the user role.<br>Checkboxes for permissions not available for this user type are grayed out.|Super admin|Admin|User|User| |**Access to UI elements**|<|<|<|<|<|<| |*Monitoring*|<|<|<|<|<|<| | |Dashboard|Enable/disable access to a specific Monitoring menu section and underlying pages.|Yes|Yes|Yes|Yes| |^|Problems|^|^|^|^|^| |^|Hosts|^|^|^|^|^| |^|Latest data|^|^|^|^|^| |^|Maps|^|^|^|^|^| |^|Discovery|^|^|^|No|No| |*Services*|<|<|<|<|<|<| | |Services|Enable/disable access to a specific Services menu section and underlying pages.|Yes|Yes|Yes|Yes| |^|Service actions|^|^|^|No|No| |^|SLA|^|^|^|^|^| |^|SLA report|^|^|^|Yes|Yes| |*Inventory*|<|<|<|<|<|<| | Overview|Enable/disable access to a specific Inventory menu section and underlying pages.|Yes|Yes|Yes|Yes| |^|Hosts|^|^|^|^|^| |*Reports*|<|<|<|<|<|<| | |System information|Enable/disable access to a specific Reports menu section and underlying pages.|Yes|No|No|No| |^|Availability report|^|^|Yes|Yes|Yes| |^|Triggers top 100|^|^|^|^|^| |^|Audit|^|^|No|No|No| |^|Action log|^|^|^|^|^| |^|Notifications|^|^|Yes|^|^| |^|Scheduled reports|^|^|^|^|^| |*Configuration*|<|<|<|<|<|<| | |Host groups|Enable/disable access to a specific *Configuration* menu section and underlying pages.|Yes|Yes|No|No| |^|Templates|^|^|^|^|^| |^|Hosts|^|^|^|^|^| |^|Maintenance|^|^|^|^|^| |^|Actions|^|^|^|^|^| |^|Event correlation|^|^|No|^|^| |^|Discovery|^|^|Yes|^|^| |*Administration*|<|<|<|<|<|<| | |General|Enable/disable access to a specific *Administration* menu section and underlying pages.|Yes|No|No|No| |^|Proxies|^|^|^|^|^| |^|Authentication|^|^|^|^|^| |^|User groups|^|^|^|^|^| |^|User roles|^|^|^|^|^| |^|Users|^|^|^|^|^| |^|Media types|^|^|^|^|^| |^|Scripts|^|^|^|^|^| |^|Queue|^|^|^|^|^| |*Default access to new UI elements*|<|Enable/disable access to the custom UI elements. Modules, if present, will be listed below.|Yes|Yes|Yes|Yes| |**Access to services**|<|<|<|<|<|<| | |Read-write access to services|Select read-write access to services:<br>**None** - no access at all<br>**All** - access to all services is read-write<br>**Service list** - select services for read-write access<br><br>The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.|All|All|None|None| |^|Read-write access to services with tag|Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-write access to services* parameter.<br>The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.|^|^|^|^| |^|Read-only access to services|Select read-only access to services:<br>**None** - no access at all<br>**All** - access to all services is read-only<br>**Service list** - select services for read-only access<br><br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|All|All| |^|Read-only access to services with tag|Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-only access to services* parameter.<br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |**Access to modules**|<|<|<|<|<|<| | |<Module name>|Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.|Yes|Yes|Yes|Yes| |^|*Default access to new modules*|Enable/disable access to modules that may be added in the future.|^|^|^|^| |**Access to API**|<|<|<|<|<|<| | |*Enabled*|Enable/disable access to API.|Yes|Yes|Yes|No| |^|*API methods*|Select *Allow list* to allow only specified API methods or *Deny list* to restrict only specified API methods.<br><br>In the search field, start typing the method name, then select the method from the auto-complete list.<br>You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action.<br><br>Wildcards are supported. Examples: `dashboard.*` (all methods of 'dashboard.' API service) `*` (any method), `*.export` (methods with '.export' name from all API services).<br><br>If no methods have been specified the Allow/Deny list rule will be ignored.|^|^|^|^| |**Access to actions**|<|<|<|<|<|<| | |Create and edit dashboards|Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.|Yes|Yes|Yes|No| |^|Create and edit maps|^|^|^|^|^| |^|Create and edit maintenance|^|^|^|No|^| |^|Add problem comments|Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.|^|^|Yes|^| |^|Change severity|^|^|^|^|^| |^|Acknowledge problems|^|^|^|^|^| |^|Close problems|^|^|^|^|^| |^|Execute scripts|Clearing this checkbox will also revoke the rights to use the `script.execute` API method.|^|^|^|^| |^|Manage API tokens|Clearing this checkbox will also revoke the rights to use all `token.` API methods.|^|^|^|^| |^|Manage scheduled reports|Clearing this checkbox will also revoke the rights to use all `report.` API methods.|^|^|No|^| |^|Manage SLA|Enable/disable the rights to manage [SLA](/manual/web_interface/frontend_sections/services/sla).|^|^|^|^| |^|Default access to new actions|Enable/disable access to new actions.|^|^|Yes|^| Notes: - Each user may have only one role assigned. - If an element is restricted, users will not be able to access it even by entering a direct URL to this element into the browser. - Users of type *User* or *Admin* cannot change their own role settings. - Users of type *Super admin* can modify settings of their own role (not available for the default *Super admin role*), but not the user type. - Users of all levels cannot change their own user type. See also: - [Configuring a user](/manual/config/users_and_usergroups/user) #### Rôles utilisateur par défaut Par défaut, Zabbix est configuré avec quatre rôles utilisateur, qui ont un ensemble prédéfini d'autorisations : - rôle Admin - rôle Guest - rôle Super admin - rôle User {width="600"} ::: noteclassic Le *rôle Super admin* par défaut ne peut pas être modifié ou supprimé, car au moins un utilisateur de super administrateur avec des privilèges illimités doit exister dans Zabbix. ::: Les utilisateurs de Zabbix avec le type Super administrateurs et les autorisations appropriées peuvent modifier ou supprimer des rôles existants ou créer de nouveaux rôles personnalisés. Pour créer un nouveau rôle, cliquez sur le bouton *Créer un rôle d'utilisateur* dans le coin supérieur droit. Pour mettre à jour un rôle existant, appuyez sur le nom du rôle pour ouvrir le formulaire de configuration.  Les options d'autorisation disponibles ainsi que les ensembles d'autorisations par défaut pour les rôles d'utilisateur préconfigurés dans Zabbix sont décrits ci-dessous. | | | | | | | | |-|----------|--------------------------------------|----|----|----|----| |**Paramètre**|<|**Description**|**Rôles utilisateur par défaut**|<|<|<| | |<|<|*rôle Super admin*|*rôle Admin*|*rôle User*|*rôle Guest*| |Type d'utilisateur|<|Le type d'utilisateur sélectionné détermine la liste des autorisations disponibles.<br>Lors de la sélection d'un type d'utilisateur, toutes les autorisations disponibles pour ce type d'utilisateur sont accordées par défaut.<br>Décochez la ou les cases pour révoquer certaines autorisations pour le rôle d'utilisateur.<br>Les cases à cocher des autorisations non disponibles pour ce type d'utilisateur sont grisées.|Super admin|Admin|User|User| |**Accès aux éléments de l'interface utilisateur**|<|<|<|<|<|<| |*Surveillance*|<|<|<|<|<|<| | |Tableau de bord|Activer/désactiver l'accès à une section spécifique du menu Monitoring et aux pages sous-jacentes.|Oui|Oui|Oui|Oui| |^|Problèmes|^|^|^|^|^| |^|Hôtes|^|^|^|^|^| |^|Dernières données|^|^|^|^|^| |^|Cartes|^|^|^|^|^| |^|Découverte|^|^|^|Non|Non| |*Services*|<|<|<|<|<|<| | |Services|Activer/désactiver l'accès à une section de menu Services spécifique et aux pages sous-jacentes.|Oui|Oui|Oui|Oui| |^|Actions de Service|^|^|^|Non|Non| |^|SLA|^|^|^|^|^| |^|Rapport SLA|^|^|^|Oui|Oui| |*Inventaire*|<|<|<|<|<|<| | Aperçu|Activer/désactiver l'accès à une section spécifique du menu Inventaire et aux pages sous-jacentes.|Oui|Oui|Oui|Oui| |^|Hôtes|^|^|^|^|^| |*Rapports*|<|<|<|<|<|<| | |Informations système|Activer/désactiver l'accès à une section spécifique du menu Rapports et aux pages sous-jacentes.|Oui|Non|Non|Non| |^|Rapport de disponibilité|^|^|Oui|Oui|Oui| |^|Top 100 des Déclencheurs |^|^|^|^|^| |^|Audit|^|^|Non|Non|Non| |^|Journal des actions|^|^|^|^|^| |^|Notifications|^|^|Oui|^|^| |^|Rapports planifiés|^|^|^|^|^| |*Configuration*|<|<|<|<|<|<| | |Groupes d'hôtes|Activer/désactiver l'accès à une section de menu *Configuration* spécifique et aux pages sous-jacentes.|Oui|Oui|Non|Non| |^|Modèles|^|^|^|^|^| |^|Hôtes|^|^|^|^|^| |^|Nettoyage|^|^|^|^|^| |^|Actions|^|^|^|^|^| |^|Corrélation d'événements|^|^|Non|^|^| |^|Découverte|^|^|Oui|^|^| |*Administration*|<|<|<|<|<|<| | |Général|Activer/désactiver l'accès à une section de menu *Administration* spécifique et aux pages sous-jacentes.|Oui|Non|Non|Non| |^|Proxies|^|^|^|^|^| |^|Authentification|^|^|^|^|^| |^|Groupes utilisateurs|^|^|^|^|^| |^|Rôles utilisateur|^|^|^|^|^| |^|Utilisateurs|^|^|^|^|^| |^|Types de médias|^|^|^|^|^| |^|Scripts|^|^|^|^|^| |^|File d'attente|^|^|^|^|^| |*Accès par défaut aux nouveaux éléments de l'interface utilisateur*|<|Activer/désactiver l'accès aux éléments de l'interface utilisateur personnalisés. Les modules, s'ils sont présents, seront listés ci-dessous.|Oui|Oui|Oui|Oui| |**Accès aux services**|<|<|<|<|<|<| | |Accès en lecture-écriture aux services|Sélectionnez l'accès en lecture-écriture aux services :<br>**Aucun** - aucun accès du tout<br>**Tous** - l'accès à tous les services est en lecture-écriture<br>**Liste des services** - sélectionnez les services pour un accès en lecture-écriture<br><br>L'accès en lecture-écriture, s'il est accordé, a priorité sur les paramètres d'accès en lecture seule et est hérité dynamiquement par les services enfants.|Tous|Tous |Aucun|Aucun| |^|Accès en lecture-écriture aux services avec balise|Spécifiez le nom de la tag et, éventuellement, la valeur pour accorder en plus un accès en lecture-écriture aux services correspondant au tag.<br>Cette option est disponible si 'Liste des services' est sélectionné dans le *Paramètre d'accès en lecture-écriture aux services*.<br>L'accès en lecture-écriture, s'il est accordé, a priorité sur les paramètres d'accès en lecture seule et est hérité dynamiquement par les services enfants.|^|^|^|^| |^|Accès en lecture seule aux services|Sélectionnez l'accès en lecture seule aux services :<br>**Aucun** - aucun accès du tout<br>**Tous** - l'accès à tous les services est en lecture seule<br >**Liste des services** - sélectionnez les services pour un accès en lecture seule<br><br>L'accès en lecture seule n'a pas priorité sur l'accès en lecture-écriture et est hérité dynamiquement par les services enfants.|^|^| Tout|Tous| |^|Accès en lecture seule aux services avec tag|Spécifiez le nom du tag et, éventuellement, la valeur pour accorder en plus un accès en lecture seule aux services correspondant au tag.<br>Cette option est disponible si 'Liste de services' est sélectionné dans le paramètre *Accès en lecture seule aux services*.<br>L'accès en lecture seule n'a pas priorité sur l'accès en lecture-écriture et est hérité dynamiquement par les services enfants.|^|^|^|^| |**Accès aux modules**|<|<|<|<|<|<| | |\<Nom du module\>|Autoriser/refuser l'accès à un module spécifique. Seuls les modules activés sont affichés dans cette section. Il n'est pas possible d'accorder ou de restreindre l'accès à un module actuellement désactivé.|Oui|Oui|Oui|Oui| |^|*Accès par défaut aux nouveaux modules*|Activer/désactiver l'accès aux modules qui pourraient être ajoutés à l'avenir.|^|^|^|^| |**Accès à l'API**|<|<|<|<|<|<| | |*Activé*|Activer/désactiver l'accès à l'API.|Oui|Oui|Oui|Non| |^|*Méthodes API*|Sélectionnez *Liste autorisée* pour n'autoriser que les méthodes API spécifiées ou *Liste refusée* pour restreindre uniquement les méthodes API spécifiées.<br><br>Dans le champ de recherche, commencez à saisir le nom de la méthode, puis sélectionnez la méthode dans la liste de saisie semi-automatique.<br>Vous pouvez également appuyer sur le bouton Sélectionner et sélectionner des méthodes dans la liste complète disponible pour ce type d'utilisateur. Notez que si certaines actions du bloc Accès aux actions sont décochées, les utilisateurs ne pourront pas utiliser les méthodes API liées à cette action.<br><br>Les caractères génériques sont pris en charge. Exemples : `dashboard.*` (toutes les méthodes du service d'API 'dashboard.') `*` (toute méthode), `*.export` (méthodes avec le nom '.export' de tous les services d'API).<br><br >Si aucune méthode n'a été spécifiée, la règle de liste Autoriser/Refuser sera ignorée.|^|^|^|^| |**Accès aux actions**|<|<|<|<|<|<| | |Créer et modifier des tableaux de bord|Désélectionner cette case révoquera également les droits d'utilisation des méthodes API `.create`, `.update` et `.delete` pour les éléments correspondants.|Oui|Oui|Oui|Non| |^|Créer et modifier des cartes|^|^|^|^|^| |^|Créer et modifier la maintenance|^|^|^|Non|^| |^|Ajouter des commentaires sur le problème|Désélectionner cette case révoquera également les droits d'effectuer l'action correspondante via la méthode API `event.acknowledge`.|^|^|Oui|^| |^|Modifier la gravité|^|^|^|^|^| |^|Acquitter les problèmes|^|^|^|^|^| |^|Fermer les problèmes|^|^|^|^|^| |^|Exécuter des scripts|Désélectionner cette case révoquera également les droits d'utilisation de la méthode API `script.execute`.|^|^|^|^| |^|Gérer les jetons d'API|Désélectionner cette case révoquera également les droits d'utilisation de toutes les méthodes d'API `token.`.|^|^|^|^| |^|Gérer les rapports planifiés|Désélectionner cette case révoquera également les droits d'utilisation de toutes les méthodes de l'API `report.`.|^|^|Non|^| |^|Gérer le SLA|Activer/désactiver les droits de gestion du [SLA](/manual/web_interface/frontend_sections/services/sla).|^|^|^|^| |^|Accès par défaut aux nouvelles actions|Activer/désactiver l'accès aux nouvelles actions.|^|^|Oui|^| Remarques : - Chaque utilisateur ne peut avoir qu'un seul rôle attribué. - Si un élément est restreint, les utilisateurs ne pourront pas y accéder même en entrant une URL directe vers cet élément dans le navigateur. - Les utilisateurs de type *User* ou *Admin* ne peuvent pas modifier leurs propres paramètres de rôle. - Les utilisateurs de type *Super admin* peuvent modifier les paramètres de leur propre rôle (non disponible pour le *rôle Super Admin* par défaut), mais pas le type d'utilisateur. - Les utilisateurs de tous les niveaux ne peuvent pas modifier leur propre type d'utilisateur. Voir également : - [Configuration d'un utilisateur](/manual/config/users_and_usergroups/user) #### Delete a host interface Delete the host interface with ID 30062. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.delete", "params": [ "30062" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30062" ] }, "id": 1 } ``` #### Suppression d'une interface hôte Supprimer l'interface hôte avec l'ID 30062. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.delete", "params": [ "30062" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30062" ] }, "id": 1 } ``` #### Delete multiple actions Delete two actions. Request: ``` {.java} { "jsonrpc": "2.0", "method": "action.delete", "params": [ "17", "18" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "17", "18" ] }, "id": 1 } ``` #### Suppression de plusieurs actions Supprimer deux actions. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "action.delete", "params": [ "17", "18" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "17", "18" ] }, "id": 1 } ``` #### Delete multiple correlations Delete two correlations. Request: ```json { "jsonrpc": "2.0", "method": "correlation.delete", "params": [ "1", "2" ], "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "correlationids": [ "1", "2" ] }, "id": 1 } ``` #### Supprimer plusieurs corrélations Supprimer deux corrélations. Requête : ```json { "jsonrpc": "2.0", "method": "correlation.delete", "params": [ "1", "2" ], "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "correlaionids": [ "1", "2" ] }, "id": 1 } ``` #### Delete multiple discovery rules Delete two discovery rules. Request: ``` {.java} { "jsonrpc": "2.0", "method": "drule.delete", "params": [ "4", "6" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "druleids": [ "4", "6" ] }, "id": 1 } ``` #### Suppression de plusieurs règles de découverte Supprimer deux règles de découverte. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "drule.delete", "params": [ "4", "6" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "druleids": [ "4", "6" ] }, "id": 1 } ``` #### Delete multiple icon maps Delete two icon maps. Request: ``` {.java} { "jsonrpc": "2.0", "method": "iconmap.delete", "params": [ "2", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "iconmapids": [ "2", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs correspondances d'icônes Supprimer deux correspondances d'icônes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "iconmap.delete", "params": [ "2", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "iconmapids": [ "2", "5" ] }, "id": 1 } ``` #### Delete multiple images Delete two images. Request: ``` {.java} { "jsonrpc": "2.0", "method": "image.delete", "params": [ "188", "192" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "imageids": [ "188", "192" ] }, "id": 1 } ``` #### Suppression de plusieurs images Supprimer deux images. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "image.delete", "params": [ "188", "192" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "imageids": [ "188", "192" ] }, "id": 1 } ``` #### Delete multiple maps Delete two maps. Request: ``` {.java} { "jsonrpc": "2.0", "method": "map.delete", "params": [ "12", "34" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "sysmapids": [ "12", "34" ] }, "id": 1 } ``` #### Suppression de plusieurs cartes Supprimer deux cartes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "map.delete", "params": [ "12", "34" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "sysmapids": [ "12", "34" ] }, "id": 1 } ``` #### Delete multiple proxies Delete two proxies. Request: ``` {.java} { "jsonrpc": "2.0", "method": "proxy.delete", "params": [ "10286", "10285" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "proxyids": [ "10286", "10285" ] }, "id": 1 } ``` #### Suppression de plusieurs proxys Supprimer deux proxys. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "proxy.delete", "params": [ "10286", "10285" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "proxyids": [ "10286", "10285" ] }, "id": 1 } ``` #### Delete multiple scripts Delete two scripts. Request: ``` {.java} { "jsonrpc": "2.0", "method": "script.delete", "params": [ "3", "4" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "scriptids": [ "3", "4" ] }, "id": 1 } ``` #### Suppression de plusieurs scripts Supprimer deux scripts. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "script.delete", "params": [ "3", "4" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "scriptids": [ "3", "4" ] }, "id": 1 } ``` #### Delete multiple triggers Delete two triggers. Request: ``` {.java} { "jsonrpc": "2.0", "method": "trigger.delete", "params": [ "12002", "12003" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "12002", "12003" ] }, "id": 1 } ``` #### Suppression de plusieurs déclencheurs Supprimer deux déclencheurs. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "trigger.delete", "params": [ "12002", "12003" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "12002", "12003" ] }, "id": 1 } ``` #### Deleting dependencies from multiple triggers Delete all dependencies from two triggers. Request: ``` {.java} { "jsonrpc": "2.0", "method": "trigger.deleteDependencies", "params": [ { "triggerid": "14544" }, { "triggerid": "14545" } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "14544", "14545" ] }, "id": 1 } ``` #### Suppression de dépendances de plusieurs déclencheurs Supprimer toutes les dépendances de deux déclencheurs. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "trigger.deleteDependencies", "params": [ { "triggerid": "14544" }, { "triggerid": "14545" } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "14544", "14545" ] }, "id": 1 } ``` #### Deleting multiple dashboards Delete two dashboards. Request: ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.delete", "params": [ "2", "3" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2", "3" ] }, "id": 1 } ``` #### Supprimer plusieurs tableaux de bord Supprimer deux tableaux de bord. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.delete", "params": [ "2", "3" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2", "3" ] }, "id": 1 } ``` #### Deleting multiple global macros Delete two global macros. Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.deleteglobal", "params": [ "32", "11" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "32", "11" ] }, "id": 1 } ``` #### Suppression de plusieurs macros globales Supprimer deux macros globales. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.deleteglobal", "params": [ "32", "11" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "globalmacroids": [ "32", "11" ] }, "id": 1 } ``` #### Deleting multiple global regular expressions. Request: ``` {.java} { "jsonrpc": "2.0", "method": "regexp.delete", "params": [ "16", "17" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "regexpids": [ "16", "17" ] }, "id": 1 } ``` #### Suppression de plusieurs expressions régulières globales. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "regexp.delete", "params": [ "16", "17" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "regexpids": [ "16", "17" ] }, "id": 1 } ``` #### Deleting multiple graph prototypes Delete two graph prototypes. Request: ``` {.java} { "jsonrpc": "2.0", "method": "graphprototype.delete", "params": [ "652", "653" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652", "653" ] }, "id": 1 } ``` #### Suppression de plusieurs prototypes de graphique Supprimer deux prototypes de graphique. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "graphprototype.delete", "params": [ "652", "653" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652", "653" ] }, "id": 1 } ``` #### Deleting multiple graphs Delete two graphs. Request: ``` {.java} { "jsonrpc": "2.0", "method": "graph.delete", "params": [ "652", "653" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652", "653" ] }, "id": 1 } ``` #### Suppression de plusieurs graphiques Supprimer deux graphiques. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "graph.delete", "params": [ "652", "653" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "graphids": [ "652", "653" ] }, "id": 1 } ``` #### Deleting multiple host groups Delete two host groups. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.delete", "params": [ "107824", "107825" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "107824", "107825" ] }, "id": 1 } ``` #### Suppression de plusieurs groupes d'hôtes Supprimer deux groupes d'hôtes. Requête: ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.delete", "params": [ "107824", "107825" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "107824", "107825" ] }, "id": 1 } ``` #### Deleting multiple host macros Delete two host macros. Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.delete", "params": [ "32", "11" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "32", "11" ] }, "id": 1 } ``` #### Suppression de plusieurs macros d'hôtes Supprimer deux macros d'hôtes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.delete", "params": [ "32", "11" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "hostmacroids": [ "32", "11" ] }, "id": 1 } ``` #### Deleting multiple host prototypes Delete two host prototypes. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostprototype.delete", "params": [ "10103", "10105" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "hostids": [ "10103", "10105" ] }, "id": 1 } ``` #### Suppression de plusieurs prototypes d'hôte Supprimer deux prototypes d'hôte. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostprototype.delete", "params": [ "10103", "10105" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "hostids": [ "10103", "10105" ] }, "id": 1 } ``` #### Deleting multiple hosts Delete two hosts. Request: ``` {.java} { "jsonrpc": "2.0", "method": "host.delete", "params": [ "13", "32" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "hostids": [ "13", "32" ] }, "id": 1 } ``` #### Suppression de plusieurs hôtes Supprimer deux hôtes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "host.delete", "params": [ "13", "32" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "hostids": [ "13", "32" ] }, "id": 1 } ``` #### Deleting multiple LLD rules Delete two LLD rules. Request: ```json { "jsonrpc": "2.0", "method": "discoveryrule.delete", "params": [ "27665", "27668" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "ruleids": [ "27665", "27668" ] }, "id": 1 } ``` #### Suppression de plusieurs règles de découverte bas niveau Supprimer deux règles de découverte bas niveau. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.delete", "params": [ "27665", "27668" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "ruleids": [ "27665", "27668" ] }, "id": 1 } ``` #### Deleting multiple maintenance periods Delete two maintenance periods. Request: ```json { "jsonrpc": "2.0", "method": "maintenance.delete", "params": [ "3", "1" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3", "1" ] }, "id": 1 } ``` #### Suppression de plusieurs maintenances Supprimer deux maintenances. Requête : ```json { "jsonrpc": "2.0", "method": "maintenance.delete", "params": [ "3", "1" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "maintenanceids": [ "3", "1" ] }, "id": 1 } ``` #### Deleting multiple media types Delete two media types. Request: ``` {.java} { "jsonrpc": "2.0", "method": "mediatype.delete", "params": [ "3", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "mediatypeids": [ "3", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs types de média Supprimer deux types de média. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "mediatype.delete", "params": [ "3", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "mediatypeids": [ "3", "5" ] }, "id": 1 } ``` #### Deleting multiple scheduled reports Delete two scheduled reports. Request: ``` {.java} { "jsonrpc": "2.0", "method": "report.delete", "params": [ "1", "2" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "reportids": [ "1", "2" ] }, "id": 1 } ``` #### Suppression de plusieurs rapports planifiés Supprimer deux rapports planifiés. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "report.delete", "params": [ "1", "2" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "reportids": [ "1", "2" ] }, "id": 1 } ``` #### Deleting multiple services Delete two services. Request: ``` {.java} { "jsonrpc": "2.0", "method": "service.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "serviceids": [ "4", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs services Supprimer deux services. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "service.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "serviceids": [ "4", "5" ] }, "id": 1 } ``` #### Deleting multiple SLAs Delete two SLA entries. Request: ``` {.java} { "jsonrpc": "2.0", "method": "sla.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "slaids": [ "4", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs SLA Supprimer deux SLA. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "sla.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "slaids": [ "4", "5" ] }, "id": 1 } ``` #### Deleting multiple template dashboards Delete two template dashboards. Request: ``` {.java} { "jsonrpc": "2.0", "method": "templatedashboard.delete", "params": [ "45", "46" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "45", "46" ] }, "id": 1 } ``` #### Suppression de plusieurs tableaux de bord de modèle Supprimer deux tableaux de bord de modèle. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "templatedashboard.delete", "params": [ "45", "46" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "45", "46" ] }, "id": 1 } ``` #### Deleting multiple templates Delete two templates. Request: ``` {.java} { "jsonrpc": "2.0", "method": "template.delete", "params": [ "13", "32" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "templateids": [ "13", "32" ] }, "id": 1 } ``` #### Suppression de plusieurs modèles Suppression de deux modèles. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "template.delete", "params": [ "13", "32" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "templateids": [ "13", "32" ] }, "id": 1 } ``` #### Deleting multiple trigger prototypes Delete two trigger prototypes. Request: ``` {.java} { "jsonrpc": "2.0", "method": "triggerprototype.delete", "params": [ "12002", "12003" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "12002", "12003" ] }, "id": 1 } ``` #### Suppression de plusieurs prototypes de déclencheur Supprimer deux prototypes de déclencheur. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "triggerprototype.delete", "params": [ "12002", "12003" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "triggerids": [ "12002", "12003" ] }, "id": 1 } ``` #### Deleting multiple user groups Delete two user groups. Request: ``` {.java} { "jsonrpc": "2.0", "method": "usergroup.delete", "params": [ "20", "21" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "usrgrpids": [ "20", "21" ] }, "id": 1 } ``` #### Suppression de plusieurs groupes d'utilisateurs Supprimer deux groupes d'utilisateurs Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usergroup.delete", "params": [ "20", "21" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "usrgrpids": [ "20", "21" ] }, "id": 1 } ``` #### Deleting multiple user roles Delete two user roles. Request: ``` {.java} { "jsonrpc": "2.0", "method": "role.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "roleids": [ "4", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs rôles utilisateur Supprimer deux rôles utilisateur. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "role.delete", "params": [ "4", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "roleids": [ "4", "5" ] }, "id": 1 } ``` #### Deleting multiple users Delete two users. Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.delete", "params": [ "1", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "1", "5" ] }, "id": 1 } ``` #### Suppression de plusieurs utilisateurs Supprimer deux utilisateurs Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.delete", "params": [ "1", "5" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "1", "5" ] }, "id": 1 } ``` #### Deleting multiple value maps Delete two value maps. Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.delete", "params": [ "1", "2" ], "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "1", "2" ] }, "id": 1 } ``` #### Suppression de plusieurs tables de correspondance Supprimer deux tables de correspondance. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.delete", "params": [ "1", "2" ], "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "valuemapids": [ "1", "2" ] }, "id": 1 } ``` #### Deleting multiple web scenarios Delete two web scenarios. Request: ``` {.java} { "jsonrpc": "2.0", "method": "httptest.delete", "params": [ "2", "3" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "httptestids": [ "2", "3" ] }, "id": 1 } ``` #### Suppression de plusieurs scénarios Web Supprimer deux scénarios Web. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "httptest.delete", "params": [ "2", "3" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "httptestids": [ "2", "3" ] }, "id": 1 } ``` ##### Deny specific check - Blacklist a specific check with DenyKey parameter. Matching keys will be disallowed. All non-matching keys will be allowed, except system.run\[\] items. For example: # Deny secure data access DenyKey=vfs.file.contents[/etc/passwd,*] ::: noteimportant A blacklist may not be a good choice, because a new Zabbix version may have new keys that are not explicitly restricted by the existing configuration. This could cause a security flaw. ::: ##### Deny specific check - Blacklist a specific check with DenyKey parameter. Matching keys will be disallowed. All non-matching keys will be allowed, except system.run\[\] items. ##### Refuser une vérification spécifique - Blacklist une vérification spécifique avec le paramètre DenyKey. Les clés correspondantes seront refusées. Toutes les clés non correspondantes seront autorisées, à l'exception des éléments system.run\[\]. Par exemple : # Refuser l'accès sécurisé aux données DenyKey=vfs.file.contents[/etc/passwd,*] ::: noteimportant Une blacklist peut ne pas être un bon choix, car une nouvelle version de Zabbix peut avoir de nouvelles clés qui ne sont pas explicitement restreintes par la configuration existante. Cela pourrait provoquer une faille de sécurité. ::: ##### Deny specific command, allow others - Blacklist a specific command with DenyKey parameter. Whitelist all other commands, with the AllowKey parameter. ```{=html} <!-- --> ``` # Disallow specific command DenyKey=system.run[ls -l /] # Allow other scripts AllowKey=system.run[*] ##### Refuser une commande spécifique, autoriser les autres - Blacklister une commande spécifique avec le paramètre DenyKey. Mettez en whitelist toutes les autres commandes, avec le paramètre AllowKey. ```{=html} <!-- --> ``` # Interdire une commande spécifique DenyKey=system.run[ls -l /] # Autoriser d'autres scripts AllowKey=system.run[*] ##### Dependent item prototype Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `ipmi.get` item we created.  Note the use of the {\#SENSOR\_ID} macro in the item prototype name and key: - *Name*: IPMI value for sensor {\#SENSOR\_ID} - *Key*: ipmi\_sensor\[{\#SENSOR\_ID}\] As type of information, *Numeric (unsigned)*. In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter: $.[?(@.id=='{#SENSOR_ID}')].value.first()  When discovery starts, one item per each IPMI sensor will be created. This item will return the integer value of the given sensor. ##### Prototype d'élément dépendant Créez un prototype d'élément avec le type "Elément dépendant" dans cette règle LLD. En tant qu'élément maître pour ce prototype, sélectionnez l'élément `ipmi.get` que nous avons créé.  Notez l'utilisation de la macro {\#SENSOR\_ID} dans le nom et la clé du prototype d'élément : - *Nom*: IPMI value for sensor {\#SENSOR\_ID} - *Clé*: ipmi\_sensor\[{\#SENSOR\_ID}\] Comme type d'information, *Numérique (non signé)*. Dans l'onglet "Prétraitement" du prototype d'élément, sélectionnez JSONPath et utilisez l'expression JSONPath suivante comme paramètre : $.[?(@.id=='{#SENSOR_ID}')].value.first()  Lorsque la découverte démarre, un élément par capteur IPMI est créé. Cet élément renverra la valeur entière du capteur donné. ##### Dependent item prototype Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `vfs.fs.get` item we created.  Note the use of custom macros in the item prototype name and key: - *Name*: Free disk space on {\#FSNAME}, type: {\#FSTYPE} - *Key*: Free\[{\#FSNAME}\] As type of information, use: - *Numeric (unsigned)* for metrics like 'free', 'total', 'used' - *Numeric (float)* for metrics like 'pfree', 'pused' (percentage) In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter: $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  When discovery starts, one item per each mountpoint will be created. This item will return the number of free bytes for the given mountpoint. ##### Prototype d'élément dépendant Créez un prototype d'article avec le type "Élément dépendant" dans cette règle LLD. Comme élément maître pour ce prototype, sélectionnez l'élément `vfs.fs.get` que nous avons créé.  Notez l'utilisation de macros personnalisées dans le nom et la clé du prototype d'élément : - *Nom*: Free disk space on {\#FSNAME}, type: {\#FSTYPE} - *Clé*: Free\[{\#FSNAME}\] Comme type d'information, utilisez : - *Numérique (non signé)* pour les métriques telles que 'free', 'total', 'used' - *Numérique (flottant)* pour les métriques telles que 'pfree', 'pused' (pourcentage) Dans l'onglet "Prétraitement" du prototype d'élément, sélectionnez JSONPath et utilisez l'expression JSONPath suivante comme paramètre : $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  Lorsque la découverte démarre, un élément par point de montage sera créé. Cet élément renverra le nombre d'octets libres pour le point de montage donné. ##### Dependent LLD rule Create a low-level discovery rule as "Dependent item" type:  As master item select the `vfs.fs.get` item we created. In the "LLD macros" tab define custom macros with the corresponding JSONPath:  ##### Règle LLD dépendante Créez une règle de découverte de bas niveau en tant que type "Élément dépendant" :  En tant qu'élément maître, sélectionnez l'élément `vfs.fs.get` que nous avons créé. Dans l'onglet "macros LLD" définissez des macros personnalisées avec le JSONPath correspondant :  ##### Dependent LLD rule Create a low-level discovery rule as "Dependent item" type:  As master item select the `ipmi.get` item we created. In the "LLD macros" tab define a custom macro with the corresponding JSONPath:  ##### Règle LLD dépendante Créez une règle de découverte de bas niveau en tant que type "Élément dépendant" :  En tant qu'élément principal, sélectionnez l'élément `ipmi.get` que nous avons créé. Dans l'onglet "Macros LLD", définissez une macro personnalisée avec le JSONPath correspondant :  ##### Deprecated internal items for history/trends The following internal items are now deprecated and will be removed in a future major release: - `zabbix[history]` - `zabbix[history_log]` - `zabbix[history_str]` - `zabbix[history_text]` - `zabbix[history_uint]` - `zabbix[trends]` - `zabbix[trends_uint]` ##### Éléments internes obsolètes pour l'historique/les tendances Les éléments internes suivants sont désormais obsolètes et seront supprimés dans une future version majeure : - `zabbix[history]` - `zabbix[history_log]` - `zabbix[history_str]` - `zabbix[history_text]` - `zabbix[history_uint]` - `zabbix[trends]` - `zabbix[trends_uint]` Deprecated widgets: - [Data overview](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/data_overview) Widgets obsolètes : - [Aperçu des données](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/data_overview) ### Description `array configuration.importcompare(object parameters)` This method allows to compare import file with current system elements and shows what will be changed if this import file will be imported. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `array configuration.importcompare(object parameters)` Cette méthode permet de comparer le fichier d'importation avec les éléments actuels du système et montre ce qui sera changé si ce fichier d'importation est importé. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `boolean configuration.import(object parameters)` This method allows to import configuration data from a serialized string. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `boolean configuration.import(object parameters)` Cette méthode permet d'importer les données de configuration sous forme de chaîne sérialisée. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array action.get(object parameters)` The method allows to retrieve actions according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array action.get(object parameters)` La méthode permet de récupérer des actions en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array alert.get(object parameters)` The method allows to retrieve alerts according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array alert.get(paramètres d'objet)` La méthode permet de récupérer les alertes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres des rôles utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array auditlog.get(object parameters)` The method allows to retrieve audit log records according to the given parameters. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array auditlog.get(paramètres d'objet)` Cette méthode permet de récupérer les enregistrement du journal d'audit en fonction des paramètres donnés. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array correlation.get(object parameters)` The method allows to retrieve correlations according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array correlation.get(object parameters)` La méthode permet de récupérer des corrélations en fonction des paramètres spécifiés. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array dashboard.get(object parameters)` The method allows to retrieve dashboards according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array dashboard.get(object parameters)` La méthode permet de récupérer des tableaux de bord en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array dcheck.get(object parameters)` The method allows to retrieve discovery checks according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array dcheck.get(object parameters)` La méthode permet de récupérer des vérifications de découverte en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array dhost.get(object parameters)` The method allows to retrieve discovered hosts according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array dhost.get(object parameters)` La méthode permet de récupérer des hôtes découverts en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array discoveryrule.get(object parameters)` The method allows to retrieve LLD rules according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array discoveryrule.get(object parameters)` La méthode permet de récupérer les règles de découverte bas niveau en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array drule.get(object parameters)` The method allows to retrieve discovery rules according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array drule.get(object parameters)` La méthode permet de récupérer des règles de découverte en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array dservice.get(object parameters)` The method allows to retrieve discovered services according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array dservice.get(object parameters)` La méthode permet de récupérer des services découverts en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array event.get(object parameters)` The method allows to retrieve events according to the given parameters. ::: noteimportant This method may return events of a deleted entity if these events have not been removed by the housekeeper yet. ::: ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array event.get(object parameters)` La méthode permet de récupérer des événements en fonction des paramètres donnés. ::: noteimportant Cette méthode peut renvoyer des événements d'une entité supprimée si ces événements n'ont pas encore été supprimés par le housekeeper. ::: ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array graph.get(object parameters)` The method allows to retrieve graphs according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `graphique entier/tableau.get(paramètres d'objet)` La méthode permet de récupérer des graphiques en fonction des paramètres donnés. ::: noteclassique Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles d'utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array graphitem.get(object parameters)` The method allows to retrieve graph items according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array graphitem.get(object parameters)` La méthode permet de récupérer des éléments de graphique en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array graphprototype.get(object parameters)` The method allows to retrieve graph prototypes according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array graphprototype.get(object parameters)` La méthode permet de récupérer des prototypes de graphiques en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array hanode.get(object parameters)` The method allows to retrieve a list of High availability cluster nodes according to the given parameters. ::: noteclassic This method is only available to *Super admin* user types. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array hanode.get(paramètres d'objet)` La méthode permet de récupérer une liste de nœuds du cluster en Haute disponibilité en fonction des paramètres donnés. ::: noteclassic Cette méthode n'est disponible pour tous les utilisateurs de type *Super admin*. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array host.get(object parameters)` The method allows to retrieve hosts according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array host.get(object parameters)` La méthode permet de récupérer les hôtes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array hostgroup.get(object parameters)` The method allows to retrieve host groups according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array hostgroup.get(object parameters)` La méthode permet de récupérer des groupes d'hôtes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array hostinterface.get(object parameters)` The method allows to retrieve host interfaces according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.create(object/array hostInterfaces)` Cette méthode permet de créer de nouvelles interfaces hôtes. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array hostprototype.get(object parameters)` The method allows to retrieve host prototypes according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array hostprototype.get(object parameters)` La méthode permet de récupérer des prototypes d'hôtes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array httptest.get(object parameters)` The method allows to retrieve web scenarios according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array httptest.get(object parameters)` La méthode permet de récupérer des scénarios Web en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array iconmap.get(object parameters)` The method allows to retrieve icon maps according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array iconmap.get(object parameters)` La méthode permet de récupérer des tables de correspondance d'icônes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array image.get(object parameters)` The method allows to retrieve images according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array image.get(object parameters)` La méthode permet de récupérer des images en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array item.get(object parameters)` The method allows to retrieve items according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array item.get(object parameters)` La méthode permet de récupérer des éléments en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array itemprototype.get(object parameters)` The method allows to retrieve item prototypes according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array itemprototype.get(object parameters)` La méthode permet de récupérer des prototypes d'éléments en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array maintenance.get(object parameters)` The method allows to retrieve maintenances according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array maintenance.get(object parameters)` La méthode permet de récupérer les maintenances en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array map.get(object parameters)` The method allows to retrieve maps according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array map.get(object parameters)` La méthode permet de récupérer des cartes en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array problem.get(object parameters)` The method allows to retrieve problems according to the given parameters. This method is for retrieving unresolved problems. It is also possible, if specified, to additionally retrieve recently resolved problems. The period that determines how old is "recently" is defined in *Administration* → *[General](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*. Problems that were resolved prior to that period are not kept in the problem table. To retrieve problems that were resolved further back in the past, use the [event.get](/manual/api/reference/event/get) method. ::: noteimportant This method may return problems of a deleted entity if these problems have not been removed by the housekeeper yet. ::: ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array problem.get(object parameters)` La méthode permet de récupérer des problèmes en fonction des paramètres donnés. Cette méthode permet de récupérer des problèmes non résolus. Il est également possible, si spécifié, de récupérer en plus les problèmes récemment résolus. La période qui détermine la période pour "récemment" est définie dans *Administration* → *[Général]'/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*. Les problèmes résolus avant cette période ne sont pas conservés dans la table des problèmes. Pour récupérer les problèmes résolus dans le passé, utilisez la méthode [event.get](/manual/api/reference/event/get) ::: noteclassic Cette méthode peut renvoyer des problèmes d'une entité supprimée si ces problèmes n'ont pas encore été supprimés par la maintenance. ::: ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array proxy.get(object parameters)` The method allows to retrieve proxies according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array proxy.get(object parameters)` La méthode permet de récupérer des proxys en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array regexp.get(object parameters)` The method allows to retrieve global regular expressions according to the given parameters. ::: noteclassic This method is available only to *Super Admin*. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array regexp.get(object parameters)` La méthode permet de récupérer des expressions régulières globales en fonction des paramètres donnés. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array report.get(object parameters)` The method allows to retrieve scheduled reports according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array report.get(object parameters)` La méthode permet de récupérer des rapports planifiés en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array role.get(object parameters)` The method allows to retrieve roles according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array role.get(object parameters)` La méthode permet de récupérer des rôles en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array script.get(object parameters)` The method allows to retrieve scripts according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array script.get(object parameters)` La méthode permet de récupérer des scripts en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array service.get(object parameters)` The method allows to retrieve services according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array service.get(object parameters)` La méthode permet de récupérer des services en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array sla.get(object parameters)` The method allows to retrieve SLA objects according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array sla.get(object parameters)` La méthode permet de récupérer des objets SLA en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array task.get(object parameters)` The method allows to retrieve tasks according to the given parameters. Method returns details only about 'diagnostic information' tasks. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array task.get(object parameters)` La méthode permet de récupérer des tâches en fonction des paramètres donnés. La méthode renvoie des détails uniquement sur les tâches d\''informations de diagnostic'. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array templatedashboard.get(object parameters)` The method allows to retrieve template dashboards according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array templatedashboard.get(object parameters)` La méthode permet de récupérer des modèles de tableaux de bord en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array template.get(object parameters)` The method allows to retrieve templates according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array template.get(object parameters)` La méthode permet de récupérer des modèles en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array token.get(object parameters)` The method allows to retrieve tokens according to the given parameters. ::: noteclassic Only *Super admin* user type is allowed to view tokens for other users. ::: ### Description `integer/array token.get(object parameters)` La méthode permet de récupérer des jetons en fonction des paramètres donnés. ::: noteclassic Seul le type d'utilisateur *Super admin* est autorisé à afficher les jetons des autres utilisateurs. ::: ### Description `integer/array trend.get(object parameters)` The method allows to retrieve trend data according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array trend.get(object parameters)` La méthode permet de récupérer des données de tendance en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array trigger.get(object parameters)` The method allows to retrieve triggers according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array trigger.get(object parameters)` La méthode permet de récupérer des déclencheurs en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array triggerprototype.get(object parameters)` The method allows to retrieve trigger prototypes according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array triggerprototype.get(object parameters)` La méthode permet de récupérer des prototypes de déclencheurs en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array user.get(object parameters)` The method allows to retrieve users according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array user.get(object parameters)` La méthode permet de récupérer les utilisateurs en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array usergroup.get(object parameters)` The method allows to retrieve user groups according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array usergroup.get(object parameters)` La méthode permet de récupérer des groupes d'utilisateurs en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array usermacro.get(object parameters)` The method allows to retrieve host and global macros according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array usermacro.get(object parameters)` La méthode permet de récupérer les macros hôtes et globales en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `integer/array valuemap.get(object parameters)` The method allows to retrieve value maps according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `integer/array valuemap.get(object parameters)` La méthode permet de récupérer des correspondances de valeurs en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object action.create(object/array actions)` This method allows to create new actions. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object action.create(object/array actions)` Cette méthode permet de créer de nouvelles actions. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object action.delete(array actionIds)` This method allows to delete actions. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object action.delete(array actionIds)` Cette méthode permet de supprimer des actions. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object action.update(object/array actions)` This method allows to update existing actions. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object action.update(object/array actions)` Cette méthode permet de mettre à jour des actions existantes. ::: noteclassic Cette méthode n'est disponible que pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du rôle de l'utilisateur. Voir [Rôles Utilisateur] (/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'information. ::: ### Description `object authentication.get(object parameters)` The method allows to retrieve authentication object according to the given parameters. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object authentication.get(object parameters)` La méthode permet de récupérer un objet d'authentification en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object authentication.update(object authentication)` This method allows to update existing authentication settings. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object authentication.update(object authentication)` Cette méthode permet de mettre à jour les paramètres d'authentification existants. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object autoregistration.get(object parameters)` The method allows to retrieve autoregistration object according to the given parameters. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object autoregistration.get(paramètres d'objet)` La méthode permet de récupérer l'objet d'enregistrement automatique en fonction des paramètres donnés. ::: noteclassic Cette méthode n'est disponible que pour le type d'utilisateur *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle utilisateur. Voir [Rôles utilisateur (/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object autoregistration.update(object autoregistration)` This method allows to update existing autoregistration. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `objet autoregistration.update (objet enregistrement automatique)` Cette méthode permet de mettre à jour l'auto-enregistrement existant. ::: noteclassic Cette méthode n'est disponible que pour le type d'utilisateur *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object correlation.create(object/array correlations)` This method allows to create new correlations. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `objet correlation.create(objet/tableau corrélations)` Cette méthode permet de créer de nouvelles corrélations. ::: noteclassic Cette méthode n'est disponible que pour le type utilisateur *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object correlation.delete(array correlationids)` This method allows to delete correlations. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object correlation.delete(array correlationids)` Cette méthode permet de supprimer les corrélations. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object correlation.update(object/array correlations)` This method allows to update existing correlations. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object correlation.update(object/array correlations)` Cette méthode permet de mettre à jour les corrélations existantes. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object dashboard.create(object/array dashboards)` This method allows to create new dashboards. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object dashboard.create(object/array dashboards)` Cette méthode permet de créer de nouveaux tableaux de bord. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object dashboard.delete(array dashboardids)` This method allows to delete dashboards. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object dashboard.delete(array dashboardids)` Cette méthode permet de supprimer des tableaux de bord. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object dashboard.update(object/array dashboards)` This method allows to update existing dashboards. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object dashboard.update(object/array dashboards)` Cette méthode permet de mettre à jour des tableaux de bord existants. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object discoveryrule.copy(object parameters)` This method allows to copy LLD rules with all of the prototypes to the given hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object discoveryrule.copy(object parameters)` Cette méthode permet de copier les règles de découverte bas niveau avec tous les prototypes sur les hôtes donnés. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object discoveryrule.create(object/array lldRules)` This method allows to create new LLD rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object discoveryrule.create(object/array lldRules)` Cette méthode permet de créer de nouvelles règles de découverte bas niveau. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object discoveryrule.delete(array lldRuleIds)` This method allows to delete LLD rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object discoveryrule.delete(array lldRuleIds)` Cette méthode permet de supprimer les règles de découverte bas niveau. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object discoveryrule.update(object/array lldRules)` This method allows to update existing LLD rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object discoveryrule.update(object/array lldRules)` Cette méthode permet de mettre à jour les règles de découverte bas niveau existantes. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object drule.create(object/array discoveryRules)` This method allows to create new discovery rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object drule.create(object/array discoveryRules)` Cette méthode permet de créer de nouvelles règles de découverte. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object drule.delete(array discoveryRuleIds)` This method allows to delete discovery rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object drule.delete(array discoveryRuleIds)` Cette méthode permet de supprimer les règles de découverte. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object drule.update(object/array discoveryRules)` This method allows to update existing discovery rules. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object drule.update(object/array discoveryRules)` Cette méthode permet de mettre à jour les règles de découverte existantes. ::: noteclassic Cette méthode est uniquement disponible pour les utilisateurs type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les paramètres du rôle utilisateur. Voir les [rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graph.create(object/array graphs)` This method allows to create new graphs. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object graph.create(object/array graphs)` Cette méthode permet de créer de nouveaux graphiques. ::: noteclassic Cette méthode est disponible uniquement pour tous les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graph.delete(array graphIds)` This method allows to delete graphs. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object graph.delete(array graphIds)` Cette méthode permet de supprimer des graphiques. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graphprototype.create(object/array graphPrototypes)` This method allows to create new graph prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `objet graphprototype.create(objet/tableau graphPrototypes)` Cette méthode permet de créer de nouveaux prototypes de graphes. ::: noteclassique Cette méthode n'est disponible que pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graphprototype.delete(array graphPrototypeIds)` This method allows to delete graph prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object graphprototype.delete(array graphPrototypeIds)` Cette méthode permet de supprimer des prototypes de graphique. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graphprototype.update(object/array graphPrototypes)` This method allows to update existing graph prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object graphprototype.update(object/array graphPrototypes)` Cette méthode permet de mettre à jour des prototypes de graphiques existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object graph.update(object/array graphs)` This method allows to update existing graphs. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object graph.update(object/array graphs)` Cette méthode permet de mettre à jour des graphiques existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object history.clear(array itemids)` This method allows to clear item history. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object history.clear(array itemids)` Cette méthode permet d'effacer l'historique des éléments. ::: noteclassic ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.create(object/array hosts)` This method allows to create new hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.create(object/array hosts)` Cette méthode permet de créer de nouveaux hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.delete(array hosts)` This method allows to delete hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.delete(array hosts)` Cette méthode permet de supprimer des hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.create(object/array hostGroups)` This method allows to create new host groups. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.create(object/array hostGroups)` Cette méthode permet de créer de nouveaux groupes d'hôtes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.delete(array hostGroupIds)` This method allows to delete host groups. A host group can not be deleted if: - it contains hosts that belong to this group only; - it is marked as internal; - it is used by a host prototype; - it is used in a global script; - it is used in a correlation condition. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.delete(array hostGroupIds)` Cette méthode permet de supprimer des groupes d'hôtes. Un groupe d'hôtes ne peut pas être supprimé si : - il contient des hôtes qui appartiennent à ce groupe uniquement ; - il est marqué comme interne ; - il est utilisé par un prototype d'hôte ; - il est utilisé dans un script global ; - il est utilisé dans une condition de corrélation. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.massadd(object parameters)` This method allows to simultaneously add multiple related objects to all the given host groups. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.massadd(object parameters)` Cette méthode permet d'ajouter simultanément plusieurs objets associés à tous les groupes d'hôtes donnés. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.massremove(object parameters)` This method allows to remove related objects from multiple host groups. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.massremove(object parameters)` Cette méthode permet de supprimer des objets associés de plusieurs groupes d'hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.massupdate(object parameters)` This method allows to replace hosts and templates with the specified ones in multiple host groups. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.massupdate(object parameters)` Cette méthode permet de remplacer les hôtes et les modèles par ceux spécifiés dans plusieurs groupes d'hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostgroup.update(object/array hostGroups)` This method allows to update existing hosts groups. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostgroup.update(object/array hostGroups)` Cette méthode permet de mettre à jour les groupes d'hôtes existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.create(object/array hostInterfaces)` This method allows to create new host interfaces. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.create(object/array hostInterfaces)` Cette méthode permet de créer de nouvelles interfaces hôtes. ::: noteclassic Cette méthode est disponible uniquement pour tous les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.delete(array hostInterfaceIds)` This method allows to delete host interfaces. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.delete(array hostInterfaceIds)` Cette méthode permet de supprimer les interfaces hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.massadd(object parameters)` This method allows to simultaneously add host interfaces to multiple hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.massadd(object parameters)` Cette méthode permet d'ajouter simultanément des interfaces hôtes à plusieurs hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.massremove(object parameters)` This method allows to remove host interfaces from the given hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.massremove(object parameters)` Cette méthode permet de supprimer les interfaces hôtes des hôtes donnés. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.replacehostinterfaces(object parameters)` This method allows to replace all host interfaces on a given host. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.replacehostinterfaces(object parameters)` Cette méthode permet de remplacer toutes les interfaces hôtes sur un hôte donné. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostinterface.update(object/array hostInterfaces)` This method allows to update existing host interfaces. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostinterface.update(object/array hostInterfaces)` Cette méthode permet de mettre à jour les interfaces hôtes existantes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.massadd(object parameters)` This method allows to simultaneously add multiple related objects to all the given hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.massadd(object parameters)` Cette méthode permet d'ajouter simultanément plusieurs objets liés à tous les hôtes donnés. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.massremove(object parameters)` This method allows to remove related objects from multiple hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.massremove(object parameters)` Cette méthode permet de supprimer des objets liés de plusieurs hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.massupdate(object parameters)` This method allows to simultaneously replace or remove related objects and update properties on multiple hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.massupdate(object parameters)` Cette méthode permet de remplacer ou de supprimer simultanément des objets associés et de mettre à jour les propriétés sur plusieurs hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostprototype.create(object/array hostPrototypes)` This method allows to create new host prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostprototype.create(object/array hostPrototypes)` Cette méthode permet de créer de nouveaux prototypes d'hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostprototype.delete(array hostPrototypeIds)` This method allows to delete host prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostprototype.delete(array hostPrototypeIds)` Cette méthode permet de supprimer des prototypes d’hôte. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object hostprototype.update(object/array hostPrototypes)` This method allows to update existing host prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object hostprototype.update(object/array hostPrototypes)` Cette méthode permet de mettre à jour les prototypes d'hôtes existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object host.update(object/array hosts)` This method allows to update existing hosts. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object host.update(object/array hosts)` Cette méthode permet de mettre à jour les hôtes existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object housekeeping.get(object parameters)` The method allows to retrieve housekeeping object according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object housekeeping.get(object parameters)` La méthode permet de récupérer l'objet de ménage selon les paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object housekeeping.update(object housekeeping)` This method allows to update existing housekeeping settings. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object housekeeping.update(object housekeeping)` Cette méthode permet de mettre à jour les paramètres de nettoyage existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object httptest.create(object/array webScenarios)` This method allows to create new web scenarios. ::: noteclassic Creating a web scenario will automatically create a set of [web monitoring items](/manual/web_monitoring/items). ::: ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object httptest.create(object/array webScenarios)` Cette méthode permet de créer de nouveaux scénarios web. ::: noteclassic La création d'un scénario Web créera automatiquement un ensemble d'[éléments de surveillance Web](/manual/web_monitoring/items). ::: ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object httptest.delete(array webScenarioIds)` This method allows to delete web scenarios. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object httptest.delete(array webScenarioIds)` Cette méthode permet de supprimer des scénarios Web. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object httptest.update(object/array webScenarios)` This method allows to update existing web scenarios. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object httptest.update(object/array webScenarios)` Cette méthode permet de mettre à jour les scénarios Web existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object iconmap.create(object/array iconMaps)` This method allows to create new icon maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object iconmap.create(object/array iconMaps)` Cette méthode permet de créer de nouvelles correspondance d'icônes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object iconmap.delete(array iconMapIds)` This method allows to delete icon maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object iconmap.delete(array iconMapIds)` Cette méthode permet de supprimer des correspondances d'icônes. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object iconmap.update(object/array iconMaps)` This method allows to update existing icon maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object iconmap.update(object/array iconMaps)` Cette méthode permet de mettre à jour les correspondances d'icônes existantes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object image.create(object/array images)` This method allows to create new images. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object image.create(object/array images)` Cette méthode permet de créer de nouvelles images. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object image.delete(array imageIds)` This method allows to delete images. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object image.delete(array imageIds)` Cette méthode permet de supprimer des images. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object image.update(object/array images)` This method allows to update existing images. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object image.update(object/array images)` Cette méthode permet de mettre à jour des images existantes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object item.create(object/array items)` This method allows to create new items. ::: noteclassic Web items cannot be created via the Zabbix API. ::: ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object item.create(object/array items)` Cette méthode permet de créer de nouveaux éléments. ::: noteclassic Les éléments Web ne peuvent pas être créés via l'API Zabbix. ::: ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object item.delete(array itemIds)` This method allows to delete items. ::: noteclassic Web items cannot be deleted via the Zabbix API. ::: ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object item.delete(array itemIds)` Cette méthode permet de supprimer des éléments. ::: noteclassic Les éléments Web ne peuvent pas être supprimés via l'API Zabbix. ::: ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object itemprototype.create(object/array itemPrototypes)` This method allows to create new item prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object itemprototype.create(object/array itemPrototypes)` Cette méthode permet de créer de nouveaux prototypes éléments. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object itemprototype.delete(array itemPrototypeIds)` This method allows to delete item prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object itemprototype.delete(array itemPrototypeIds)` Cette méthode permet de supprimer des prototypes d’éléments. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object itemprototype.update(object/array itemPrototypes)` This method allows to update existing item prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object itemprototype.update(object/array itemPrototypes)` Cette méthode permet de mettre à jour les prototypes d'éléments existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object item.update(object/array items)` This method allows to update existing items. ::: noteclassic Web items cannot be updated via the Zabbix API. ::: ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object item.update(object/array items)` Cette méthode permet de mettre à jour les éléments existants. ::: noteclassic Les éléments Web ne peuvent pas être mis à jour via l'API Zabbix. ::: ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object maintenance.create(object/array maintenances)` This method allows to create new maintenances. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object maintenance.create(object/array maintenances)` Cette méthode permet de créer de nouvelles maintenances. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object maintenance.delete(array maintenanceIds)` This method allows to delete maintenance periods. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object maintenance.delete(array maintenanceIds)` Cette méthode permet de supprimer des maintenances. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object maintenance.update(object/array maintenances)` This method allows to update existing maintenances. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object maintenance.update(object/array maintenances)` Cette méthode permet de mettre à jour les maintenances existantes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object map.create(object/array maps)` This method allows to create new maps. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object map.create(object/array maps)` Cette méthode permet de créer de nouvelles cartes. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object map.delete(array mapIds)` This method allows to delete maps. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object map.delete(array mapIds)` Cette méthode permet de supprimer des cartes. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateur. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object map.update(object/array maps)` This method allows to update existing maps. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object map.update(object/array maps)` Cette méthode permet de mettre à jour les cartes existantes. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object mediatype.create(object/array mediaTypes)` This method allows to create new media types. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object mediatype.create(object/array mediaTypes)` Cette méthode permet de créer de nouveaux types de médias. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object mediatype.delete(array mediaTypeIds)` This method allows to delete media types. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object mediatype.delete(array mediaTypeIds)` Cette méthode permet de supprimer des types de média. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object mediatype.update(object/array mediaTypes)` This method allows to update existing media types. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object mediatype.update(object/array mediaTypes)` Cette méthode permet de mettre à jour les types de médias existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object proxy.create(object/array proxies)` This method allows to create new proxies. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object proxy.create(object/array proxies)` Cette méthode permet de créer de nouveaux proxys. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object proxy.delete(array proxies)` This method allows to delete proxies. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object proxy.delete(array proxies)` Cette méthode permet de supprimer des proxys. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object proxy.update(object/array proxies)` This method allows to update existing proxies. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object proxy.update(object/array proxies)` Cette méthode permet de mettre à jour les proxys existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object regexp.create(object/array regularExpressions)` This method allows to create new global regular expressions. ::: noteclassic This method is only available to *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object regexp.create(object/array regularExpressions)` Cette méthode permet de créer de nouvelles expressions régulières globales. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object regexp.delete(array regexpids)` This method allows to delete global regular expressions. ::: noteclassic This method is only available to *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object regexp.delete(array regexpids)` Cette méthode permet de supprimer des expressions régulières globales. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object regexp.update(object/array regularExpressions)` This method allows to update existing global regular expressions. ::: noteclassic This method is only available to *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object regexp.update(object/array regularExpressions)` Cette méthode permet de mettre à jour les expressions régulières globales existantes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object report.create(object/array reports)` This method allows to create new scheduled reports. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object report.create(object/array reports)` Cette méthode permet de créer de nouveaux rapports planifiés. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object report.delete(array reportids)` This method allows to delete scheduled reports. ::: noteclassic This method is only available to *Admin* and *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object report.delete(array reportids)` Cette méthode permet de supprimer des rapports planifiés. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object report.update(object/array reports)` This method allows to update existing scheduled reports. ::: noteclassic This method is only available to *Admin* and *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object report.update(object/array reports)` Cette méthode permet de mettre à jour les rapports programmés existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object role.create(object/array roles)` This method allows to create new roles. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object role.create(object/array roles)` Cette méthode permet de créer de nouveaux rôles. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object role.delete(array roleids)` This method allows to delete roles. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object role.delete(array roleids)` Cette méthode permet de supprimer des rôles. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object role.update(object/array roles)` This method allows to update existing roles. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object role.update(object/array roles)` Cette méthode permet de mettre à jour les rôles existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object script.create(object/array scripts)` This method allows to create new scripts. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object script.create(object/array scripts)` Cette méthode permet de créer de nouveaux scripts. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object script.delete(array scriptIds)` This method allows to delete scripts. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object script.delete(array scriptIds)` Cette méthode permet de supprimer des scripts. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object script.execute(object parameters)` This method allows to run a script on a host or event. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object script.execute(object parameters)` Cette méthode permet d'exécuter un script sur un hôte ou un événement. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object script.getscriptsbyhosts(array hostIds)` This method allows to retrieve scripts available on the given hosts. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object script.getscriptsbyhosts(array hostIds)` Cette méthode permet de récupérer les scripts disponibles sur les hosts donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object script.update(object/array scripts)` This method allows to update existing scripts. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object script.update(object/array scripts)` Cette méthode permet de mettre à jour les scripts existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object service.create(object/array services)` This method allows to create new services. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object service.create(object/array services)` Cette méthode permet de créer de nouveaux services. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object service.delete(array serviceIds)` This method allows to delete services. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object service.delete(array serviceIds)` Cette méthode permet de supprimer des services. ::: noteclassic Cette méthode est disponible pour tous les types d'utilisateur. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object service.update(object/array services)` This method allows to update existing services. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object service.update(object/array services)` Cette méthode permet de mettre à jour les services existants. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object settings.get(object parameters)` The method allows to retrieve settings object according to the given parameters. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object settings.get(object parameters)` La méthode permet de récupérer l'objet de paramètres en fonction des paramètres donnés. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object settings.update(object settings)` This method allows to update existing common settings. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object settings.update(object settings)` Cette méthode permet de mettre à jour les paramètres communs existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object sla.create(object/array SLAs)` This method allows to create new SLA objects. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object sla.create(object/array SLAs)` Cette méthode permet de créer de nouveaux objets SLA. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object sla.delete(array slaids)` This method allows to delete SLA entries. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object sla.delete(array slaids)` Cette méthode permet de supprimer les entrées SLA. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object sla.update(object/array slaids)` This method allows to update existing SLA entries. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object sla.update(object/array slaids)` Cette méthode permet de mettre à jour les entrées SLA existantes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object task.create(object/array tasks)` This method allows to create a new task (such as collect diagnostic data or check items or low-level discovery rules without config reload). ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object task.create(object/array tasks)` Cette méthode permet de créer une nouvelle tâche (comme collecter des données de diagnostic ou vérifier des éléments ou des règles de découverte de bas niveau sans recharger la configuration). ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.create(object/array templates)` This method allows to create new templates. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.create(object/array templates)` Cette méthode permet de créer de nouveaux modèles. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object templatedashboard.create(object/array templateDashboards)` This method allows to create new template dashboards. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object templatedashboard.create(object/array templateDashboards)` Cette méthode permet de créer de nouveaux modèles de tableaux de bord. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object templatedashboard.delete(array templateDashboardIds)` This method allows to delete template dashboards. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object templatedashboard.delete(array templateDashboardIds)` Cette méthode permet de supprimer des tableaux de bord de modèle. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object templatedashboard.update(object/array templateDashboards)` This method allows to update existing template dashboards. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object templatedashboard.update(object/array templateDashboards)` Cette méthode permet de mettre à jour les modèles de tableaux de bord existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.delete(array templateIds)` This method allows to delete templates. Deleting a template will cause deletion of all template entities (items, triggers, graphs, etc.). To leave template entities with the hosts, but delete the template itself, first unlink the template from required hosts using one of these methods: [template.update](/manual/api/reference/template/update), [template.massupdate](/manual/api/reference/template/massupdate), [host.update](/manual/api/reference/host/update), [host.massupdate](/manual/api/reference/host/massupdate). ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.delete(array templateIds)` Cette méthode permet de supprimer des modèles. La suppression d'un modèle entraînera la suppression de toutes les entités du modèle (éléments, déclencheurs, graphiques, etc.). Pour laisser les entités de modèle sur les hôtes, mais supprimer le modèle lui-même, dissociez d'abord le modèle des hôtes requis en utilisant l'une de ces méthodes : [template.update](/manual/api/reference/template/update), [template.massupdate](/manual/api/reference/template/massupdate), [host.update](/manual/api/reference/host/update), [host.massupdate](/manual/api/reference/host/massupdate). ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.massadd(object parameters)` This method allows to simultaneously add multiple related objects to the given templates. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.massadd(object parameters)` Cette méthode permet d'ajouter simultanément plusieurs objets liés aux modèles donnés. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.massremove(object parameters)` This method allows to remove related objects from multiple templates. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.massremove(object parameters)` Cette méthode permet de supprimer les objets liés de plusieurs modèles. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.massupdate(object parameters)` This method allows to simultaneously replace or remove related objects and update properties on multiple templates. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.massupdate(object parameters)` Cette méthode permet de remplacer ou de supprimer simultanément des objets associés et de mettre à jour les propriétés de plusieurs modèles. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object template.update(object/array templates)` This method allows to update existing templates. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object template.update(object/array templates)` Cette méthode permet de mettre à jour les modèles existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object trigger.adddependencies(object/array triggerDependencies)` This method allows to create new trigger dependencies. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object trigger.adddependencies(object/array triggerDependencies)` Cette méthode permet de créer de nouvelles dépendances de déclencheur. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object trigger.create(object/array triggers)` This method allows to create new triggers. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object trigger.create(object/array triggers)` Cette méthode permet de créer de nouveaux déclencheurs. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object trigger.delete(array triggerIds)` This method allows to delete triggers. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object trigger.delete(array triggerIds)` Cette méthode permet de supprimer des déclencheurs. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object trigger.deletedependencies(string/array triggers)` This method allows to delete all trigger dependencies from the given triggers. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object trigger.deletedependencies(string/array triggers)` Cette méthode permet de supprimer toutes les dépendances des déclencheurs donnés. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object triggerprototype.create(object/array triggerPrototypes)` This method allows to create new trigger prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object triggerprototype.create(object/array triggerPrototypes)` Cette méthode permet de créer de nouveaux prototypes de trigger. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object triggerprototype.delete(array triggerPrototypeIds)` This method allows to delete trigger prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object triggerprototype.delete(array triggerPrototypeIds)` Cette méthode permet de supprimer des prototypes de déclencheur. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object triggerprototype.update(object/array triggerPrototypes)` This method allows to update existing trigger prototypes. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object triggerprototype.update(object/array triggerPrototypes)` Cette méthode permet de mettre à jour les prototypes de déclencheurs existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object trigger.update(object/array triggers)` This method allows to update existing triggers. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object trigger.update(object/array triggers)` Cette méthode permet de mettre à jour les déclencheurs existants. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object user.checkAuthentication` This method checks and prolongs user session. ::: noteimportant Calling **user.checkAuthentication** method prolongs user session by default. ::: ### Description `object user.checkAuthentication` Cette méthode vérifie et prolonge la session utilisateur. ::: noteimportant L'appel de la méthode **user.checkAuthentication** prolonge la session utilisateur par défaut. ::: ### Description `object user.create(object/array users)` This method allows to create new users. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ::: noteclassic The strength of user password is validated according the password policy rules defined by Authentication API. See [Authentication API](/manual/api/reference/authentication) for more information. ::: ### Description `object user.create(object/array users)` Cette méthode permet de créer de nouveaux utilisateurs. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ::: noteclassic La force du mot de passe de l'utilisateur est validée selon les règles de politique de mot de passe définies par l'API d'authentification. Voir l'[API d'authentification](/manual/api/reference/authentication) pour plus d'informations. ::: ### Description `object user.delete(array users)` This method allows to delete users. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object user.delete(array users)` Cette méthode permet de supprimer des utilisateurs. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usergroup.create(object/array userGroups)` This method allows to create new user groups. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usergroup.create(object/array userGroups)` Cette méthode permet de créer de nouveaux groupes d'utilisateurs. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usergroup.delete(array userGroupIds)` This method allows to delete user groups. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usergroup.delete(array userGroupIds)` Cette méthode permet de supprimer des groupes d'utilisateurs. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usergroup.update(object/array userGroups)` This method allows to update existing user groups. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usergroup.update(object/array userGroups)` Cette méthode permet de mettre à jour les groupes d'utilisateurs existants. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.createglobal(object/array globalMacros)` This method allows to create new global macros. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.createglobal(object/array globalMacros)` Cette méthode permet de créer de nouvelles macros globales. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.create(object/array hostMacros)` This method allows to create new host macros. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.create(object/array hostMacros)` Cette méthode permet de créer de nouvelles macros hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.delete(array hostMacroIds)` This method allows to delete host macros. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.delete(array hostMacroIds)` Cette méthode permet de supprimer les macros d'hôtes. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Admin* et *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.deleteglobal(array globalMacroIds)` This method allows to delete global macros. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.deleteglobal(array globalMacroIds)` Cette méthode permet de supprimer les macros globales. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.updateglobal(object/array globalMacros)` This method allows to update existing global macros. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.updateglobal(object/array globalMacros)` Cette méthode permet de mettre à jour les macros globales existantes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object usermacro.update(object/array hostMacros)` This method allows to update existing host macros. ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object usermacro.update(object/array hostMacros)` Cette méthode permet de mettre à jour les macros hôtes existantes. ::: noteclassic Cette méthode est disponible uniquement pour les types d'utilisateurs *Admin* et *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôles utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object user.unblock(array userids)` This method allows to unblock users. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object user.unblock(array userids)` Cette méthode permet de débloquer les utilisateurs. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object user.update(object/array users)` This method allows to update existing users. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ::: noteclassic The strength of user password is validated according the password policy rules defined by Authentication API. See [Authentication API](/manual/api/reference/authentication) for more information. ::: ### Description `object user.update(object/array users)` Cette méthode permet de mettre à jour les utilisateurs existants. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ::: noteclassic La force du mot de passe de l'utilisateur est validée selon les règles de politique de mot de passe définies par l'API d'authentification. Voir l'[API d'authentification](/manual/api/reference/authentication) pour plus d'informations. ::: ### Description `object valuemap.create(object/array valuemaps)` This method allows to create new value maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object valuemap.create(object/array valuemaps)` Cette méthode permet de créer de nouvelles correspondances de valeurs. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object valuemap.delete(array valuemapids)` This method allows to delete value maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object valuemap.delete(array valuemapids)` Cette méthode permet de supprimer des tables de correspondance. ::: noteclassic Cette méthode est disponible uniquement pour les utilisateurs de type *Super admin*. Les autorisations d'appel de la méthode peuvent être révoquées dans les réglages du rôle d'utilisateur. Voir les [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `object valuemap.update(object/array valuemaps)` This method allows to update existing value maps. ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `object valuemap.update(object/array valuemaps)` Cette méthode permet de mettre à jour les correspondances de valeurs existantes. ::: noteclassic Cette méthode est seulement disponible pour les utilisateurs du type *Super admin*. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle d'utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `string apiinfo.version(array)` This method allows to retrieve the version of the Zabbix API. ::: noteimportant This method is only available to unauthenticated users and must be called without the `auth` parameter in the JSON-RPC request. ::: ### Description `string apiinfo.version(array)` Cette méthode permet de récupérer la version de l'API Zabbix. ::: noteimportant Cette méthode n'est disponible que pour les utilisateurs non authentifiés et doit être appelée sans le paramètre "auth" dans la requête JSON-RPC. ::: ### Description `string configuration.export(object parameters)` This method allows to export configuration data as a serialized string. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `string configuration.export(paramètres d'objet)` Cette méthode permet d'exporter les données de configuration sous forme de chaîne sérialisée. ::: noteclassic Cette méthode est disponible pour les utilisateurs de tout type. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres de rôle utilisateur. Voir [Rôles utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ### Description `string/object user.login(object parameters)` This method allows to log in to the API and generate an authentication token. ::: notewarning When using this method, you also need to do [user.logout](/manual/api/reference/user/logout) to prevent the generation of a large number of open session records. ::: ::: noteimportant This method is only available to unauthenticated users and must be called without the `auth` parameter in the JSON-RPC request. ::: ### Description `string/object user.login(object parameters)` Cette méthode permet de se connecter à l'API et de générer un jeton d'authentification. ::: notewarning Lorsque vous utilisez cette méthode, vous devez également faire [user.logout](/manual/api/reference/user/logout) pour empêcher la génération d'un grand nombre d'enregistrements de session ouverts. ::: ::: noteimportant Cette méthode n'est disponible que pour les utilisateurs non authentifiés et doit être appelée sans le paramètre "auth" dans la requête JSON-RPC. ::: ### Description `string/object user.logout(array)` This method allows to log out of the API and invalidates the current authentication token. ::: noteclassic This method is available to users of any type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. ::: ### Description `string/object user.logout(array)` Cette méthode permet de se déconnecter de l'API et invalide le jeton d'authentification actuel. ::: noteclassic Cette méthode est disponible à tous les types d'utilisateurs. Les autorisations d'appeler la méthode peuvent être révoquées dans les paramètres du le rôle d'utilisateur. Voir [Rôles Utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) pour plus d'informations. ::: ## DESCRIPTION **zabbix\_agent2** is an application for monitoring parameters of various services.\ \ [ ]{#lbAE} ## DESCRIPTION **zabbix\_agent2** est une application de surveillance des paramètres de divers services.\ \ [ ]{#lbAE} ## DESCRIPTION **zabbix\_agentd** is a daemon for monitoring various server parameters. [ ]{#lbAE} ## DESCRIPTION **zabbix\_agentd** est un démon pour la surveillance de divers paramètres du serveur. [ ]{#lbAE} ## DESCRIPTION **zabbix\_get** is a command line utility for getting data from Zabbix agent. [ ]{#lbAE} ## DESCRIPTION **zabbix\_get** est un utilitaire de ligne de commande pour obtenir des données de l'agent Zabbix.[ ]{#lbAE} ## DESCRIPTION **zabbix\_js** is a command line utility that can be used for embedded script testing. [ ]{#lbAE} ## DESCRIPTION **zabbix\_js** est un utilitaire de ligne de commande qui peut être utilisé pour tester des scripts intégrés. [ ]{#lbAE} ## DESCRIPTION **zabbix\_proxy** is a daemon that collects monitoring data from devices and sends it to Zabbix server. [ ]{#lbAE} ## DESCRIPTION **zabbix\_proxy** est un démon qui collecte les données de surveillance des appareils et les envoie au serveur Zabbix. [ ]{#lbAE} ## DESCRIPTION **zabbix\_sender** is a command line utility for sending monitoring data to Zabbix server or proxy. On the Zabbix server an item of type **Zabbix trapper** should be created with corresponding key. Note that incoming values will only be accepted from hosts specified in **Allowed hosts** field for this item. [ ]{#lbAE} ## DESCRIPTION **zabbix\_sender** est un utilitaire de ligne de commande pour envoyer des données de surveillance au serveur ou au proxy Zabbix. Sur le serveur Zabbix, un élément de type **trappeur Zabbix** doit être créé avec la clé correspondante. Notez que les valeurs entrantes ne seront acceptées qu'à partir des hôtes spécifiés dans le champ **Hôtes autorisés** pour cet élément. [ ]{#lbAE} ## DESCRIPTION **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE} ## DESCRIPTION **zabbix\_server** est le démon principal du logiciel Zabbix. [ ]{#lbAE} ## DESCRIPTION **zabbix\_web\_service** is an application for providing web services to Zabbix components. [ ]{#lbAE} ## DESCRIPTION **zabbix\_web\_service** est une application permettant de fournir des services Web aux composants Zabbix. [ ]{#lbAE} #### Details about export - All supported elements are exported in one file. - Host and template entities (items, triggers, graphs, discovery rules) that are inherited from linked templates are not exported. Any changes made to those entities on a host level (such as changed item interval, modified regular expression or added prototypes to the low-level discovery rule) will be lost when exporting; when importing, all entities from linked templates are re-created as on the original linked template. - Entities created by low-level discovery and any entities depending on them are not exported. For example, a trigger created for an LLD-rule generated item will not be exported. #### Détails sur l'exportation - Tous les éléments pris en charge sont exportés dans un fichier. - Les entités d'hôte et de modèle (éléments, déclencheurs, graphiques, règles de découverte) héritées de modèles liés ne sont pas exportées. Toutes les modifications apportées à ces entités au niveau de l'hôte (telles que la modification de l'intervalle de l'élément, la modification de l''expression régulière ou les prototypes ajoutés à la règle de découverte de bas niveau) seront perdues lors de l'exportation. Lors de l'importation, toutes les entités des modèles liés sont recréées comme sur le modèle lié d'origine. - Les entités créées par la découverte de bas niveau et les entités qui en dépendent ne sont pas exportées. Par exemple, un déclencheur créé pour un élément généré par une règle LLD ne sera pas exporté. ### Details tag The details object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**version**<br>(required)|integer|SNMP interface version.<br><br>Possible values are:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|integer|Whether to use bulk SNMP requests.<br><br>Possible values are:<br>0 - don't use bulk requests;<br>1 - (default) - use bulk requests.| |community|string|SNMP community (required). Used only by SNMPv1 and SNMPv2 interfaces.| |securityname|string|SNMPv3 security name. Used only by SNMPv3 interfaces.| |securitylevel|integer|SNMPv3 security level. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - (default) - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |authpassphrase|string|SNMPv3 authentication passphrase. Used only by SNMPv3 interfaces.| |privpassphrase|string|SNMPv3 privacy passphrase. Used only by SNMPv3 interfaces.| |authprotocol|integer|SNMPv3 authentication protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - (default) - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |privprotocol|integer|SNMPv3 privacy protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - (default) - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |contextname|string|SNMPv3 context name. Used only by SNMPv3 interfaces.| ### Tag de détails L'objet détails a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**version**<br>(obligatoire)|integer|Version de l'interface SNMP.<br><br>Les valeurs possibles sont :<br>1 - SNMPv1 ;<br>2 - SNMPv2c ;<br>3 - SNMPv3| |bulk|integer|Utiliser ou non les requêtes SNMP en masse.<br><br>Les valeurs possibles sont :<br>0 - ne pas utiliser les requêtes en masse ;<br>1 - (par défaut) - utiliser les requêtes en masse.| |community|string|Communauté SNMP (obligatoire). Utilisé uniquement par les interfaces SNMPv1 et SNMPv2.| |securityname|string|Nom de sécurité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |securitylevel|integer|Niveau de sécurité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - (par défaut) - noAuthNoPriv ;<br>1 - authNoPriv ;<br>2 - authPriv.| |authpassphrase|string|Phrase secrète d'authentification SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |privpassphrase|string|Phrase secrète de confidentialité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| |authprotocol|integer|Protocole d'authentification SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - (par défaut) - MD5 ;<br>1 - SHA1 ;<br>2 - SHA224 ;<br>3 - SHA256 ;<br >4 - SHA384 ;<br>5 - SHA512.| |privprotocol|integer|Protocole de confidentialité SNMPv3. Utilisé uniquement par les interfaces SNMPv3.<br><br>Les valeurs possibles sont :<br>0 - (par défaut) - DES ;<br>1 - AES128 ;<br>2 - AES192 ;<br>3 - AES256 ;<br >4 - AES192C ;<br>5 - AES256C.| |contextname|string|nom de contexte SNMPv3. Utilisé uniquement par les interfaces SNMPv3.| #### Details The virtual machine monitoring is done in two steps. First, virtual machine data is gathered by *vmware collector* Zabbix processes. Those processes obtain necessary information from VMware web services over the SOAP protocol, pre-process it and store into Zabbix server shared memory. Then, this data is retrieved by pollers using Zabbix simple check [VMware keys](/manual/config/items/itemtypes/simple_checks/vmware_keys). Starting with Zabbix version 2.4.4 the collected data is divided into 2 types: VMware configuration data and VMware performance counter data. Both types are collected independently by *vmware collectors*. Because of this it is recommended to enable more collectors than the monitored VMware services. Otherwise retrieval of VMware performance counter statistics might be delayed by the retrieval of VMware configuration data (which takes a while for large installations). Currently only datastore, network interface and disk device statistics and custom performance counter items are based on the VMware performance counter information. #### Détails La supervision de la machine virtuelle s'effectue en deux étapes. Premièrement, les données de la machine virtuelle sont collectées par les processus Zabbix *vmware collector*. Ces processus obtiennent les informations nécessaires auprès des services Web VMware via le protocole SOAP, les traitent préalablement et les stockent dans la mémoire partagée du serveur Zabbix. Ces informations sont ensuite récupérées par les pollers à l'aide des [clés VMware](/manual/config/items/itemtypes/simple_checks/vmware_keys) des vérifications simples de Zabbix. À partir de la version 2.4.4 de Zabbix, les données collectées sont divisées en 2 types : les données de configuration VMware et les données de compteurs de performance VMware. Les deux types sont collectés indépendamment par les *collecteurs vmware*. Pour cette raison, il est recommandé d'activer plus de collecteurs que les services VMware surveillés. Sinon, la récupération des statistiques de compteurs de performance VMware pourrait être retardée par la récupération des données de configuration VMware (ce qui prend un certain temps pour les installations de grande taille). Actuellement, seules les statistiques de banque de données, d'interface réseau et de périphérique de disque, ainsi que les éléments de compteur de performance personnalisés sont basés sur les informations du compteur de performance VMware. #### Developing modules Modules are written in PHP language. Model-view-controller (MVC) software pattern design is preferred, as it is also used in Zabbix frontend and will ease the development. PHP strict typing is also welcome but not mandatory. Please note that with modules you can easily add new menu items and respective views and actions to Zabbix frontend. Currently it is not possible to register new API or create new database tables through modules. #### Développer des modules Les modules sont écrits en langage PHP. La conception de modèles logiciels modèle-vue-contrôleur (MVC) est préférée, car elle est également utilisée dans l'interface Zabbix et facilitera le développement. Le typage PHP strict est également le bienvenu mais pas obligatoire. Veuillez noter qu'avec les modules, vous pouvez facilement ajouter de nouveaux éléments de menu et des vues et actions respectives à l'interface Zabbix. Actuellement, il n'est pas possible d'enregistrer une nouvelle API ou de créer de nouvelles tables de base de données via des modules. # dhost.get # dhost.get ### 'Diagnostic information' request object The diagnostic information task request object has the following properties. Statistic request object for all types of properties is [described in detail below](/manual/api/reference/task/object#statistic_request_object). |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |historycache|object|History cache statistic request. Available on server and proxy.| |valuecache|object|Items cache statistic request. Available on server.| |preprocessing|object|Preprocessing manager statistic request. Available on server and proxy.| |alerting|object|Alert manager statistic request. Available on server.| |lld|object|LLD manager statistic request. Available on server.| ### Objet de requête 'Informations de diagnostic' L'objet de demande de tâche d'informations de diagnostic a les propriétés suivantes. L'objet de requête statistique pour tous les types de propriétés est [décrit en détail ci-dessous](/manual/api/reference/task/object#statistic_request_object). |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |historycache|object|Demande de statistiques de cache d'historique. Disponible sur serveur et proxy.| |valuecache|object|Requête de statistiques de cache d'éléments. Disponible sur serveur.| |preprocessing|object|Requête de statistiques du gestionnaire de prétraitement. Disponible sur serveur et proxy.| |alerting|object|Demande de statistiques du gestionnaire d'alertes. Disponible sur serveur.| |lld|object|Requête de statistiques du gestionnaire LLD. Disponible sur serveur.| #### Disable action Disable action, that is, set its status to "1". Request: ``` {.java} { "jsonrpc": "2.0", "method": "action.update", "params": { "actionid": "2", "status": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "2" ] }, "id": 1 } ``` #### Désactiver l'action Désactive l'action, c'est-à-dire définir son statut sur "1". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "action.update", "params": { "actionid": "2", "status": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "actionids": [ "2" ] }, "id": 1 } ``` #### Disable correlation Request: ``` {.java} { "jsonrpc": "2.0", "method": "correlation.update", "params": { "correlationid": "1", "status": "1" }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Désactivation d'une corrélation Requête : ``` {.java} { "jsonrpc": "2.0", "method": "correlation.update", "params": { "correlationid": "1", "status": "1" }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Disable trapping Disable LLD trapping for discovery rule. Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "28336", "allow_traps": "0" }, "id": 36, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "28336" ] }, "id": 36 } ``` #### Désactivation des traps Désactiver les traps d'une règle Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.update", "params": { "itemid": "28336", "allow_traps": "0" }, "id": 36, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "itemids": [ "28336" ] }, "id": 36 } ``` #### Disabling ability to execute scripts Update role with ID "5", disable ability to execute scripts. Request: ```json { "jsonrpc": "2.0", "method": "role.update", "params": [ { "roleid": "5", "rules": { "actions": [ { "name": "execute_scripts", "status": "0" } ] } } ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` #### Désactivation de la possibilité d'exécuter des scripts Mettre à jour le rôle avec l'ID "5", désactiver la possibilité d'exécuter des scripts. Requête : ```json { "jsonrpc": "2.0", "method": "role.update", "params": [ { "roleid": "5", "rules": { "actions": [ { "name": "execute_scripts", "status": "0" } ] } } ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` #### Disabling a host prototype Disable a host prototype, that is, set its status to 1. Request: ```json { "jsonrpc": "2.0", "method": "hostprototype.update", "params": { "hostid": "10092", "status": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10092" ] }, "id": 1 } ``` #### Désactivation d'un prototype d'hôte Désactivez un prototype d'hôte, c'est-à-dire définissez son statut sur 1. Requête : ```json { "jsonrpc": "2.0", "method": "hostprototype.update", "params": { "hostid": "10092", "status": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10092" ] }, "id": 1 } ``` #### Disabling a user group Disable a user group. Request: ```json { "jsonrpc": "2.0", "method": "usergroup.update", "params": { "usrgrpid": "17", "users_status": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "usrgrpids": [ "17" ] }, "id": 1 } ``` #### Désactivation d'un groupe d'utilisateurs Désactiver un groupe d'utilisateurs. Requête : ```json { "jsonrpc": "2.0", "method": "usergroup.update", "params": { "usrgrpid": "17", "users_status": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "usrgrpids": [ "17" ] }, "id": 1 } ``` #### Disabling default web server error pages It is recommended to disable default error pages to avoid information exposure. Web server is using built-in error pages by default:  Default error pages should be replaced/removed as part of the web server hardening process. The "ErrorDocument" directive can be used to define a custom error page/text for Apache web server (used as an example). Please refer to documentation of your web server to find help on how to replace/remove default error pages. #### Désactivation des pages d'erreur du serveur Web par défaut Il est recommandé de désactiver les pages d'erreur par défaut pour éviter l'exposition d'informations. Le serveur Web utilise par défaut les pages d'erreur intégrées :  Les pages d'erreur par défaut doivent être remplacées/supprimées dans le cadre du processus de renforcement du serveur Web. La directive "ErrorDocument" peut être utilisée pour définir une page/un texte d'erreur personnalisé pour le serveur Web Apache (utilisé comme exemple). Veuillez vous référer à la documentation de votre serveur Web pour trouver de l'aide sur la façon de remplacer/supprimer les pages d'erreur par défaut. ### Disabling high availability To disable a high availability cluster: - make backup copies of configuration files - stop standby nodes - remove the HANodeName parameter from the active primary server - restart the primary server (it will start in standalone mode) ### Désactivation de la haute disponibilité Pour désactiver un cluster haute disponibilité : - faire des copies de sauvegarde des fichiers de configuration - arrêter les nœuds de secours - supprimer le paramètre HANodeName du serveur principal actif - redémarrer le serveur principal (il démarrera en mode autonome) #### Disabling scheduled report Request: ```json { "jsonrpc": "2.0", "method": "report.update", "params": { "reportid": "1", "status": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "reportids": [ "1" ] }, "id": 1 } ``` #### Désactivation du rapport programmé Requête : ```json { "jsonrpc": "2.0", "method": "report.update", "params": { "reportid": "1", "status": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "reportids": [ "1" ] }, "id": 1 } ``` #### Discovered entities When server runs, it will create real items, triggers and graphs based on the values the SNMP discovery rule returns. In the host configuration they are prefixed with an orange link to a discovery rule they come from. {width="600"} {width="600"} {width="600"} #### Entités découvertes Lorsque le serveur s'exécute, il crée des éléments réels, des déclencheurs et des graphiques en fonction des valeurs renvoyées par la règle de découverte SNMP. Dans la configuration de l'hôte, ils sont précédés d'un lien orange vers une règle de découverte d'origine. {width="600"} {width="600"} {width="600"} ### Discovered host ::: noteclassic Discovered host are created by the Zabbix server and cannot be modified via the API. ::: The discovered host object contains information about a host discovered by a network discovery rule. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |dhostid|string|ID of the discovered host.| |druleid|string|ID of the discovery rule that detected the host.| |lastdown|timestamp|Time when the discovered host last went down.| |lastup|timestamp|Time when the discovered host last went up.| |status|integer|Whether the discovered host is up or down. A host is up if it has at least one active discovered service.<br><br>Possible values:<br>0 - host up;<br>1 - host down.| ### Hôte découvert ::: noteclassic Les hôtes découverts sont créés par le serveur Zabbix et ne peuvent pas être modifiés via l'API. ::: L'objet hôte découvert contient des informations sur un hôte découvert par une règle de découverte du réseau. Il a les propriétés suivantes. | Propriété | [Type](/manual/api/reference_commentary#data_types)| Description | | --- | --- | --- | | dhostid | string | ID l'hôte découvert. | | druleid | string | ID de la règle de découverte qui a détecté l'hôte. | | lastdown | timestamp | Heure à laquelle l'hôte découvert a été injoignable pour la dernière fois. | | lastup | timestamp | Heure à laquelle l'hôte découvert a été joignable pour la dernière fois. | | status | integer | Indique si l'hôte découvert est actif ou non. Un hôte est actif s'il possède au moins un service découvert actif.<br><br>Valeurs possibles :<br>0 - hôte joignable ;<br>1 - hôte injoignable. | ### Discovered service ::: noteclassic Discovered services are created by the Zabbix server and cannot be modified via the API. ::: The discovered service object contains information about a service discovered by a network discovery rule on a host. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dserviceid|string|ID of the discovered service.| |dcheckid|string|ID of the discovery check used to detect the service.| |dhostid|string|ID of the discovered host running the service.| |dns|string|DNS of the host running the service.| |ip|string|IP address of the host running the service.| |lastdown|timestamp|Time when the discovered service last went down.| |lastup|timestamp|Time when the discovered service last went up.| |port|integer|Service port number.| |status|integer|Status of the service.<br><br>Possible values:<br>0 - service up;<br>1 - service down.| |value|string|Value returned by the service when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.| ### Service découvert ::: noteclassic Les services découverts sont créés par le serveur Zabbix et ne peuvent pas être modifiés via l'API. ::: L'objet service découvert contient des informations sur un service découvert par une règle de découverte de réseau sur un hôte. Il a les propriétés suivantes. |Propriété|Type|Description| --|--|------| |dserviceid|string|ID du service découvert.| |dcheckid|string|ID du test de découverte utilisé pour détecter le service.| |dhostid|string|ID de l'hôte découvert exécutant le service.| |dns|string|Nom DNS de l'hôte exécutant le service.| |ip|string|Adresse IP de l'hôte exécutant le service.| |lastdown|timestamp|Heure à laquelle le service découvert était inactif la dernière fois.| |lastup|timestamp|Heure à laquelle le service découvert était actif la dernière fois.| |port|integer|Numéro de port du service.| |status|integer|Statut du service.<br><br>Valeurs possibles :<br>0 - service actif ;<br>1 - service inactif.| |value|string|Valeur renvoyée par le service lors d'un test de découverte agent Zabbix, SNMPv1, SNMPv2 ou SNMPv3.| ##### Discovering MBean attributes Discovery item: `jmx.get[attributes,"com.example:type=*,*"]` Response: ``` {.json} [ { "object": "com.example:type=*", "domain": "com.example", "properties": { "type": "Simple" } }, { "object": "com.zabbix:type=yes,domain=zabbix.com,data-source=/dev/rand,ключ=значение,obj=true", "domain": "com.zabbix", "properties": { "type": "Hello", "domain": "com.example", "data-source": "/dev/rand", "ключ": "значение", "obj": true } } ] ``` ##### Découvrir les attributs MBean Elément de découverte : `jmx.get[attributes,"com.example:type=*,*"]` Réponse : ``` {.json} [ { "object": "com.example:type=*", "domain": "com.example", "properties": { "type": "Simple" } }, { "object": "com.zabbix:type=yes,domain=zabbix.com,data-source=/dev/rand,ключ=значение,obj=true", "domain": "com.zabbix", "properties": { "type": "Hello", "domain": "com.example", "data-source": "/dev/rand", "ключ": "значение", "obj": true } } ] ``` ##### Discovering MBeans Discovery item: `jmx.get[beans,"com.example:type=*,*"]` Response: ``` {.json} [ { "object": "com.example:type=Hello,data-src=data-base,ключ=значение", "domain": "com.example", "properties": { "data-src": "data-base", "ключ": "значение", "type": "Hello" } }, { "object": "com.example:type=Atomic", "domain": "com.example", "properties": { "type": "Atomic" } } ] ``` ##### Découvrir les MBeans Elément de découverte : `jmx.get[beans,"com.example:type=*,*"]` Réponse : ``` {.json} [ { "object": "com.example:type=Hello,data-src=data-base,ключ=значение", "domain": "com.example", "properties": { "data-src": "data-base", "ключ": "значение", "type": "Hello" } }, { "object": "com.example:type=Atomic", "domain": "com.example", "properties": { "type": "Atomic" } } ] ``` #### Discovery actions The following conditions can be used in discovery-based events: |Condition type|Supported operators|Description| |--|--|------| |*Host IP*|equals<br>does not equal|Specify an IP address range or a range to exclude for a discovered host.<br>**equals** - host IP is in the range.<br>**does not equal** - host IP is not in the range.<br>It may have the following formats:<br>Single IP: 192.168.1.33<br>Range of IP addresses: 192.168.1-10.1-254<br>IP mask: 192.168.4.0/24<br>List: 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>Support for spaces in the list format is provided since Zabbix 3.0.0.| |*Service type*|equals<br>does not equal|Specify a service type of a discovered service or a service type to exclude.<br>**equals** - matches the discovered service.<br>**does not equal** - does not match the discovered service.<br>Available service types: SSH, LDAP, SMTP, FTP, HTTP, HTTPS *(available since Zabbix 2.2 version)*, POP, NNTP, IMAP, TCP, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping, telnet *(available since Zabbix 2.2 version)*.| |*Service port*|equals<br>does not equal|Specify a TCP port range of a discovered service or a range to exclude.<br>**equals** - service port is in the range.<br>**does not equal** - service port is not in the range.| |*Discovery rule*|equals<br>does not equal|Specify a discovery rule or a discovery rule to exclude.<br>**equals** - using this discovery rule.<br>**does not equal** - using any other discovery rule, except this one.| |*Discovery check*|equals<br>does not equal|Specify a discovery check or a discovery check to exclude.<br>**equals** - using this discovery check.<br>**does not equal** - using any other discovery check, except this one.| |*Discovery object*|equals|Specify the discovered object.<br>**equals** - equal to discovered object (a device or a service).| |*Discovery status*|equals|**Up** - matches 'Host Up' and 'Service Up' events<br>**Down** - matches 'Host Down' and 'Service Down' events<br>**Discovered** - matches 'Host Discovered' and 'Service Discovered' events<br>**Lost** - matches 'Host Lost' and 'Service Lost' events| |*Uptime/Downtime*|is greater than or equals<br>is less than or equals|Uptime for 'Host Up' and 'Service Up' events. Downtime for 'Host Down' and 'Service Down' events.<br>**is greater than or equals** - is more or equal to. Parameter is given in seconds.<br>**is less than or equals** - is less or equal to. Parameter is given in seconds.| |*Received value*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals<br>contains<br>does not contain|Specify the value received from an agent (Zabbix, SNMP) check in a discovery rule. String comparison. If several Zabbix agent or SNMP checks are configured for a rule, received values for each of them are checked (each check generates a new event which is matched against all conditions).<br>**equals** - equal to the value.<br>**does not equal** - not equal to the value.<br>**is greater than or equals** - more or equal to the value.<br>**is less than or equals** - less or equal to the value.<br>**contains** - contains the substring. Parameter is given as a string.<br>**does not contain** - does not contain the substring. Parameter is given as a string.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.| ::: noteclassic Service checks in a discovery rule, which result in discovery events, do not take place simultaneously. Therefore, if **multiple** values are configured for `Service type`, `Service port` or `Received value` conditions in the action, they will be compared to one discovery event at a time, but **not** to several events simultaneously. As a result, actions with multiple values for the same check types may not be executed correctly. ::: #### Actions de découverte Les conditions suivantes peuvent être utilisées dans les événements basés sur la découverte : |Type de condition|Opérateurs pris en charge|Description| |--|--|------| |*IP hôte*|égal<br>n'est pas égal|Spécifiez une plage d'adresses IP ou une plage à exclure pour un hôte découvert.<br>**égal** - l'adresse IP de l'hôte est dans la plage.<br>** n'est pas égal** - l'IP de l'hôte n'est pas dans la plage.<br>Il peut avoir les formats suivants :<br>IP unique : 192.168.1.33<br>Plage d'adresses IP : 192.168.1-10.1-254<br >Masque IP : 192.168.4.0/24<br>Liste : 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>La prise en charge des espaces dans le format de liste est fournie depuis Zabbix 3.0 .0.| |*Type de service*|égal<br>n'est pas égal|Spécifiez un type de service d'un service découvert ou un type de service à exclure.<br>**égal** - correspond au service découvert.<br>**n'est pas égal** - ne correspond pas au service découvert.<br>Types de services disponibles : SSH, LDAP, SMTP, FTP, HTTP, HTTPS *(disponible depuis la version Zabbix 2.2)*, POP, NNTP, IMAP, TCP, agent Zabbix, Agent SNMPv1, agent SNMPv2, agent SNMPv3, ping ICMP, telnet *(disponible depuis la version Zabbix 2.2)*.| |*Port de service*|égal<br>n'est pas égal|Spécifiez une plage de ports TCP d'un service découvert ou une plage à exclure.<br>**égal** - le port de service est dans la plage.<br>**n'est pas égal** - le port de service n'est pas dans la plage.| |*Règle de découverte*|égal<br>n'est pas égal|Spécifiez une règle de découverte ou une règle de découverte à exclure.<br>**égal** - en utilisant cette règle de découverte.<br>**n'est pas égal** - en utilisant n'importe quelle autre règle de découverte, sauf celle-ci.| |*Test de découverte*|égal<br>n'est pas égal|Spécifiez une vérification de découverte ou une vérification de découverte à exclure.<br>**égal** - en utilisant cette vérification de découverte.<br>**n'est pas égal** - en utilisant n'importe quel autre contrôle de découverte, sauf celui-ci.| |*Objet de découverte*|égal|Spécifiez l'objet découvert.<br>**égal** - égal à l'objet découvert (un appareil ou un service).| |*État de la découverte*|égal|**Fonctionne** - correspond aux événements 'Hôte fonctionne' et 'Service fonctionne'<br>**Arrête** - correspond aux événements 'Hôte arrêté' et 'Service arrêté'<br>** Découvert** - correspond aux événements 'Hôte découvert' et 'Service découvert'<br>**Perdu** - correspond aux événements 'Hôte perdu' et 'Service perdu'| |*Fonctionnement/Arrêt*|est supérieur ou égal<br>est inférieur ou égal|Uptime pour les événements 'Hôte fonctionne' et 'Service fonctionne'. Temps d'arrêt pour les événements 'Host Down' et 'Service Down'.<br>**est supérieur ou égal à** - est supérieur ou égal à. Le paramètre est donné en secondes.<br>**est inférieur ou égal à** - est inférieur ou égal à. Le paramètre est donné en secondes.| |*Valeur reçue*|égal<br>n'est pas égal<br>est supérieur ou égal à<br>est inférieur ou égal à<br>contient<br>ne contient pas|Spécifiez la valeur reçue d'un agent (Zabbix, SNMP) vérifient une règle de découverte. Comparaison de chaînes. Si plusieurs agents Zabbix ou contrôles SNMP sont configurés pour une règle, les valeurs reçues pour chacun d'eux sont vérifiées (chaque contrôle génère un nouvel événement qui correspond à toutes les conditions).<br>**égal** - égal à la valeur. <br>**n'est pas égal** - n'est pas égal à la valeur.<br>**est supérieur ou égal à** - supérieur ou égal à la valeur.<br>**est inférieur ou égal à** - inférieur ou égal à la valeur.<br>**contient** - contient la sous-chaîne. Le paramètre est donné sous forme de chaîne.<br>**ne contient pas** - ne contient pas la sous-chaîne. Le paramètre est donné sous forme de chaîne.| |*Proxy*|égal<br>n'est pas égal|Spécifiez un proxy ou un proxy à exclure.<br>**égal** - en utilisant ce proxy.<br>**n'est pas égal** - en utilisant un autre proxy sauf celui-ci.| ::: noteclassic Les vérifications de service dans une règle de découverte, qui entraînent des événements de découverte, n'ont pas lieu simultanément. Par conséquent, si **plusieurs** valeurs sont configurées pour les conditions `Type de service`, `Port de service` ou `Valeur reçue` dans l'action, elles seront comparées à un événement de découverte à la fois, mais **pas** à plusieurs événements simultanément. Par conséquent, les actions avec plusieurs valeurs pour les mêmes types de contrôle peuvent ne pas être exécutées correctement. ::: ### Discovery check The discovery check object defines a specific check performed by a network discovery rule. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dcheckid|string|*(readonly)* ID of the discovery check.| |druleid|string|*(readonly)* ID of the discovery rule that the check belongs to.| |key\_|string|The value of this property differs depending on the type of the check:<br>- key to query for Zabbix agent checks, required;<br>- SNMP OID for SNMPv1, SNMPv2 and SNMPv3 checks, required.| |ports|string|One or several port ranges to check separated by commas. Used for all checks except for ICMP.<br><br>Default: 0.| |snmp\_community|string|SNMP community.<br><br>Required for SNMPv1 and SNMPv2 agent checks.| |snmpv3\_authpassphrase|string|Authentication passphrase used for SNMPv3 agent checks with security level set to *authNoPriv* or *authPriv*.| |snmpv3\_authprotocol|integer|Authentication protocol used for SNMPv3 agent checks with security level set to *authNoPriv* or *authPriv*.<br><br>Possible values:<br>0 - *(default)* MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |snmpv3\_contextname|string|SNMPv3 context name. Used only by SNMPv3 checks.| |snmpv3\_privpassphrase|string|Privacy passphrase used for SNMPv3 agent checks with security level set to *authPriv*.| |snmpv3\_privprotocol|integer|Privacy protocol used for SNMPv3 agent checks with security level set to *authPriv*.<br><br>Possible values:<br>0 - *(default)* DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |snmpv3\_securitylevel|string|Security level used for SNMPv3 agent checks.<br><br>Possible values:<br>0 - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |snmpv3\_securityname|string|Security name used for SNMPv3 agent checks.| |**type**<br>(required)|integer|Type of check.<br><br>Possible values:<br>0 - SSH;<br>1 - LDAP;<br>2 - SMTP;<br>3 - FTP;<br>4 - HTTP;<br>5 - POP;<br>6 - NNTP;<br>7 - IMAP;<br>8 - TCP;<br>9 - Zabbix agent;<br>10 - SNMPv1 agent;<br>11 - SNMPv2 agent;<br>12 - ICMP ping;<br>13 - SNMPv3 agent;<br>14 - HTTPS;<br>15 - Telnet.| |uniq|integer|Whether to use this check as a device uniqueness criteria. Only a single unique check can be configured for a discovery rule. Used for Zabbix agent, SNMPv1, SNMPv2 and SNMPv3 agent checks.<br><br>Possible values:<br>0 - *(default)* do not use this check as a uniqueness criteria;<br>1 - use this check as a uniqueness criteria.| |host\_source|integer|Source for host name.<br><br>Possible values:<br>1 - *(default)* DNS;<br>2 - IP;<br>3 - discovery value of this check.| |name\_source|integer|Source for visible name.<br><br>Possible values:<br>0 - *(default)* not specified;<br>1 - DNS;<br>2 - IP;<br>3 - discovery value of this check.| ### Test de découverte L'objet test de découverte définit une vérification spécifique effectuée par une règle de découverte du réseau. Il a les propriétés suivantes. | Propriété | [Type](/manual/api/reference_commentary#data_types)| Description | |--------|---------------------------------------------------|-----------| | dcheckid | string | *(lecture seule)* ID du test de découverte. | | druleid | string | *(lecture seule)* ID de la règle de découverte à laquelle le test appartient. | | key_ | string | La valeur de cette propriété diffère selon le type de test :<br>- clé pour interroger les tests d'agent Zabbix, obligatoire ;<br>- SNMP OID pour les tests SNMPv1, SNMPv2 et SNMPv3, obligatoire. | | ports | string | Une ou plusieurs plages de ports à vérifier, séparées par des virgules. Utilisé pour toutes les vérifications sauf ICMP.<br><br>Par défaut : 0. | | snmp_community | string | Communauté SNMP.<br><br>Obligatoire pour les vérifications d'agent SNMPv1 et SNMPv2. | | snmpv3_authpassphrase | string | Phrase secrète Auth utilisée pour les vérifications d'agent SNMPv3 avec un niveau de sécurité défini sur *authNoPriv* ou *authPriv*. | | snmpv3_authprotocol | integer | Protocole d'authentification utilisé pour les vérifications d'agent SNMPv3 avec un niveau de sécurité défini sur *authNoPriv* ou *authPriv*.<br><br>Valeurs possibles :<br>0 - *(par défaut)* MD5 ;1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512. | | snmpv3_contextname | string | Nom du contexte SNMPv3. Utilisé uniquement par les vérifications SNMPv3. | | snmpv3_privpassphrase | string | Phrase secrète Priv utilisée pour les vérifications d'agent SNMPv3 avec un niveau de sécurité défini sur *authPriv*. | | snmpv3_privprotocol | integer | Protocole de confidentialité utilisé pour les vérifications d'agent SNMPv3 avec un niveau de sécurité défini sur *authPriv*.<br><br>Valeurs possibles :<br>0 - *(par défaut)* DES ;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C. | | snmpv3_securitylevel | string | Niveau de sécurité utilisé pour les vérifications d'agent SNMPv3.<br><br>Valeurs possibles :<br>0 - noAuthNoPriv ;<br>1 - authNoPriv ;<br>2 - authPriv. | | snmpv3_securityname | string | Nom de sécurité utilisé pour les vérifications d'agent SNMPv3. | | **type**<br>(obligatoire) | integer | Type de vérifications.<br><br>Valeurs possibles :<br>0 - SSH ;<br>1 - LDAP ;<br>2 - SMTP ;<br>3 - FTP ;<br>4 - HTTP ;<br>5 - POP ;<br>6 - NNTP ;<br>7 - IMAP ;<br>8 - TCP ;<br>9 - agent Zabbix ;<br>10 - agent SNMPv1 ;<br>11 - agent SNMPv2 ;<br>12 - ping ICMP ;<br>13 - agent SNMPv3 ;<br>14 - HTTPS ;<br>15 - Telnet. | | uniq | integer | Indique s'il faut utiliser cette vérification comme critère d'unicité du périphérique. Une seule vérification unique peut être configurée par règle de découverte. Utilisé pour les vérifications d'agent Zabbix, SNMPv1, SNMPv2 et SNMPv3.<br><br>Valeurs possibles :<br>0 - *(par défaut)* ne pas utiliser cette vérification comme critère d'unicité ;<br>1 - utiliser cette vérification comme critère d'unicité. | | host_source | integer | Source for host name.<br><br>Possible values:<br>1 - *(default)* DNS;<br>2 - IP;<br>3 - discovery value of this check. | | name_source | integer | Source for visible name.<br><br>Possible values:<br>0 - *(default)* not specified;<br>1 - DNS;<br>2 - IP;<br>3 - discovery value of this check. | #### Discovery events Zabbix periodically scans the IP ranges defined in network discovery rules. Frequency of the check is configurable for each rule individually. Once a host or a service is discovered, a discovery event (or several events) are generated. Zabbix generates the following events: |Event|When generated| |--|--------| |Service Up|Every time Zabbix detects active service.| |Service Down|Every time Zabbix cannot detect service.| |Host Up|If at least one of the services is UP for the IP.| |Host Down|If all services are not responding.| |Service Discovered|If the service is back after downtime or discovered for the first time.| |Service Lost|If the service is lost after being up.| |Host Discovered|If host is back after downtime or discovered for the first time.| |Host Lost|If host is lost after being up.| #### Événements de découverte Zabbix analyse périodiquement les plages IP définies dans les règles de découverte du réseau. La fréquence de la vérification est configurable pour chaque règle individuellement. Une fois qu'un hôte ou un service est découvert, un événement de découverte (ou plusieurs événements) est généré. Zabbix génère les événements suivants : |Événement|Généré quand| |--|--------| |Service Up|Chaque fois que Zabbix détecte un service actif.| |Service Down|Chaque fois que Zabbix ne peut pas détecter le service.| |Hôte Up|Si au moins un des services est UP pour l'IP.| |Hôte Down|Si tous les services ne répondent pas.| |Service découvert|Si le service est de retour après un temps d'arrêt ou découvert pour la première fois.| |Service perdu|Si le service est perdu après avoir été activé.| |Hôte découvert|Si l'hôte est de retour après un temps d'arrêt ou découvert pour la première fois.| |Hôte perdu|Si l'hôte est perdu après avoir été activé.| ### Discovery of disabled systemd units It is now also possible to discover **disabled** systemd units using the *systemd.unit.discovery* item key, supported by Zabbix agent 2. Note that to have items and triggers created from prototypes for disabled systemd units, it may be necessary to adjust (or remove) prohibiting LLD filters for the {#UNIT.ACTIVESTATE} and {#UNIT.UNITFILESTATE} macros. For more details, see [Discovery of systemd services](/manual/discovery/low_level_discovery/examples/systemd). ### Découverte des unités systemd désactivées Il est désormais également possible de découvrir les unités systemd **désactivées** à l'aide de la clé d'élément *systemd.unit.discovery*, pris en charge par l'agent Zabbix 2. Notez que pour avoir des éléments et des déclencheurs créés à partir de prototypes pour les unités systemd désactivées, il peut être nécessaire d'ajuster (ou de supprimer) les filtres LLD d'interdiction pour les macros {#UNIT.ACTIVESTATE} et {#UNIT.UNITFILESTATE}. Pour plus de détails, voir [Découverte des services systemd](/manual/discovery/low_level_discovery/examples/systemd). ##### Discovery of disabled systemd units Since Zabbix 6.0.1 it is also possible to discover **disabled** systemd units. In this case three macros are returned in the resulting JSON: - {#UNIT.PATH} - {#UNIT.ACTIVESTATE} - {#UNIT.UNITFILESTATE}. ::: noteimportant To have items and triggers created from prototypes for disabled systemd units, make sure to adjust (or remove) prohibiting LLD filters for {#UNIT.ACTIVESTATE} and {#UNIT.UNITFILESTATE}. ::: ##### Découverte des unités systemd désactivées Depuis Zabbix 6.0.1, il est également possible de découvrir les unités systemd **désactivées**. Dans ce cas, trois macros sont renvoyées dans le JSON résultant : - {#UNIT.PATH} - {#UNIT.ACTIVESTATE} - {#UNIT.UNITFILESTATE}. ::: noteimportant Pour que des éléments et des déclencheurs soient créés à partir de prototypes pour les unités systemd désactivées, assurez-vous d'ajuster (ou de supprimer) les filtres LLD interdisant pour {#UNIT.ACTIVESTATE} et {#UNIT.UNITFILESTATE}. ::: # discoveryrule.copy # discoveryrule.copy # discoveryrule.create # discoveryrule.create # discoveryrule.delete # discoveryrule.delete # discoveryrule.get # discoveryrule.get ### Discovery rule The discovery rule object defines a network discovery rule. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |druleid|string|*(readonly)* ID of the discovery rule.| |**iprange**<br>(required)|string|One or several IP ranges to check separated by commas.<br><br>Refer to the [network discovery configuration](/manual/discovery/network_discovery/rule) section for more information on supported formats of IP ranges.| |**name**<br>(required)|string|Name of the discovery rule.| |delay|string|Execution interval of the discovery rule. Accepts seconds, time unit with suffix and user macro.<br><br>Default: 1h.| |nextcheck|timestamp|*(readonly)* Time when the discovery rule will be executed next.| |proxy\_hostid|string|ID of the proxy used for discovery.| |status|integer|Whether the discovery rule is enabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Règle de découverte L'objet de règle de découverte définit une règle de découverte du réseau. Il a les propriétés suivantes. |Proptiété|Type|Description| |--|--|------| |druleid|string|*(lecture seule)* ID de la règle de découverte.| |**iprange**<br>(obligatoire)|string|Une ou plusieurs plages IP à vérifier, séparées par des virgules.<br><br>Se référer à la section de [configuration d'une règle de découverte du réseau](/manual/discovery/network_discovery/rule) pour plus d'informations sur les formats de plages IP supportés.| |**name**<br>(obligatoire)|string|Nom de la règle de découverte.| |delay|string|Intervalle d'exécution de la règle de découverte. Accepte les secondes, les unités de temps avec suffixe et les macros utilisateur.<br><br>Par défaut : 1h.| |nextcheck|timestamp|*(lecture seule)* Heure à laquelle la règle de découverte sera exécutée la prochaine fois.| |proxy\_hostid|string|ID du proxy utilisé pour la découverte.| |status|integer|Indique si la règle de découverte est activée.<br><br>Valeurs possibles :<br>0 - *(par défaut)* activée ;<br>1 - désactivée.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # discoveryrule.update # discoveryrule.update #### Discovery Zabbix can use a low-level discovery rule to automatically discover VMware hypervisors and virtual machines.  All mandatory input fields are marked with a red asterisk. The discovery rule key in the above screenshot is *vmware.hv.discovery\[{$VMWARE.URL}\]*. #### Découverte Zabbix peut utiliser une règle de découverte de bas niveau pour découvrir automatiquement les hyperviseurs VMware et les machines virtuelles.  Tous les champs obligatoires sont marqués par un astérisque rouge. La clé de la règle de découverte dans la capture d'écran ci-dessus est *vmware.hv.discovery\[{$VMWARE.URL}\]* #### Discovery Zabbix periodically scans the IP ranges defined in [network discovery rules](/manual/discovery/network_discovery/rule). The frequency of the check is configurable for each rule individually. Note that one discovery rule will always be processed by a single discoverer process. The IP range will not be split between multiple discoverer processes. Each rule has a set of service checks defined to be performed for the IP range. ::: noteclassic Discovery checks are processed independently from the other checks. If any checks do not find a service (or fail), other checks will still be processed. ::: Every check of a service and a host (IP) performed by the network discovery module generates a discovery event. |Event|Check of service result| |--|--------| |*Service Discovered*|The service is 'up' after it was 'down' or when discovered for the first time.| |*Service Up*|The service is 'up', after it was already 'up'.| |*Service Lost*|The service is 'down' after it was 'up'.| |*Service Down*|The service is 'down', after it was already 'down'.| |*Host Discovered*|At least one service of a host is 'up' after all services of that host were 'down' or a service is discovered which belongs to a not registered host.| |*Host Up*|At least one service of a host is 'up', after at least one service was already 'up'.| |*Host Lost*|All services of a host are 'down' after at least one was 'up'.| |*Host Down*|All services of a host are 'down', after they were already 'down'.| #### Découverte Zabbix analyse périodiquement les plages IP définies dans les [règles de découverte du réseau](/manual/discovery/network_discovery/rule). La fréquence du contrôle est configurable pour chaque règle individuellement. Notez qu'une règle de découverte sera toujours traitée par un processus de découverte unique. La plage d'adresses IP ne sera pas divisée entre plusieurs processus de découverte. Chaque règle comporte un ensemble de vérifications de service à exécuter pour la plage IP. ::: noteclassic Les vérifications de découverte sont traités indépendamment des autres vérifications. Si des vérifications ne trouvent pas de service (ou échouent), les autres vérifications seront toujours traitées. ::: Chaque vérification d'un service et d'un hôte (IP) effectuée par le module de découverte du réseau génère un événement de découverte. | Événement |Vérification du résultat du service | | --- | --- | | *Service Discovered* | Le service est 'démarré' après avoir été 'arrêté' ou lorsqu'il est découvert la première fois. | | *Service Up* | Le service est 'démarré'. | | *Service Lost* | Le service est 'arrêté' après avoir été 'démarré'. | | *Service Down* | Le service est 'arrêté'. | | *Host Discovered* | Au moins un des services d'un hôte est "démarré" après que tous les services de cet hôte aient été "arrêtés" ou un service est découvert qui appartient à un hôte non-enregistré. | | *Host Up* | Au moins un service d'un hôte est 'démarré'. | | *Host Lost* | Tous les services d'un hôte sont 'arrêtés' après qu'au moins un des services ait été 'arrêté'. | | *Host Down* | Tous les services d'un hôte sont 'arrêtés'. | #### Display #### Affichage #### Display Based on acknowledgment information it is possible to configure how the problem count is displayed in the dashboard or maps. To do that, you have to make selections in the *Problem display* option, available in both [map configuration](/manual/config/visualization/maps/map#creating_a_map) and the *Problems by severity* [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard##adding_widgets). It is possible to display all problem count, unacknowledged problem count as separated from the total or unacknowledged problem count only. Based on problem update information (acknowledgment, etc.), it is possible to configure update operations - send a message or execute remote commands. #### Affichage En fonction des informations d'acquittement, il est possible de configurer l'affichage du nombre de problèmes dans le tableau de bord ou les cartes. Pour ce faire, vous devez effectuer des sélections dans l'option *Affichage des problèmes*, disponible à la fois dans la [configuration de la carte](/manual/config/visualization/maps/map#creating_a_map) et dans le [widget de tableau de bord](/manual/web_interface/frontend_sections/monitoring/dashboard##adding_widgets) *Problèmes par gravité*. Il est possible d'afficher tous les problèmes répertoriés, tous problèmes non acquittés séparés du nombre de problèmes total ou non acquittés uniquement. En fonction des informations de mise à jour du problème (acquittement, etc.), il est possible de configurer les opérations de mise à jour - envoi de message ou exécution de commandes à distance. ##### Displaying hosts in maintenance An orange wrench icon  next to the host name indicates that this host is in maintenance in: - *Monitoring → Dashboard* - *Monitoring → Problems* - *Inventory → Hosts → Host inventory details* - *Configuration → Hosts* (See 'Status' column)  Maintenance details are displayed when the mouse pointer is positioned over the icon. Additionally, hosts in maintenance get an orange background in *Monitoring → Maps*. ##### Affichage des hôtes en maintenance Une icône de clé orange  à côté du nom de l'hôte indique que cet hôte est en maintenance dans : - *Surveillance → Tableau de bord* - *Surveillance → Problèmes* - *Inventaire → Hôtes → Détails de l'inventaire de l'hôte* - *Configuration → Hôtes* (Voir la colonne 'Statut')  Les détails de la maintenance s'affichent lorsque le pointeur de la souris est positionné sur l'icône. De plus, les hôtes en maintenance obtiennent un fond orange dans *Surveillance → Cartes*. ##### Displaying suppressed problems Normally problems for hosts in maintenance are suppressed, i.e. not displayed in the frontend. However, it is also possible to configure that suppressed problems are shown, by selecting the *Show suppressed problems* option in these locations: - *Monitoring* → *Dashboard* (in *Problem hosts*, *Problems*, *Problems by severity*, *Trigger overview* widget configuration) - *Monitoring* → *Problems* (in the filter) - *Monitoring* → *Maps* (in map configuration) - Global [notifications](/manual/web_interface/user_profile/global_notifications) (in user profile configuration) When suppressed problems are displayed, the following icon is displayed: . Rolling a mouse over the icon displays more details:  ##### Affichage des problèmes supprimés Normalement, les problèmes des hôtes en maintenance sont supprimés, c'est-à-dire qu'ils ne sont pas affichés dans l'interface. Cependant, il est également possible de configurer l'affichage des problèmes supprimés en sélectionnant l'option *Afficher les problèmes supprimés* à ces emplacements : - *Surveillance* → *Tableau de bord* (dans la configuration des widgets *Hôtes problématiques*, *Problèmes*, *Problèmes par sévérité*, *Aperçu des déclencheurs* ) - *Surveillance* → *Problèmes* (dans le filtre) - *Surveillance* → *Cartes* (dans la configuration de la carte) - [Notifications](/manual/web_interface/user_profile/global_notifications) globales (dans la configuration du profil utilisateur) Lorsque des problèmes supprimés sont affichés, l'icône suivante s'affiche : . Passez la souris sur l'icône pour afficher plus de détails :  #### Displaying trigger status With a trigger defined, you might be interested to see its status. If the CPU load has exceeded the threshold level you defined in the trigger, the problem will be displayed in *Monitoring → Problems*. {width="600"} The flashing in the status column indicates a recent change of trigger status, one that has taken place in the last 30 minutes. #### Affichage du statut des déclencheurs Avec un déclencheur défini, vous serez interessé de voir son statut. Si la charge CPU a dépassé le seuil que vous avez défini pour le déclencheur, le problème sera affiché dans *Surveillance → Problèmes*. {width="600"} Le clignotement indique un changement récent de l'état du déclencheur, celui qui a eu lieu au cours des 30 dernières minutes. ##### Display In the item list dependent items are displayed with their master item name as prefix. {width="600"} If a master item is deleted, so are all its dependent items. ##### Affichage Dans la liste d'éléments, les éléments dépendants sont affichés avec leur nom d'élément principal comme préfixe. {width="600"} Si un élément principal est supprimé, tous ses éléments dépendants le sont également. #### Display The following screen will be displayed when trying to access the Zabbix frontend while in maintenance mode. The screen is refreshed every 30 seconds in order to return to a normal state without user intervention when the maintenance is over.  IP addresses defined in ZBX\_GUI\_ACCESS\_IP\_RANGE will be able to access the frontend as always. #### Affichage L’écran suivant s’affiche lorsque vous tentez d’accéder à l’interface Zabbix en mode maintenance. L'écran est actualisé toutes les 30 secondes afin de revenir à un état normal sans intervention de l'utilisateur une fois la maintenance terminée.  Les adresses IP définies dans ZBX\_GUI\_ACCESS\_IP\_RANGE pourront accéder à l'interface comme à d'habitude. ##### Display This is the result in *Monitoring → Latest data*: {width="600"} Note that if a single numeric value is sent in, the data graph will show a horizontal line to the left and to the right of the time point of the value. ##### Affichage Voici le résultat dans *Surveillance → Dernières données* : {width="600"} Notez que si une seule valeur numérique est envoyée, le graphique de données affichera une ligne horizontale à gauche et à droite du point temporel de la valeur. #### Display To view web scenarios configured for a host, go to *Monitoring → Hosts*, locate the host in the list and click on the *Web* hyperlink in the last column. Click on the scenario name to get detailed information. {width="600"} An overview of web scenarios can also be displayed in *Monitoring → Dashboard* by a Web monitoring widget. Recent results of the web scenario execution are available in the *Monitoring → Latest data* section. #### Affichage Pour afficher les scénarios Web configurés pour un hôte, accédez à *Surveillance → Hôtes*, localisez l'hôte dans la liste et cliquez sur l'hyperlien *Web* dans la dernière colonne. Cliquez sur le nom du scénario pour obtenir des informations détaillées. {width="600"} Un aperçu des scénarios Web peut également être affiché dans *Surveillance → Tableau de bord* par un widget de surveillance Web. Les résultats récents de l'exécution du scénario Web sont disponibles dans la section *Surveillance → Dernières données*. #### Docker base images Zabbix components are provided on Ubuntu, Alpine Linux and CentOS base images: |Image|Version| |---|---| |[alpine](https://hub.docker.com/_/alpine/)|3.12| |[ubuntu](https://hub.docker.com/_/ubuntu/)|20.04 (focal)| |[centos](https://hub.docker.com/_/centos/)|8| All images are configured to rebuild latest images if base images are updated. #### Images de base Docker Les composants Zabbix sont fournis sur les images de base Ubuntu, Alpine Linux et CentOS : |Image|Version| |---|---| |[alpine](https://hub.docker.com/_/alpine/)|3.12| |[ubuntu](https://hub.docker.com/_/ubuntu/)|20.04 (focal)| |[centos](https://hub.docker.com/_/centos/)|8| Toutes les images sont configurées pour reconstruire les dernières images si les images de base sont mises à jour. ### Docker Compose Zabbix provides compose files also for defining and running multi-container Zabbix components in Docker. These compose files are available in Zabbix docker official repository on github.com: <https://github.com/zabbix/zabbix-docker>. These compose files are added as examples, they are overloaded. For example, they contain proxies with MySQL and SQLite3 support. There are a few different versions of compose files: |File name|Description| |--|--------| |`docker-compose_v3_alpine_mysql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on Alpine Linux with MySQL database support.| |`docker-compose_v3_alpine_mysql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on Alpine Linux with MySQL database support.| |`docker-compose_v3_alpine_pgsql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on Alpine Linux with PostgreSQL database support.| |`docker-compose_v3_alpine_pgsql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on Alpine Linux with PostgreSQL database support.| |`docker-compose_v3_centos_mysql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on CentOS 8 with MySQL database support.| |`docker-compose_v3_centos_mysql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on CentOS 8 with MySQL database support.| |`docker-compose_v3_centos_pgsql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on CentOS 8 with PostgreSQL database support.| |`docker-compose_v3_centos_pgsql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on CentOS 8 with PostgreSQL database support.| |`docker-compose_v3_ubuntu_mysql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on Ubuntu 20.04 with MySQL database support.| |`docker-compose_v3_ubuntu_mysql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on Ubuntu 20.04 with MySQL database support.| |`docker-compose_v3_ubuntu_pgsql_latest.yaml`|The compose file runs the latest version of Zabbix 6.0 components on Ubuntu 20.04 with PostgreSQL database support.| |`docker-compose_v3_ubuntu_pgsql_local.yaml`|The compose file locally builds the latest version of Zabbix 6.0 and runs Zabbix components on Ubuntu 20.04 with PostgreSQL database support.| ::: noteimportant Available Docker compose files support version 3 of Docker Compose. ::: ### Composition Docker Zabbix fournit également des fichiers de composition pour définir et exécuter des composants Zabbix multi-conteneurs dans Docker. Ces fichiers de composition sont disponibles dans le référentiel officiel Zabbix docker sur github.com : <https://github.com/zabbix/zabbix-docker>. Ces fichiers de composition sont ajoutés à titre d'exemples, ils sont surchargés. Par exemple, ils contiennent des proxies prenant en charge MySQL et SQLite3. Il existe plusieurs versions différentes des fichiers de composition : |Nom du fichier|Description| |--|--------| |`docker-compose_v3_alpine_mysql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur Alpine Linux avec prise en charge de la base de données MySQL.| |`docker-compose_v3_alpine_mysql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur Alpine Linux avec prise en charge de la base de données MySQL.| |`docker-compose_v3_alpine_pgsql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur Alpine Linux avec prise en charge de la base de données PostgreSQL.| |`docker-compose_v3_alpine_pgsql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur Alpine Linux avec prise en charge de la base de données PostgreSQL.| |`docker-compose_v3_centos_mysql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur CentOS 8 avec prise en charge de la base de données MySQL.| |`docker-compose_v3_centos_mysql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur CentOS 8 avec la prise en charge de la base de données MySQL.| |`docker-compose_v3_centos_pgsql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur CentOS 8 avec prise en charge de la base de données PostgreSQL.| |`docker-compose_v3_centos_pgsql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur CentOS 8 avec la prise en charge de la base de données PostgreSQL.| |`docker-compose_v3_ubuntu_mysql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur Ubuntu 20.04 avec prise en charge de la base de données MySQL.| |`docker-compose_v3_ubuntu_mysql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur Ubuntu 20.04 avec la prise en charge de la base de données MySQL.| |`docker-compose_v3_ubuntu_pgsql_latest.yaml`|Le fichier de composition exécute la dernière version des composants Zabbix 5.4 sur Ubuntu 20.04 avec prise en charge de la base de données PostgreSQL.| |`docker-compose_v3_ubuntu_pgsql_local.yaml`|Le fichier de composition construit localement la dernière version de Zabbix 5.4 et exécute les composants Zabbix sur Ubuntu 20.04 avec la prise en charge de la base de données PostgreSQL.| ::: noteimportant Les fichiers Docker Compose disponibles prennent en charge la version 3 de Docker Compose. ::: #### Docker file sources Everyone can follow Docker file changes using the Zabbix [official repository](https://github.com/zabbix/zabbix-docker) on [github.com](https://github.com/). You can fork the project or make your own images based on official Docker files. #### Sources des fichiers Docker Tout le monde peut suivre les modifications du fichier Docker en utilisant le [dépôt officiel](https://github.com/zabbix/zabbix-docker) de Zabbix sur [github.com](https://github.com/). Vous pouvez faire un fork du projet ou créer vos propres images basées sur les fichiers Docker officiels. ### Docker |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |docker.container\_info\[<ID>,<info>\]|<|<|<| |Low-level information about a container.|An output of the [ContainerInspect](https://docs.docker.com/engine/api/v1.28/#operation/ContainerInspect) API call serialized as JSON|**ID** - ID or name of the container.<br>**info** - the amount of information returned. Supported values: *short* (default) or *full*.|The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.container\_stats\[<ID>\]|<|<|<| |Container resource usage statistics.|An output of the [ContainerStats](https://docs.docker.com/engine/api/v1.28/#operation/ContainerStats) API call and CPU usage percentage serialized as JSON|**ID** - ID or name of the container.| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers|<|<|<| |A list of containers.|An output of the [ContainerList](https://docs.docker.com/engine/api/v1.28/#operation/ContainerList) API call serialized as JSON|\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers.discovery\[<options>\]|<|<|<| |A list of containers. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object |**options** - specifies whether all or only running containers should be discovered. Supported values:<br>*true* - return all containers;<br>*false* - return only running containers (default).| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.data\_usage|<|<|<| |Information about current data usage.|An output of the [SystemDataUsage](https://docs.docker.com/engine/api/v1.28/#operation/SystemDataUsage) API call serialized as JSON|\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images|<|<|<| |A list of images.|An output of the [ImageList](https://docs.docker.com/engine/api/v1.28/#operation/ImageList) API call serialized as JSON|\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images.discovery|<|<|<| |A list of images. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object |\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.info|<|<|<| |System information.|An output of the [SystemInfo](https://docs.docker.com/engine/api/v1.28/#operation/SystemInfo) API call serialized as JSON|\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.ping|<|<|<| |Test if a Docker daemon is alive or not.|1 - connection is alive<br><br>0 - connection is broken|\-| The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| ### Docker |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |docker.container\_info \[\<ID\>,\<info\>\]|<|<|<| |Informations de bas niveau sur un conteneur.|Une sortie de l'appel d'API [ContainerInspect](https://docs.docker.com/engine/api/v1.28/#operation/ContainerInspect) sérialisé au format JSON|**ID** - ID ou nom du conteneur.<br>**info** - la quantité d'informations renvoyées. Valeurs prises en charge : *short* (par défaut) ou *full*.|L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.container\_stats \[\<ID\>\]|<|<|<| |Statistiques d'utilisation des ressources du conteneur.|Une sortie de l'appel d'API [ContainerStats](https://docs.docker.com/engine/api/v1.28/#operation/ContainerStats) et du pourcentage d'utilisation du processeur sérialisés en tant que JSON|**ID** - ID ou nom du conteneur| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.containers|<|<|<| |Une liste de conteneurs.|Une sortie de l'appel d'API [ContainerList](https://docs.docker.com/engine/api/v1.28/#operation/ContainerList) sérialisée au format JSON|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.containers.discovery\[\<options\>\]|<|<|<| |Une liste de conteneurs. Utilisé pour [découverte de bas niveau](/manual/discovery/low_level_discovery/).|Objet JSON |**options** - spécifie si tous les conteneurs ou uniquement ceux en cours d'exécution doivent être découverts. Valeurs prises en charge :<br>*true* - renvoie tous les conteneurs ;<br>*false* - renvoie uniquement les conteneurs en cours d'exécution (par défaut).| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.data\_usage|<|<|<| |Informations sur l'utilisation actuelle des données.|Une sortie de l'appel d'API [SystemDataUsage](https://docs.docker.com/engine/api/v1.28/#operation/SystemDataUsage) sérialisée au format JSON|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.images|<|<|<| |Une liste d'images.|Une sortie de l'appel d'API [ImageList](https://docs.docker.com/engine/api/v1.28/#operation/ImageList) sérialisée au format JSON|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.images.discovery|<|<|<| |Une liste d'images. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/).|Objet JSON|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.info|<|<|<| |Informations système.||Informations système.|Une sortie de l'appel d'API [SystemInfo](https://docs.docker.com/engine/api/v1.28/#operation/SystemInfo) sérialisée au format JSON|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| |docker.ping|<|<|<| |Teste si un démon Docker est actif ou non.|1 - la connexion est active<br><br>0 - la connexion est interrompue|\-| L'utilisateur Agent2 ('zabbix') doit être ajouté au [groupe](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) 'docker' pour des privilèges suffisants. Sinon, la vérification échouera.| ### Docker Zabbix provides [Docker](https://www.docker.com) images for each Zabbix component as portable and self-sufficient containers to speed up deployment and update procedure. Zabbix components come with MySQL and PostgreSQL database support, Apache2 and Nginx web server support. These images are separated into different images. ### Docker Zabbix fourni des images [Docker](https://www.docker.com) pour chaque composant Zabbix en tant que conteneurs portables et auto-suffisants pour accélérer le déploiement et mettre à jour la procédure. Les composants Zabbix sont fournis avec la prise en charge de base de données MySQL et PostgreSQL, le support des serveurs web Apache2 et Nginx. Ces images sont séparées en différentes images. # drule.create # drule.create # drule.delete # drule.delete # drule.get # drule.get # drule.update # drule.update # dservice.get # dservice.get #### Dynamic widgets When [configuring](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets) some of the widgets: - Classic graph - Graph prototype - Item value - Plain text - URL there is an extra option called *Dynamic item*. You can check this box to make the widget dynamic - i.e. capable of displaying different content based on the selected host. Now, when saving the dashboard, you will notice that a new host selection field has appeared atop the dashboard for selecting the host (while the *Select* button allows selecting the host group in a popup):  Thus you have a widget, which can display content that is based on the data from the host that is selected. The benefit of this is that you do not need to create extra widgets just because, for example, you want to see the same graphs containing data from various hosts. #### Widgets dynamiques Lors de la [configuration](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets) de certains widgets - Graphique classique - Prototype de graphique - Valeur d'élément - Texte brut - URL il existe une option supplémentaire appelée *Elément dynamique*. Vous pouvez cocher cette case pour rendre le widget dynamique - c'est-à-dire capable d'afficher un contenu différent en fonction de l'hôte sélectionné. Désormais, lors de l'enregistrement du tableau de bord, vous remarquerez qu'un nouveau champ de sélection d'hôte est apparu en haut du tableau de bord pour sélectionner l'hôte (tandis que le bouton *Sélectionner* permet de sélectionner le groupe d'hôtes dans une fenêtre contextuelle) :  Ainsi, vous avez un widget, qui peut afficher du contenu basé sur les données de l'hôte sélectionné. L'avantage de ceci est que vous n'avez pas besoin de créer des widgets supplémentaires simplement parce que, par exemple, vous voulez voir les mêmes graphiques contenant des données provenant de différents hôtes. #### Easy Connect Easy Connect uses the following parameters to connect to the database: - *Host* - the host name or IP address of the database server computer (DBHost parameter in the configuration file). - *Port* - the listening port on the database server (DBPort parameter in the configuration file; if not set the default 1521 port will be used). - <service\_name> - the service name of the database you want to access (DBName parameter in the configuration file). **Example:** Database parameters set in the server or proxy configuration file (zabbix\_server.conf and zabbix\_proxy.conf): DBHost=localhost DBPort=1521 DBUser=myusername DBName=ORCL DBPassword=mypassword Connection string used by Zabbix to establish connection: DBUser/DBPassword@DBHost:DBPort/DBName During Zabbix frontend installation, set the corresponding parameters in the *Configure DB connection* step of the setup wizard: - Database host: localhost - Database port: 1521 - Database name: ORCL - User: myusername - Password: mypassword {width="600"} Alternatively, these parameters can be set in the frontend configuration file (zabbix.conf.php): $DB["TYPE"] = 'ORACLE'; $DB["SERVER"] = 'localhost'; $DB["PORT"] = '1521'; $DB["DATABASE"] = 'ORCL'; $DB["USER"] = 'myusername'; $DB["PASSWORD"] = 'mypassword'; #### Easy Connect Easy Connect utilise les paramètres suivants pour se connecter à la base de données : - *Host* - le nom d'hôte ou l'adresse IP du serveur de la base de données (paramètre DBHost dans le fichier de configuration). - *Port* - le port d'écoute sur le serveur de base de données (paramètre DBPort dans le fichier de configuration ; s'il n'est pas défini, le port 1521 sera utilisé par défaut). - <service\_name> - le nom de service de la base de données à laquelle vous souhaitez accéder (paramètre DBName dans le fichier de configuration). **Exemple:** Paramètres de base de données définis dans le fichier de configuration du serveur ou du proxy (zabbix\_server.conf et zabbix\_proxy.conf): DBHost=localhost DBPort=1521 DBUser=myusername DBName=ORCL DBPassword=mypassword Chaîne de connexion utilisée par Zabbix pour établir la connexion : DBUser/DBPassword@DBHost:DBPort/DBName Lors de l'installation de l'interface Zabbix, définissez les paramètres correspondants à l'étape *Configurer la connexion à la base de données* de l'assistant d'installation : - Database host: localhost - Database port: 1521 - Database name: ORCL - User: myusername - Password: mypassword {width="600"} Alternativement, ces paramètres peuvent être définis dans le fichier de configuration frontal (zabbix.conf.php): $DB["TYPE"] = 'ORACLE'; $DB["SERVER"] = 'localhost'; $DB["PORT"] = '1521'; $DB["DATABASE"] = 'ORCL'; $DB["USER"] = 'myusername'; $DB["PASSWORD"] = 'mypassword'; ##### Editing linked entities If you try to edit an item or trigger that was linked from the template, you may realize that many key options are disabled for editing. This makes sense as the idea of templates is that things are edited in one-touch manner on the template level. However, you still can, for example, enable/disable an item on the individual host and set the update interval, history length and some other parameters. ::: noteimportant Any customizations to the entities implemented on a template-level will override the previous customizations of the entities on a host-level. ::: If you want to edit the entity fully, you have to edit it on the template level (template level shortcut is displayed in the form name), keeping in mind that these changes will affect all hosts that have this template linked to them. ##### Modification des entités liées Si vous essayez de modifier un élément ou un déclencheur lié à partir du modèle, vous vous rendrez peut-être compte que de nombreuses options clés sont désactivées pour la modification. Cela a du sens car l'idée des modèles est que les choses sont modifiées en une seule fois au niveau du modèle. Cependant, vous pouvez toujours, par exemple, activer/désactiver un élément sur l'hôte individuel et définir l'intervalle de mise à jour, la durée de l'historique et certains autres paramètres. ::: noteimportant Toute personnalisation des entités implémentée au niveau du modèle remplacera les personnalisations précédentes des entités au niveau de l'hôte. ::: Si vous souhaitez modifier entièrement l'entité, vous devez la modifier au niveau du modèle (le raccourci au niveau du modèle est affiché dans le nom du formulaire), en gardant à l'esprit que ces modifications affecteront tous les hôtes auxquels ce modèle est lié. ### Editing services Click on the *Edit* button to access the edit mode. When in edit mode, the listing is complemented with checkboxes before the entries and also these additional options: -  - add a child service to this service -  - edit this service -  - delete this service {width="600"} To [configure](/manual/it_services/service) a new service, click on the *Create service* button in the top right-hand corner. ### Edition des services Cliquez sur le bouton *Modifier* pour accéder au mode édition. En mode édition, la liste est complétée par des cases à cocher avant les entrées et également ces options supplémentaires : -  - ajouter un service enfant à ce service -  - modifier ce service -  - supprimer ce service {width="600"} Pour [configurer](/manual/it_services/service) un nouveau service, cliquez sur le bouton *Créer un service* dans le coin supérieur droit. ### Editing services Click on the *Edit* button to access the edit mode. When in edit mode, the listing is complemented with checkboxes before the entries and also these additional options: -  - add a child service to this service -  - edit this service -  - delete this service {width="600"} To [configure](#service_configuration) a new service, click on the *Create service* button in the top right-hand corner. Two buttons below the list offer some mass-editing options: - *Mass update* - mass update service properties - *Delete* - delete the services To use these options, mark the checkboxes before the respective services, then click on the required button. ### Édition des services Cliquez sur le bouton *Modifier* pour accéder au mode édition. En mode édition, la liste est complétée par des cases à cocher avant les entrées et également ces options supplémentaires : -  - ajouter un service enfant à ce service -  - modifier ce service -  - supprimer ce service {width="600"} Pour [configurer](#service_configuration) un nouveau service, cliquez sur le bouton *Créer un service* en haut à droite. Deux boutons sous la liste offrent des options d'édition en masse : - *Mise à jour en masse* - mise à jour en masse des propriétés du service - *Supprimer* - supprimer les services Pour utiliser ces options, cochez les cases devant les services respectifs, puis cliquez sur le bouton requis. #### Element tags Element tag values are explained in the table below. #### Tags d'éléments Les valeurs de tag d'éléments sont expliquées dans le tableau ci-dessous. #### Enabling a host Enable host monitoring, i.e. set its status to 0. Request: ```json { "jsonrpc": "2.0", "method": "host.update", "params": { "hostid": "10126", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10126" ] }, "id": 1 } ``` #### Activation d'un hôte Activez la surveillance de l'hôte, c'est-à-dire définissez son statut sur 0. Requête : ```json { "jsonrpc": "2.0", "method": "host.update", "params": { "hostid": "10126", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "10126" ] }, "id": 1 } ``` #### Enabling a media type Enable a media type, that is, set its status to "0". Request: ```json { "jsonrpc": "2.0", "method": "mediatype.update", "params": { "mediatypeid": "6", "status": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "6" ] }, "id": 1 } ``` #### Activation d'un type de média Activez un type de média, c'est-à-dire définissez son état sur "0". Requête : ```json { "jsonrpc": "2.0", "method": "mediatype.update", "params": { "mediatypeid": "6", "status": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "mediatypeids": [ "6" ] }, "id": 1 } ``` #### Enabling an item Enable an item, that is, set its status to "0". Request: ```json { "jsonrpc": "2.0", "method": "item.update", "params": { "itemid": "10092", "status": 0 }, "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemids": [ "10092" ] }, "id": 1 } ``` #### Activation d'un élément Activez un élément, c'est-à-dire définissez son état sur "0". Requête : ```json { "jsonrpc": "2.0", "method": "item.update", "params": { "itemid": "10092", "status": 0 }, "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemids": [ "10092" ] }, "id": 1 } ``` #### Enabling a trigger Enable a trigger, that is, set its status to 0. Request: ```json { "jsonrpc": "2.0", "method": "trigger.update", "params": { "triggerid": "13938", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` #### Activer un déclencheur Activer un déclencheur, c’est-à-dire définir son statut à 0. Requête : ```json { "jsonrpc": "2.0", "method": "trigger.update", "params": { "triggerid": "13938", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` #### Enabling a trigger prototype Enable a trigger prototype, that is, set its status to 0. Request: ```json { "jsonrpc": "2.0", "method": "triggerprototype.update", "params": { "triggerid": "13938", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` #### Activation d'un prototype de déclencheur Activer un prototype de déclencheur, c’est-à-dire définir son statut à 0. Requête : ```json { "jsonrpc": "2.0", "method": "triggerprototype.update", "params": { "triggerid": "13938", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` #### Enabling a web scenario Enable a web scenario, that is, set its status to "0". Request: ```json { "jsonrpc": "2.0", "method": "httptest.update", "params": { "httptestid": "5", "status": 0 }, "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "httptestids": [ "5" ] }, "id": 1 } ``` #### Activer un scénario Web Activer un scénario Web, c’est-à-dire définir son statut à "0". Requête : ```json { "jsonrpc": "2.0", "method": "httptest.update", "params": { "httptestid": "5", "status": 0 }, "auth": "700ca65537074ec963db7efabda78259", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "httptestids": [ "5" ] }, "id": 1 } ``` ### Enabling high availability ### Activation du cluster HA #### Enabling MIB files On RedHat-based systems the mib files should be enabled by default. On Debian-based systems you have to edit file `/etc/snmp/snmp.conf` and comment out the line that says `mibs :` # As the snmp packages come without MIB files due to license reasons, loading # of MIBs is disabled by default. If you added the MIBs you can re-enable # loading them by commenting out the following line. #mibs : #### Activation fichiers MIB Sur les systèmes basés sur RedHat les fichiers mib doivent être activés par défaut. Sur les systèmes basés sur Debian, vous devez éditer le fichier `/etc/snmp/snmp.conf` et décommenter la ligne qui dit `mibs :` # As the snmp packages come without fichiers MIB due to license reasons, loading # of MIBs is disabled by default. If you added the MIBs you can reenable # loading them by commenting out the following line. #mibs : #### Enabling multiple hosts Enable monitoring of two hosts, i.e., set their status to 0. Request: ```json { "jsonrpc": "2.0", "method": "host.massupdate", "params": { "hosts": [ { "hostid": "69665" }, { "hostid": "69666" } ], "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "hostids": [ "69665", "69666" ] }, "id": 1 } ``` #### Activation de plusieurs hôtes Activer la surveillance de deux hôtes, c’est-à-dire, définir leur statut à 0. Requête : ```json { "jsonrpc": "2.0", "method": "host.massupdate", "params": { "hosts": [ { "hostid": "69665" }, { "hostid": "69666" } ], "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "hostids": [ "69665", "69666" ] }, "id": 1 } ``` #### Encoding settings To make sure that the acquired data are not corrupted you may specify the correct encoding for processing the check (e.g. 'vfs.file.contents') in the `encoding` parameter. The list of supported encodings (code page identifiers) may be found in documentation for [libiconv](http://www.gnu.org/software/libiconv/) (GNU Project) or in Microsoft Windows SDK documentation for "Code Page Identifiers". If no encoding is specified in the `encoding` parameter the following resolution strategies are applied: - If encoding is not specified (or is an empty string) it is assumed to be UTF-8, the data is processed "as-is"; - BOM analysis - applicable for items 'vfs.file.contents', 'vfs.file.regexp', 'vfs.file.regmatch'. An attempt is made to determine the correct encoding by using the byte order mark (BOM) at the beginning of the file. If BOM is not present - standard resolution (see above) is applied instead. #### Paramètres d'encodage Pour vous assurer que les données acquises ne sont pas corrompues, vous pouvez spécifier l'encodage correct pour le traitement de la vérification (par exemple, 'vfs.file.contents') dans le paramètre `encoding`. La liste des encodages pris en charge (identifiants de page de code) peut être trouvée dans la documentation de [libiconv](http://www.gnu.org/software/libiconv/) (Projet GNU) ou dans la documentation du SDK Microsoft Windows pour "Code Page Identifiers ". Si aucun encodage n'est spécifié dans le paramètre "encoding", les stratégies de résolution suivantes sont appliquées : - Si l'encodage n'est pas spécifié (ou s'il s'agit d'une chaîne vide), il est supposé être UTF-8, les données sont traitées "telles quelles" ; - Analyse BOM - applicable pour les éléments 'vfs.file.contents', 'vfs.file.regexp', 'vfs.file.regmatch'. Une tentative est faite pour déterminer le codage correct en utilisant la marque d'ordre d'octet (BOM) au début du fichier. Si la nomenclature n'est pas présente, la résolution standard (voir ci-dessus) est appliquée à la place. ##### Encryption The **Encryption** tab allows you to require [encrypted](/manual/encryption) connections with the host. |Parameter|Description| |--|--------| |*Connections to host*|How Zabbix server or proxy connects to Zabbix agent on a host: no encryption (default), using PSK (pre-shared key) or certificate.| |*Connections from host*|Select what type of connections are allowed from the host (i.e. from Zabbix agent and Zabbix sender). Several connection types can be selected at the same time (useful for testing and switching to other connection type). Default is "No encryption".| |*Issuer*|Allowed issuer of certificate. Certificate is first validated with CA (certificate authority). If it is valid, signed by the CA, then the *Issuer* field can be used to further restrict allowed CA. This field is intended to be used if your Zabbix installation uses certificates from multiple CAs. If this field is empty then any CA is accepted.| |*Subject*|Allowed subject of certificate. Certificate is first validated with CA. If it is valid, signed by the CA, then the *Subject* field can be used to allow only one value of *Subject* string. If this field is empty then any valid certificate signed by the configured CA is accepted.| |*PSK identity*|Pre-shared key identity string.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |*PSK*|Pre-shared key (hex-string). Maximum length: 512 hex-digits (256-byte PSK) if Zabbix uses GnuTLS or OpenSSL library, 64 hex-digits (32-byte PSK) if Zabbix uses mbed TLS (PolarSSL) library. Example: 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952| ##### Chiffrement L'onglet **Chiffrement** vous permet d'exiger des connexions [cryptées](/manual/encryption) avec l'hôte. |Paramètre|Description| |--|--------| |*Connexions à l'hôte*|Comment le serveur ou le proxy Zabbix se connecte à l'agent Zabbix sur un hôte : pas de cryptage (par défaut), en utilisant PSK (clé pré-partagée) ou un certificat.| |*Connexions depuis l'hôte*|Sélectionnez le type de connexions autorisées depuis l'hôte (c'est-à-dire depuis l'agent Zabbix et le sender Zabbix). Plusieurs types de connexion peuvent être sélectionnés en même temps (utile pour tester et passer à un autre type de connexion). La valeur par défaut est "Aucun cryptage".| |*Émetteur*|Émetteur autorisé du certificat. Le certificat est d'abord validé auprès de l'AC (autorité de certification). S'il est valide, signé par l'AC, le champ *Émetteur* peut être utilisé pour restreindre davantage l'AC autorisée. Ce champ est destiné à être utilisé si votre installation Zabbix utilise des certificats de plusieurs autorités de certification. Si ce champ est vide, toute autorité de certification est acceptée.| |*Sujet*|Sujet autorisé du certificat. Le certificat est d'abord validé avec CA. S'il est valide, signé par l'autorité de certification, le champ *Sujet* peut être utilisé pour n'autoriser qu'une seule valeur de chaîne *Sujet*. Si ce champ est vide, tout certificat valide signé par l'autorité de certification configurée est accepté.| |*Identité PSK*|Chaîne d'identité de clé pré-partagée.<br>Ne mettez pas d'informations sensibles dans l'identité PSK, elle est transmise sans chiffrement sur le réseau pour informer un récepteur quel PSK utiliser.| |*PSK*|Clé pré-partagée (chaîne hexadécimale). Longueur maximale : 512 chiffres hexadécimaux (PSK de 256 octets) si Zabbix utilise la bibliothèque GnuTLS ou OpenSSL, 64 chiffres hexadécimaux (PSK de 32 octets) si Zabbix utilise la bibliothèque mbed TLS (PolarSSL). Exemple : 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952| ##### Entity uniqueness criteria When adding entities (items, triggers, graphs etc.) from a template it is important to know what of those entities already exist on the host and need to be updated and what entities differ. The uniqueness criteria for deciding upon the sameness/difference are: - for items - the item key - for triggers - trigger name and expression - for custom graphs - graph name and its items ##### Critère d'unicité de l'entité Lors de l'ajout d'entités (éléments, déclencheurs, graphiques, etc.) à partir d'un modèle, il est important de savoir quelles entités existent déjà sur l'hôte et doivent être mises à jour, ainsi que les entités qui diffèrent. Les critères d’unicité pour décider de la similitude/différence sont les suivants : - pour les éléments - la clé de l'élément - pour les déclencheurs - nom et expression du déclencheur - pour les graphiques personnalisés - nom du graphique et ses éléments #### Environment files In the same directory with compose files on github.com you can find files with default environment variables for each component in compose file. These environment files are named like `.env_<type of component>`. #### Fichiers d'environnement Dans le même répertoire avec les fichiers compose sur github.com, vous pouvez trouver des fichiers avec des variables d'environnement par défaut pour chaque composant dans le fichier compose. Ces fichiers d'environnement sont nommés comme ceci :`.env_<type de composant>`. #### Error handling Up to that point everything we've tried has worked fine. But what happens if we try to make an incorrect call to the API? Let's try to create another host by calling [host.create](/manual/api/reference/host/create) but omitting the mandatory `groups` parameter. ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "Linux server", "interfaces": [ { "type": 1, "main": 1, "useip": 1, "ip": "192.168.3.1", "dns": "", "port": "10050" } ] }, "id": 7, "auth": "0424bd59b807674191e7d77572075f33" } ``` The response will then contain an error message: ```json { "jsonrpc": "2.0", "error": { "code": -32602, "message": "Invalid params.", "data": "No groups for host \"Linux server\"." }, "id": 7 } ``` If an error occurred, instead of the `result` property, the response object will contain an `error` property with the following data: - `code` - an error code; - `message` - a short error summary; - `data` - a more detailed error message. Errors can occur in different cases, such as, using incorrect input values, a session timeout or trying to access unexisting objects. Your application should be able to gracefully handle these kinds of errors. #### Gestion des erreurs Jusque là, tout ce que nous avons essayé a bien fonctionné. Mais que se passe-t-il si nous essayons de faire un appel incorrect à l'API ? Essayons de créer un autre hôte en appelant la méthode [host.create](/manual/api/reference/host/create) mais en omettant le paramètre obligatoire `groups`. ```json { "jsonrpc": "2.0", "method": "host.create", "params": { "host": "Linux server", "interfaces": [ { "type": 1, "main": 1, "useip": 1, "ip": "192.168.3.1", "dns": "", "port": "10050" } ] }, "id": 7, "auth": "0424bd59b807674191e7d77572075f33" } ``` La réponse contiendra alors un message d'erreur : ```json { "jsonrpc": "2.0", "error": { "code": -32602, "message": "Invalid params.", "data": "No groups for host \"Linux server\"." }, "id": 7 } ``` Si une erreur survient, au lieu de la propriété `result`, l'objet de réponse contiendra une propriété `error` avec les données suivantes : - `code` - un code d'erreur ; - `message` - un résumé succinct de l'erreur ; - `data` - un message d'erreur plus détaillé. Des erreurs peuvent survenir dans différents cas, tels que l'utilisation de valeurs d'entrée incorrectes, l'expiration du délai d'une session ou la tentative d'accès à des objets non existants. Votre application doit pouvoir gérer ce type d’erreurs. #### Escalation examples #### Exemples d'escalade # event.acknowledge # event.acknowledge #### Event correlation Create custom event correlation rules. [Correlation API](/manual/api/reference/correlation) #### Corrélation d'événements Créez des règles de corrélation d'événements personnalisées. [API Correlation](/manual/api/reference/correlation) ##### Event correlation Event correlation (also called global event correlation) is a way to set up custom event closing (resulting in OK event generation) rules. The rules define how the new problem events are paired with existing problem events and allow to close the new event or the matched events by generating corresponding OK events. However, event correlation must be configured very carefully, as it can negatively affect event processing performance or, if misconfigured, close more events than intended (in the worst case even all problem events could be closed). A few configuration tips: 1. always reduce the correlation scope by setting a unique tag for the control event (the event that is paired with old events) and use the 'new event tag' correlation condition 2. don't forget to add a condition based on the old event when using 'close old event' operation, or all existing problems could be closed 3. avoid using common tag names used by different correlation configurations ##### Corrélation d'événements La corrélation d'événements (également appelée corrélation d'événements globale) permet de configurer des règles personnalisées de fermeture d'événement (entraînant la création d'événements OK). Les règles définissent la manière dont les nouveaux événements problèmes sont associés à des événements problèmes existants et permettent de fermer le nouvel événement ou les événements correspondants en générant des événements OK correspondants. Cependant, la corrélation d'événements doit être configurée très soigneusement, car elle peut affecter négativement les performances de traitement des événements ou, si elle est mal configurée, fermer plus d'événements que prévu (dans le pire des cas, tous les problèmes peuvent être fermés). Quelques conseils de configuration : 1. toujours réduire la portée de la corrélation en définissant un tag unique pour la vérification de l'événement (l'événement associé à des événements anciens) et en utilisant la condition de corrélation 'nouveau tag d'événement' 2. ne pas oublier d'ajouter une condition basée sur l'ancien événement lors de l'utilisation de l'opération 'fermer l'ancien événement', ou tous les problèmes existants pourraient être fermés 3. évitez d'utiliser des noms de tag identiques utilisés par différentes configurations de corrélation # event.get # event.get #### Event menu Clicking on the problem name brings up the event menu:  The event menu allows to: - filter the problems of the trigger - access the trigger configuration - access a simple graph/item history of the underlying item(s) - access an external ticket of the problem (if configured, see the *Include event menu entry* option when configuring [webhooks](/manual/config/notifications/media/webhook)) - execute global [scripts](/manual/web_interface/frontend_sections/administration/scripts) (these scripts need to have their scope defined as 'Manual event action'). This feature may be handy for running scripts used for managing problem tickets in external systems. #### Menu de l'événement Cliquer sur le nom du problème fait apparaître le menu des événements :  Le menu événement permet de : - filtrer les problèmes du déclencheur - accéder à la configuration du déclencheur - accéder à un simple graphique/historique des éléments du ou des éléments sous-jacents - accéder à un ticket externe du problème (si configuré, voir l'option *Inclure l'entrée du menu de l'événement* lors de la configuration des [webhooks](/manual/config/notifications/media/webhook)) - executer des [scripts globaux](/manual/web_interface/frontend_sections/administration/scripts) (ces scripts doivent avoir leur portée définie comme 'Action manuelle d'événemen'). Cette fonctionnalité peut être pratique pour exécuter des scripts utilisés pour gérer les tickets de problème dans des systèmes externes. #### Events Retrieve events generated by triggers, network discovery and other Zabbix systems for more flexible situation management or third-party tool integration. [Event API](/manual/api/reference/event) #### Evénements Récupérez les événements générés par les déclencheurs, la découverte du réseau et les autres systèmes Zabbix pour une gestion plus flexible des situations ou une intégration à des outils tiers. [API Evénement](/manual/api/reference/event) ### Event tag The event tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Event tag name.| |value|string|Event tag value.| ### Tag d'événement L'objet tag d'événement a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Nom du tag d'événement.| |valeur|chaîne|Valeur du tag d'événement.| ### Example ### Exemple ##### Example 11 Check if client local time is in sync with Zabbix server time. Use of function fuzzytime(): fuzzytime(/MySQL_DB/system.localtime,10s)=0 The trigger will change to the problem state in case when local time on server MySQL\_DB and Zabbix server differs by more than 10 seconds. Note that 'system.localtime' must be configured as a [passive check](/manual/appendix/items/activepassive#passive_checks). ##### Exemple 11 Vérifiez si l'heure locale du client est synchronisée avec l'heure du serveur Zabbix. Utilisation de la fonction fuzzytime() : fuzzytime(/MySQL_DB/system.localtime,10s)=0 Le déclencheur passera à l'état problème si l'heure locale sur le serveur MySQL\_DB et le serveur Zabbix diffère de plus de 10 secondes. Notez que 'system.localtime' doit être configuré en tant que [contrôle passif](/manual/appendix/items/activepassive#passive_checks). ##### Example 13 Using the value of another item to get a trigger threshold: last(/Template PfSense/hrStorageFree[{#SNMPVALUE}])<last(/Template PfSense/hrStorageSize[{#SNMPVALUE}])*0.1 The trigger will fire if the free storage drops below 10 percent. ##### Exemple 13 Utiliser la valeur d'un autre élément pour obtenir un seuil de déclenchement : last(/Template PfSense/hrStorageFree[{#SNMPVALUE}])<last(/Template PfSense/hrStorageSize[{#SNMPVALUE}])*0.1 Le déclencheur se déclenchera si l'espace libre tombe en dessous de 10 %. ##### Example 15 Comparing string values of two items - operands here are functions that return strings. Problem: create an alert if Ubuntu version is different on different hosts last(/NY Zabbix server/vfs.file.contents[/etc/os-release])<>last(/LA Zabbix server/vfs.file.contents[/etc/os-release]) ##### Exemple 15 Comparaison des valeurs de chaîne de deux éléments - les opérandes sont ici des fonctions qui renvoient des chaînes. Problème : créer une alerte si la version d'Ubuntu est différente sur différents hôtes last(/NY Zabbix server/vfs.file.contents[/etc/os-release])<>last(/LA Zabbix server/vfs.file.contents[/etc/os-release]) ##### Example 16 Comparing two string values - operands are: - a function that returns a string - a combination of macros and strings Problem: detect changes in the DNS query The item key is: net.dns.record[8.8.8.8,{$WEBSITE_NAME},{$DNS_RESOURCE_RECORD_TYPE},2,1] with macros defined as {$WEBSITE_NAME} = example.com {$DNS_RESOURCE_RECORD_TYPE} = MX and normally returns: example.com MX 0 mail.example.com So our trigger expression to detect if the DNS query result deviated from the expected result is: last(/Zabbix server/net.dns.record[8.8.8.8,{$WEBSITE_NAME},{$DNS_RESOURCE_RECORD_TYPE},2,1])<>"{$WEBSITE_NAME} {$DNS_RESOURCE_RECORD_TYPE} 0 mail.{$WEBSITE_NAME}" Notice the quotes around the second operand. ##### Exemple 16 Comparaison de deux valeurs de chaîne - les opérandes sont : - une fonction qui renvoie une chaîne - une combinaison de macros et de chaînes Problème : détecter les changements dans la requête DNS La clé de l'élément est : net.dns.record[8.8.8.8,{$WEBSITE_NAME},{$DNS_RESOURCE_RECORD_TYPE},2,1] avec des macros définies comme {$WEBSITE_NAME} = example.com {$DNS_RESOURCE_RECORD_TYPE} = MX et renvoie normalement : example.com MX 0 mail.example.com Donc, notre expression de déclenchement pour détecter si le résultat de la requête DNS s'écarte du résultat attendu est : last(/Zabbix server/net.dns.record[8.8.8.8,{$WEBSITE_NAME},{$DNS_RESOURCE_RECORD_TYPE},2,1])<>"{$WEBSITE_NAME} {$DNS_RESOURCE_RECORD_TYPE} 0 mail.{$WEBSITE_NAME}" Remarquez les guillemets autour du deuxième opérande. ##### Example 17 Comparing two string values - operands are: - a function that returns a string - a string constant with special characters \\ and " Problem: detect if the `/tmp/hello` file content is equal to: \" //hello ?\" Option 1) write the string directly last(/Zabbix server/vfs.file.contents[/tmp/hello])="\\\" //hello ?\\\"" Notice how \\ and " characters are escaped when the string gets compared directly. Option 2) use a macro {$HELLO_MACRO} = \" //hello ?\" in the expression: last(/Zabbix server/vfs.file.contents[/tmp/hello])={$HELLO_MACRO} ##### Exemple 17 Comparaison de deux valeurs de chaîne - les opérandes sont : - une fonction qui renvoie une chaîne - une chaîne constante avec des caractères spéciaux \\ et " Problème : détecter si le contenu du fichier `/tmp/hello` est égal à : \" //hello ?\" Option 1) écrire la chaîne directement last(/Zabbix server/vfs.file.contents[/tmp/hello])="\\\" //hello ?\\\"" Remarquez comment les caractères \\ et " sont échappés lorsque la chaîne est comparée directement. Option 2) utiliser une macro {$HELLO_MACRO} = \" //hello ?\" dans l'expression : last(/Zabbix server/vfs.file.contents[/tmp/hello])={$HELLO_MACRO} ##### Example 18 Comparing long-term periods. Problem: Load of Exchange server increased by more than 10% last month trendavg(/Exchange/system.cpu.load,1M:now/M)>1.1*trendavg(/Exchange/system.cpu.load,1M:now/M-1M) You may also use the [Event name](/manual/config/triggers/trigger#configuration) field in trigger configuration to build a meaningful alert message, for example to receive something like `"Load of Exchange server increased by 24% in July (0.69) comparing to June (0.56)"` the event name must be defined as: Load of {HOST.HOST} server increased by {{?100*trendavg(//system.cpu.load,1M:now/M)/trendavg(//system.cpu.load,1M:now/M-1M)}.fmtnum(0)}% in {{TIME}.fmttime(%B,-1M)} ({{?trendavg(//system.cpu.load,1M:now/M)}.fmtnum(2)}) comparing to {{TIME}.fmttime(%B,-2M)} ({{?trendavg(//system.cpu.load,1M:now/M-1M)}.fmtnum(2)}) It is also useful to allow manual closing in trigger configuration for this kind of problem. ##### Exemple 18 Comparer de longues périodes de temps. Problème : la charge du serveur Exchange a augmenté de plus de 10 % le mois dernier trendavg(/Exchange/system.cpu.load,1M:now/M)>1.1*trendavg(/Exchange/system.cpu.load,1M:now/M-1M) Vous pouvez également utiliser le champ [Nom de l'événement](/manual/config/triggers/trigger#configuration) dans la configuration du déclencheur pour créer un message d'alerte significatif, par exemple pour recevoir quelque chose comme `"Load of Exchange server increased by 24% in July (0.69) comparing to June (0.56)"` le nom de l'événement doit être défini comme : Load of {HOST.HOST} server increased by {{?100*trendavg(//system.cpu.load,1M:now/M)/trendavg(//system.cpu.load,1M:now/M-1M)}.fmtnum(0)}% in {{TIME}.fmttime(%B,-1M)} ({{?trendavg(//system.cpu.load,1M:now/M)}.fmtnum(2)}) comparing to {{TIME}.fmttime(%B,-2M)} ({{?trendavg(//system.cpu.load,1M:now/M-1M)}.fmtnum(2)}) Il est également utile d'autoriser la fermeture manuelle dans la configuration du déclencheur pour ce type de problème. ##### Example 1 Calculating percentage of free disk space on '/'. Use of function **last**: 100*last(//vfs.fs.size[/,free])/last(//vfs.fs.size[/,total]) Zabbix will take the latest values for free and total disk spaces and calculate percentage according to the given formula. ##### Exemple 1 Calcul du pourcentage d'espace disque libre sur '/'. Utilisation de la fonction **last**: 100*last(//vfs.fs.size[/,free])/last(//vfs.fs.size[/,total]) Zabbix prendra les dernières valeurs pour les espaces disque libres et totaux et calculera le pourcentage selon la formule donnée. ##### Example 1 Message subject: Problem: {TRIGGER.NAME} When you receive the message, the message subject will be replaced by something like: Problem: Processor load is too high on Zabbix server ##### Exemple 1 Objet du message: Problème : {TRIGGER.NAME} Lorsque vous recevez le message, le sujet du message sera remplacé par quelque chose comme : Problème : la charge du processeur est trop élevée sur le serveur Zabbix ##### Example 1 Sending a repeated notification once every 30 minutes (5 times in total) to a 'MySQL Administrators' group. To configure: - in Operations tab, set the *Default operation step duration* to '30m' (30 minutes) - Set the escalation steps to be *From* '1' *To* '5' - Select the 'MySQL Administrators' group as recipients of the message {width="600"} Notifications will be sent at 0:00, 0:30, 1:00, 1:30, 2:00 hours after the problem starts (unless, of course, the problem is resolved sooner). If the problem is resolved and a recovery message is configured, it will be sent to those who received at least one problem message within this escalation scenario. ::: noteclassic If the trigger that generated an active escalation is disabled, Zabbix sends an informative message about it to all those that have already received notifications. ::: ##### Exemple 1 Envoi d'une notification répétée une fois toutes les 30 minutes (5 fois au total) à un groupe 'MySQL Administrators'. Pour le configurer : - Dans l'onglet Opérations, définissez la *durée de l'étape d'opération par défaut* à '30m' (30 minutes) - Définissez les étapes d'escalade sur *De* '1' *À* '5' - Sélectionnez le groupe 'MySQL Administrators' comme destinataires du message {width="600"} Les notifications seront envoyées 0:00, 0:30, 1:00, 1:30, 2:00 heures après le début du problème (à moins, bien sûr, que le problème ne soit résolu plus tôt). Si le problème est résolu et qu'un message de récupération est configuré, il sera envoyé à ceux qui ont reçu au moins un message de problème dans ce scénario d'escalade. ::: noteclassic Si le déclencheur qui a généré une escalade active est désactivé, Zabbix envoie un message informatif à ce sujet à tous ceux qui ont déjà reçu des notifications. ::: ##### Example 1 Send simple GET requests to retrieve data from services such as Elasticsearch: - Create a GET item with URL: `localhost:9200/?pretty` - Notice the response: ```{=html} <!-- --> ``` { "name" : "YQ2VAY-", "cluster_name" : "elasticsearch", "cluster_uuid" : "kH4CYqh5QfqgeTsjh2F9zg", "version" : { "number" : "6.1.3", "build_hash" : "af51318", "build_date" : "2018-01-26T18:22:55.523Z", "build_snapshot" : false, "lucene_version" : "7.1.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You know, for search" } - Now extract the version number using a JSONPath preprocessing step: `$.version.number` ##### Exemple 1 Envoyez des requêtes GET simples pour extraire des données de services tels que Elasticsearch : - Créer un élément GET avec l'URL : `localhost:9200/?pretty` - Notez la réponse : ```{=html} <!-- --> ``` { "name" : "YQ2VAY-", "cluster_name" : "elasticsearch", "cluster_uuid" : "kH4CYqh5QfqgeTsjh2F9zg", "version" : { "number" : "6.1.3", "build_hash" : "af51318", "build_date" : "2018-01-26T18:22:55.523Z", "build_snapshot" : false, "lucene_version" : "7.1.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You know, for search" } - Extrayez maintenant le numéro de version en utilisant une étape de prétraitement JSONPath : `$.version.number` ##### Example 1 Something very simple: UserParameter=ping[*],echo $1 We may define unlimited number of items for monitoring all having format ping\[something\]. - ping\[0\] - will always return '0' - ping\[aaa\] - will always return 'aaa' ##### Exemple 1 Quelque chose de très simple : UserParameter=ping[*],echo $1 Nous pouvons définir un nombre illimité d'éléments pour la surveillance de tous les formats ping\[quelque chose\]. - ping\[0\] - retournera toujours '0' - ping\[aaa\] - retournera toujours 'aaa' ##### Example 1 Stop repetitive problem events from the same network port.  This global correlation rule will correlate problems if *Host* and *Port* tag values exist on the trigger and they are the same in the original event and the new one. The operation will close new problem events on the same network port, keeping only the original problem open. ##### Exemple 1 Arrêtez les événements de problème répétitifs à partir du même port réseau.  Cette règle de corrélation globale corrélera les problèmes si les valeurs des tags *Host* et *Port* existent sur le déclencheur et qu'elles sont identiques dans l'événement d'origine et le nouveau. L'opération fermera les nouveaux événements de problème sur le même port réseau, en gardant uniquement le problème d'origine ouvert. ##### Example 1 Temperature in server room is too high. Problem expression: last(/server/temp)>20 Recovery expression: last(/server/temp)<=15 ##### Exemple 1 La température dans la salle des serveurs est trop élevée. Expression du problème : last(/server/temp)>20 Expression de récupération : last(/server/temp)<=15 ##### Example 1 The processor load is too high on Zabbix server. last(/Zabbix server/system.cpu.load[all,avg1])>5 By using the function 'last()', we are referencing the most recent value. `/Zabbix server/system.cpu.load[all,avg1]` gives a short name of the monitored parameter. It specifies that the host is 'Zabbix server' and the key being monitored is 'system.cpu.load\[all,avg1\]'. Finally, `>5` means that the trigger is in the PROBLEM state whenever the most recent processor load measurement from Zabbix server is greater than 5. ##### Exemple 1 La charge du processeur est trop élevée sur le serveur Zabbix. last(/Zabbix server/system.cpu.load[all,avg1])>5 En utilisant la fonction 'last()', nous faisons référence à la valeur la plus récente. `/Zabbix server/system.cpu.load[all,avg1]` donne un nom court du paramètre surveillé. Il spécifie que l'hôte est 'Zabbix server' et que la clé surveillée est 'system.cpu.load\[all,avg1\]'. Enfin, `>5` signifie que le déclencheur est dans l'état PROBLÈME chaque fois que la mesure de la charge du processeur la plus récente du serveur Zabbix est supérieure à 5. ##### Example 1 To create a "Web scenario failed" trigger, you can define a trigger expression: last(/host/web.test.fail[Scenario])<>0 Make sure to replace 'Scenario' with the real name of your scenario. ##### Exemple 1 Pour créer un déclencheur "Échec du scenario Web", vous pouvez définir une expression de déclencheur : last(/host/web.test.fail[Scenario])<>0 Assurez-vous de remplacer 'Scenario' par le vrai nom de votre scénario. ##### Example 1 Total disk space of host group 'MySQL Servers'. sum(last_foreach(/*/vfs.fs.size[/,total]?[group="MySQL Servers"])) ##### Exemple 1 Espace disque total du groupe d'hôtes 'MySQL Servers'. sum(last_foreach(/*/vfs.fs.size[/,total]?[group="MySQL Servers"])) ##### Example 1 Use of host-level macro in the "Status of SSH daemon" item key: `net.tcp.service[ssh,,{$SSH_PORT}]` This item can be assigned to multiple hosts, providing that the value of **{$SSH\_PORT}** is defined on those hosts. ##### Exemple 1 Utilisation d'une macro au niveau de l'hôte dans la clé d'élément "État du démon SSH" : `net.tcp.service[ssh,,{$SSH_PORT}]` Cet élément peut être attribué à plusieurs hôtes, à condition que la valeur de **{$SSH\_PORT}** soit définie sur ces hôtes. ##### Example 1 Use of the following expression in low-level discovery to discover databases except a database with a specific name: ^TESTDATABASE$  Chosen *Expression type*: "Result is FALSE". Doesn't match name, containing string "*TESTDATABASE*". ##### Exemple 1 Utilisation de l'expression suivante dans la découverte de bas niveau pour découvrir des bases de données à l'exception d'une base de données portant un nom spécifique : ^TESTDATABASE$  *Type d'expression* choisi : "Le résultat est FAUX". Ne correspond pas au nom, contenant la chaîne "*TESTDATABASE*". ##### Example 1 Using host metadata to distinguish between Linux and Windows hosts. Say you would like the hosts to be autoregistered by the Zabbix server. You have active Zabbix agents (see "Configuration" section above) on your network. There are Windows hosts and Linux hosts on your network and you have "Linux by Zabbix agent" and "Windows by Zabbix agent" templates available in your Zabbix frontend. So at host registration, you would like the appropriate Linux/Windows template to be applied to the host being registered. By default, only the hostname is sent to the server at autoregistration, which might not be enough. In order to make sure the proper template is applied to the host you should use host metadata. ##### Exemple 1 Utilisation de métadonnées d'hôte pour distinguer les hôtes Linux et Windows. Supposons que vous souhaitiez que les hôtes soient automatiquement enregistrés par le serveur Zabbix. Vous avez des agents Zabbix actifs (voir la section "Configuration" ci-dessus) sur votre réseau. Il existe des hôtes Windows et des hôtes Linux sur votre réseau et vous avez des modèles "Template OS Linux" et "Template OS Windows" disponibles dans votre interface Zabbix. Ainsi, lors de l'enregistrement de l'hôte, vous souhaitez que le modèle Linux/Windows approprié soit appliqué à l'hôte en cours d'enregistrement. Par défaut, seul le nom d'hôte est envoyé au serveur lors de l'enregistrement automatique, ce qui pourrait ne pas suffire. Afin de vous assurer que le modèle approprié est appliqué à l'hôte, vous devez utiliser les métadonnées de l'hôte. ##### Example 2 Calculating a 10-minute average of the number of values processed by Zabbix. Use of function **avg**: avg(/Zabbix Server/zabbix[wcache,values],10m) Note that extensive use of calculated items with long time periods may affect performance of Zabbix server. ##### Exemple 2 Calcul d'une moyenne sur 10 minutes du nombre de valeurs traitées par Zabbix. Utilisation de la fonction **avg**: avg(/Zabbix Server/zabbix[wcache,values],10m) Notez qu'une utilisation intensive d'éléments calculés avec de longues périodes peut affecter les performances du serveur Zabbix. ##### Example 2 Free disk space is too low. Problem expression: it is less than 10GB for last 5 minutes max(/server/vfs.fs.size[/,free],5m)<10G Recovery expression: it is more than 40GB for last 10 minutes min(/server/vfs.fs.size[/,free],10m)>40G ##### Exemple 2 L'espace disque libre est trop faible. Expression du problème : moins de 10 Go pendant les 5 dernières minutes max(/server/vfs.fs.size[/,free],5m)<10G Expression de récupération : plus de 40 Go pendant les 10 dernières minutes min(/server/vfs.fs.size[/,free],10m)>40G ##### Example 2 Let's add more sense! UserParameter=mysql.ping[*],mysqladmin -u$1 -p$2 ping | grep -c alive This parameter can be used for monitoring availability of MySQL database. We can pass user name and password: mysql.ping[zabbix,our_password] ##### Exemple 2 Ajoutons un peu de sens ! UserParameter=mysql.ping[*],mysqladmin -u$1 -p$2 ping | grep -c alive Ce paramètre peut être utilisé pour superviser la disponibilité de la base de données MySQL. Nous pouvons passer le nom d'utilisateur et le mot de passe : mysql.ping[zabbix,our_password] ##### Example 2 Message: Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])} When you receive the message, the message will be replaced by something like: Processor load is: 1.45 ##### Exemple 2 Message : Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])} Lorsque vous recevez le message, le message sera remplacé par quelque chose comme : Processor load is: 1.45 ##### Example 2 Monitoring of uptime: |Parameter|Description| |--|--------| |**OID**|MIB::sysUpTime.0| |**Key**|router.uptime| |**Value type**|Float| |**Units**|uptime| |**Preprocessing step: Custom multiplier**|0.01| ##### Exemple 2 Surveillance de la disponibilité : |Paramètre|Description| |--|--------| |**OID**|MIB::sysUpTime.0| |**Key**|router.uptime| |**Value type**|Float| |**Units**|uptime| |**Étape de prétraitement : multiplicateur personnalisé**|0.01| ##### Example 2 Sending a delayed notification about a long-standing problem. To configure: - In Operations tab, set the *Default operation step duration* to '10h' (10 hours) - Set the escalation steps to be *From* '2' *To* '2' {width="600"} A notification will only be sent at Step 2 of the escalation scenario, or 10 hours after the problem starts. You can customize the message text to something like 'The problem is more than 10 hours old'. ##### Exemple 2 Envoi d'une notification différée concernant un problème de longue date. Configurer : - Dans l'onglet Opérations, définissez la *durée de l'étape d'opération par défaut* sur '10h' (10 heures) - Définissez les étapes d'escalade sur *De* '2' *À* '2' {width="600"} Une notification ne sera envoyée qu'à l'étape 2 du scénario d'escalade, ou 10 heures après le début du problème. Vous pouvez personnaliser le texte du message avec quelque chose comme "Le problème date de plus de 10 heures". ##### Example 2 Send simple POST requests to retrieve data from services such as Elasticsearch: - Create a POST item with URL: `http://localhost:9200/str/values/_search?scroll=10s` - Configure the following POST body to obtain the processor load (1 min average per core) ```{=html} <!-- --> ``` { "query": { "bool": { "must": [{ "match": { "itemid": 28275 } }], "filter": [{ "range": { "clock": { "gt": 1517565836, "lte": 1517566137 } } }] } } } - Received: ```{=html} <!-- --> ``` { "_scroll_id": "DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAAkFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAJRZZUTJWQVktVFNacU5nRHhlcEI0QUxRAAAAAAAAACYWWVEyVkFZLVRTWnFOZ0R4ZXBCNEFMUQAAAAAAAAAnFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAKBZZUTJWQVktVFNacU5nRHhlcEI0QUxR", "took": 18, "timed_out": false, "_shards": { "total": 5, "successful": 5, "skipped": 0, "failed": 0 }, "hits": { "total": 1, "max_score": 1.0, "hits": [{ "_index": "dbl", "_type": "values", "_id": "dqX9VWEBV6sEKSMyk6sw", "_score": 1.0, "_source": { "itemid": 28275, "value": "0.138750", "clock": 1517566136, "ns": 25388713, "ttl": 604800 } }] } } - Now use a JSONPath preprocessing step to get the item value: `$.hits.hits[0]._source.value` ##### Exemple 2 Envoyez des requêtes POST simples pour extraire des données de services tels que Elasticsearch : - Créez un élément POST avec l'URL : `http://localhost:9200/str/values/_search?scroll=10s` - Configurez le corps POST suivant pour obtenir la charge du processeur (moyenne 1 min par cœur) ```{=html} <!-- --> ``` { "query": { "bool": { "must": [{ "match": { "itemid": 28275 } }], "filter": [{ "range": { "clock": { "gt": 1517565836, "lte": 1517566137 } } }] } } } - Reçu : ```{=html} <!-- --> ``` { "_scroll_id": "DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAAkFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAJRZZUTJWQVktVFNacU5nRHhlcEI0QUxRAAAAAAAAACYWWVEyVkFZLVRTWnFOZ0R4ZXBCNEFMUQAAAAAAAAAnFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAKBZZUTJWQVktVFNacU5nRHhlcEI0QUxR", "took": 18, "timed_out": false, "_shards": { "total": 5, "successful": 5, "skipped": 0, "failed": 0 }, "hits": { "total": 1, "max_score": 1.0, "hits": [{ "_index": "dbl", "_type": "values", "_id": "dqX9VWEBV6sEKSMyk6sw", "_score": 1.0, "_source": { "itemid": 28275, "value": "0.138750", "clock": 1517566136, "ns": 25388713, "ttl": 604800 } }] } } - Utilisez maintenant une étape de prétraitement JSONPath pour obtenir la valeur de l’élément: `$.hits.hits[0]._source.value` ##### Example 2 Sum of latest values of all items matching net.if.in\[\*\] on the host. sum(last_foreach(/host/net.if.in[*])) ##### Exemple 2 Somme des dernières valeurs de tous les éléments correspondant à net.if.in\[\*\] sur l'hôte. sum(last_foreach(/host/net.if.in[*])) ##### 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: length(last(/host/web.test.error[Scenario]))>0 and last(/host/web.test.fail[Scenario])>0 Make sure to replace 'Scenario' with the real name of your scenario. ##### Exemple 2 Pour créer un déclencheur "Échec du scenario Web" avec une description de problème utile dans le nom du déclencheur, vous pouvez définir un déclencheur avec le nom suivant : Echec du scenario Web "Scenario": {ITEM.VALUE} Et l'expression de déclencheur : length(last(/host/web.test.error[Scenario]))>0 and last(/host/web.test.fail[Scenario])>0 Assurez-vous de remplacer 'Scenario' par le vrai nom de votre scénario. ##### Example 2 Use of host-level macro in the "CPU load is too high" trigger: `last(/ca_001/system.cpu.load[,avg1])>{$MAX_CPULOAD}` Such a trigger would be created on the template, not edited in individual hosts. ::: notetip If you want to use the amount of values as the function parameter (for example, **max(/host/key,\#3)**), include hash mark in the macro definition like this: SOME\_PERIOD => \#3 ::: ##### Exemple 2 Utilisation de la macro au niveau de l'hôte dans le déclencheur "La charge du processeur est trop élevée" : `last(/ca_001/system.cpu.load[,avg1])>{$MAX_CPULOAD}` Un tel déclencheur serait créé sur le modèle, et non modifié sur des hôtes individuels. ::: notetip Si vous souhaitez utiliser la quantité de valeurs comme paramètre de fonction (pour exemple, **max(/host/key,\#3)**), incluez le signe dièse dans la définition de la macro comme ceci : SOME\_PERIOD => \#3 ::: ##### Example 2 www.example.com is overloaded. last(/www.example.com/system.cpu.load[all,avg1])>5 or min(/www.example.com/system.cpu.load[all,avg1],10m)>2 The expression is true when either the current processor load is more than 5 or the processor load was more than 2 during last 10 minutes. ##### Exemple 2 www.example.com est surchargé. last(/www.example.com/system.cpu.load[all,avg1])>5 or min(/www.example.com/system.cpu.load[all,avg1],10m)>2 L'expression est vraie lorsque la charge actuelle du processeur est supérieure à 5 ou que la charge du processeur était supérieure à 2 au cours des 10 dernières minutes. ##### Example 3 Average processor load of host group 'MySQL Servers'. avg(last_foreach(/*/system.cpu.load[,avg1]?[group="MySQL Servers"])) ##### Exemple 3 Charge moyenne du processeur du groupe d'hôtes 'MySQL Servers'. avg(last_foreach(/*/system.cpu.load[,avg1]?[group="MySQL Servers"])) ##### Example 3 Calculating total bandwidth on eth0. Sum of two functions: last(//net.if.in[eth0,bytes])+last(//net.if.out[eth0,bytes]) ##### Exemple 3 Calcul de la bande passante totale sur eth0. Somme de deux fonctions : last(//net.if.in[eth0,bytes])+last(//net.if.out[eth0,bytes]) ##### Example 3 Checking if Zabbix API is alive, using [apiinfo.version](/manual/api/reference/apiinfo/version). - Item configuration:  Note the use of the POST method with JSON data, setting request headers and asking to return headers only: - Item value preprocessing with regular expression to get HTTP code:  - Checking the result in *Latest data*: {width="600"} ##### Exemple 3 Vérifier si l'API Zabbix est vivant en utilisant [apiinfo.version](/manual/api/reference/apiinfo/version). - Configuration de l'élément :  Notez l'utilisation de la méthode POST avec les données JSON, la définition des en-têtes de requête et le renvoi des en-têtes uniquement : - Prétraitement de la valeur d'élément avec une expression régulière pour obtenir le code HTTP :  - Vérification du résultat dans *Dernières données* : {width="600"} ##### Example 3 Escalating the problem to the Boss. In the first example above we configured periodical sending of messages to MySQL administrators. In this case, the administrators will get four messages before the problem will be escalated to the Database manager. Note that the manager will get a message only in case the problem is not acknowledged yet, supposedly no one is working on it. {width="600"} Details of Operation 2:  Note the use of {ESC.HISTORY} macro in the customized message. The macro will contain information about all previously executed steps on this escalation, such as notifications sent and commands executed. ##### Exemple 3 Faire remonter le problème au Boss. Dans le premier exemple ci-dessus, nous avons configuré l'envoi périodique de messages aux administrateurs MySQL. Dans ce cas, les administrateurs recevront quatre messages avant que le problème ne soit transmis au gestionnaire de base de données. Notez que le responsable ne recevra un message que si le problème n'est pas encore acquitté, c'est-à-dire que personne n'y travaille. {width="600"} Détails de l'opération 2 :  Notez l'utilisation de la macro {ESC.HISTORY} dans le message personnalisé. La macro contiendra des informations sur toutes les étapes précédemment exécutées sur cette escalade, telles que les notifications envoyées et les commandes exécutées. ##### Example 3 How many lines matching a regular expression in a file? UserParameter=wc[*],grep -c "$2" $1 This parameter can be used to calculate number of lines in a file. wc[/etc/passwd,root] wc[/etc/services,zabbix] ##### Exemple 3 Combien de lignes correspondent à une expression régulière dans un fichier ? UserParameter=wc[*],grep -c "$2" $1 Ce paramètre peut être utilisé pour calculer le nombre de ligne dans un fichier. wc[/etc/passwd,root] wc[/etc/services,zabbix] ##### Example 3 Message: Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})} MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)} MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)} When you receive the message, the message will be replaced by something like: Latest value: 1.45 MAX for 15 minutes: 2.33 MIN for 15 minutes: 1.01 ##### Exemple 3 Message : Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})} MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)} MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)} Lorsque vous recevez le message, le message sera remplacé par quelque chose comme : Latest value: 1.45 MAX for 15 minutes: 2.33 MIN for 15 minutes: 1.01 ##### Example 3 To create a "Web application is slow" trigger, you can define a trigger expression: last(/host/web.test.in[Scenario,,bps])<10000 Make sure to replace 'Scenario' with the real name of your scenario. ##### Exemple 3 Pour créer un déclencheur "Application Web lente", vous pouvez définir une expression de déclencheur : last(/host/web.test.in[Scenario,,bps])<10000 Assurez-vous de remplacer 'Scenario' par le vrai nom de votre scénario. ##### Example 3 Use of two macros in the "CPU load is too high" trigger: `min(/ca_001/system.cpu.load[,avg1],{$CPULOAD_PERIOD})>{$MAX_CPULOAD}` Note that a macro can be used as a parameter of trigger function, in this example function **min()**. ##### Exemple 3 Utilisation de deux macros dans le déclencheur "La charge CPU est trop élevée" : `min(/ca_001/system.cpu.load[,avg1],{$CPULOAD_PERIOD})>{$MAX_CPULOAD}` Notez qu'une macro peut être utilisée comme paramètre de la fonction de déclenchement, dans cet exemple la fonction **min()**. ##### Example 4 5-minute average of the number of queries per second for host group 'MySQL Servers'. avg(avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)) ##### Exemple 4 Moyenne sur 5 minutes du nombre de requêtes par seconde pour le groupe d'hôtes 'MySQL Servers'. avg(avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)) ##### Example 4 A more complex scenario. After multiple messages to MySQL administrators and escalation to the manager, Zabbix will try to restart the MySQL database. It will happen if the problem exists for 2:30 hours and it hasn't been acknowledged. If the problem still exists, after another 30 minutes Zabbix will send a message to all guest users. If this does not help, after another hour Zabbix will reboot server with the MySQL database (second remote command) using IPMI commands. {width="600"} ##### Exemple 4 Un scénario plus complexe. Après plusieurs messages aux administrateurs MySQL et une escalade vers le responsable, Zabbix essaiera de redémarrer la base de données MySQL. Cela se produira si le problème existe depuis 2h30 et qu'il n'a pas été acquitté. Si le problème persiste, après 30 minutes supplémentaires, Zabbix enverra un message à tous les utilisateurs invités. Si cela ne résout pas le problème, après une heure supplémentaire, Zabbix redémarrera le serveur avec la base de données MySQL (deuxième commande à distance) à l'aide des commandes IPMI. {width="600"} ##### Example 4 Calculating percentage of incoming traffic. More complex expression: 100*last(//net.if.in[eth0,bytes])/(last(//net.if.in[eth0,bytes])+last(//net.if.out[eth0,bytes])) See also: [Examples of aggregate calculations](/manual/config/items/itemtypes/calculated/aggregate#usage_examples) ##### Exemple 4 Calcul du pourcentage du trafic entrant. Expression plus complexe : 100*last(//net.if.in[eth0,bytes])/(last(//net.if.in[eth0,bytes])+last(//net.if.out[eth0,bytes])) Voir également : [Exemples de calculs agrégés](/manual/config/items/itemtypes/calculated/aggregate#usage_examples) ##### Example 4 Message: http://<server_ip_or_name>/zabbix/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} When you receive the message, it will contain a link to the *Event details* page, which provides information about the event, its trigger, and a list of latest events generated by the same trigger. ##### Exemple 4 Message : http://<server_ip_or_name>/zabbix/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} Lorsque vous recevez le message, il contient un lien vers la page *Détails de l'événement*, qui fournit des informations sur l'événement, son déclencheur et une liste des derniers événements générés par le même déclencheur. ##### Example 4 Retrieving weather information by connecting to the Openweathermap public service. - Configure a master item for bulk data collection in a single JSON:  Note the usage of macros in query fields. Refer to the [Openweathermap API](https://openweathermap.org/current) for how to fill them. Sample JSON returned in response to HTTP agent: ``` {.json} { "body": { "coord": { "lon": 40.01, "lat": 56.11 }, "weather": [{ "id": 801, "main": "Clouds", "description": "few clouds", "icon": "02n" }], "base": "stations", "main": { "temp": 15.14, "pressure": 1012.6, "humidity": 66, "temp_min": 15.14, "temp_max": 15.14, "sea_level": 1030.91, "grnd_level": 1012.6 }, "wind": { "speed": 1.86, "deg": 246.001 }, "clouds": { "all": 20 }, "dt": 1526509427, "sys": { "message": 0.0035, "country": "RU", "sunrise": 1526432608, "sunset": 1526491828 }, "id": 487837, "name": "Stavrovo", "cod": 200 } } ``` The next task is to configure dependent items that extract data from the JSON. - Configure a sample dependent item for humidity:  Other weather metrics such as 'Temperature' are added in the same manner. - Sample dependent item value preprocessing with JSONPath:  - Check the result of weather data in *Latest data*: {width="600"} ##### Exemple 4 Récupération des informations météorologiques en se connectant au service public Openweathermap. - Configurez un élément principal pour la collecte de données en bloc dans un seul JSON :  Notez l'utilisation de macros dans les champs de requête. Reportez-vous à l'API [Openweathermap](https://openweathermap.org/current) pour savoir comment les remplir. Exemple de code JSON renvoyé en réponse à l'agent HTTP : ``` {.json} { "body": { "coord": { "lon": 40.01, "lat": 56.11 }, "weather": [{ "id": 801, "main": "Clouds", "description": "few clouds", "icon": "02n" }], "base": "stations", "main": { "temp": 15.14, "pressure": 1012.6, "humidity": 66, "temp_min": 15.14, "temp_max": 15.14, "sea_level": 1030.91, "grnd_level": 1012.6 }, "wind": { "speed": 1.86, "deg": 246.001 }, "clouds": { "all": 20 }, "dt": 1526509427, "sys": { "message": 0.0035, "country": "RU", "sunrise": 1526432608, "sunset": 1526491828 }, "id": 487837, "name": "Stavrovo", "cod": 200 } } ``` La tâche suivante consiste à configurer les éléments dépendants qui extraient les données du JSON. - Configurez un élément dépendant pour l'humidité :  D'autres métriques météorologiques telles que 'Température' sont ajoutées de la même manière. - Exemple de prétraitement de la valeur de l'élément dépendant avec JSONPath :  - Vérifiez le résultat des données météorologiques dans *Dernières données* : {width="600"} ##### Example 4 Someone is downloading a large file from the Internet. Use of function min: min(/www.example.com/net.if.in[eth0,bytes],5m)>100K The expression is true when number of received bytes on eth0 is more than 100 KB within last 5 minutes. ##### Exemple 4 Quelqu'un télécharge une fichier volumineux sur Internet. Utilisation de la fonction min : min(/www.example.com/net.if.in[eth0,bytes],5m)>100K L'expression est vraie lorsque le nombre d'octets reçus sur eth0 est supérieur à 100 Ko au cours des 5 dernières minutes. ##### Example 4 Synchronize the agent unavailability condition with the item update interval: - define {$INTERVAL} macro and use it in the item update interval; - use {$INTERVAL} as parameter of the agent unavailability trigger: `nodata(/ca_001/agent.ping,{$INTERVAL})=1` ##### Exemple 4 Synchronisez la condition d'indisponibilité de l'agent avec l'intervalle de mise à jour de l'élément : - définir la macro {$INTERVAL} et l'utiliser dans l'intervalle de mise à jour de l'élément ; - utilisez {$INTERVAL} comme paramètre du déclencheur d'indisponibilité de l'agent : `nodata(/ca_001/agent.ping,{$INTERVAL})=1` ##### Example 5 An escalation with several operations assigned to one step and custom intervals used. The default operation step duration is 30 minutes. {width="600"} Notifications will be sent as follows: - to MySQL administrators at 0:00, 0:30, 1:00, 1:30 after the problem starts - to Database manager at 2:00 and 2:10 (and not at 3:00; seeing that steps 5 and 6 overlap with the next operation, the shorter custom step duration of 10 minutes in the next operation overrides the longer step duration of 1 hour tried to set here) - to Zabbix administrators at 2:00, 2:10, 2:20 after the problem starts (the custom step duration of 10 minutes working) - to guest users at 4:00 hours after the problem start (the default step duration of 30 minutes returning between steps 8 and 11) ##### Exemple 5 Une escalade avec plusieurs opérations affectées à une étape et des intervalles personnalisés utilisés. La durée de l'étape de fonctionnement par défaut est de 30 minutes. {width="600"} Les notifications seront envoyées comme suit : - aux administrateurs MySQL 0:00, 0:30, 1:00, 1:30 après le début du problème - au gestionnaire de base de données 2:00 et 2:10 après le début du problème (et non à 3:00 ; étant donné que les étapes 5 et 6 se chevauchent avec l'opération suivante, la durée d'étape personnalisée plus courte de 10 minutes dans l'opération suivante remplace la durée d'étape plus longue de 1 heure essayé de définir ici) - aux administrateurs Zabbix 2:00, 2:10, 2:20 après le début du problème (la durée de l'étape personnalisée de 10 minutes de travail) - aux utilisateurs invités 4:00 heures après le début du problème (la durée d'étape par défaut de 30 minutes revient entre les étapes 8 et 11) ##### Example 5 Average CPU load on all hosts in multiple host groups that have the specific tags. avg(last_foreach(/*/system.cpu.load?[(group="Servers A" or group="Servers B" or group="Servers C") and (tag="Service:" or tag="Importance:High")])) ##### Exemple 5 Charge CPU moyenne sur tous les hôtes dans plusieurs groupes d'hôtes qui ont des tags spécifiques. avg(last_foreach(/*/system.cpu.load?[(group="Servers A" or group="Servers B" or group="Servers C") and (tag="Service:" or tag="Importance:High")])) ##### Example 5 Both nodes of clustered SMTP server are down. Note use of two different hosts in one expression: last(/smtp1.example.com/net.tcp.service[smtp])=0 and last(/smtp2.example.com/net.tcp.service[smtp])=0 The expression is true when both SMTP servers are down on both smtp1.example.com and smtp2.example.com. ##### Exemple 5 Les deux nœuds du serveur SMTP en cluster sont arrêtés. Notez l'utilisation de deux hôtes différents dans une expression : last(/smtp1.example.com/net.tcp.service[smtp])=0 and last(/smtp2.example.com/net.tcp.service[smtp])=0 L'expression est vraie lorsque les deux serveurs SMTP sont en panne sur smtp1.example.com et smtp2.example.com. ##### Example 5 Connecting to Nginx status page and getting its metrics in bulk. - Configure Nginx following the [official guide](https://nginx.ru/en/docs/http/ngx_http_stub_status_module.html). ```{=html} <!-- --> ``` - Configure a master item for bulk data collection:  Sample Nginx stub status output: Active connections: 1 Active connections: server accepts handled requests 52 52 52 Reading: 0 Writing: 1 Waiting: 0 The next task is to configure dependent items that extract data. - Configure a sample dependent item for requests per second:  - Sample dependent item value preprocessing with regular expression `server accepts handled requests\s+([0-9]+) ([0-9]+) ([0-9]+)`: {width="600"} - Check the complete result from stub module in *Latest data*: {width="600"} ##### Exemple 5 Connexion à la page d'état de Nginx et obtention de ses métriques en masse. - Configurez Nginx en suivant le [guide officiel] (https://nginx.ru/en/docs/http/ngx_http_stub_status_module.html). ```{=html} <!-- --> ``` - Configurez un élément principal pour la collecte de données en masse :  Exemple de sortie d'état du stub Nginx : Active connections: 1 Active connections: server accepts handled requests 52 52 52 Reading: 0 Writing: 1 Waiting: 0 La tâche suivante consiste à configurer les éléments dépendants qui extraient les données. - Configurez un exemple d'élément dépendant pour les requêtes par seconde :  - Exemple de prétraitement de la valeur de l'élément dépendant avec une expression régulière `le serveur accepte les requêtes traitées\s+([0-9]+) ([0-9]+) ([0-9]+)` : {width="600"} - Vérifiez le résultat complet du module stub dans *Dernières données* : {width="600"} ##### Example 5 Informing about values from several hosts in a trigger expression. Message: Problem name: {TRIGGER.NAME} Trigger expression: {TRIGGER.EXPRESSION} 1. Item value on {HOST.NAME1}: {ITEM.VALUE1} ({ITEM.NAME1}) 2. Item value on {HOST.NAME2}: {ITEM.VALUE2} ({ITEM.NAME2}) When you receive the message, the message will be replaced by something like: Problem name: Processor load is too high on a local host Trigger expression: last(/Myhost/system.cpu.load[percpu,avg1])>5 or last(/Myotherhost/system.cpu.load[percpu,avg1])>5 1. Item value on Myhost: 0.83 (Processor load (1 min average per core)) 2. Item value on Myotherhost: 5.125 (Processor load (1 min average per core)) ##### Exemple 5 Informer sur les valeurs de plusieurs hôtes dans une expression de déclencheur. Message: Problem name: {TRIGGER.NAME} Trigger expression: {TRIGGER.EXPRESSION} 1. Item value on {HOST.NAME1}: {ITEM.VALUE1} ({ITEM.NAME1}) 2. Item value on {HOST.NAME2}: {ITEM.VALUE2} ({ITEM.NAME2}) Lorsque vous recevez le message, le message sera remplacé par quelque chose comme : Problem name: Processor load is too high on a local host Trigger expression: last(/Myhost/system.cpu.load[percpu,avg1])>5 or last(/Myotherhost/system.cpu.load[percpu,avg1])>5 1. Item value on Myhost: 0.83 (Processor load (1 min average per core)) 2. Item value on Myotherhost: 5.125 (Processor load (1 min average per core)) ##### Example 6 Calculation used on the latest item value sums of a whole host group. sum(last_foreach(/*/net.if.out[eth0,bytes]?[group="video"])) / sum(last_foreach(/*/nginx_stat.sh[active]?[group="video"])) ##### Exemple 6 Calcul utilisé sur les dernières sommes de valeur d'élément d'un groupe d'hôtes entier. sum(last_foreach(/*/net.if.out[eth0,bytes]?[group="video"])) / sum(last_foreach(/*/nginx_stat.sh[active]?[group="video"])) ##### Example 6 Receiving details of both the problem event and recovery event in a [recovery](/manual/config/notifications/action/recovery_operations) message: Message: Problem: Event ID: {EVENT.ID} Event value: {EVENT.VALUE} Event status: {EVENT.STATUS} Event time: {EVENT.TIME} Event date: {EVENT.DATE} Event age: {EVENT.AGE} Event acknowledgment: {EVENT.ACK.STATUS} Event update history: {EVENT.UPDATE.HISTORY} Recovery: Event ID: {EVENT.RECOVERY.ID} Event value: {EVENT.RECOVERY.VALUE} Event status: {EVENT.RECOVERY.STATUS} Event time: {EVENT.RECOVERY.TIME} Event date: {EVENT.RECOVERY.DATE} Operational data: {EVENT.OPDATA} When you receive the message, the macros will be replaced by something like: Problem: Event ID: 21874 Event value: 1 Event status: PROBLEM Event time: 13:04:30 Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: OK Event time: 13:10:07 Event date: 2018.01.02 Operational data: Current value is 0.83 ::: noteimportant Separate notification macros for the original problem event and recovery event are supported since Zabbix 2.2.0. ::: ##### Exemple 6 Réception des détails de l'événement de problème et de l'événement de récupération dans un message de [récupération](/manual/config/notifications/action/recovery_operations) : Message : Problème : Event ID: {EVENT.ID} Event value: {EVENT.VALUE} Event status: {EVENT.STATUS} Event time: {EVENT.TIME} Event date: {EVENT.DATE} Event age: {EVENT.AGE} Event acknowledgment: {EVENT.ACK.STATUS} Event update history: {EVENT.UPDATE.HISTORY} Récupération : Event ID: {EVENT.RECOVERY.ID} Event value: {EVENT.RECOVERY.VALUE} Event status: {EVENT.RECOVERY.STATUS} Event time: {EVENT.RECOVERY.TIME} Event date: {EVENT.RECOVERY.DATE} Operational data: {EVENT.OPDATA} Lorsque vous recevrez le message, les macros seront remplacées par quelque chose comme : Problème : Event ID: 21874 Event value: 1 Event status: PROBLEM Event time: 13:04:30 Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Récupération : Event ID: 21896 Event value: 0 Event status: OK Event time: 13:10:07 Event date: 2018.01.02 Operational data: Current value is 0.83 ::: noteimportant Les macros de notification distinctes pour l'événement de problème d'origine et l'événement de récupération sont prises en charge depuis Zabbix 2.2.0. ::: ##### Example 6 Use host prototype macro to configure items for discovered hosts: - on a host prototype define user macro {$SNMPVALUE} with {\#SNMPVALUE} [low-level discovery](/manual/config/macros/lld_macros) macro as a value:  - assign *Generic SNMPv2* template to the host prototype; - use {$SNMPVALUE} in the *SNMP OID* field of *Generic SNMPv2* template items. ##### Exemple 6 Utilisez la macro de prototype d'hôte pour configurer des éléments pour les hôtes découverts : - sur un prototype d'hôte, définissez la macro utilisateur {$SNMPVALUE} avec la macro {\#SNMPVALUE} de [découverte de bas niveau](/manual/config/macros/lld_macros) comme valeur :  - attribuer le modèle *Generic SNMPv2* au prototype hôte ; - utilisez {$SNMPVALUE} dans le champ *SNMP OID* des éléments de modèle *Generic SNMPv2*. ##### Example 6 Zabbix agent needs to be upgraded. Use of function find(): find(/example.example.com/agent.version,,"like","beta8")=1 The expression is true if Zabbix agent has version beta8. ##### Exemple 6 L'agent Zabbix doit être mis à jour. Utilisation de la fonction find() : find(/example.example.com/agent.version,,"like","beta8")=1 L'expression est vraie si l'agent Zabbix a la version beta8. ##### Example 7 Server is unreachable. count(/example.example.com/icmpping,30m,,"0")>5 The expression is true if host "example.example.com" is unreachable more than 5 times in the last 30 minutes. ##### Exemple 7 Le serveur est inaccessible. count(/example.example.com/icmpping,30m,,"0")>5 L'expression est vraie si l'hôte "example.example.com" est inaccessible plus de 5 fois au cours des 30 dernières minutes. ##### Example 7 The total number of unsupported items in host group 'Zabbix servers'. sum(last_foreach(/*/zabbix[host,,items_unsupported]?[group="Zabbix servers"])) ##### Exemple 7 Le nombre total d'éléments non pris en charge dans le groupe d'hôtes 'Zabbix servers'. sum(last_foreach(/*/zabbix[host,,items_unsupported]?[group="Zabbix servers"])) ##### Example 8 No heartbeats within last 3 minutes. Use of function nodata(): nodata(/example.example.com/tick,3m)=1 To make use of this trigger, 'tick' must be defined as a Zabbix [trapper](/manual/config/items/itemtypes/trapper) item. The host should periodically send data for this item using zabbix\_sender. If no data is received within 180 seconds, the trigger value becomes PROBLEM. *Note* that 'nodata' can be used for any item type. ##### Exemple 8 Aucun battement de cœur au cours des 3 dernières minutes. Utilisation de la fonction nodata() : nodata(/example.example.com/tick,3m)=1 Pour utiliser ce déclencheur, 'tick' doit être défini comme un élément Zabbix [trapper](/manual/config/items/itemtypes/trapper). L'hôte doit envoyer périodiquement des données pour cet élément en utilisant zabbix\_sender. Si aucune donnée n'est reçue dans les 180 secondes, la valeur de déclenchement devient PROBLÈME. *Notez* que 'nodata' peut être utilisé pour n'importe quel type d'élément. ##### Example configuration for Apache # .. ProxyPass "/" http://host/zabbix/ ProxyPassReverse "/" http://host/zabbix/ ProxyPassReverseCookiePath /zabbix / ProxyPassReverseCookieDomain host zabbix.example.com # .. ##### Exemple de configuration pour Apache # .. ProxyPass "/" http://host/zabbix/ ProxyPassReverse "/" http://host/zabbix/ ProxyPassReverseCookiePath /zabbix / ProxyPassReverseCookieDomain host zabbix.example.com # .. ##### Example configuration for nginx # .. location / { # .. proxy_cookie_path /zabbix /; proxy_pass http://192.168.0.94/zabbix/; # .. ##### Exemple de configuration pour nginx # .. location / { # .. proxy_cookie_path /zabbix /; proxy_pass http://192.168.0.94/zabbix/; # .. #### Example Getting memory usage of *apache* process. If using this OID syntax: HOST-RESOURCES-MIB::hrSWRunPerfMem["index","HOST-RESOURCES-MIB::hrSWRunPath", "/usr/sbin/apache2"] the index number will be looked up here: ... HOST-RESOURCES-MIB::hrSWRunPath.5376 = STRING: "/sbin/getty" HOST-RESOURCES-MIB::hrSWRunPath.5377 = STRING: "/sbin/getty" HOST-RESOURCES-MIB::hrSWRunPath.5388 = STRING: "/usr/sbin/apache2" HOST-RESOURCES-MIB::hrSWRunPath.5389 = STRING: "/sbin/sshd" ... Now we have the index, 5388. The index will be appended to the data OID in order to receive the value we are interested in: HOST-RESOURCES-MIB::hrSWRunPerfMem.5388 = INTEGER: 31468 KBytes #### Exemple Obtenir l'utilisation de la mémoire du processus *apache*. Si vous utilisez cette syntaxe d'OID : HOST-RESOURCES-MIB::hrSWRunPerfMem["index","HOST-RESOURCES-MIB::hrSWRunPath", "/usr/sbin/apache2"] Le numéro d'index sera recherché ici : ... HOST-RESOURCES-MIB::hrSWRunPath.5376 = STRING: "/sbin/getty" HOST-RESOURCES-MIB::hrSWRunPath.5377 = STRING: "/sbin/getty" HOST-RESOURCES-MIB::hrSWRunPath.5388 = STRING: "/usr/sbin/apache2" HOST-RESOURCES-MIB::hrSWRunPath.5389 = STRING: "/sbin/sshd" ... Maintenant que nous avons l'index 5388. L'index sera ajouté à l'OID de données afin de recevoir la valeur qui nous intéresse : HOST-RESOURCES-MIB::hrSWRunPerfMem.5388 = INTEGER: 31468 KBytes *Example:* Problem *Web camera 3 is down* has tags `type:video surveillance`, `floor:1st` and `name:webcam 3` and status *Warning* The service **Web camera 3** has the only problem tag specified: `name:webcam 3` {width=600} Service status will change from *OK* to *Warning* when this problem is detected. If the service **Web camera 3** had problem tags `name:webcam 3` and `floor:2nd`, its status would not be changed, when the problem is detected, because the conditions are only partially met. *Exemple:* Problème *La caméra Web 3 est en panne* a des tags `type:videosurveillance`, `floor:1st` et `name:webcam 3` et un statut *Warning* Le service **caméra Web 3** a le seul tag de problème spécifiée : `name:webcam 3` {width=600} L'état du service passera de *OK* à *Avertissement* lorsque ce problème sera détecté. Si le service **Caméra Web 3** avait des tags de problème `name:webcam 3` et `floor:2nd`, son statut ne serait pas modifié, lorsque le problème est détecté, car les conditions ne sont que partiellement remplies. ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemple ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples ### Examples ### Exemples #### Examples #### Exemples #### Examples #### Exemples #### Examples #### Exemples #### Examples #### Exemples #### Examples #### Exemples #### Examples **Example 1** # git checkout 6.0 # docker-compose -f ./docker-compose_v3_alpine_mysql_latest.yaml up -d The command will download latest Zabbix 6.0 images for each Zabbix component and run them in detach mode. ::: noteimportant Do not forget to download `.env_<type of component>` files from github.com official Zabbix repository with compose files. ::: **Example 2** # git checkout 6.0 # docker-compose -f ./docker-compose_v3_ubuntu_mysql_local.yaml up -d The command will download base image Ubuntu 20.04 (focal), then build Zabbix 6.0 components locally and run them in detach mode. #### Exemples **Exemple 1** # git checkout 6.0 # docker-compose -f ./docker-compose_v3_alpine_mysql_latest.yaml up -d La commande téléchargera les dernières images Zabbix 6.0 pour chaque composant Zabbix et les exécutera en mode détaché. ::: noteimportant N'oubliez pas de télécharger les fichiers `.env_<type de composant>` depuis le référentiel officiel Zabbix de github.com avec les fichiers compose. ::: **Exemple 2** # git checkout 6.0 # docker-compose -f ./docker-compose_v3_ubuntu_mysql_local.yaml up -d La commande téléchargera l'image de base Ubuntu 20.04 (focal), puis construira les composants Zabbix 5.4 localement et les exécutera en mode détaché. #### Examples Examples here illustrate how you can use macros in messages. #### Exemples Les exemples illustrent ici comment vous pouvez utiliser des macros dans les messages. #### Examples Examples of [global scripts](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script) that may be used as remote commands in action operations. #### Exemples Exemples de [scripts globaux](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script) pouvant être utilisés comme commandes distantes dans les opérations d'action. #### Examples Here are some code snippets showing how to add Zabbix protocol header to the data you want to send in order to obtain the packet you should send to Zabbix so that it is interpreted correctly. These code snippets assume that the data is not larger than 1GB, thus the large packet format is not used. ##### Python ```python packet = b"ZBXD\1" + struct.pack("<II", len(data), 0) + data ``` or ```python def zbx_create_header(plain_data_size, compressed_data_size=None): protocol = b"ZBXD" flags = 0x01 if compressed_data_size is None: datalen = plain_data_size reserved = 0 else: flags |= 0x02 datalen = compressed_data_size reserved = plain_data_size return protocol + struct.pack("<BII", flags, datalen, reserved) packet = zbx_create_header(len(data)) + data ``` ##### Perl ```perl my $packet = "ZBXD\1" . pack("(II)<", length($data), 0) . $data; ``` or ```perl sub zbx_create_header($;$) { my $plain_data_size = shift; my $compressed_data_size = shift; my $protocol = "ZBXD"; my $flags = 0x01; my $datalen; my $reserved; if (!defined($compressed_data_size)) { $datalen = $plain_data_size; $reserved = 0; } else { $flags |= 0x02; $datalen = $compressed_data_size; $reserved = $plain_data_size; } return $protocol . chr($flags) . pack("(II)<", $datalen, $reserved); } my $packet = zbx_create_header(length($data)) . $data; ``` ##### PHP ```php $packet = "ZBXD\1" . pack("VV", strlen($data), 0) . $data; ``` or ```php function zbx_create_header($plain_data_size, $compressed_data_size = null) { $protocol = "ZBXD"; $flags = 0x01; if (is_null($compressed_data_size)) { $datalen = $plain_data_size; $reserved = 0; } else { $flags |= 0x02; $datalen = $compressed_data_size; $reserved = $plain_data_size; } return $protocol . chr($flags) . pack("VV", $datalen, $reserved); } $packet = zbx_create_header(strlen($data)) . $data; ``` ##### Bash ```bash datalen=$(printf "%08x" ${#data}) datalen="\\x${datalen:6:2}\\x${datalen:4:2}\\x${datalen:2:2}\\x${datalen:0:2}" printf "ZBXD\1${datalen}\0\0\0\0%s" "$data" ``` #### Exemples Voici quelques extraits de code montrant comment ajouter un en-tête de protocole Zabbix aux données que vous souhaitez envoyer dans l'ordre pour obtenir le paquet que vous devez envoyer à Zabbix afin qu'il soit interprété correctement. Ces extraits de code supposent que les données ne dépassent pas 1 Go, le format de gros paquets n'est donc pas utilisé. #####Python ```python packet = b"ZBXD\1" + struct.pack("<II", len(data), 0) + data ``` ou ```python def zbx_create_header(plain_data_size, compressed_data_size=None): protocol = b"ZBXD" flags = 0x01 if compressed_data_size is None: datalen = plain_data_size reserved = 0 else: flags |= 0x02 datalen = compressed_data_size reserved = plain_data_size return protocol + struct.pack("<BII", flags, datalen, reserved) packet = zbx_create_header(len(data)) + data ``` ##### Perl ```perl my $packet = "ZBXD\1" . pack("(II)<", length($data), 0) . $data; ``` ou ```perl sub zbx_create_header($;$) { my $plain_data_size = shift; my $compressed_data_size = shift; my $protocol = "ZBXD"; my $flags = 0x01; my $datalen; my $reserved; if (!defined($compressed_data_size)) { $datalen = $plain_data_size; $reserved = 0; } else { $flags |= 0x02; $datalen = $compressed_data_size; $reserved = $plain_data_size; } return $protocol . chr($flags) . pack("(II)<", $datalen, $reserved); } my $packet = zbx_create_header(length($data)) . $data; ``` ##### PHP ```php $packet = "ZBXD\1" . pack("VV", strlen($data), 0) . $data; ``` ou ```php function zbx_create_header($plain_data_size, $compressed_data_size = null) { $protocol = "ZBXD"; $flags = 0x01; if (is_null($compressed_data_size)) { $datalen = $plain_data_size; $reserved = 0; } else { $flags |= 0x02; $datalen = $compressed_data_size; $reserved = $plain_data_size; } return $protocol . chr($flags) . pack("VV", $datalen, $reserved); } $packet = zbx_create_header(strlen($data)) . $data; ``` ##### Bash ```bash datalen=$(printf "%08x" ${#data}) datalen="\\x${datalen:6:2}\\x${datalen:4:2}\\x${datalen:2:2}\\x${datalen:0:2}" printf "ZBXD\1${datalen}\0\0\0\0%s" "$data" ``` ##### Examples Numeric (unsigned) value: {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":3,"name":"Agent availability","clock":1519304285,"ns":123456789,"value":1,"type":3} Numeric (float) value: {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":4,"name":"CPU Load","clock":1519304285,"ns":123456789,"value":0.1,"type":0} Character, text value: {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":2,"name":"Agent version","clock":1519304285,"ns":123456789,"value":"3.4.4","type":4} Log value: {"host":{"host":"Host A","name":"Host A visible"},"groups":["Group X","Group Y","Group Z"],"itemid":1,"name":"Messages in log file","clock":1519304285,"ns":123456789,"timestamp":1519304285,"source":"","severity":0,"eventid":0,"value":"log file message","type":2} ##### Exemples Valeur numérique (non signée) : {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":3,"name":"Agent availability","clock":1519304285,"ns":123456789,"value":1,"type":3} Valeur numérique (float) : {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":4,"name":"CPU Load","clock":1519304285,"ns":123456789,"value":0.1,"type":0} Valeur textuelle ou caractère : {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":2,"name":"Agent version","clock":1519304285,"ns":123456789,"value":"3.4.4","type":4} Valeur de log : {"host":{"host":"Host A","name":"Host A visible"},"groups":["Group X","Group Y","Group Z"],"itemid":1,"name":"Messages in log file","clock":1519304285,"ns":123456789,"timestamp":1519304285,"source":"","severity":0,"eventid":0,"value":"log file message","type":2} ##### Examples Numeric (unsigned) value: {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":3,"name":"Agent availability","clock":1519311600,"count":60,"min":1,"avg":1,"max":1,"type":3} Numeric (float) value: {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":4,"name":"CPU Load","clock":1519311600,"count":60,"min":0.01,"avg":0.15,"max":1.5,"type":0} ##### Exemples Valeur numérique (non signée) : {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":3,"name":"Agent availability","clock":1519311600,"count":60,"min":1,"avg":1,"max":1,"type":3} Valeur numérique (float) : {"host":{"host":"Host B","name":"Host B visible"},"groups":["Group X","Group Y","Group Z"],"itemid":4,"name":"CPU Load","clock":1519311600,"count":60,"min":0.01,"avg":0.15,"max":1.5,"type":0} ##### Examples of correct/incorrect syntax Expressions (including function calls) cannot be used as history, trend, or foreach [function](/manual/appendix/functions) parameters. However, those functions themselves can be used in other (non-historical) function parameters. |Expression|Example| |-|---------| |Valid|`avg(last(/host/key1),last(/host/key2)*10,last(/host/key1)*100)`<br>`max(avg(avg_foreach(/*/system.cpu.load?[group="Servers A"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers B"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers C"],5m)))`| |Invalid|`sum(/host/key,10+2)`<br>`sum(/host/key, avg(10,2))`<br>`sum(/host/key,last(/host/key2))`| Note that in an expression like: sum(sum_foreach(//resptime[*],5m))/sum(count_foreach(//resptime[*],5m)) it cannot be guaranteed that both parts of the equation will always have the same set of values. While one part of the expression is evaluated, a new value for the requested period may arrive and then the other part of the expression will have a different set of values. ##### Exemples de syntaxe correcte/incorrecte Les expressions (y compris les appels de fonction) ne peuvent pas être utilisées comme paramètres d'historique, de tendance ou de la [fonction](/manual/appendix/functions) foreach. Cependant, ces fonctions elles-mêmes peuvent être utilisées dans d'autres paramètres de fonction (non historiques). |Expression|Exemple| |-|---------| |Valide|`avg(last(/host/key1),last(/host/key2)*10,last(/host/key1)*100)`<br>`max(avg(avg_foreach(/*/system.cpu.load?[group="Servers A"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers B"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers C"],5m)))`| |Invalide|`sum(/host/key,10+2)`<br>`sum(/host/key, avg(10,2))`<br>`sum(/host/key,last(/host/key2))`| Notez que dans une expression comme : sum(sum_foreach(//resptime[*],5m))/sum(count_foreach(//resptime[*],5m)) il ne peut être garanti que les deux parties de l'équation auront toujours le même ensemble de valeurs. Pendant qu'une partie de l'expression est évaluée, une nouvelle valeur pour la période demandée peut arriver, puis l'autre partie de l'expression aura un ensemble de valeurs différent. #### Examples of hardware configuration The table provides examples of hardware configuration, assuming a **Linux/BSD/Unix** platform. These are size and hardware configuration examples to start with. Each Zabbix installation is unique. Make sure to benchmark the performance of your Zabbix system in a staging or development environment, so that you can fully understand your requirements before deploying the Zabbix installation to its production environment. |Installation size|Monitored metrics^**1**^|CPU/vCPU cores|Memory<br>(GiB)|Database|Amazon EC2^**2**^| |-|-|-|-|-|-| |Small|1 000|2|8|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL|m6i.large/m6g.large| |Medium|10 000|4|16|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL|m6i.xlarge/m6g.xlarge| |Large|100 000|16|64|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL,<br>Oracle|m6i.4xlarge/m6g.4xlarge| |Very large|1 000 000|32|96|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL,<br>Oracle|m6i.8xlarge/m6g.8xlarge| ^**1**^ 1 metric = 1 item + 1 trigger + 1 graph<br> ^**2**^ Example with Amazon general purpose EC2 instances, using ARM64 or x86_64 architecture, a proper instance type like Compute/Memory/Storage optimised should be selected during Zabbix installation evaluation and testing before installing in its production environment. ::: noteclassic Actual configuration depends on the number of active items and refresh rates very much (see [database size](/manual/installation/requirements#Database_size) section of this page for details). It is highly recommended to run the database on a separate box for large installations. ::: #### Exemples de configuration matérielle Le tableau fournit des exemples de configuration matérielle, en supposant une plate-forme **Linux/BSD/Unix**. Ce sont des exemples de taille et de configuration matérielle pour commencer. Chaque installation Zabbix est unique. Assurez-vous de comparer les performances de votre système Zabbix dans un environnement de test ou de développement, afin de bien comprendre vos besoins avant de déployer l'installation de Zabbix dans son environnement de production. |Taille de l'installation|Métriques surveillées^**1**^|Cœurs de CPU/vCPU|Mémoire<br>(Gio)|Base de données|Amazon EC2^**2**^| |-|-|-|-|-|-| |Petite|1 000|2|8|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL|m6i.large/m6g.large| |Moyenne|10 000|4|16|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL|m6i.xlarge/m6g.xlarge| |Grande|100 000|16|64|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL,<br>Oracle|m6i.4xlarge/m6g.4xlarge| |Très grande|1 000 000|32|96|MySQL Server,<br>Percona Server,<br>MariaDB Server,<br>PostgreSQL,<br>Oracle|m6i.8xlarge/m6g.8xlarge| ^**1**^ 1 métrique = 1 élément + 1 déclencheur + 1 graphique<br> ^**2**^ Exemple avec des instances EC2 à usage général d'Amazon, utilisant l'architecture ARM64 ou x86_64, un type d'instance approprié tel que Calcul/Mémoire/Storage optimisé doit être sélectionné lors de l'évaluation et des tests d'installation de Zabbix avant l'installation dans son environnement de production. ::: noteclassic La configuration réelle dépend beaucoup du nombre d'éléments actifs et des taux de rafraîchissement (voir la section [taille de la base de données](/manual/installation/requirements#Database_size) de cette page pour plus de détails). Il est fortement recommandé d'exécuter la base de données sur un serveur séparé pour les grandes installations. ::: #### Examples of OS/hardware configuration The table provides examples of OS/hardware configurations: ||Installation size/OS version<br>(dedicated servers/on-prem/virtual/clouds)|<|<|<|Containers base|Large/very large installations<br>(dedicated servers/on-prem/virtual/clouds)|<|<|<| |--|-|-|-|-|-|-|-|-|-| | |Small|Medium|Large|Very large|All|Database|Server|Frontend|Proxy| |**Linux-based operating systems**|<|<|<|<|<|<|<|<|<| |*Alma Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Alpine*|3.14-3.16+|<|<|<|+|+|+|+|+| |*Amazon Linux*|Preview release^**1**^|<|<|<| |+|+|+|+| |*Debian*|11+|<|-|<| | | | | | |*OpenSUSE*|15.4+|<|-|<| | | | | | |*Oracle Linux*|8+, 9+|<|<|<|+|+|+|+|+| |*Raspbian*|11+|-|<|<| | | | | | |*Rocky Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Red Hat Enterprise Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Red Hat Enterprise Linux (UBI)*|8+, 9+|<|<|<|+| | | | | |*SUSE Linux Enterprise*|15.4+|<|<|<| |+|+|+|+| |*Ubuntu LTS*|20.04+, 22.04+|<|<|<|+|+|+|+|+| |**UNIX/BSD/other operating systems**|<|<|<|<|<|<|<|<|<| | | | | | |Jails/Zones/LPAR| | | | | |*FreeBSD*|13.1+|<|<|<|+|+|+|+|+| |*HP-UX*|HP-UX 11i v3|<|<|<| | |+|+|+| |*IBM AIX*|AIX 7.3+|<|<|<|+|+|+|+|+| |*macOS*|12.4+|<|-|<| | | | | | |*NetBSD*|9+|<|-|<|+| | | |+| |*OmniOS*|Long-term support (LTS) release|<|<|<|+|+|+|+|+| |*OpenBSD*|7.1+|<|-|<|+| | | |+| |*Solaris*|11.4+|<|<|<|+|+|+|+|+| ##### Exemples de configuration OS/matérielle Le tableau fourni plusieurs exemples de configuration OS/matérielle : ||Taille de l'installation/version du système d'exploitation<br>(serveurs dédiés/on-prem/virtuel/clouds)|<|<|<|Base de conteneurs|Grandes/très grandes installations<br>(serveurs dédiés/on-mre/virtuels/clouds)|<|<|<| |--|-|-|-|-|-|-|-|-|-| | |Petit|Moyen|Grand|Très grand|Tous|Base de données|Serveur|Frontend|Proxy| |**Linux-based operating systems**|<|<|<|<|<|<|<|<|<| |*Alma Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Alpine*|3.14-3.16+|<|<|<|+|+|+|+|+| |*Amazon Linux*|Preview release^**1**^|<|<|<| |+|+|+|+| |*Debian*|11+|<|-|<| | | | | | |*OpenSUSE*|15.4+|<|-|<| | | | | | |*Oracle Linux*|8+, 9+|<|<|<|+|+|+|+|+| |*Raspbian*|11+|-|<|<| | | | | | |*Rocky Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Red Hat Enterprise Linux*|8+, 9+|<|<|<| |+|+|+|+| |*Red Hat Enterprise Linux (UBI)*|8+, 9+|<|<|<|+| | | | | |*SUSE Linux Enterprise*|15.4+|<|<|<| |+|+|+|+| |*Ubuntu LTS*|20.04+, 22.04+|<|<|<|+|+|+|+|+| |**UNIX/BSD/autres systèmes d'exploitation**|<|<|<|<|<|<|<|<|<| | | | | | |Jails/Zones/LPAR| | | | | |*FreeBSD*|13.1+|<|<|<|+|+|+|+|+| |*HP-UX*|HP-UX 11i v3|<|<|<| | |+|+|+| |*IBM AIX*|AIX 7.3+|<|<|<|+|+|+|+|+| |*macOS*|12.4+|<|-|<| | | | | | |*NetBSD*|9+|<|-|<|+| | | |+| |*OmniOS*|Long-term support (LTS) release|<|<|<|+|+|+|+|+| |*OpenBSD*|7.1+|<|-|<|+| | | |+| |*Solaris*|11.4+|<|<|<|+|+|+|+|+| ##### Examples of simple user parameters A simple command: UserParameter=ping,echo 1 The agent will always return '1' for an item with 'ping' key. A more complex example: UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive The agent will return '1', if MySQL server is alive, '0' - otherwise. ##### Exemples de paramètres utilisateur simples Une commande simple : UserParameter=ping,echo 1 L'agent renverra toujours '1' pour une élément avec la clé 'ping'. Un exemple plus complexe : UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive L'agent renverra '1', si le serveur MySQL est actif, '0' - sinon. #### Examples of triggers #### Exemples de déclencheurs ##### Examples Problem: {"clock":1519304285,"ns":123456789,"value":1,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"eventid":42, "hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} Recovery: {"clock":1519304345,"ns":987654321,"value":0,"eventid":43,"p_eventid":42} Problem (multiple problem event generation): {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} Recovery: {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":43} {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":42} ##### Exemples Problème : {"clock":1519304285,"ns":123456789,"value":1,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"eventid":42, "hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} Récupération : {"clock":1519304345,"ns":987654321,"value":0,"eventid":43,"p_eventid":42} Problème (génération multiple d'événements problème) : {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]} Récupération : {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":43} {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":42} ### Examples Request: ``` {.java} { "jsonrpc": "2.0", "method": "authentication.update", "params": { "http_auth_enabled": 1, "http_case_sensitive": 0, "http_login_form": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ "http_auth_enabled", "http_case_sensitive", "http_login_form" ], "id": 1 } ``` ### Exemples Requête : ``` {.java} { "jsonrpc": "2.0", "method": "authentication.update", "params": { "http_auth_enabled": 1, "http_case_sensitive": 0, "http_login_form": 1 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ "http_auth_enabled", "http_case_sensitive", "http_login_form" ], "id": 1 } ``` ### Examples Request: ``` {.java} { "jsonrpc": "2.0", "method": "autoregistration.update", "params": { "tls_accept": "3", "tls_psk_identity": "PSK 001", "tls_psk": "11111595725ac58dd977beef14b97461a7c1045b9a1c923453302c5473193478" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` ### Exemples Requête : ``` {.java} { "jsonrpc": "2.0", "method": "autoregistration.update", "params": { "tls_accept": "3", "tls_psk_identity": "PSK 001", "tls_psk": "11111595725ac58dd977beef14b97461a7c1045b9a1c923453302c5473193478" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` ### Examples Request: ``` {.java} { "jsonrpc": "2.0", "method": "housekeeping.update", "params": { "hk_events_mode": "1", "hk_events_trigger": "200d", "hk_events_internal": "2d", "hk_events_discovery": "2d" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ "hk_events_mode", "hk_events_trigger", "hk_events_internal", "hk_events_discovery" ], "id": 1 } ``` ### Exemples Requête : ``` {.java} { "jsonrpc": "2.0", "method": "housekeeping.update", "params": { "hk_events_mode": "1", "hk_events_trigger": "200d", "hk_events_internal": "2d", "hk_events_discovery": "2d" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ "hk_events_mode", "hk_events_trigger", "hk_events_internal", "hk_events_discovery" ], "id": 1 } ``` ### Examples Request: ```json { "jsonrpc": "2.0", "method": "settings.update", "params": { "login_attempts": "1", "login_block": "1m" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ "login_attempts", "login_block" ], "id": 1 } ``` ### Exemples Requête : ```json { "jsonrpc": "2.0", "method": "settings.update", "params": { "login_attempts": "1", "login_block": "1m" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ "login_attempts", "login_block" ], "id": 1 } ``` ### Examples Request: ```json { "jsonrpc": "2.0", "method": "user.checkAuthentication", "params": { "sessionid": "673b8ba11562a35da902c66cf5c23fa2" }, "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "userid": "1", "username": "Admin", "name": "Zabbix", "surname": "Administrator", "url": "", "autologin": "1", "autologout": "0", "lang": "ru_RU", "refresh": "0", "theme": "default", "attempt_failed": "0", "attempt_ip": "127.0.0.1", "attempt_clock": "1355919038", "rows_per_page": "50", "timezone": "Europe/Riga", "roleid": "3", "type": 3, "sessionid": "673b8ba11562a35da902c66cf5c23fa2" "debug_mode": 0, "userip": "127.0.0.1", "gui_access": 0 }, "id": 1 } ``` ::: noteclassic Response is similar to [User.login](/manual/api/reference/user/login) call response with "userData" parameter set to true (the difference is that user data is retrieved by session id and not by username / password). ::: ### Exemples Requête : ```json { "jsonrpc": "2.0", "method": "user.checkAuthentication", "params": { "sessionid": "673b8ba11562a35da902c66cf5c23fa2" }, "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "userid": "1", "username": "Admin", "name": "Zabbix", "surname": "Administrator", "url": "", "autologin": "1", "autologout": "0", "lang": "ru_RU", "refresh": "0", "theme": "default", "attempt_failed": "0", "attempt_ip": "127.0.0.1", "attempt_clock": "1355919038", "rows_per_page": "50", "timezone": "Europe/Riga", "roleid": "3", "type": 3, "sessionid": "673b8ba11562a35da902c66cf5c23fa2" "debug_mode": 0, "userip": "127.0.0.1", "gui_access": 0 }, "id": 1 } ``` ::: noteclassic La réponse est similaire à la réponse à l'appel [User.login](/manual/api/reference/user/login) avec le paramètre "userData" défini sur vrai (la différence est que les données utilisateur sont récupérées par identifiant de session et non par nom d'utilisateur/mot de passe) . ::: ### Examples The following examples aim to only describe the configuration of the dashboard widget field objects for the *Map* widget. For more information on configuring a dashboard, see [`dashboard.create`](/manual/api/reference/dashboard/create). ### Exemples Les exemples suivants visent à décrire uniquement la configuration des objets de champ du widget de tableau de bord pour le widget *Map*. Pour plus d'informations sur la configuration d'un tableau de bord, consultez [`dashboard.create`](/manual/api/reference/dashboard/create). ### Examples The following examples aim to only describe the configuration of the dashboard widget field objects for the *Plain text* widget. For more information on configuring a dashboard, see [`dashboard.create`](/manual/api/reference/dashboard/create). ### Exemples Les exemples suivants visent à décrire uniquement la configuration des objets de champ du widget de tableau de bord pour le widget *Texte brut*. Pour plus d'informations sur la configuration d'un tableau de bord, consultez [`dashboard.create`](/manual/api/reference/dashboard/create). ### Examples The following examples aim to only describe the configuration of the dashboard widget field objects for the *Problem hosts* widget. For more information on configuring a dashboard, see [`dashboard.create`](/manual/api/reference/dashboard/create). ### Exemples Les exemples suivants visent à décrire uniquement la configuration des objets de champ du widget de tableau de bord pour le widget *Hôtes problématiques*. Pour plus d'informations sur la configuration d'un tableau de bord, consultez [`dashboard.create`](/manual/api/reference/dashboard/create). #### Examples The ways in which macro functions can be used to customize macro values is illustrated in the following examples on received values: |Received value|Macro|Output| |----|----|----| |`24.3413523`|`{{ITEM.VALUE}.fmtnum(2)}`|`24.34`| |`24.3413523`|`{{ITEM.VALUE}.fmtnum(0)}`|`24`| |`12:36:01`|`{{TIME}.fmttime(%B)}`|`October`| |`12:36:01`|`{{TIME}.fmttime(%d %B,-1M/M)}`|`1 September`| |`123Log line`|`{{ITEM.VALUE}.regsub(^[0-9]+, Problem)}`|`Problem`| |`123 Log line`|`{{ITEM.VALUE}.regsub("^([0-9]+)", "Problem")}`|`Problem`| |`123 Log line`|`{{ITEM.VALUE}.regsub("^([0-9]+)", Problem ID: \1)}`|`Problem ID: 123`| |`Log line`|`{{ITEM.VALUE}.regsub(".*", "Problem ID: \1")}`|''Problem ID: ''| |`MySQL crashed errno 123`|`{{ITEM.VALUE}.regsub("^(\w+).*?([0-9]+)", " Problem ID: \1_\2 ")}`|'' Problem ID: MySQL\_123 ''| |`123 Log line`|`{{ITEM.VALUE}.regsub("([1-9]+", "Problem ID: \1")}`|`*UNKNOWN*` (invalid regular expression)| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+)", \1)}`|`customername`| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+)", \2)}`|`1`| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+", \1)}`|`{{#IFALIAS}.regsub("(.*)_([0-9]+", \1)}` (invalid regular expression)| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}"}`|`{$MACRO:"customername"}`| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \2)}"}`|`{$MACRO:"1"}`| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+\", \1)}"}`|`{$MACRO:"{{#M}.regsub(\"(.*)_([0-9]+\", \1)}"}` (invalid regular expression)| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+)\\", \1)}\"}"`|`"{$MACRO:\"customername\"}"`| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+)\\", \2)}\"}"`|`"{$MACRO:\"1\"}")`| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+\\", \1)}\"}"`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+\\", \1)}\"}")` (invalid regular expression)| ##### Seeing full item values Long values of resolved {ITEM.VALUE} and {ITEM.LASTVALUE} macros are truncated to 20 characters. To see the full values of these macros you may use macro functions, e.g.: `{{ITEM.VALUE}.regsub("(.*)", \1)}`<br> `{{ITEM.LASTVALUE}.regsub("(.*)", \1)}` #### Exemples Les façons dont les fonctions de macro peuvent être utilisées pour personnaliser les valeurs de macro sont illustrées dans les exemples suivants sur les valeurs reçues : |Valeur reçue|Macro|Sortie| |----|----|----| |`24.3413523`|`{{ITEM.VALUE}.fmtnum(2)}`|`24.34`| |`24.3413523`|`{{ITEM.VALUE}.fmtnum(0)}`|`24`| |`12:36:01`|`{{TIME}.fmttime(%B)}`|`October`| |`12:36:01`|`{{TIME}.fmttime(%d %B,-1M/M)}`|`1 September`| |`123Log line`|`{{ITEM.VALUE}.regsub(^[0-9]+, Problem)}`|`Problem`| |`123 Log line`|`{{ITEM.VALUE}.regsub("^([0-9]+)", "Problem")}`|`Problem`| |`123 Log line`|`{{ITEM.VALUE}.regsub("^([0-9]+)", Problem ID: \1)}`|`Problem ID: 123`| |`Log line`|`{{ITEM.VALUE}.regsub(".*", "Problem ID: \1")}`|''Problem ID: ''| |`MySQL crashed errno 123`|`{{ITEM.VALUE}.regsub("^(\w+).*?([0-9]+)", " Problem ID: \1_\2 ")}`|'' Problem ID: MySQL\_123 ''| |`123 Log line`|`{{ITEM.VALUE}.regsub("([1-9]+", "Problem ID: \1")}`|`*UNKNOWN*` (invalid regular expression)| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+)", \1)}`|`customername`| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+)", \2)}`|`1`| |`customername_1`|`{{#IFALIAS}.regsub("(.*)_([0-9]+", \1)}`|`{{#IFALIAS}.regsub("(.*)_([0-9]+", \1)}` (invalid regular expression)| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}"}`|`{$MACRO:"customername"}`| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \2)}"}`|`{$MACRO:"1"}`| |`customername_1`|`{$MACRO:"{{#IFALIAS}.regsub(\"(.*)_([0-9]+\", \1)}"}`|`{$MACRO:"{{#M}.regsub(\"(.*)_([0-9]+\", \1)}"}` (invalid regular expression)| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+)\\", \1)}\"}"`|`"{$MACRO:\"customername\"}"`| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+)\\", \2)}\"}"`|`"{$MACRO:\"1\"}")`| |`customername_1`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+\\", \1)}\"}"`|`"{$MACRO:\"{{#IFALIAS}.regsub(\\"(.*)_([0-9]+\\", \1)}\"}")` (invalid regular expression)| ##### Affichage des valeurs complètes des éléments Les valeurs longues des macros {ITEM.VALUE} et {ITEM.LASTVALUE} résolues sont tronquées à 20 caractères. Pour voir les valeurs complètes de ces macros, vous pouvez utiliser des fonctions de macro, par exemple : `{{ITEM.VALUE}.regsub("(.*)", \1)}`<br> `{{ITEM.LASTVALUE}.regsub("(.*)", \1)}` #### Examples Working hours. Monday - Friday from 9:00 till 18:00: 1-5,09:00-18:00 Working hours plus weekend. Monday - Friday from 9:00 till 18:00 and Saturday, Sunday from 10:00 till 16:00: 1-5,09:00-18:00;6-7,10:00-16:00 #### Exemples Heures d'ouverture. Lundi - Vendredi de 9h00 à 18h00 : 1-5,09:00-18:00 Horaires de travail plus week-end. Lundi - Vendredi de 9h00 à 18h00 et Samedi, Dimanche de 10h00 à 16h00 : 1-5,09:00-18:00;6-7,10:00-16:00 ## EXAMPLES **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH} ## EXEMPLES **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH} ## EXAMPLES **zabbix\_js -s script-file.js -p example** [ ]{#lbAG} ## EXEMPLES **zabbix\_js -s script-file.js -p example** [ ]{#lbAG} ## EXAMPLES **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of monitored host. Use monitored host and Zabbix server defined in agent configuration file. **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\ Send **342.45** as the value for **mysql.queries** item of **Monitored Host** host using Zabbix server defined in agent configuration file. \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt** \ Send values from file **data\_values.txt** to Zabbix server with IP **192.168.1.113**. Host names and keys are defined in the file. \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\ Send a timestamped value from the commandline to Zabbix server, specified in the agent configuration file. Dash in the input data indicates that hostname also should be used from the same configuration file. \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\ Send empty value of an item to the Zabbix server with IP address **192.168.1.113** on port **10000** from the commandline. Empty values must be indicated by empty double quotes. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with certificate. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\ Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with pre-shared key (PSK). [ ]{#lbAI} ## EXEMPLES **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\ Envoyer **342.45** comme valeur pour l'élément **mysql.queries** de l'hôte surveillé. Utiliser l'hôte surveillé et le serveur Zabbix définis dans le fichier de configuration de l'agent. **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\ Envoyer **342.45** comme valeur pour l'élément **mysql.queries** de l'hôte **Monitored Host** utilisant le serveur Zabbix défini dans le fichier de configuration de l'agent. \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt** \ Envoyer les valeurs du fichier **data\_values.txt** au serveur Zabbix avec l'IP **192.168.1.113**. Les noms d'hôte et les clés sont définis dans le fichier. \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\ Envoyer une valeur horodatée depuis la ligne de commande au serveur Zabbix, spécifiée dans le fichier de configuration de l'agent. Le tiret dans les données d'entrée indique que le nom d'hôte doit également être utilisé à partir du même fichier de configuration. \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\ Envoyer la valeur vide d'un élément au serveur Zabbix avec l'adresse IP **192.168.1.113** sur le port **10000** à partir de la ligne de commande. Les valeurs vides doivent être indiquées par des guillemets doubles vides. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\ Envoyez **342.45** comme valeur pour l'élément **mysql.queries** de l'hôte **Monitored Host** au serveur avec l'IP **192.168.1.113** en utilisant TLS avec certificat. **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\ Envoyez **342.45** comme valeur pour l'élément **mysql.queries** de l'hôte **Monitored Host** au serveur avec l'IP **192.168.1.113** en utilisant TLS avec la clé pré-partagée (PSK). [ ]{#lbAI} ##### Example with an inline regex modifier Use of the following regular expression including an inline modifier (?i) to match the characters "error": (?i)error  Chosen *Expression type*: "Result is TRUE". Characters "error" are matched. ##### Exemple avec un modificateur de regex en ligne Utilisation de l'expression régulière suivante incluant un modificateur en ligne (?i) pour faire correspondre les caractères "error": (?i)error  *Type d'expression* choisi : "Le résultat est VRAI". Les caractères "error" sont mis en correspondance. ### Example workflow The following section will walk you through some usage examples in more detail. ### Exemple de flux de travail La section suivante vous guidera à travers quelques exemples d'utilisation plus détaillés. #### Exit code Before version 2.2 Zabbix agent returned 0 in case of successful exit and 255 in case of failure. Starting from version 2.2 and higher Zabbix agent returns 0 in case of successful exit and 1 in case of failure. #### Code de sortie Avant la version 2.2, l'agent Zabbix renvoyait 0 en cas de sortie réussie et 255 en cas d'échec. A partir de la version 2.2 et supérieure, l'agent Zabbix renvoie 0 en cas de réussite et 1 en cas d'échec. #### Exit codes Starting from version 4.4.8 Zabbix agent 2 can also be compiled with older OpenSSL versions (1.0.1, 1.0.2). In this case Zabbix provides mutexes for locking in OpenSSL. If a mutex lock or unlock fails then an error message is printed to the standard error stream (STDERR) and Agent 2 exits with return code 2 or 3, respectively. #### Codes de sortie À partir de la version 4.4.8, l'agent Zabbix 2 peut également être compilé avec les anciennes versions d'OpenSSL (1.0.1, 1.0.2). Dans ce cas, Zabbix fournit des mutex pour le verrouillage dans OpenSSL. Si un verrouillage ou un déverrouillage mutex échoue, un message d'erreur est écrit dans le flux d'erreurs standard (STDERR) et l'agent 2 quitte avec le code de retour 2 ou 3, respectivement. ## EXIT STATUS The exit status is 0 if the values were sent and all of them were successfully processed by server. If data was sent, but processing of at least one of the values failed, the exit status is 2. If data sending failed, the exit status is 1. [ ]{#lbAH} ## ETAT DE SORTIE L'état de sortie est 0 si les valeurs ont été envoyées et qu'elles ont toutes été traitées avec succès par le serveur. Si des données ont été envoyées, mais que le traitement d'au moins une des valeurs a échoué, l'état de sortie est 2. Si l'envoi des données a échoué, l'état de sortie est 1. [ ]{#lbAH} ### Expandable lists in latest data subfilter Expandable lists have been introduced in the [latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) subfilter: - For each entity group (e.g. tags, hosts) up to 10 rows of entities are now displayed. If there are more entities, this list can be expanded to a maximum of 1000 entries (the value of SUBFILTER_VALUES_PER_GROUP in [frontend definitions](/manual/web_interface/definitions)) by clicking on a three-dot icon displayed at the end. Previously a non-expandable maximum of 100 entries was the limit. - In the list of *Tag values* up to 10 rows of tag names are now displayed. If there are more tag names with values, this list can be expanded to a maximum of 200 tag names by clicking on a three-dot icon displayed at the bottom. Previously, a non-expandable maximum of 20 rows with tag names was the limit. For each tag name up to 10 rows of values are displayed (expandable to 1000 entries (the value of SUBFILTER_VALUES_PER_GROUP in [frontend definitions](/manual/web_interface/definitions))). ### Listes extensibles dans le sous-filtre des dernières données Des listes extensibles ont été introduites dans le sous-filtre des [dernières données](/manual/web_interface/frontend_sections/monitoring/latest_data) : - Pour chaque groupe d'entités (par exemple, tags, hôtes), jusqu'à 10 lignes d'entités sont désormais affichées. S'il y a plus d'entités, cette liste peut être étendue à un maximum de 1000 entrées (la valeur de SUBFILTER_VALUES_PER_GROUP dans les [définitions de l'interface](/manual/web_interface/definitions)) en cliquant sur l'icône à trois points affichée à la fin. Auparavant, un maximum non extensible de 100 entrées était la limite. - Dans la liste des *Valeurs de tag*, jusqu'à 10 lignes de noms de tag sont désormais affichées. S'il y a plus de noms de tag avec des valeurs, cette liste peut être étendue à un maximum de 200 noms de tag en cliquant sur l'icône à trois points affichée en bas. Auparavant, un maximum non extensible de 20 lignes avec des noms de tag était la limite. Pour chaque nom de tag, jusqu'à 10 lignes de valeurs sont affichées (extensibles à 1 000 entrées (la valeur de SUBFILTER_VALUES_PER_GROUP dans les [définitions de l'interface](/manual/web_interface/definitions))). #### Export and import Export and import Zabbix configuration data for configuration backups, migration or large-scale configuration updates. [Configuration API](/manual/api/reference/configuration) #### Exportation et importation Exportez et importez les données de configuration Zabbix pour les sauvegardes de configuration, les migrations ou les mises à jour de configuration à grande échelle. [API Configuration ](/manual/api/reference/configuration) ##### Export format Data can be exported using the Zabbix web frontend or [Zabbix API](/manual/api/reference/configuration). Supported export formats are YAML, XML and JSON. ##### Format d'exportation Les données peuvent être exportées à l'aide de l'interface Web Zabbix ou de l'[API Zabbix](/manual/api/reference/configuration). Les formats d'exportation pris en charge sont YAML, XML and JSON. #### Exporting a template Export the configuration of template "10571" as an XML string. Request: ```json { "jsonrpc": "2.0", "method": "configuration.export", "params": { "options": { "templates": [ "10571" ] }, "format": "xml" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:00:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter>&lt;dt&gt;Server uptime: (.*)&lt;/dt&gt;</parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>6805d4c39a624a8bab2cc8ab63df1ab3</uuid><name>CPU load</name><key>system.cpu.load</key><value_type>FLOAT</value_type><triggers><trigger><uuid>ab4c2526c2bc42e48a633082255ebcb3</uuid><expression>avg(/New template/system.cpu.load,3m)&gt;2</expression><name>CPU load too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n", "id": 1 } ``` #### Export d'un modèle Exporter la configuration du modèle "10571" sous forme de chaîne XML. Requête : ```json { "jsonrpc": "2.0", "method": "configuration.export", "params": { "options": { "templates": [ "10571" ] }, "format": "xml" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:00:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter><dt>Server uptime: (.*)</dt></parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>6805d4c39a624a8bab2cc8ab63df1ab3</uuid><name>CPU load</name><key>system.cpu.load</key><value_type>FLOAT</value_type><triggers><trigger><uuid>ab4c2526c2bc42e48a633082255ebcb3</uuid><expression>avg(/New template/system.cpu.load,3m)>2</expression><name>CPU load too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n", · "id": 1 } ``` #### Exporting To export hosts, do the following: - Go to: *Configuration* → *Hosts* - Mark the checkboxes of the hosts to export - Click on *Export* below the list  Depending on the selected format, hosts are exported to a local file with a default name: - *zabbix\_export\_hosts.yaml* - in YAML export (default option for export) - *zabbix\_export\_hosts.xml* - in XML export - *zabbix\_export\_hosts.json* - in JSON export #### Export Pour exporter les hôtes, procéder comme suit : - Aller dans *Configuration* → *Hôtes* - Cocher les cases des hôtes à exporter - Cliquer sur *Exporter* sous la liste  Selon le format sélectionné, les hôtes sont exportés vers un fichier local avec un nom par défaut : - *zabbix\_export\_hosts.yaml* - pour l'exportation YAML (option par défaut pour l'exportation) - *zabbix\_export\_hosts.xml* - pour l'exportation XML - *zabbix\_export\_hosts.json* - pour l'exportation JSON #### Exporting To export media types, do the following: - Go to: *Administration* → *Media types* - Mark the checkboxes of the media types to export - Click on *Export* below the list  Depending on the selected format, media types are exported to a local file with a default name: - *zabbix\_export\_mediatypes.yaml* - in YAML export (default option for export) - *zabbix\_export\_mediatypes.xml* - in XML export - *zabbix\_export\_mediatypes.json* - in JSON export #### Exportation Pour exporter des types de médias, procéder comme suit : - Aller dans : *Administration* → *Types de médias* - Cocher les cases des types de médias à exporter - Cliquer sur le bouton *Exporter* sous la liste  Selon le format sélectionné, les types de médias sont exportés vers un fichier local avec un nom par défaut : - *zabbix\_export\_mediatypes.yaml* - pour une exportation YAML (option d'exportation par défaut) - *zabbix\_export\_mediatypes.xml* - pour une exportation XML - *zabbix\_export\_mediatypes.json* - pour une exportation JSON #### Exporting To export network maps, do the following: - Go to: *Monitoring* → *Maps* - Mark the checkboxes of the network maps to export - Click on *Export* below the list  Depending on the selected format, maps are exported to a local file with a default name: - *zabbix\_export\_maps.yaml* - in YAML export (default option for export) - *zabbix\_export\_maps.xml* - in XML export - *zabbix\_export\_maps.json* - in JSON export #### Export Pour exporter les cartes, procéder comme suit : - Aller dans *Surveillance* → *Cartes* - Cocher les cases des cartes à exporter - Cliquer sur *Exporter* sous la liste  Selon le format sélectionné, les cartes sont exportées vers un fichier local avec un nom par défaut : - *zabbix\_export\_mapss.yaml* - pour l'exportation YAML (option par défaut pour l'exportation) - *zabbix\_export\_mapss.xml* - pour l'exportation XML - *zabbix\_export\_maps.json* - pour l'exportation JSON ###### Export request A request to execute the Export function of the Exporter interface. | | | |---|---| |direction|agent → plugin| |response|no| Parameters specific to export requests: |Name|Type|Comments| |---------|--------|----------| |key|string|The plugin key.| |parameters|array of strings (optional)|The parameters for Export function.| *Example:* {"id":4,"type":6,"key":"test.key","parameters":["foo","bar"]} ###### Requête d'exportation Une demande d'exécution de la fonction Exporter de l'interface Exporter. | | | |---|---| |direction|agent → plugin| |réponse|non| Paramètres spécifiques aux requêtes d'export : |Nom|Type|Commentaires| |---------|--------|----------| |key|string|La clé du plugin.| |parameters|tableau de chaînes (facultatif)|Les paramètres de la fonction d'exportation.| *Exemple:* {"id":4,"type":6,"key":"test.key","parameters":["foo","bar"]} ###### Export response Response from the Export function of the Exporter interface. | | | |---|---| |direction|plugin → agent| |response|n/a| Parameters specific to export responses: |Name|Type|Comments| |---------|--------|----------| |value|string (optional) |Response value from the Export function. Absent, if error is returned.| |error|string (optional) |Error message if the Export function has not been executed successfully. Absent, if value is returned.| *Examples:* {"id":5,"type":7,"value":"response"} or {"id":5,"type":7,"error":"error message"} ###### Réponse de l'exportation Réponse de la fonction Exporter de l'interface Exporter. | | | |---|---| |direction|plugin → agent| |réponse|n/a| Paramètres spécifiques aux réponses d'exportation : |Nom|Type|Commentaires| |---------|--------|----------| |value|string (facultatif) |Valeur de réponse de la fonction d'exportation. Absent, si une erreur est renvoyée.| |error|string (facultatif) |Message d'erreur si la fonction d'exportation n'a pas été exécutée avec succès. Absent, si la valeur est renvoyée.| *Exemples :* {"id":5,"type":7,"value":"response"} ou {"id":5,"type":7,"error":"message d'erreur"} #### Exposed metrics The stats items gather the statistics in bulk and return a JSON, which is the basis for dependent items to get their data from. The following [internal metrics](/manual/config/items/itemtypes/internal) are returned by either of the two items: - `zabbix[boottime]` - `zabbix[hosts]` - `zabbix[items]` - `zabbix[items_unsupported]` - `zabbix[preprocessing_queue]` (server only) - `zabbix[process,<type>,<mode>,<state>]` (only process type based statistics) - `zabbix[rcache,<cache>,<mode>]` - `zabbix[requiredperformance]` - `zabbix[triggers]` (server only) - `zabbix[uptime]` - `zabbix[vcache,buffer,<mode>]` (server only) - `zabbix[vcache,cache,<parameter>]` - `zabbix[version]` - `zabbix[vmware,buffer,<mode>]` - `zabbix[wcache,<cache>,<mode>]` ('trends' cache type server only) #### Métriques exposées Les éléments de statistiques rassemblent les statistiques en bloc et renvoient un JSON, qui est la base des éléments dépendants pour obtenir leurs données. [Mes métriques internes](/manual/config/items/itemtypes/internal) suivantes sont renvoyées par l'un ou l'autre des deux éléments : - `zabbix[boottime]` - `zabbix[hosts]` - `zabbix[items]` - `zabbix[items_unsupported]` - `zabbix[preprocessing_queue]` (serveur uniquement) - `zabbix[process,<type>,<mode>,<state>]` (uniquement pour les statistiques basé sur le type de processus) - `zabbix[rcache,<cache>,<mode>]` - `zabbix[requiredperformance]` - `zabbix[triggers]` (serveur uniquement) - `zabbix[uptime]` - `zabbix[vcache,buffer,<mode>]` (serveur uniquement) - `zabbix[vcache,cache,<parameter>]` - `zabbix[version]` - `zabbix[vmware,buffer,<mode>]` - `zabbix[wcache,<cache>,<mode>]` (type cache 'trends' sur le serveur uniquement) ### Expression macros {ITEM.KEY<1-9>} macros are now supported inside [expression macros](/manual/config/macros/expression_macros). ### Macros d'expression Les macros {ITEM.KEY<1-9>} sont désormais prises en charge dans les [macros d'expression](/manual/config/macros/expression_macros). ### Extended SNMP gateway functionality SNMP gateway can now provide information about triggers in a problem state and reveal host information in trigger details. Additionally, it is now possible to limit the rate of SNMP traps sent by SNMP gateway. The list of supported OIDs has been extended with a new OID **.10** for a comma-delimited list of trigger hostnames. New parameters have been added to the SNMP gateway configuration file: - *ProblemBaseOID* - OID of the problem trigger table; - *ProblemMinSeverity* - minimum severity, triggers having lower severity will not be included; - *ProblemHideAck* - if specified, only triggers with unacknowledged problems will be included; - *ProblemTagFilter* - if specified, only triggers with the specified tag name will be included; - *TrapTimer* - if set, Zabbix will send no more than one trap of the highest severity in the given time frame. For details, see [Zabbix SNMP Gateway](https://git.zabbix.com/projects/ZT/repos/snmp-gateway/browse/README.md). ### Fonctionnalité de passerelle SNMP étendue La passerelle SNMP peut désormais fournir des informations sur les déclencheurs dans un état problématique et révéler des informations sur l'hôte dans les détails du déclencheur. De plus, il est désormais possible de limiter le taux de traps SNMP envoyés par la passerelle SNMP. La liste des OID pris en charge a été étendue avec un nouvel OID **.10** pour une liste délimitée par des virgules de noms d'hôte de déclencheur. De nouveaux paramètres ont été ajoutés au fichier de configuration de la passerelle SNMP : - *ProblemBaseOID* - OID de la table de déclenchement du problème ; - *ProblemMinSeverity* - sévérité minimale, les déclencheurs ayant une sévérité inférieure ne seront pas inclus ; - *ProblemHideAck* - si spécifié, seuls les déclencheurs avec des problèmes non acquittés seront inclus ; - *ProblemTagFilter* - si spécifié, seuls les déclencheurs avec le nom de tag spécifié seront inclus ; - *TrapTimer* - s'il est défini, Zabbix n'enverra pas plus d'un trap de la plus haute sévérité dans le laps de temps donné. Pour plus de détails, voir [Passerelle SNMP Zabbix](https://git.zabbix.com/projects/ZT/repos/snmp-gateway/browse/README.md). #### Extracting matching part of regular expression Sometimes we may want to extract only the interesting value from a target file instead of returning the whole line when a regular expression match is found. Since Zabbix 2.2.0, log items have the ability to extract desired values from matched lines. This is accomplished by the additional **output** parameter in `log` and `logrt` items. Using the 'output' parameter allows to indicate the "capturing group" of the match that we may be interested in. So, for example log[/path/to/the/file,"large result buffer allocation.*Entries: ([0-9]+)",,,,\1] should allow returning the entry count as found in the content of: Fr Feb 07 2014 11:07:36.6690 */ Thread Id 1400 (GLEWF) large result buffer allocation - /Length: 437136/Entries: 5948/Client Ver: >=10/RPC ID: 41726453/User: AUser/Form: CFG:ServiceLevelAgreement Only the number will be returned because **\\1** refers to the first and only capturing group: **(\[0-9\]+)**. And, with the ability to extract and return a number, the value can be used to define triggers. #### Extraction de la partie correspondante de l'expression régulière Nous pouvons parfois vouloir extraire uniquement la valeur intéressante d'un fichier cible au lieu de renvoyer la ligne entière lorsqu'une correspondance d'expression régulière est trouvée. Depuis Zabbix 2.2.0, les éléments de fichiers journaux ont la possibilité d'extraire les valeurs souhaitées des lignes correspondantes. Ceci est accompli par le paramètre supplémentaire **output** dans les éléments `log` et `logrt`. L'utilisation du paramètre 'output' permet d'indiquer le "groupe capturé" de la correspondance qui pourrait nous intéresser. Ainsi, par exemple : log[/path/to/the/file,"large result buffer allocation.*Entries: ([0-9]+)",,,,\1] devrait permettre de renvoyer le nombre d'entrées tel que trouvé dans le contenu de : Fr Feb 07 2014 11:07:36.6690 */ Thread Id 1400 (GLEWF) large result buffer allocation - /Length: 437136/Entries: 5948/Client Ver: >=10/RPC ID: 41726453/User: AUser/Form: CFG:ServiceLevelAgreement Le nombre uniquement sera retourné parce que **\\1** se réfère au premier et seul groupe capturé : **(\[0-9\]+)** Et, avec la possibilité d'extraire et de renvoyer un nombre, la valeur peut être utilisée pour définir des déclencheurs. ### Failover to standby node Zabbix will fail over to another node automatically if the active node stops. There must be at least one node in standby status for the failover to happen. How fast will the failover be? All nodes update their last access time (and status, if it is changed) every 5 seconds. So: - If the active node shuts down and manages to report its status as "stopped", another node will take over within **5 seconds**. - If the active node shuts down/becomes unavailable without being able to update its status, standby nodes will wait for the **failover delay** + 5 seconds to take over The failover delay is configurable, with the supported range between 10 seconds and 15 minutes (one minute by default). To change the failover delay, you may run: ``` zabbix_server -R ha_set_failover_delay=5m ``` ### Failover to standby node Zabbix basculera automatiquement vers un autre nœud si le nœud actif s'arrête. Il doit y avoir au moins un nœud en état de veille pour que le basculement se produise. À quelle vitesse le basculement se fera-t-il ? Tous les nœuds mettent à jour leur heure de dernier accès (et leur état, s'il est modifié) toutes les 5 secondes. Alors: - Si le nœud actif s'arrête et parvient à signaler son état comme "arrêté", un autre nœud prendra le relais dans les **5 secondes**. - Si le nœud actif s'arrête/devient indisponible sans pouvoir mettre à jour son état, les nœuds de secours attendront le **délai de basculement** + 5 secondes pour prendre le relais Le délai de basculement est configurable, avec une plage prise en charge comprise entre 10 secondes et 15 minutes (une minute par défaut). Pour modifier le délai de basculement, vous pouvez exécuter : ``` zabbix_server -R ha_set_failover_delay=5m ``` ##### Favorite custom graphs no longer supported It is no longer possible to add custom graphs to favorites in *Monitoring* -> *Hosts* -> *Graphs*. After the upgrade any existing custom graphs will be removed from favorites. ##### Les graphiques personnalisés favoris ne sont plus pris en charge Il n'est plus possible d'ajouter des graphiques personnalisés aux favoris dans *Surveillance* -> *Hôtes* -> *Graphiques*. Après la mise à niveau, tous les graphiques personnalisés existants seront supprimés des favoris. ##### Field size limit Maximum field size has been increased for the following fields: - [Item preprocessing](/manual/config/items/preprocessing#configuration) parameters - [Media type](/manual/config/notifications/media#common-parameters) message ##### Limite de taille de champ La taille maximale des champs a été augmentée pour les champs suivants : - Paramètres de [prétraitement des éléments](/manual/config/items/preprocessing#configuration) - Message de [type de média](/manual/config/notifications/media#common-parameters) ## FILES */usr/local/etc/zabbix\_agent2.conf* Default location of Zabbix agent 2 configuration file (if not modified during compile time). [ ]{#lbAH} ## FICHIERS */usr/local/etc/zabbix\_agent2.conf* Emplacement par défaut du fichier de configuration de l'agent Zabbix 2 (s'il n'a pas été modifié lors de la compilation). [ ]{#lbAH} ## FILES */usr/local/etc/zabbix\_agentd.conf* Default location of Zabbix agent configuration file (if not modified during compile time). [ ]{#lbAI} ## FICHIERS */usr/local/etc/zabbix\_agentd.conf* Emplacement par défaut du fichier de configuration de l'agent Zabbix (s'il n'a pas été modifié lors de la compilation). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_proxy.conf* Default location of Zabbix proxy configuration file (if not modified during compile time). [ ]{#lbAI} ## FICHIERS */usr/local/etc/zabbix\_proxy.conf* Emplacement par défaut du fichier de configuration du proxy Zabbix (s'il n'a pas été modifié lors de la compilation). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_server.conf* Default location of Zabbix server configuration file (if not modified during compile time). [ ]{#lbAI} ## FICHIERS */usr/local/etc/zabbix\_server.conf* Emplacement par défaut du fichier de configuration du serveur Zabbix (s'il n'a pas été modifié lors de la compilation). [ ]{#lbAI} ## FILES */usr/local/etc/zabbix\_web\_service.conf* Default location of Zabbix web service configuration file (if not modified during compile time). [ ]{#lbAG} ## FICHIERS */usr/local/etc/zabbix\_web\_service.conf* Emplacement par défaut du fichier de configuration du service Web Zabbix (s'il n'a pas été modifié lors de la compilation). [ ]{#lbAG} ##### File system Because of the trap file implementation, Zabbix needs the file system to support inodes to differentiate files (the information is acquired by a stat() call). ##### Système de fichiers En raison de l'implémentation du fichier de trap, Zabbix a besoin du système de fichiers pour prendre en charge les inodes afin de différencier les différents fichiers (les informations sont acquises par un appel stat()). ##### Filter buttons | | | |--|--------| ||Apply specified filtering criteria (without saving).| ||Reset current filter and return to saved parameters of the current tab. On the main tab, this will clear the filter.| ||Save current filter parameters in a new tab. Only available on the main tab.| ||Replace tab parameters with currently specified parameters. Not available on the main tab.| ##### Boutons de filtrage | | | |--|--------| ||Appliquer les critères de filtrage spécifiés (sans enregistrer).| ||Réinitialiser le filtre actuel et revenir aux paramètres enregistrés de l'onglet actuel. Dans l'onglet principal, cela effacera le filtre.| ||Enregistrer les paramètres de filtre actuels dans un nouvel onglet. Uniquement disponible sur l'onglet principal.| ||Remplacer les paramètres de l'onglet par les paramètres actuellement spécifiés. Non disponible sur l'onglet principal.| #### Filter expression The filter expression is an arithmetical expression in infix notation. Supported operands: |Operand|Description|Example| |--|------|------| |`"<text>"`<br>`'<text>'`|Text constant.|'value: \\'1\\''<br>"value: '1'"| |`<number>`|Numeric constant supporting scientific notation.|123| |`<jsonpath starting with $>`|Value referred to by the JSONPath from the input document root node; only definite paths are supported.|$.object.name| |`<jsonpath starting with @>`|Value referred to by the JSONPath from the current object/element; only definite paths are supported.|@.name| Supported operators: |Operator|Type|Description|Result| |--|--------|----|----| |`-`|binary|Subtraction.|Number.| |`+`|binary|Addition.|Number.| |`/`|binary|Division.|Number.| |`*`|binary|Multiplication.|Number.| |`==`|binary|Is equal to.|Boolean (1 or 0).| |`!=`|binary|Is not equal to.|Boolean (1 or 0).| |`<`|binary|Is less than.|Boolean (1 or 0).| |`<=`|binary|Is less than or equal to.|Boolean (1 or 0).| |`>`|binary|Is greater than.|Boolean (1 or 0).| |`>=`|binary|Is greater than or equal to.|Boolean (1 or 0).| |`=~`|binary|Matches regular expression.|Boolean (1 or 0).| |`!`|unary|Boolean not.|Boolean (1 or 0).| |`||`|binary|Boolean or.|Boolean (1 or 0).| |`&&`|binary|Boolean and.|Boolean (1 or 0).| #### Expression de filtre L'expression de filtre est une expression arithmétique en notation infix. Opérandes pris en charge : |Opérande|Description|Exemple| |--|------|------| |`"<text>"`<br>`'<text>'`|Constante de texte.|'value: \\'1\\''<br>"value: '1'"| |`<number>`|Constante numérique prenant en charge la notation scientifique.|123| |`<jsonpath starting with $>`|Valeur référencée par JSONPath à partir du nœud racine du document d'entrée ; seuls les chemins définis sont pris en charge.|$.object.name| |`<jsonpath starting with @>`|Valeur référencée par le JSONPath à partir de l'objet/élément actuel ; seuls les chemins définis sont pris en charge.|@.name| Opérateurs pris en charge : |Opérateur|Type|Description|Résultat| |--|--------|----|----| |`-`|binaire|Soustraction.|Nombre.| |`+`|binaire|Addition.|Nombre.| |`/`|binaire|Division.|Nombre.| |`*`|binaire|Multiplication.|Nombre.| |`==`|binaire|Est égal à.|Booléen (1 ou 0).| |`!=`|binaire|N'est pas égal à.|Booléen (1 ou 0).| |`<`|binaire|Est inférieur à.|Booléen (1 ou 0).| |`<=`|binaire|Est inférieur ou égal à.|Booléen (1 ou 0).| |`>`|binaire|Est supérieur à.|Booléen (1 ou 0).| |`>=`|binaire|Est supérieur ou égal à.|Booléen (1 ou 0).| |`=~`|binaire|Correspond à l'expression régulière.|Booléen (1 ou 0).| |`!`|unaire|Non booléen.|Booléen (1 ou 0).| |`||`|binaire|Ou booléen.|Booléen (1 ou 0).| |`&&`|binaire|Et booléen.|Booléen (1 ou 0).| ##### Filtering by host In the *by host* mode results can be filtered by a host or by the host group. Specifying a parent host group implicitly selects all nested host groups. ##### Filtrage par hôte En mode *par hôte*, les résultats peuvent être filtrés par hôte ou par groupe d'hôtes. La spécification d'un groupe d'hôtes parent sélectionne implicitement tous les groupes d'hôtes imbriqués. #### Filtering VMware event log records Using a regular expression preprocessing to filter unnecessary events of the VMWare event log. 1\. On a working VMWare Hypervisor host check that the event log item `vmware.eventlog[<url>,<mode>]` is present and working properly. Note that the event log item could already be present on the hypervisor if the *Template VM VMWare* template has been linked during the host creation. 2\. On the VMWare Hypervisor host create a [dependent item](/manual/config/items/itemtypes/dependent_items) of 'Log' type and set the event log item as its master. In the "Preprocessing" tab of the dependent item select the "Matches regular expression" validation option and fill pattern, for example: ".* logged in .*" - filters all logging events in the event log "\bUser\s+\K\S+" - filter only lines with usernames from the event log ::: noteimportant If the regular expression is not matched then the dependent item becomes unsupported with a corresponding error message. To avoid this mark the "Custom on fail" checkbox and select to discard unmatched value, for example. ::: Another approach that allows using matching groups and output control is to select "Regular expression" option in the "Preprocessing" tab and fill parameters, for example: pattern: ".*logged in.*", output: "\0" - filters all logging events in the event log pattern "User (.*?)(?=\ )", output: "\1" - filter only usernames from the event log #### Filtrage des enregistrements du journal des événements VMware Utilisation d'un prétraitement d'expression régulière pour filtrer les événements inutiles du journal des événements VMWare. 1\. Sur un hôte VMWare Hypervisor en état de marche, vérifiez que l'élément du journal des événements `vmware.eventlog[<url>,<mode>]` est présent et fonctionne correctement. Notez que l'élément du journal des événements peut déjà être présent sur l'hyperviseur si le modèle *Template VM VMWare* a été lié lors de la création de l'hôte. 2\. Sur l'hôte VMWare Hypervisor, créez un [élément dépendant](/manual/config/items/itemtypes/dependent_items) de type 'Log' et définissez l'élément du journal des événements comme maître. Dans l'onglet "Prétraitement" de la rubrique dépendante sélectionnez l'option de validation "Correspond à l'expression régulière" et le motif de remplissage, par exemple : ".* logged in .*" - filters all logging events in the event log "\bUser\s+\K\S+" - filter only lines with usernames from the event log ::: noteimportant Si l'expression régulière ne correspond pas, l'élément dépendant devient non pris en charge avec un message d'erreur correspondant. Pour éviter cela, cochez la case "Personnalisé en cas d'échec" et sélectionnez pour ignorer la valeur sans correspondance, par exemple. ::: Une autre approche qui permet d'utiliser les groupes de correspondance et le contrôle de sortie consiste à sélectionner l'option "Expression régulière" dans l'onglet "Prétraitement" et à remplir les paramètres, par exemple : pattern: ".*logged in.*", output: "\0" - filters all logging events in the event log pattern "User (.*?)(?=\ )", output: "\1" - filter only usernames from the event log #### Filter settings remembered In several Monitoring pages (*Problems*, *Hosts*, *Latest data*) the current filter settings are now remembered in the user profile. When the user opens the page again, the filter settings will have stayed the same. Additionally, the marking of a changed (but not saved) favorite filter is now a green dot next to the filter name, instead of the filter name in italics. #### Paramètres de filtre mémorisés Dans plusieurs pages de surveillance (*Problèmes*, *Hôtes*, *Dernières données*), les paramètres de filtre actuels sont désormais mémorisés dans le profil de l'utilisateur. Lorsque l'utilisateur ouvre à nouveau la page, les paramètres de filtrage restent les mêmes. De plus, le marquage d'un filtre favori modifié (mais non enregistré) est désormais un point vert à côté du nom du filtre, au lieu du nom du filtre en italique. #### Find HTTP agent item Find HTTP agent item with post body type XML for specific host ID. Request: ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "hostids": "10255", "filter": { "type": 19, "post_type": 3 } }, "id": 3, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "28252", "type": "19", "snmp_oid": "", "hostid": "10255", "name": "template item", "key_": "ti", "delay": "30s", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "localhost", "query_fields": [ { "mode": "xml" } ], "posts": "<body>\r\n<![CDATA[{$MACRO}<foo></bar>]]>\r\n</body>", "status_codes": "200", "follow_redirects": "0", "post_type": "3", "http_proxy": "", "headers": [], "retrieve_mode": "1", "request_method": "3", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "", "prevvalue": "" } ], "id": 3 } ``` #### Rechercher un élément d'agent HTTP Recherchez l'élément d'agent HTTP avec le type de corps XML pour un ID d'hôte spécifique. Requête : ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "hostids": "10255", "filter": { "type": 19, "post_type": 3 } }, "id": 3, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "28252", "type": "19", "snmp_oid": "", "hostid": "10255", "name": "template item", "key_": "ti", "delay": "30s", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "localhost", "query_fields": [ { "mode": "xml" } ], "posts": "<body>\r\n<![CDATA[{$MACRO}<foo></bar>]]>\r\n</body>", "status_codes": "200", "follow_redirects": "0", "post_type": "3", "http_proxy": "", "headers": [], "retrieve_mode": "1", "request_method": "3", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "", "prevvalue": "" } ], "id": 3 } ``` #### Find HTTP agent item prototype Find HTTP agent item prototype with request method HEAD for specific host ID. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.get", "params": { "hostids": "10254", "filter": { "type": "19", "request_method": "3" } }, "id": 17, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "28257", "type": "19", "snmp_oid": "", "hostid": "10254", "name": "discovered", "key_": "item[{#INAME}]", "delay": "{#IUPDATE}", "history": "90d", "trends": "30d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "28255", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "2", "description": "", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "{#IURL}", "query_fields": [], "posts": "", "status_codes": "", "follow_redirects": "0", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "3", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 17 } ``` #### Recherche du prototype d'élément d'agent HTTP Recherchez le prototype d'élément d'agent HTTP avec la méthode de requête HEAD pour un ID d'hôte spécifique. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.get", "params": { "hostids": "10254", "filter": { "type": "19", "request_method": "3" } }, "id": 17, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "28257", "type": "19", "snmp_oid": "", "hostid": "10254", "name": "discovered", "key_": "item[{#INAME}]", "delay": "{#IUPDATE}", "history": "90d", "trends": "30d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "28255", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "2", "description": "", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "{#IURL}", "query_fields": [], "posts": "", "status_codes": "", "follow_redirects": "0", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "3", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 17 } ``` #### Finding dependent item Find one Dependent item for item with ID "25545". Request: ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "filter": { "type": "18", "master_itemid": "25545" }, "limit": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "25547", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Seconds", "key_": "apache.status.uptime.seconds", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "", "evaltype": "0", "master_itemid": "25545", "jmx_endpoint": "", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 1 } ``` #### Recherche d'un élément dépendant Trouvez un élément dépendant pour l'élément avec l'ID "25545". Requête : ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "filter": { "type": "18", "master_itemid": "25545" }, "limit": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "25547", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Seconds", "key_": "apache.status.uptime.seconds", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "", "evaltype": "0", "master_itemid": "25545", "jmx_endpoint": "", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 1 } ``` #### Finding dependent items by key Retrieve all dependent items from host with ID "10116" that have the word "apache" in the key. Request: ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "hostids": "10116", "search": { "key_": "apache" }, "filter": { "type": 18 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "25550", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Days", "key_": "apache.status.uptime.days", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "25545", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "25555", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Hours", "key_": "apache.status.uptime.hours", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "25545", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" } ], "id": 1 } ``` #### Recherche d'éléments dépendants par clé Récupérez tous les éléments dépendants de l'hôte avec l'ID "10116" dont la clé contient le mot "apache". Requête : ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "hostids": "10116", "search": { "key_": "apache" }, "filter": { "type": 18 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "25550", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Days", "key_": "apache.status.uptime.days", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "25545", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "25555", "type": "18", "snmp_oid": "", "hostid": "10116", "name": "Hours", "key_": "apache.status.uptime.hours", "delay": "0", "history": "90d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "25545", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" } ], "id": 1 } ``` #### Finding items by key Retrieve all items used in triggers specific host ID that have word "system.cpu" in the item key and sort results by name. Request: ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "hostids": "10084", "with_triggers": true, "search": { "key_": "system.cpu" }, "sortfield": "name" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "42269", "type": "18", "snmp_oid": "", "hostid": "10084", "name": "CPU utilization", "key_": "system.cpu.util", "delay": "0", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "%", "logtimefmt": "", "templateid": "42267", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "CPU utilization in %.", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "42264", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42259", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (15m avg)", "key_": "system.cpu.load[all,avg15]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42219", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42249", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (1m avg)", "key_": "system.cpu.load[all,avg1]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42209", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42257", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (5m avg)", "key_": "system.cpu.load[all,avg5]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42217", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42260", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Number of CPUs", "key_": "system.cpu.num", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42220", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" } ], "id": 1 } ``` #### Recherche d'éléments par clé Récupérez tous les éléments utilisés dans les ID d'hôte spécifiques des déclencheurs qui ont le mot "system.cpu" dans la clé d'élément et triez les résultats par nom. Requête : ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": "extend", "hostids": "10084", "with_triggers": true, "search": { "key_": "system.cpu" }, "sortfield": "name" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "42269", "type": "18", "snmp_oid": "", "hostid": "10084", "name": "CPU utilization", "key_": "system.cpu.util", "delay": "0", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "%", "logtimefmt": "", "templateid": "42267", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "0", "description": "CPU utilization in %.", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "42264", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42259", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (15m avg)", "key_": "system.cpu.load[all,avg15]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42219", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42249", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (1m avg)", "key_": "system.cpu.load[all,avg1]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42209", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42257", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Load average (5m avg)", "key_": "system.cpu.load[all,avg5]", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42217", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" }, { "itemid": "42260", "type": "0", "snmp_oid": "", "hostid": "10084", "name": "Number of CPUs", "key_": "system.cpu.num", "delay": "1m", "history": "7d", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "42220", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "0", "interfaceid": "1", "description": "", "inventory_link": "0", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "uuid": "", "state": "0", "error": "", "parameters": [], "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0" } ], "id": 1 } ``` #### Flexible intervals Flexible intervals allow to redefine the default update interval for specific time periods. A flexible interval is defined with *Interval* and *Period* where: - *Interval* – the update interval for the specified time period - *Period* – the time period when the flexible interval is active (see the [time periods](/manual/appendix/time_period) for detailed description of the *Period* format) Up to seven flexible intervals can be defined. If multiple flexible intervals overlap, the smallest *Interval* value is used for the overlapping period. Note that if the smallest value of overlapping flexible intervals is '0', no polling will take place. Outside the flexible intervals the default update interval is used. Note that if the flexible interval equals the length of the period, the item will be checked exactly once. If the flexible interval is greater than the period, the item might be checked once or it might not be checked at all (thus such configuration is not advisable). If the flexible interval is less than the period, the item will be checked at least once. If the flexible interval is set to '0', the item is not polled during the flexible interval period and resumes polling according to the default *Update interval* once the period is over. Examples: |Interval|Period|Description| |--------|------|-----------| |10|1-5,09:00-18:00|Item will be checked every 10 seconds during working hours.| |0|1-7,00:00-7:00|Item will not be checked during the night.| |0|7-7,00:00-24:00|Item will not be checked on Sundays.| |60|1-7,12:00-12:01|Item will be checked at 12:00 every day. Note that this was used as a workaround for scheduled checks and starting with Zabbix 3.0 it is recommended to use scheduling intervals for such checks.| #### Intervalles flexibles Les intervalles flexibles permettent de redéfinir l'intervalle de mise à jour par défaut pour des périodes spécifiques. Un intervalle flexible est défini avec *Intervalle* et *Période* où : - *Intervalle* - l'intervalle d’actualisation pour la période spécifiée - *Période* - la période pendant laquelle l'intervalle flexible est actif (voir les [périodes](/fr/manual/appendix/time_period) pour la description détaillée du format de la *Période*) Jusqu'à sept intervalles flexibles peuvent être définis. Si plusieurs intervalles flexibles se chevauchent, la plus petite valeur d'*intervalle* est utilisée pour la période de chevauchement. Notez que si la plus petite valeur où les intervalles se chevauchant est '0', aucune interrogation n'aura lieu. En dehors des intervalles flexibles, l'intervalle d’actualisation par défaut est utilisé. Notez que si l'intervalle flexible est égal à la longueur de la période, l'élément sera vérifié une seule fois. Si l'intervalle flexible est supérieur à la période, l'élément peut être vérifié une fois ou il peut ne pas être vérifié du tout (une telle configuration n'est donc pas conseillée). Si l'intervalle flexible est inférieur à la période, l'élément sera vérifié au moins une fois. Si l'intervalle flexible est défini sur '0', l'élément n'est pas interrogé pendant la période d'intervalle flexible et reprend l'interrogation en fonction de l'*intervalle d’actualisation* par défaut une fois la période terminée. Exemples : |Intervalle|Période|Description| |--------|------|-----------| |10|1-5,09:00-18:00|L'élément sera vérifié toutes les 10 secondes pendant les heures de travail.| |0|1-7,00:00-7:00|L'élément ne sera pas vérifié pendant la nuit.| |0|7-7,00:00-24:00|L'élément ne sera pas vérifié le dimanche.| |60|1-7,12:00-12:01|L'élément sera vérifié à 12h00 tous les jours. Notez que cela a été utilisé comme une solution de contournement pour les contrôles planifiés et à partir de Zabbix 3.0, il est recommandé d'utiliser des intervalles de planification pour ces vérifications.| #### Flexible user parameters Flexible user parameters accept parameters with the key. This way a flexible user parameter can be the basis for creating several items. Flexible user parameters have the following syntax: UserParameter=key[*],command |Parameter|Description| |--|--------| |**Key**|Unique item key. The \[\*\] defines that this key accepts parameters within the brackets.<br>Parameters are given when configuring the item.| |**Command**|Command to be executed to evaluate value of the key.<br>*For flexible user parameters only*:<br>You may use positional references $1…$9 in the command to refer to the respective parameter in the item key.<br>Zabbix parses the parameters enclosed in \[ \] of the item key and substitutes $1,...,$9 in the command accordingly.<br>$0 will be substituted by the original command (prior to expansion of $0,...,$9) to be run.<br>Positional references are interpreted regardless of whether they are enclosed between double (") or single (') quotes.<br>To use positional references unaltered, specify a double dollar sign - for example, awk '{print $$2}'. In this case `$$2` will actually turn into `$2` when executing the command.| ::: noteimportant Positional references with the $ sign are searched for and replaced by Zabbix agent only for flexible user parameters. For simple user parameters, such reference processing is skipped and, therefore, any $ sign quoting is not necessary. ::: ::: noteimportant Certain symbols are not allowed in user parameters by default. See [UnsafeUserParameters](/manual/appendix/config/zabbix_agentd) documentation for a full list. ::: #### Paramètres utilisateur flexibles Les paramètres utilisateur flexibles acceptent des paramètres dans la clé. Ainsi, un paramètre utilisateur flexible peut servir de base à la création de plusieurs éléments. Les paramètres utilisateur flexibles ont la syntaxe suivante : UserParameter=clé[*],commande |Paramètre|Description| |--|--------| |**Clé**|Clé d'élément unique. Le \[\*\] définit que cette clé accepte les paramètres entre parenthèses.<br>Les paramètres sont donnés lors de la configuration de l'élément.| |**Commande**|Commande à exécuter pour évaluer la valeur de la clé.<br>*Pour les paramètres utilisateur flexibles uniquement* :<br>Vous pouvez utiliser des références de position $1…$9 dans la commande pour faire référence au paramètre respectif dans la clé de l'élément.<br>Zabbix analyse les paramètres entre \[ \] de la clé de l'élément et remplace $1,...,$9 dans la commande en conséquence.<br>$0 sera remplacé par la commande d'origine (avant l'expansion de $0,...,$9) à exécuter.<br>Les références de position sont interprétées qu'elles soient entre guillemets doubles (") ou simples (').<br>Pour utiliser des références de position inchangées, spécifiez un double signe dollar - par exemple, awk '{print $$2}' Dans ce cas `$$2` se transformera en `$2` lors de l'exécution de la commande.| ::: noteimportant Les références positionnelles avec le signe $ sont recherchées et remplacées par l'agent Zabbix uniquement pour les paramètres utilisateur flexibles. Pour les paramètres utilisateur simples, ce traitement de référence est ignoré et, par conséquent, toute citation du signe $ est inutile. ::: ::: noteimportant Certains symboles ne sont pas autorisés dans les paramètres utilisateur par défaut. Voir la documentation [UnsafeUserParameters](/manual/appendix/config/zabbix_agentd) pour une liste complète. ::: #### Flipping frontend locales It has been observed that frontend locales may flip without apparent logic, i. e. some pages (or parts of pages) are displayed in one language while other pages (or parts of pages) in a different language. Typically the problem may appear when there are several users, some of whom use one locale, while others use another. A known workaround to this is to disable multithreading in PHP and Apache. The problem is related to how setting the locale works [in PHP](https://www.php.net/manual/en/function.setlocale): locale information is maintained per process, not per thread. So in a multi-thread environment, when there are several projects run by same Apache process, it is possible that the locale gets changed in another thread and that changes how data can be processed in the Zabbix thread. For more information, please see related problem reports: - [ZBX-10911](https://support.zabbix.com/browse/ZBX-10911) (Problem with flipping frontend locales) - [ZBX-16297](https://support.zabbix.com/browse/ZBX-16297) (Problem with number processing in graphs using the `bcdiv` function of BC Math functions) #### Inverser les paramètres régionaux de l'interface web Il a été observé que les paramètres régionaux de l'interface web peuvent basculer sans logique apparente, c'est-à-dire que certaines pages (ou parties de pages) sont affichées dans une langue tandis que d'autres pages (ou parties de pages) sont affichées dans une langue différente. En règle générale, le problème peut apparaître lorsqu'il y a plusieurs utilisateurs, dont certains utilisent un paramètre régional, tandis que d'autres en utilisent un autre. Une solution de contournement connue consiste à désactiver le multithreading dans PHP et Apache. Le problème est lié au fonctionnement de la définition des paramètres régionaux [en PHP](https://www.php.net/manual/en/function.setlocale) : les informations sur les paramètres régionaux sont conservées par processus, et non par thread. Ainsi, dans un environnement multi-thread, lorsque plusieurs projets sont exécutés par le même processus Apache, il est possible que les paramètres régionaux soient modifiés dans un autre thread et que cela modifie la façon dont les données peuvent être traitées dans le thread Zabbix. Pour plus d'informations, veuillez consulter les rapports de problèmes associés : - [ZBX-10911](https://support.zabbix.com/browse/ZBX-10911) (Problème avec la bascule des paramètres régionaux de l'interface web) - [ZBX-16297](https://support.zabbix.com/browse/ZBX-16297) (Problème avec le traitement des nombres dans les graphiques en utilisant la fonction `bcdiv` des fonctions BC Math) ### Float history The float history object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|float|Received value.| ### Historique des flottants L'objet d'historique flottant a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Heure à laquelle cette valeur a été reçue.| |itemid|string|ID de l'élément associé.| |ns|integer|Nanosecondes lorsque la valeur a été reçue.| |value|float|Valeur reçue.| ### Float trend The float trend object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Timestamp of an hour for which the value was calculated. E. g. timestamp of 04:00:00 means values calculated for period 04:00:00-04:59:59.| |itemid|integer|ID of the related item.| |num|integer|Number of values that were available for the hour.| |value\_min|float|Hourly minimum value.| |value\_avg|float|Hourly average value.| |value\_max|float|Hourly maximum value.| ### Tendance float L'objet de tendance float a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Horodatage d'une heure pour laquelle la valeur a été calculée. Par exemple. l'horodatage de 04:00:00 signifie des valeurs calculées pour la période 04:00:00-04:59:59.| |itemid|integer|ID de l'élément connexe.| |num|integer|Nombre de valeurs disponibles pour l'heure.| |value\_min|float|Valeur horaire minimum.| |value\_avg|float|Valeur horaire moyenne.| |value\_max|float|Valeur horaire maximum.| ##### Footnotes ^**1**^A Linux-specific note. Zabbix agent must have read-only access to filesystem */proc*. Kernel patches from www.grsecurity.org limit access rights of non-privileged users. ^**2**^ `vfs.dev.read[]`, `vfs.dev.write[]`: Zabbix agent will terminate "stale" device connections if the item values are not accessed for more than 3 hours. This may happen if a system has devices with dynamically changing paths or if a device gets manually removed. Note also that these items, if using an update interval of 3 hours or more, will always return '0'. ^**3**^ `vfs.dev.read[]`, `vfs.dev.write[]`: If default *all* is used for the first parameter then the key will return summary statistics, including all block devices like sda, sbd and their partitions (sda1, sda2, sdb3...) and multiple devices (MD raid) based on those block devices/partitions and logical volumes (LVM) based on those block devices/partitions. In such cases returned values should be considered only as relative value (dynamic in time) but not as absolute values. ^**4**^ SSL (HTTPS) is supported only if agent is compiled with cURL support. Otherwise the item will turn unsupported. ##### Notes de bas de page ^**1**^Une note spécifique à Linux. L'agent Zabbix doit avoir un accès en lecture seule au système de fichiers */proc*. Les correctifs du noyau de www.grsecurity.org limitent les droits d'accès des utilisateurs non privilégiés. ^**2**^ `vfs.dev.read[]`, `vfs.dev.write[]` : l'agent Zabbix mettra fin aux connexions de périphérique "stale" si les valeurs des éléments ne sont pas consultées pendant plus de 3 heures. Cela peut se produire si un système comporte des périphériques dont les chemins changent dynamiquement ou si un périphérique est supprimé manuellement. Notez également que ces éléments, s'ils utilisent un intervalle de mise à jour de 3 heures ou plus, renverront toujours '0'. ^**3**^ `vfs.dev.read[]`, `vfs.dev.write[]` : si la valeur par défaut *all* est utilisée pour le premier paramètre, la clé renverra des statistiques récapitulatives, y compris tous les périphériques de bloc comme sda, sbd et leurs partitions (sda1, sda2, sdb3 ...) et plusieurs périphériques (MD raid) basés sur ces périphériques/partitions de bloc et volumes logiques (LVM) basés sur ces périphériques/partitions de bloc. Dans de tels cas, les valeurs renvoyées doivent être considérées uniquement comme des valeurs relatives (dynamiques dans le temps) mais pas comme des valeurs absolues. ^**4**^ SSL (HTTPS) n'est pris en charge que si l'agent est compilé avec la prise en charge cURL. Sinon, l'élément deviendra non pris en charge. ##### Footnotes ^**1**^ Default value. ##### Notes de bas de page ^**1**^ Valeur par défaut. ##### Footnotes ^**1**^ For string values, only the string will be exported (e.g. "EMAIL") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only. ##### Notes de bas de page ^**1**^ Pour les valeurs de type chaîne de caractères, seule la chaîne sera exportée (par exemple "EMAIL") sans la numérotation utilisée dans ce tableau. Les nombres pour les valeurs de plage (correspondant aux valeurs API) dans ce tableau sont utilisés uniquement pour l'ordre. ##### Footnotes ^**1**^ For string values, only the string will be exported (e.g. "ZABBIX\_ACTIVE") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only. ##### Notes de bas de page ^**1**^ Pour les valeurs de type chaîne de caractères, seule la chaîne sera exportée (par exemple "ZABBIX\_ACTIVE") sans la numérotation utilisée dans ce tableau. Les nombres pour les valeurs de plage (correspondant aux valeurs de l'API) dans ce tableau est utilisé sur demande uniquement. ##### Footnotes ^**1**^ If multiple macros in a field or macros mixed with text are not supported for the location, a single macro has to fill the whole field. ^**2**^ Macros used in tag names and values are resolved only during event generation process. ^**3**^ URLs that contain a [secret macro](/manual/config/macros/user_macros#configuration) will not work, as the macro in them will be resolved as "\*\*\*\*\*\*". ##### Notes de bas de page ^**1**^ Si plusieurs macros dans un champ ou des macros mélangées à du texte ne sont pas prises en charge pour l'emplacement, une seule macro doit remplir tout le champ. ^**2**^ Les macros utilisées dans les noms et les valeurs des tags sont résolues uniquement lors du processus de génération d'événements. ^**3**^ Les URL qui contiennent une [macro secrète](/manual/config/macros/user_macros#configuration) ne fonctionneront pas, car la macro qu'elles contiennent sera résolue comme "\*\*\*\*\*\*". ##### Footnotes ^**1**^ In the fields marked with ^[1](lld_macros#footnotes)^ a single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported. ##### Notes de bas de page ^**1**^ Dans les champs marqués par ^[1](lld_macros#footnotes)^ une seule macro doit remplir tout le champ. Les macros multiples dans un champ ou les macros mélangées avec du texte ne sont pas prises en charge. ##### Footnotes ^**1**^ The `{HOST.*}` macros supported in item key parameters will resolve to the interface that is selected for the item. When used in items without interfaces they will resolve to either the Zabbix agent, SNMP, JMX or IPMI interface of the host in this order of priority or to 'UNKNOWN' if the host does not have any interface. ^**2**^ In global scripts, interface IP/DNS fields and web scenarios the macro will resolve to the main agent interface, however, if it is not present, the main SNMP interface will be used. If SNMP is also not present, the main JMX interface will be used. If JMX is not present either, the main IPMI interface will be used. If the host does not have any interface, the macro resolves to 'UNKNOWN'. ^**3**^ Only the **avg**, **last**, **max** and **min** functions, with seconds as parameter are supported in this macro in map labels. ^**4**^ `{HOST.*}` macros are supported in web scenario *Variables*, *Headers*, *SSL certificate file* and *SSL key file* fields and in scenario step *URL*, *Post*, *Headers* and *Required string* fields. Since Zabbix 5.4.0, `{HOST.*}` macros are no longer supported in web scenario *Name* and web scenario step *Name* fields. ^**5**^ Only the **avg**, **last**, **max** and **min** functions, with seconds as parameter are supported within this macro in graph names. The {HOST.HOST<1-9>} macro can be used as host within the macro. For example: * last(/Cisco switch/ifAlias[{#SNMPINDEX}]) * last(/{HOST.HOST}/ifAlias[{#SNMPINDEX}]) ^**6**^ Supported since 5.2.5. ##### Notes de bas de page ^**1**^ Les macros `{HOST.*}` prises en charge dans les paramètres de clé d'élément seront résolues sur l'interface sélectionnée pour l'élément. Lorsqu'ils sont utilisés dans des éléments sans interfaces, ils seront résolus soit par l'agent Zabbix, l'interface SNMP, JMX ou IPMI de l'hôte dans cet ordre de priorité, soit par 'INCONNU' si l'hôte n'a pas d'interface. ^**2**^ Dans les scripts globaux, les champs d'interface IP/DNS et les scénarios Web, la macro résoudra l'interface de l'agent principal, cependant, si elle n'est pas présente, l'interface SNMP principale sera utilisée. Si SNMP n'est pas présent non plus, l'interface JMX principale sera utilisée. Si JMX n'est pas présent non plus, l'interface IPMI principale sera utilisée. Si l'hôte n'a pas d'interface, la macro se résout en 'UNKNOWN'. ^**3**^ Seules les fonctions **avg**, **last**, **max** et **min**, avec des secondes comme paramètre, sont prises en charge dans cette macro dans les étiquettes de carte. ^**4**^ Les macros `{HOST.*}` sont prises en charge dans les champs *Variables*, *Entêtes*, *Fichier de certificat SSL* et *Fichier de clé SSL* du scénario Web et dans les étapes de scénario *URL*, *Post*, *Entêtes* et * Champs de chaîne* obligatoires. Depuis Zabbix 5.4.0, les macros `{HOST.*}` ne sont plus prises en charge dans les champs du scénario Web *Nom* et de l'étape du scénario Web *Nom*. ^**5**^ Seules les fonctions **avg**, **last**, **max** et **min**, avec des secondes comme paramètre, sont prises en charge dans cette macro dans les noms de graphique. La macro {HOST.HOST<1-9>} peut être utilisée comme hôte dans la macro. Par exemple: * last(/Cisco switch/ifAlias[{#SNMPINDEX}]) * last(/{HOST.HOST}/ifAlias[{#SNMPINDEX}]) ^**6**^ Pris en charge depuis 5.2.5. ##### Form buttons Buttons at the bottom of the form allow to perform several operations. | | | |--|--------| ||Add a report. This button is only available for new reports.| ||Update the properties of a report.| ||Create another report based on the properties of the current report.| ||Test if report configuration is correct by sending a report to the current user.| ||Delete the report.| ||Cancel the editing of report properties.| ##### Boutons de formulaire Des boutons en bas du formulaire permettent d'effectuer plusieurs opérations. | | | |--|--------| ||Ajouter un rapport. Ce bouton n'est disponible que pour les nouveaux rapports.| ||Mettre à jour les propriétés d'un rapport.| ||Créer un autre rapport basé sur les propriétés du rapport actuel.| ||Tester si la configuration du rapport est correcte en envoyant un rapport à l'utilisateur actuel.| ||Supprimer le rapport.| ||Annuler la modification des propriétés du rapport.| #### FreeBSD See values supported for 'memtype' parameter on FreeBSD in the table. |Supported value|Description|Source in kinfo\_proc structure|Tries to be compatible with| |--|------|--|--| |vsize|Virtual memory size|kp\_eproc.e\_vm.vm\_map.size or ki\_size|ps -o vsz| |pmem|Percentage of real memory|calculated from rss|ps -o pmem| |rss|Resident set size|kp\_eproc.e\_vm.vm\_rssize or ki\_rssize|ps -o rss| |size ^[1](proc_mem_notes#footnotes)^|Size of process (code + data + stack)|tsize + dsize + ssize| | |tsize|Text (code) size|kp\_eproc.e\_vm.vm\_tsize or ki\_tsize|ps -o tsiz| |dsize|Data size|kp\_eproc.e\_vm.vm\_dsize or ki\_dsize|ps -o dsiz| |ssize|Stack size|kp\_eproc.e\_vm.vm\_ssize or ki\_ssize|ps -o ssiz| #### FreeBSD Vous trouverez les valeurs prises en charge pour le paramètre 'memtype' sous FreeBSD dans le tableau suivant. |Valeur prise en charge|Description|Source dans la structure kinfo\_proc|Essaye d'être compatible avec| |--|------|--|--| |vsize|Taille de la mémoire virtuelle|kp\_eproc.e\_vm.vm\_map.size ou ki\_size|ps -o vsz| |pmem|Pourcentage de mémoire réelle|calculé à partir de rss|ps -o pmem| |rss|Taille de l'ensemble résident|kp\_eproc.e\_vm.vm\_rssize ou ki\_rssize|ps -o rss| |size ^[1](proc_mem_notes#footnotes)^|Taille du processus (code + données + pile)|tsize + dsize + ssize| | |tsize|Taille du texte (code)|kp\_eproc.e\_vm.vm\_tsize ou ki\_tsize|ps -o tsiz| |dsize|Taille des données|kp\_eproc.e\_vm.vm\_dsize ou ki\_dsize|ps -o dsiz| |ssize|Taille de la pile|kp\_eproc.e\_vm.vm\_ssize ou ki\_ssize|ps -o ssiz| ##### Frontend configuration A Zabbix proxy does not have a frontend; it communicates with Zabbix server only. ##### Configuration de l'interface Un proxy Zabbix n'a pas d'interface ; il communique uniquement avec le serveur Zabbix. ##### Frontend configuration A Zabbix proxy does not have a frontend; it communicates with Zabbix server only. ##### Configuration de l'interface Un proxy Zabbix n'a pas d'interface ; il communique uniquement avec le serveur Zabbix. ##### Frontend configuration A Zabbix proxy does not have a frontend; it communicates with Zabbix server only. ##### Configuration de l'interface Un proxy Zabbix n'a pas d'interface ; il communique uniquement avec le serveur Zabbix. ### Frontend languages Catalan and Romanian languages are now enabled in the frontend. ### Langues de l'interface Web Les langues Catalan and Roumaine sont maintenant activées sur l'interface Web. ### Frontend languages German and Vietnamese languages are now enabled in the frontend. ### Langues de l'interface Les langues allemande et vietnamienne sont maintenant activées dans le frontend. ### Frontend ##### Miscellaneous - Warnings about incorrect housekeeping configuration for TimescaleDB are now displayed if history or trend tables contain compressed chunks, but *Override item history period* or *Override item trend period* options are disabled. For more information, see [TimescaleDB setup](/manual/appendix/install/timescaledb#configuration). ### Interface ##### Divers - Des avertissements concernant une configuration de maintenance incorrecte pour TimescaleDB sont désormais affichés si les tables d'historique ou de tendance contiennent des blocs compressés, mais les options *Remplacer la période d'historique de l'élément* ou *Remplacer la période de tendance de l'élément* sont désactivées. Pour plus d'informations, voir [Configuration TimescaleDB](/manual/appendix/install/timescaledb#configuration). ##### Frontend The minimum supported screen width for Zabbix frontend is 1200px. Mandatory requirements are needed always. Optional requirements are needed for the support of the specific function. |Software|Mandatory status|Version|Comments| |--|-|-|------| |*Apache*|yes|1.3.12 or later| | |*PHP*|^|7.2.5 or later,<br>(*since Zabbix 6.0.6*) 8.0, 8.1|Recommended to use PHP 7.4 or later. | |PHP extensions:|<|<|<| |*gd*|yes|2.0.28 or later|PHP GD extension must support PNG images (*--with-png-dir*), JPEG (*--with-jpeg-dir*) images and FreeType 2 (*--with-freetype-dir*).| |*bcmath*|^| |php-bcmath (*--enable-bcmath*)| |*ctype*|^| |php-ctype (*--enable-ctype*)| |*libXML*|^|2.6.15 or later|php-xml, if provided as a separate package by the distributor.| |*xmlreader*|^| |php-xmlreader, if provided as a separate package by the distributor.| |*xmlwriter*|^| |php-xmlwriter, if provided as a separate package by the distributor.| |*session*|^| |php-session, if provided as a separate package by the distributor.| |*sockets*|^| |php-net-socket (*--enable-sockets*). Required for user script support.| |*mbstring*|^| |php-mbstring (*--enable-mbstring*)| |*gettext*|^| |php-gettext (*--with-gettext*). Required for translations to work.| |*ldap*|No| |php-ldap. Required only if LDAP authentication is used in the frontend.| |*openssl*|^| |php-openssl. Required only if SAML authentication is used in the frontend.| |*mysqli*|^| |Required if MySQL is used as Zabbix backend database.| |*oci8*|^| |Required if Oracle is used as Zabbix backend database.| |*pgsql*|^| |Required if PostgreSQL is used as Zabbix backend database.| Third-party frontend libraries that are supplied with Zabbix: |Library|Mandatory status|Minimum version|Comments| |--|-|-|------| |[jQuery JavaScript Library](https://jquery.com/)|Yes|3.6.0|JavaScript library that simplifies the process of cross-browser development.| |[jQuery UI](https://jqueryui.com/)|^|1.12.1|A set of user interface interactions, effects, widgets, and themes built on top of jQuery.| |[OneLogin's SAML PHP Toolkit](https://github.com/onelogin/php-saml)|^|3.4.1|A PHP toolkit that adds SAML 2.0 authentication support to be able to sign in to Zabbix.| |[Symfony Yaml Component](https://symfony.com/doc/current/components/yaml.html)|^|5.1.0|Adds support to export and import Zabbix configuration elements in the YAML format.| ::: noteclassic Zabbix may work on previous versions of Apache, MySQL, Oracle, and PostgreSQL as well. ::: ::: noteimportant For other fonts than the default DejaVu, PHP function [imagerotate](http://php.net/manual/en/function.imagerotate.php) might be required. If it is missing, these fonts might be rendered incorrectly when a graph is displayed. This function is only available if PHP is compiled with bundled GD, which is not the case in Debian and other distributions. ::: Third-party libraries used for writing and debugging Zabbix frontend code: |Library|Mandatory status|Minimum version|Description| |--|-|-|------| |[Composer](https://getcomposer.org/)|No|2.4.1|An application-level package manager for PHP that provides a standard format for managing dependencies of PHP software and required libraries.| |[PHPUnit](https://phpunit.de/)|^|8.5.29|A PHP unit testing framework for testing Zabbix frontend.| |[SASS](https://sass-lang.com/)|^|3.4.22|A preprocessor scripting language that is interpreted and compiled into Cascading Style Sheets (CSS).| ##### Interface Web La largeur d'écran minimale prise en charge pour l'interface Zabbix est de 1200 pixels. Les pré-requis obligatoires sont toujours nécessaires. Des pré-requis facultatives sont nécessaires pour la prise en charge de fonctions spécifiques. |Logiciel|Obligatoire|Version|Commentaires| |--|-|-|------| |*Apache*|Oui|1.3.12 ou version ultérieure| | |*PHP*|^|7.2.5 ou version ultérieure,<br>(*depuis Zabbix 6.0.6*) 8.0, 8.1| Recommandé d'utiliser PHP 7.4 ou version ultérieure. | |Extensions PHP :|<|<|<| |*gd*|Oui|2.0.28 ou version ultérieure|L'extension PHP GD doit prendre en charge les images PNG(*--with-png-dir*), JPEG (*--with-jpeg-dir*) et FreeType 2 (*--with-freetype-dir*).| |*bcmath*|<| |php-bcmath (*--enable-bcmath*)| |*ctype*|<| |php-ctype (*--enable-ctype*)| |*libXML*|<|2.6.15 ou version ultérieure|php-xml, s'il est fourni dans un package séparé par le distributeur.| |*xmlreader*|<| |php-xmlreader, s'il est fourni dans un package séparé par le distributeur.| |*xmlwriter*|<| |php-xmlwriter, s'il est fourni dans un package séparé par le distributeur.| |*session*|<| |php-session, s'il est fourni dans un package séparé par le distributeur.| |*sockets*|<| |php-net-socket (*--enable-sockets*). Requis pour la prise en charge des scripts utilisateur.| |*mbstring*|<| |php-mbstring (*--enable-mbstring*)| |*gettext*|<| |php-gettext (*--with-gettext*). Requis pour que les traductions fonctionnent.| |*ldap*|Non| |php-ldap. Requis uniquement si l'authentification LDAP est utilisée pour le frontend.| |*openssl*|<| |php-openssl. Requis uniquement si l'authentification SAML est utilisée pour le frontend.| |*mysqli*|<| |Requis si MySQL est utilisé comme base de données backend Zabbix.| |*oci8*|<| |Requis si Oracle est utilisé comme base de données backend Zabbix.| |*pgsql*|<| |Requis si PostgreSQL est utilisé comme base de données backend Zabbix.| Librairies tierces fournies avec Zabbix : |Librairie|Obligatoire|Version minimale|Commentaires| |--|-|-|------| |[jQuery JavaScript Library](https://jquery.com/)|Oui|3.6.0|Bibliothèque JavaScript qui simplifie le processus de développement multi-navigateur.| |[jQuery UI](https://jqueryui.com/)|^|1.12.1|Un ensemble d'interactions, d'effets, de widgets et de thèmes d'interface utilisateur construits sur jQuery.| |[OneLogin's SAML PHP Toolkit](https://github.com/onelogin/php-saml)|^|3.4.1|Une boîte à outils PHP qui ajoute la prise en charge de l'authentification SAML 2.0 pour pouvoir se connecter à Zabbix.| |[Symfony Yaml Component](https://symfony.com/doc/current/components/yaml.html)|^|5.1.0|Ajoute la prise en charge de l'exportation et de l'importation des éléments de configuration Zabbix au format YAML.| ::: noteclassic Zabbix peut également fonctionner sur les versions précédentes d'Apache, MySQL, Oracle et PostgreSQL. ::: ::: noteimportant Pour d'autres polices que la DejaVu par défaut, la fonction PHP [imagerotate](http://php.net/manual/en/function.imagerotate.php) peut être requise. Si elle est manquante, ces polices peuvent être rendues de manière incorrecte lors de l'affichage d'un graphique. Cette fonction n'est disponible que si PHP est compilé avec GD fourni, ce qui n'est pas le cas dans Debian et d'autres distributions. ::: Bibliothèques tierces utilisées pour écrire et déboguer le code frontal Zabbix : |Librairie|Obligatoire|Version minimale|Commentaires| |--|-|-|------| |[Composer](https://getcomposer.org/)|Non|2.4.1|Un gestionnaire de packages au niveau de l'application pour PHP qui fournit un format standard pour la gestion des dépendances des logiciels PHP et des bibliothèques requises.| |[PHPUnit](https://phpunit.de/)|^|8.5.29|Un framework de test unitaire PHP pour tester l'interface Zabbix.| |[SASS](https://sass-lang.com/)|^|3.4.22|Un langage de script de préprocesseur qui est interprété et compilé dans des feuilles de style en cascade (CSS).| #### Frontend To enable encryption with certificate and database host identity verification for connections between Zabbix frontend and the database: - Check *Database TLS encryption* and *Verify database certificate* - Specify path to *Database TLS key file* - Specify path to *Database TLS CA file* - Specify path to *Database TLS certificate file* - Check *Database host verification* {width="600"} Alternatively, this can be set in */etc/zabbix/web/zabbix.conf.php:* $DB['ENCRYPTION'] = true; $DB['KEY_FILE'] = ''; $DB['CERT_FILE'] = ''; $DB['CA_FILE'] = '/etc/ssl/pgsql/root.crt'; $DB['VERIFY_HOST'] = true; $DB['CIPHER_LIST'] = ''; ... #### Frontend Pour activer le chiffrement avec certificat et vérification de l'identité de l'hôte de la base de données pour les connexions entre l'interface Zabbix et la base de données : - Cochez *Cryptage TLS de la base de données* et *Vérifiez le certificat de la base de données* - Spécifiez le chemin d'accès au *fichier de clé TLS de la base de données* - Spécifiez le chemin d'accès au * fichier CA TLS de la base de données * - Spécifiez le chemin d'accès au *fichier de certificat TLS de la base de données* - Cochez * Vérification de l'hôte de la base de données * {width="600"} Alternativement, cela peut être défini dans */etc/zabbix/web/zabbix.conf.php :* $DB['ENCRYPTION'] = true; $DB['KEY_FILE'] = ''; $DB['CERT_FILE'] = ''; $DB['CA_FILE'] = '/etc/ssl/pgsql/root.crt'; $DB['VERIFY_HOST'] = true; $DB['CIPHER_LIST'] = ''; ... #### Frontend To enable transport-only encryption for connections between Zabbix frontend and the database: - Check *Database TLS encryption* - Leave *Verify database certificate* unchecked {width="600"} #### Frontend Pour activer le chiffrement de transport uniquement pour les connexions entre l'interface Zabbix et la base de données : - Cochez *Cryptage TLS de la base de données* - Laissez *Vérifier le certificat de la base de données* décoché {width="600"} #### Frontend To enable transport-only encryption for connections between Zabbix frontend and the database: - Check *Database TLS encryption* - Leave *Verify database certificate* unchecked {width="600"} #### Frontend Pour activer le chiffrement de transport uniquement pour les connexions entre Zabbix frontend et la base de données : - Cochez *Database TLS encryption* - Laissez *Verify database certificate* décoché {width="600"} #### Function parameters Function parameters allow to specify: - host and item key (functions referencing the host item history only) - function-specific parameters - other expressions (not available for functions referencing the host item history, see [other expressions](#other_expressions) for examples) The host and item key can be specified as `/host/key`. The referenced item must be in a supported state (except for **nodata()** function, which is calculated for unsupported items as well). While other trigger expressions as function parameters are limited to non-history functions in triggers, this limitation does not apply in [calculated items](/manual/config/items/itemtypes/calculated). #### Paramètres de la fonction Les paramètres de fonction permettent de spécifier : - l'hôte et la clé de l'élément (fonctions se référant uniquement à l'historique de l'élément de l'hôte) - paramètres spécifiques à la fonction - d'autres expressions (non disponibles pour les fonctions faisant référence l'historique de l'élément de l'hôte, voir les [autres expressions](#other_expressions) pourexemples) L'hôte et la clé de l'élément peuvent être spécifiés comme `/host/key`. L'élément référencé doit être dans un état pris en charge (sauf pour la fonction **nodata()**, qui est également calculé pour les éléments non pris en charge). Alors que d'autres expressions de déclenchement en tant que paramètres de fonction sont limitées à fonctions non historiques dans les déclencheurs, cette limitation ne s'applique pas dans les [éléments calculés](/manual/config/items/itemtypes/calculated). ##### Functions for Prometheus histograms It has been possible to collect [Prometheus metrics](/manual/config/items/itemtypes/prometheus) in Zabbix for a while now, but some of the metrics are difficult to work with. Specifically, the metrics of histogram type can be presented in Zabbix as multiple items with the same key names, but different parameters. However, even though such items are logically related and represent the same data, it has been difficult to analyze the collected data without specialized functions. To cover this functionality gap in the new version, **rate()** and **histogram\_quantile()** functions, producing the same result as their PromQL counterparts, have been added. Other new additions to complement this functionality are the **bucket\_rate\_foreach()** and the **bucket\_percentile()** functions. For more information see: - [History functions](/manual/appendix/functions/history#history_functions1) (see **rate()**) - [Aggregate functions](/manual/appendix/functions/aggregate#aggregate_functions1) (see **histogram\_quantile()**, **bucket\_percentile()**) - [Foreach functions](/manual/appendix/functions/aggregate/foreach) (see **bucket\_rate\_foreach()**) ##### Fonctions pour les histogrammes Prometheus Il est possible de collecter des [métriques Prometheus](/manual/config/items/itemtypes/prometheus) dans Zabbix depuis un certain temps déjà, mais certaines métriques sont difficiles à utiliser. Plus précisément, les métriques de type histogramme peuvent être présentées dans Zabbix sous la forme de plusieurs éléments avec les mêmes noms de clés, mais des paramètres différents. Cependant, même si ces éléments sont logiquement liés et représentent les mêmes données, il a été difficile d'analyser les données collectées sans fonctions spécialisées. Pour combler cette lacune de fonctionnalité dans la nouvelle version, les fonctions **rate()** et **histogram\_quantile()**, produisant le même résultat que leurs homologues PromQL, ont été ajoutées. D'autres nouveaux ajouts pour compléter cette fonctionnalité sont les fonctions **bucket\_rate\_foreach()** et **bucket\_percentile()**. Pour plus d'informations, voir : - [Fonctions d'historique](/manual/appendix/functions/history#history_functions) (voir **rate()**) - [Fonctions d'agrégation](/manual/appendix/functions/aggregate#aggregate_functions) (voir **histogram\_quantile()**, **bucket\_percentile()**) - [Fonctions foreach](/manual/appendix/functions/aggregate/foreach) (voir **bucket\_rate\_foreach()**) #### Functions Functions allow to calculate the collected values (average, minimum, maximum, sum), find strings, reference current time and other factors. A complete list of [supported functions](/manual/appendix/functions) is available. Typically functions return numeric values for comparison. When returning strings, comparison is possible with the **=** and **<>** operators (see [example](#example_14)). #### Les fonctions Des fonctions permettent de calculer les valeurs collectées (moyenne, minimum, maximum, somme), rechercher des chaînes, référencer l'heure actuelle et d'autres facteurs. Une liste complète des [fonctions prises en charge](/manual/appendix/functions) est disponible. Généralement, les fonctions renvoient des valeurs numériques à des fins de comparaison. Lorsqu'elles renvoient des chaînes, la comparaison est possible avec les opérateurs **=** et **<>** (voir l'[exemple](#example_14)). #### Functions Functions can be used at the end of JSONPath. Multiple functions can be chained if the preceding function returns value that is accepted by the following function. Supported functions: |Function|Description|Input|Output| |--|--------|----|----| |`avg`|Average value of numbers in input array.|Array of numbers.|Number.| |`min`|Minimum value of numbers in input array.|Array of numbers.|Number.| |`max`|Maximum value of numbers in input array.|Array of numbers.|Number.| |`sum`|Sum of numbers in input array.|Array of numbers.|Number.| |`length`|Number of elements in input array.|Array.|Number.| |`first`|The first array element.|Array.|A JSON construct (object, array, value) depending on input array contents.| Quoted numeric values are accepted by the JSONPath aggregate functions. It means that the values are converted from string type to numeric if aggregation is required. Incompatible input will cause the function to generate error. #### Fonctions Les fonctions peuvent être utilisées à la fin d'un JSONPath. Plusieurs fonctions peuvent être chaînées si la fonction précédente renvoie une valeur acceptée par la fonction suivante. Fonctions prises en charge : |Fonction|Description|Entrée|Sortie| |--|--------|----|----| |`avg`|Valeur moyenne des nombres dans le tableau d'entrée.|Tableau de nombres.|Nombre.| |`min`|Valeur minimale des nombres dans le tableau d'entrée.|Tableau de nombres.|Nombre.| |`max`|Valeur maximale des nombres dans le tableau d'entrée.|Tableau de nombres.|Nombre.| |`sum`|Somme des nombres dans le tableau d'entrée.|Tableau de nombres.|Nombre.| |`length`|Nombre d'éléments dans le tableau d'entrée.|Tableau.|Nombre.| |`first`|Le premier élément du tableau.|Tableau.|Une construction JSON (objet, tableau, valeur) en fonction du contenu du tableau d'entrée.| Les valeurs numériques entre guillemets sont acceptées par les fonctions d'agrégation JSONPath. Cela signifie que les valeurs sont converties du type chaîne en numérique si l'agrégation est requise. Une entrée incompatible entraînera la génération d'une erreur par la fonction. ### Further reading You now know enough to start working with the Zabbix API, but don't stop here. For further reading we suggest you have a look at the [list of available APIs](/manual/api/reference). ### Lectures complémentaires Vous en savez maintenant assez pour commencer à travailler avec l'API Zabbix, mais ne vous arrêtez pas là. Pour en savoir plus, nous vous conseillons de consulter la [liste des API disponibles](/manual/api/reference). #### General #### Général #### General advice - monitor required parameters only - tune 'Update interval' for all items. Keeping a small update interval may be good for nice graphs, however, this may overload Zabbix - tune parameters for default templates - tune housekeeping parameters - do not monitor parameters which return the same information. - avoid the use of triggers with long period given as function argument. For example, max(/host/key,1h) will be calculated significantly slower than max(/host/key,1m). #### Conseils généraux - surveiller uniquement les paramètres nécessaires - régler 'intervalle de mise à jour' pour tous les éléments. Garder un petit intervalle de mise à jour peut afficher de beaux graphiques, cependant, cela peut surcharger Zabbix - régler les paramètres pour les modèles par défaut - régler les paramètres de maintenance - ne surveillez pas des paramètres qui renvoient la même information. - éviter l'utilisation de déclencheurs avec une longue période donnée comme argument de fonction. Par exemple, max(/host/key,1h) sera calculé beaucoup plus lentement que max(/host/key,1m). #### General attributes The *User* tab contains general user attributes:  All mandatory input fields are marked with a red asterisk. |Parameter|Description| |--|--------| |*Username*|Unique username, used as the login name.| |*Name*|User first name (optional).<br>If not empty, visible in acknowledgment information and notification recipient information.| |*Last name*|User last name (optional).<br>If not empty, visible in acknowledgment information and notification recipient information.| |*Groups*|Select [user groups](usergroup) the user belongs to. Starting with Zabbix 3.4.3 this field is auto-complete so starting to type the name of a user group will offer a dropdown of matching groups. Scroll down to select. Alternatively, click on *Select* to add groups. Click on 'x' to remove the selected.<br>Adherence to user groups determines what host groups and hosts the user will have [access to](permissions).| |*Password*|Two fields for entering the user password.<br>With an existing password, contains a *Password* button, clicking on which opens the password fields.<br>Note that passwords longer than 72 characters will be truncated.| |*Language*|Language of the Zabbix frontend.<br>The php gettext extension is required for the translations to work.| |*Time zone*|Select the time zone to override global [time zone](/manual/web_interface/time_zone#overview) on user level or select **System default** to use global time zone settings.| |*Theme*|Defines how the frontend looks like:<br>**System default** - use default system settings<br>**Blue** - standard blue theme<br>**Dark** - alternative dark theme<br>**High-contrast light** - light theme with high contrast<br>**High-contrast dark** - dark theme with high contrast| |*Auto-login*|Mark this checkbox to make Zabbix remember the user and log the user in automatically for 30 days. Browser cookies are used for this.| |*Auto-logout*|With this checkbox marked the user will be logged out automatically, after the set amount of seconds (minimum 90 seconds, maximum 1 day).<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 90s, 5m, 2h, 1d.<br>Note that this option will not work:<br>\* If the "Show warning if Zabbix server is down" global configuration option is enabled and Zabbix frontend is kept open;<br>\* When Monitoring menu pages perform background information refreshes;<br>\* If logging in with the *Remember me for 30 days* option checked.| |*Refresh*|Set the refresh rate used for graphs, plain text data, etc. Can be set to 0 to disable.| |*Rows per page*|You can determine how many rows per page will be displayed in lists.| |*URL (after login)*|You can make Zabbix transfer the user to a specific URL after successful login, for example, to Problems page.| #### Attributs généraux L'onglet *Utilisateur* contient les attributs utilisateur généraux :  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. |Paramètre|Description| |--|--------| |*Nom d'utilisateur*|Nom d'utilisateur unique, utilisé comme nom de connexion.| |*Prénom*|Prénom de l'utilisateur (facultatif).<br>Si non vide, visible dans les informations d'accusé de réception et les informations du destinataire de la notification.| |*Nom*|Nom de l'utilisateur (facultatif).<br>Si non vide, visible dans les informations d'accusé de réception et les informations sur le destinataire de la notification.| |*Groupes*|Sélectionnez les [groupes d'utilisateurs](usergroup) auquels l'utilisateur appartient. À partir de Zabbix 3.4.3, ce champ est auto-complété, donc commencer à taper le nom d'un groupe d'utilisateurs offrira une liste déroulante des groupes correspondants. Faites défiler vers le bas pour sélectionner. Vous pouvez également cliquer sur *Sélectionner* pour ajouter des groupes. Cliquez sur 'x' pour supprimer la sélection.<br>L'adhésion aux groupes d'utilisateurs détermine les groupes d'hôtes et les hôtes auxquels l'utilisateur aura [accès](permissions).| |*Mot de passe*|Deux champs pour entrer le mot de passe de l'utilisateur.<br>Avec un mot de passe existant, contient un bouton *Mot de passe*, en cliquant sur lequel ouvre les champs du mot de passe.<br>Notez que les mots de passe de plus de 72 caractères seront tronqués.| |*Langue*|Langue de l'interface Zabbix.<br>L'extension php gettext est requise pour que les traductions fonctionnent.| |*Fuseau horaire*|Sélectionnez le fuseau horaire pour remplacer le [fuseau horaire](/manual/web_interface/time_zone#overview) global au niveau de l'utilisateur ou sélectionnez **Défaut du système** pour utiliser les paramètres de fuseau horaire globaux.| |*Thème*|Définit à quoi ressemble l'interface :<br>**Défaut du système** - utilise les paramètres système par défaut<br>**Bleu** - thème bleu standard<br>**Sombre** - thème sombre alternatif <br>**Lumière à contraste élevé** - thème clair à contraste élevé<br>**Sombre à contraste élevé** - thème sombre à contraste élevé| |*Connexion automatique*|Cochez cette case pour que Zabbix se souvienne de l'utilisateur et connecte l'utilisateur automatiquement pendant 30 jours. Les cookies du navigateur sont utilisés à cette fin.| |*Déconnexion automatique*|Avec cette case cochée, l'utilisateur sera déconnecté automatiquement, après le nombre de secondes défini (minimum 90 secondes, maximum 1 jour).<br>Les [suffixes de temps](/manual/appendix/suffixes) sont pris en charge, par exemple 90s, 5m, 2h, 1d.<br>Notez que cette option ne fonctionnera pas :<br>\* Si l'option de configuration globale "Afficher l'avertissement si le serveur Zabbix est en panne" est activée et que l'interface Zabbix est maintenue ouverte ;<br> \* Lorsque les pages du menu Surveillance exécutent des actualisations des informations d'arrière-plan ;<br>\* Si vous vous connectez avec l'option *Se souvenir de moi pendant 30 jours* cochée.| |*Actualiser*|Définissez le taux de rafraîchissement utilisé pour les graphiques, les données en texte brut, etc. Peut être défini sur 0 pour désactiver.| |*Lignes par page*|Vous pouvez déterminer combien de lignes par page seront affichées dans les listes.| |*URL (après connexion)*|Vous pouvez faire en sorte que Zabbix transfère l'utilisateur vers une URL spécifique après une connexion réussie, par exemple, vers la page Problèmes.| #### General Change certain global configuration options. [Autoregistration API](/manual/api/reference/autoregistration) | [Icon map API](/manual/api/reference/iconmap) | [Image API](/manual/api/reference/image) | [User macro API](/manual/api/reference/usermacro) | [Settings API](/manual/api/reference/settings) | [Housekeeping API](/manual/api/reference/housekeeping) #### Général Modifiez certaines options de configuration globales. [API Enregistrement automatique](/manual/api/reference/autoregistration) | [API Icône map](/manual/api/reference/iconmap) | [API Image](/manual/api/reference/image) | [API Macro utilisateur](/manual/api/reference/usermacro) | [API Réglages](/manual/api/reference/settings) | [API Housekeeping](/manual/api/reference/housekeeping) #### Generate multiple tokens Generate two tokens. Request: ```json { "jsonrpc": "2.0", "method": "token.generate", "params": [ "1", "2" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "tokenid": "1", "token": "bbcfce79a2d95037502f7e9a534906d3466c9a1484beb6ea0f4e7be28e8b8ce2" }, { "tokenid": "2", "token": "fa1258a83d518eabd87698a96bd7f07e5a6ae8aeb8463cae33d50b91dd21bd6d" } ], "id": 0 } ``` #### Générer plusieurs tokens Générez deux tokens. Requête : ```json { "jsonrpc": "2.0", "method": "token.generate", "params": [ "1", "2" ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "tokenid": "1", "token": "bbcfce79a2d95037502f7e9a534906d3466c9a1484beb6ea0f4e7be28e8b8ce2" }, { "tokenid": "2", "token": "fa1258a83d518eabd87698a96bd7f07e5a6ae8aeb8463cae33d50b91dd21bd6d" } ], "id": 0 } ``` ##### Generating from history/trends Graphs can be drawn based on either item [history or trends](/manual/config/items/history_and_trends). For the users who have frontend [debug mode](/manual/web_interface/debug_mode) activated, a gray, vertical caption is displayed at the bottom right of a graph indicating where the data come from. Several factors influence whether history of trends is used: - longevity of item history. For example, item history can be kept for 14 days. In that case, any data older than the fourteen days will be coming from trends. ```{=html} <!-- --> ``` - data congestion in the graph. If the amount of seconds to display in a horizontal graph pixel exceeds 3600/16, trend data are displayed (even if item history is still available for the same period). ```{=html} <!-- --> ``` - if trends are disabled, item history is used for graph building - if available for that period. This is supported starting with Zabbix 2.2.1 (before, disabled trends would mean an empty graph for the period even if item history was available). ##### Générer à partir de l'historique/des tendances Les graphiques peuvent être dessinés en fonction de l'un ou l'autre des éléments [historique ou tendances](/manual/config/items/history_and_trends). Pour les utilisateurs qui ont le [mode débogage](/manual/web_interface/debug_mode) frontal activé, une légende verticale grise s'affiche en bas à droite d'un graphique indiquant d'où proviennent les données. Plusieurs facteurs influencent l'utilisation de l'historique ou des tendances : - longévité de l'historique de l'élément. Par exemple, l'historique des éléments peut être conservé pendant 14 jours. Dans ce cas, toutes les données antérieures à ces quatorze jours proviendront des tendances. ```{=html} <!-- --> ``` - congestion des données dans le graphique. Si le nombre de secondes à afficher dans un pixel de graphique horizontal dépasse 3600/16, les données de tendance sont affichées (même si l'historique des éléments est toujours disponible pour la même période). ```{=html} <!-- --> ``` - si les tendances sont désactivées, l'historique des éléments est utilisé pour la création de graphiques - s'il est disponible pour cette période. Ceci est pris en charge à partir de Zabbix 2.2.1 (auparavant, les tendances désactivées signifiaient un graphique vide pour la période même si l'historique des éléments était disponible). #### Generating PSK For example, a 256-bit (32 bytes) PSK can be generated using the following commands: - with *OpenSSL*: ```{=html} <!-- --> ``` $ openssl rand -hex 32 af8ced32dfe8714e548694e2d29e1a14ba6fa13f216cb35c19d0feb1084b0429 - with *GnuTLS*: ```{=html} <!-- --> ``` $ psktool -u psk_identity -p database.psk -s 32 Generating a random key for user 'psk_identity' Key stored to database.psk $ cat database.psk psk_identity:9b8eafedfaae00cece62e85d5f4792c7d9c9bcc851b23216a1d300311cc4f7cb Note that "psktool" above generates a database file with a PSK identity and its associated PSK. Zabbix expects just a PSK in the PSK file, so the identity string and colon (':') should be removed from the file. #### Génération de PSK Par exemple, un PSK de 256 bits (32 octets) peut être généré à l'aide des commandes suivantes : - avec *OpenSSL* : ```{=html} <!-- --> ``` $ openssl rand -hex 32 af8ced32dfe8714e548694e2d29e1a14ba6fa13f216cb35c19d0feb1084b0429 - avec *GnuTLS* : ```{=html} <!-- --> ``` $ psktool -u psk_identity -p database.psk -s 32 Generating a random key for user 'psk_identity' Key stored to database.psk $ cat database.psk psk_identity:9b8eafedfaae00cece62e85d5f4792c7d9c9bcc851b23216a1d300311cc4f7cb Notez que la commande "psktool" ci-dessus génère un fichier de base de données avec une identité PSK et son PSK associé. Zabbix ne prévoit qu'un PSK dans le fichier PSK. Par conséquent, la chaîne d'identité et les deux-points (':') doivent être supprimés du fichier. #### Geomap widget error The maps in the Geomap widget may not load correctly, if you have upgraded from an older Zabbix version with NGINX and didn't switch to the new NGINX configuration file during the upgrade. To fix the issue, you can discard the old configuration file, use the configuration file from 6.0 package and reconfigure it as described in the [download instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql&ws=nginx) in section *e. Configure PHP for Zabbix frontend*. Alternatively, you can manually edit an existing NGINX configuration file (typically, */etc/zabbix/nginx.conf*). To do so, open the file and locate the following block: location ~ /(api\/|conf[^\.]|include|locale|vendor) { deny all; return 404; } Then, replace this block with: location ~ /(api\/|conf[^\.]|include|locale) { deny all; return 404; } location /vendor { deny all; return 404; } #### Erreur du widget Geomap Les cartes du widget Geomap peuvent ne pas se charger correctement si vous avez effectué une mise à niveau à partir d'une ancienne version de Zabbix avec NGINX et que vous n'êtes pas passé au nouveau fichier de configuration NGINX lors de la mise à niveau. Pour résoudre le problème, vous pouvez supprimer l'ancien fichier de configuration, utiliser le fichier de configuration du package 6.0 et le reconfigurer comme décrit dans les [instructions de téléchargement](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version =8&db=mysql&ws=nginx) dans la section *e. Configurer PHP pour l'interface Zabbix*. Vous pouvez également modifier manuellement un fichier de configuration NGINX existant (généralement, */etc/zabbix/nginx.conf*). Pour ce faire, ouvrez le fichier et localisez le bloc suivant : · location ~ /(api\/|conf[^\.]|include|locale|vendor) { · deny · all; · return · 404; · } Ensuite, remplacez ce bloc par : · location ~ /(api\/|conf[^\.]|include|locale) { · deny · all; · return · 404; · } · location /vendor { · deny · all; · return · 404; · } #### Get a count of standby nodes Request: ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "countOutput": true, "filter": { "status": 0 } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": "3", "id": 1 } ``` #### Obtenir le nombre de nœuds standby Requête : ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "countOutput": true, "filter": { "status": 0 } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": "3", "id": 1 } ``` #### Get a list of nodes ordered by status Request: ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "preservekeys": true, "sortfield": "status", "sortorder": "DESC" }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "ckuo7i1nw000h0sajj3l3hh8u": { "ha_nodeid": "ckuo7i1nw000h0sajj3l3hh8u", "name": "node-active", "address": "192.168.1.13", "port": "10051", "lastaccess": "1635335704", "status": "3" }, "ckuo7i1nw000e0sajwfttc1mp": { "ha_nodeid": "ckuo7i1nw000e0sajwfttc1mp", "name": "node6", "address": "192.168.1.10", "port": "10053", "lastaccess": "1635332902", "status": "2" }, "ckuo7i1nv000c0sajz85xcrtt": { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "name": "node4", "address": "192.168.1.8", "port": "10052", "lastaccess": "1635334214", "status": "1" }, "ckuo7i1nv000a0saj1fcdkeu4": { "ha_nodeid": "ckuo7i1nv000a0saj1fcdkeu4", "name": "node2", "address": "192.168.1.6", "port": "10051", "lastaccess": "1635335705", "status": "0" } }, "id": 1 } ``` #### Obtenir une liste de nœuds classés par statut Requête : ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "preservekeys": true, "sortfield": "status", "sortorder": "DESC" }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "ckuo7i1nw000h0sajj3l3hh8u": { "ha_nodeid": "ckuo7i1nw000h0sajj3l3hh8u", "name": "node-active", "address": "192.168.1.13", "port": "10051", "lastaccess": "1635335704", "status": "3" }, "ckuo7i1nw000e0sajwfttc1mp": { "ha_nodeid": "ckuo7i1nw000e0sajwfttc1mp", "name": "node6", "address": "192.168.1.10", "port": "10053", "lastaccess": "1635332902", "status": "2" }, "ckuo7i1nv000c0sajz85xcrtt": { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "name": "node4", "address": "192.168.1.8", "port": "10052", "lastaccess": "1635334214", "status": "1" }, "ckuo7i1nv000a0saj1fcdkeu4": { "ha_nodeid": "ckuo7i1nv000a0saj1fcdkeu4", "name": "node2", "address": "192.168.1.6", "port": "10051", "lastaccess": "1635335705", "status": "0" } }, "id": 1 } ``` #### Get a list of specific nodes by their IDs Request: ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "ha_nodeids": ["ckuo7i1nw000e0sajwfttc1mp", "ckuo7i1nv000c0sajz85xcrtt"] }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "name": "node4", "address": "192.168.1.8", "port": "10052", "lastaccess": "1635334214", "status": "1" }, { "ha_nodeid": "ckuo7i1nw000e0sajwfttc1mp", "name": "node6", "address": "192.168.1.10", "port": "10053", "lastaccess": "1635332902", "status": "2" } ], "id": 1 } ``` #### Obtenir une liste de nœuds spécifiques par leurs ID Requête : ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "ha_nodeids": ["ckuo7i1nw000e0sajwfttc1mp", "ckuo7i1nv000c0sajz85xcrtt"] }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "name": "node4", "address": "192.168.1.8", "port": "10052", "lastaccess": "1635334214", "status": "1" }, { "ha_nodeid": "ckuo7i1nw000e0sajwfttc1mp", "name": "node6", "address": "192.168.1.10", "port": "10053", "lastaccess": "1635332902", "status": "2" } ], "id": 1 } ``` #### Get a list of stopped nodes Request: ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "output": ["ha_nodeid", "address", "port"], "filter": { "status": 1 } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "ha_nodeid": "ckuo7i1nw000g0sajjsjre7e3", "address": "192.168.1.12", "port": "10051" }, { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "address": "192.168.1.8", "port": "10052" }, { "ha_nodeid": "ckuo7i1nv000d0sajd95y1b6x", "address": "192.168.1.9", "port": "10053" } ], "id": 1 } ``` #### Obtenir une liste des nœuds arrêtés Requête : ```json { "jsonrpc": "2.0", "method": "hanode.get", "params": { "output": ["ha_nodeid", "address", "port"], "filter": { "status": 1 } }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "ha_nodeid": "ckuo7i1nw000g0sajjsjre7e3", "address": "192.168.1.12", "port": "10051" }, { "ha_nodeid": "ckuo7i1nv000c0sajz85xcrtt", "address": "192.168.1.8", "port": "10052" }, { "ha_nodeid": "ckuo7i1nv000d0sajd95y1b6x", "address": "192.168.1.9", "port": "10053" } ], "id": 1 } ``` #### Getting Java gateway You can install Java gateway either from the sources or packages downloaded from [Zabbix website](http://www.zabbix.com/download.php). Using the links below you can access information how to get and run Zabbix Java gateway, how to configure Zabbix server (or Zabbix proxy) to use Zabbix Java gateway for JMX monitoring, and how to configure Zabbix items in Zabbix frontend that correspond to particular JMX counters. |Installation from|Instructions|Instructions| |-----------------|------------|------------| |*Sources*|[Installation](/manual/installation/install#installing_java_gateway)|[Setup](/manual/concepts/java/from_sources)| |*RHEL packages*|[Installation](/manual/installation/install_from_packages/rhel#java_gateway_installation)|[Setup](/manual/concepts/java/from_rhel)| |*Debian/Ubuntu packages*|[Installation](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)|[Setup](/manual/concepts/java/from_debian_ubuntu)| #### Obtenir la passerelle Java Vous pouvez installer la passerelle Java soit depuis les sources, soit en téléchargeant les packages depuis le [site web Zabbix](http://www.zabbix.com/download.php). En utilisant les liens ci-dessous vous pouvez accéder aux informations sur comment récupérer et exécuter le passerelle Java Zabbix, comment configurer le serveur Zabbix (ou le proxy Zabbix) pour utiliser la passerelle Java Zabbix pour la supervision JMX, et comment configurer les éléments Zabbix dans l'interface web qui correspondent aux compteurs JMX particuliers. |Installation depuis|Instructions|Instructions| |-------------------|------------|------------| |*Sources*|[Installation](/fr/manual/installation/install#installation_de_la_passerelle_java)|[Configuration](/fr/manual/concepts/java/from_sources)| |*packages RHEL*|[Installation](/fr/manual/installation/install_from_packages/rhel#installation_de_la_passerelle_java)|[Configuration](/fr/manual/concepts/java/from_rhel)| |*packages Debian/Ubuntu*|[Installation](/fr/manual/installation/install_from_packages/debian_ubuntu#installation_de_la_passerelle_java)|[Configuration](/fr/manual/concepts/java/from_debian_ubuntu)| #### Global event correlation Events may not get correlated correctly if the time interval between the first and second event is very small, i.e. half a second and less. #### Corrélation globale des événements Les événements peuvent ne pas être corrélés correctement si l'intervalle de temps entre le premier et le deuxième événement est très petit, c'est-à-dire une demi-seconde et moins. ### Global macro The global macro object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |globalmacroid|string|*(readonly)* ID of the global macro.| |**macro**<br>(required)|string|Macro string.| |**value**<br>(required)|string|Value of the macro.| |type|integer|Type of macro.<br><br>Possible values:<br>0 - *(default)* Text macro;<br>1 - Secret macro;<br>2 - Vault secret.| |description|string|Description of the macro.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Macro globale L'objet macro globale possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |globalmacroid|string|*(lecture seule)* ID de la macro globale.| |**macro**<br>(obligatoire)|string|Chaîne de la macro.| |**value**<br>(obligatoire)|string|Valeur de la macro.| |type|integer|Type de la macro.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Macro texte;<br>1 - Macro secrète ;<br>2 - Secret du coffre-fort.| |description|string|Description de la macro.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. ##### Global messages displayed As the messages arrive, they are displayed in a floating section on the right hand side. This section can be repositioned freely by dragging the section header.  For this section, several controls are available: -  **Snooze** button silences the currently active alarm sound; -  **Mute/Unmute** button switches between playing and not playing the alarm sounds at all. ##### Affichage des messages globaux Lorsque les messages arrivent, ils sont affichés dans une section flottante sur le côté droit. Cette section peut être repositionnée librement en faisant glisser son en-tête.  Pour cette section, plusieurs contrôles sont disponibles : -  le bouton **Reporter** coupe le son de l'alarme active ; -  le bouton **Sourdine/Enlever la sourdine** bascule entre jouer et ne pas jouer les sons de l'alarme. # graph.create # graph.create # graph.delete # graph.delete # graph.get # graph.get # graphitem.get # graphitem.get ### Graph item ::: noteclassic Graph items can only be modified via the `graph` API. ::: The graph item object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitemid|string|*(readonly)* ID of the graph item.| |**color**<br>(required)|string|Graph item's draw color as a hexadecimal color code.| |**itemid**<br>(required)|string|ID of the item.| |calc\_fnc|integer|Value of the item that will be displayed.<br><br>Possible values:<br>1 - minimum value;<br>2 - *(default)* average value;<br>4 - maximum value;<br>7 - all values;<br>9 - last value, used only by pie and exploded graphs.| |drawtype|integer|Draw style of the graph item.<br><br>Possible values:<br>0 - *(default)* line;<br>1 - filled region;<br>2 - bold line;<br>3 - dot;<br>4 - dashed line;<br>5 - gradient line.| |graphid|string|ID of the graph that the graph item belongs to.| |sortorder|integer|Position of the item in the graph.<br><br>Default: starts with 0 and increases by one with each entry.| |type|integer|Type of graph item.<br><br>Possible values:<br>0 - *(default)* simple;<br>2 - graph sum, used only by pie and exploded graphs.| |yaxisside|integer|Side of the graph where the graph item's Y scale will be drawn.<br><br>Possible values:<br>0 - *(default)* left side;<br>1 - right side.| ### Élément de graphique ::: noteclassic Les éléments du graphique ne peuvent être modifiés que via l'API `graph`. ::: L'objet élément de graphique possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitemid|string|*(lecture seule)* ID de l'élément de graphique.| |**color**<br>(obligatoire)|string|Couleur de tracé de l'élément du graphique sous forme de code de couleur hexadécimal.| |**itemid**<br>(obligatoire)|string|ID de l'élément.| |calc\_fnc|integer|Valeur de l'élément qui sera affiché.<br><br>Valeurs possibles :<br>1 - valeur minimale ;<br>2 - *(par défaut)* valeur moyenne ;<br>4 - valeur maximale ;<br>7 - toutes les valeurs ;<br>9 - dernière valeur, utilisée uniquement par les graphiques circulaires et éclatés.| |drawtype|integer|Style de dessin de l'élément de graphique.<br><br>Valeurs possibles :<br>0 - ligne *(par défaut)* ;<br>1 - zone remplie ;<br>2 - ligne en gras ;< br>3 - point ;<br>4 - ligne pointillée ;<br>5 - ligne dégradée.| |graphid|string|ID du graphe auquel appartient l'élément de graphe.| |sortorder|integer|Position de l'élément dans le graphique.<br><br>Par défaut : commence par 0 et augmente de un à chaque entrée.| |type|integer|Type d'élément de graphique.<br><br>Valeurs possibles :<br>0 - *(par défaut)* simple ;<br>2 - somme de graphique, utilisé uniquement par les graphiques à secteurs et éclatés.| |yaxisside|integer|Côté du graphique où l'échelle Y de l'élément graphique sera tracée.<br><br>Valeurs possibles :<br>0 - *(par défaut)* côté gauche ;<br>1 - côté droit.| # graphprototype.create # graphprototype.create # graphprototype.delete # graphprototype.delete # graphprototype.get # graphprototype.get #### Graph prototypes The following screenshot illustrates how we can use these macros in graph prototypes: {width="600"} {width="600"} A summary of our discovery rule: {width="600"} #### Prototypes de graphiques La capture d'écran suivante illustre comment nous pouvons utiliser ces macros dans des prototypes de graphe : {width="600"} {width="600"} Un résumé de notre règle de découverte : {width="600"} ### Graph prototype The graph prototype object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |graphid|string|*(readonly)* ID of the graph prototype.| |**height**<br>(required)|integer|Height of the graph prototype in pixels.| |**name**<br>(required)|string|Name of the graph prototype.| |**width**<br>(required)|integer|Width of the graph prototype in pixels.| |graphtype|integer|Graph prototypes's layout type.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - stacked;<br>2 - pie;<br>3 - exploded.| |percent\_left|float|Left percentile.<br><br>Default: 0.| |percent\_right|float|Right percentile.<br><br>Default: 0.| |show\_3d|integer|Whether to show discovered pie and exploded graphs in 3D.<br><br>Possible values:<br>0 - *(default)* show in 2D;<br>1 - show in 3D.| |show\_legend|integer|Whether to show the legend on the discovered graph.<br><br>Possible values:<br>0 - hide;<br>1 - *(default)* show.| |show\_work\_period|integer|Whether to show the working time on the discovered graph.<br><br>Possible values:<br>0 - hide;<br>1 - *(default)* show.| |templateid|string|*(readonly)* ID of the parent template graph prototype.| |yaxismax|float|The fixed maximum value for the Y axis.| |yaxismin|float|The fixed minimum value for the Y axis.| |ymax\_itemid|string|ID of the item that is used as the maximum value for the Y axis.<br><br>Starting with Zabbix 6.0.7, if user have no access to specified item, the graph is rendered like ymax\_type would be set to '0' (calculated).| |ymax\_type|integer|Maximum value calculation method for the Y axis.<br><br>Possible values:<br>0 - *(default)* calculated;<br>1 - fixed;<br>2 - item.| |ymin\_itemid|string|ID of the item that is used as the minimum value for the Y axis.<br><br>Starting with Zabbix 6.0.7, if user have no access to specified item, the graph is rendered like ymin\_type would be set to '0' (calculated).| |ymin\_type|integer|Minimum value calculation method for the Y axis.<br><br>Possible values:<br>0 - *(default)* calculated;<br>1 - fixed;<br>2 - item.| |discover|integer|Graph prototype discovery status.<br><br>Possible values:<br>0 - *(default)* new graphs will be discovered;<br>1 - new graphs will not be discovered and existing graphs will be marked as lost.| |uuid|string|Universal unique identifier, used for linking imported graph prototypes to already existing ones. Used only for graph prototypes on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Prototype de graphique L'objet prototype de graphique a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |graphid|string|*(lecture seule)* ID du prototype de graphique.| |**height**<br>(obligatoire)|integer|Hauteur du prototype de graphique en pixels.| |**name**<br>(obligatoire)|string|Nom du prototype de graphique.| |**width**<br>(obligatoire)|integer|Largeur du prototype de graphique en pixels.| |graphtype|integer|Type de disposition du prototype de graphique.<br><br>Valeurs possibles :<br>0 - *(par défaut)* normal ;<br>1 - empilé ;<br>2 - circulaire ;<br>3 - éclaté.| |percent\_left|float|Centile gauche.<br><br>Par défaut : 0.| |percent\_right|float|Centile droit.<br><br>Par défaut : 0.| |show\_3d|integer|Indique s'il faut afficher les graphiques circulaires et éclatés découverts en 3D.<br><br>Valeurs possibles :<br>0 - *(par défaut)* afficher en 2D ;<br>1 - afficher en 3D.| |show\_legend|integer|Indique s'il faut afficher la légende sur le graphique découvert.<br><br>Valeurs possibles :<br>0 - masquer ;<br>1 - *(par défaut)* afficher.| |show\_work\_period|integer|Indique s'il faut afficher le temps de travail sur le graphique découvert.<br><br>Valeurs possibles :<br>0 - masquer ;<br>1 - *(par défaut)* afficher.| |templateid|string|*(lecture seule)* ID du prototype de graphique du modèle parent.| |yaxismax|float|La valeur maximale fixe pour l'axe Y.| |yaxismin|float|La valeur minimale fixe pour l'axe Y.| |ymax\_itemid|string|ID de l'élément utilisé comme valeur maximale pour l'axe Y.<br><br>À partir de Zabbix 6.0.7, si l'utilisateur n'a pas accès à l'élément spécifié, le graphique est rendu comme si ymax\_type était défini à '0' (calculé).| |ymax\_type|integer|Méthode de calcul de la valeur maximale pour l'axe Y.<br><br>Valeurs possibles :<br>0 - *(par défaut)* calculé ;<br>1 - fixe ;<br>2 - élément.| |ymin\_itemid|string|ID de l'élément utilisé comme valeur minimale pour l'axe Y.<br><br>À partir de Zabbix 6.0.7, si l'utilisateur n'a pas accès à l'élément spécifié, le graphique est rendu comme si ymin\_type était défini à '0' (calculé).| |ymin\_type|integer|Méthode de calcul de la valeur minimale pour l'axe Y.<br><br>Valeurs possibles :<br>0 - *(par défaut)* calculé ;<br>1 - fixe ;<br>2 - élément.| |discover|integer|Statut de découverte du prototype de graphique.<br><br>Valeurs possibles :<br>0 - *(par défaut)* de nouveaux graphiques seront découverts ;<br>1 - de nouveaux graphiques ne seront pas découverts et les graphiques existants seront marqués comme perdus. | |uuid|string|Identifiant unique universel, utilisé pour lier les prototypes de graphique importés à ceux déjà existants. Utilisé uniquement pour les prototypes de graphique de modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # graphprototype.update # graphprototype.update #### Graphs Edit graphs or separate graph items for better presentation of the gathered data. [Graph API](/manual/api/reference/graph) | [Graph item API](/manual/api/reference/graphitem) #### Graphiques Modifiez des graphiques ou des éléments de graphique séparés pour une meilleure présentation des données recueillies. [API Graphique](/manual/api/reference/graph) | [API Élément de graphique](/manual/api/reference/graphitem) ##### Graphs With the item working for a while, it might be time to see something visual. [Simple graphs](/manual/config/visualization/graphs/simple) are available for any monitored numeric item without any additional configuration. These graphs are generated on runtime. To view the graph, go to *Monitoring → Latest data* and click on the 'Graph' link next to the item. {width="600"} ##### Graphiques Avec l'élément fonctionnant pendant un certain temps, il est peut-être temps de voir quelque chose de visuel. Les [graphiques simples](/manual/config/visualization/graphs/simple) sont disponibles pour tout élément numérique surveillé sans aucune configuration supplémentaire. Ces graphiques sont générés à l'exécution. Pour afficher le graphique, accédez à *Surveillance → Dernières données* et cliquez sur le lien "Graphique" à côté de l'élément. {width="600"} ### Graph The graph object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |graphid|string|*(readonly)* ID of the graph.| |**height**<br>(required)|integer|Height of the graph in pixels.| |**name**<br>(required)|string|Name of the graph| |**width**<br>(required)|integer|Width of the graph in pixels.| |flags|integer|*(readonly)* Origin of the graph.<br><br>Possible values are:<br>0 - *(default)* a plain graph;<br>4 - a discovered graph.| |graphtype|integer|Graph's layout type.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - stacked;<br>2 - pie;<br>3 - exploded.| |percent\_left|float|Left percentile.<br><br>Default: 0.| |percent\_right|float|Right percentile.<br><br>Default: 0.| |show\_3d|integer|Whether to show pie and exploded graphs in 3D.<br><br>Possible values:<br>0 - *(default)* show in 2D;<br>1 - show in 3D.| |show\_legend|integer|Whether to show the legend on the graph.<br><br>Possible values:<br>0 - hide;<br>1 - *(default)* show.| |show\_work\_period|integer|Whether to show the working time on the graph.<br><br>Possible values:<br>0 - hide;<br>1 - *(default)* show.| |show\_triggers|integer|Whether to show the trigger line on the graph.<br><br>Possible values:<br>0 - hide;<br>1 - *(default)* show.| |templateid|string|*(readonly)* ID of the parent template graph.| |yaxismax|float|The fixed maximum value for the Y axis.<br><br>Default: 100.| |yaxismin|float|The fixed minimum value for the Y axis.<br><br>Default: 0.| |ymax\_itemid|string|ID of the item that is used as the maximum value for the Y axis.<br><br>Starting with Zabbix 6.0.7, if user have no access to specified item, the graph is rendered like ymax\_type would be set to '0' (calculated).| |ymax\_type|integer|Maximum value calculation method for the Y axis.<br><br>Possible values:<br>0 - *(default)* calculated;<br>1 - fixed;<br>2 - item.| |ymin\_itemid|string|ID of the item that is used as the minimum value for the Y axis.<br><br>Starting with Zabbix 6.0.7, if user have no access to specified item, the graph is rendered like ymax\_type would be set to '0' (calculated).| |ymin\_type|integer|Minimum value calculation method for the Y axis.<br><br>Possible values:<br>0 - *(default)* calculated;<br>1 - fixed;<br>2 - item.| |uuid|string|Universal unique identifier, used for linking imported graphs to already existing ones. Used only for graphs on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Graphique L'objet graphique a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |graphid|string|*(lecture seule)* ID du graphique.| |**height**<br>(obligatoire)|integer|Hauteur du graphique en pixels.| |**name**<br>(obligatoire)|string|Nom du graphique.| |**width**<br>(obligatoire)|integer|Largeur du graphique en pixels.| |flags|integer|*(lecture seule)* Origine du graphique.<br><br>Les valeurs possibles sont :<br>0 - *(par défaut)* un graphique simple ;<br>4 - un graphique découvert.| |graphtype|integer|Type de disposition du graphique.<br><br>Valeurs possibles :<br>0 - *(par défaut)* normal ;<br>1 - empilé ;<br>2 - circulaire ;<br>3 - éclaté.| |percent\_left|float|Centile gauche.<br><br>Par défaut : 0.| |percent\_right|float|Centile droit.<br><br>Par défaut : 0.| |show\_3d|integer|Indique s'il faut afficher les graphiques circulaires et éclatés en 3D.<br><br>Valeurs possibles :<br>0 - *(par défaut)* afficher en 2D ;<br>1 - afficher en 3D.| |show\_legend|integer|Indique s'il faut afficher la légende sur le graphique.<br><br>Valeurs possibles :<br>0 - masquer ;<br>1 - *(par défaut)* afficher.| |show\_work\_period|integer|Indique s'il faut afficher le temps de travail sur le graphique.<br><br>Valeurs possibles :<br>0 - masquer ;<br>1 - *(par défaut)* afficher.| |show\_triggers|integer|Indique s'il faut afficher la ligne de déclenchement sur le graphique.<br><br>Valeurs possibles :<br>0 - masquer ;<br>1 - *(par défaut)* afficher.| |templateid|string|*(lecture seule)* ID du graphique de modèle parent.| |yaxismax|float|La valeur maximale fixe pour l'axe Y.<br><br>Par défaut : 100.| |yaxismin|float|La valeur minimale fixe pour l'axe Y.<br><br>Par défaut : 0.| |ymax\_itemid|string|ID de l'élément utilisé comme valeur maximale pour l'axe Y.<br><br>À partir de Zabbix 6.0.7, si l'utilisateur n'a pas accès à l'élément spécifié, le graphique est rendu comme si ymax\_type était défini à '0' (calculé).| |ymax\_type|integer|Méthode de calcul de la valeur maximale pour l'axe Y.<br><br>Valeurs possibles :<br>0 - *(par défaut)* calculé ;<br>1 - fixe ;<br>2 - élément.| |ymin\_itemid|string|ID de l'élément utilisé comme valeur minimale pour l'axe Y.<br><br>À partir de Zabbix 6.0.7, si l'utilisateur n'a pas accès à l'élément spécifié, le graphique est rendu comme si ymin\_type était défini à '0' (calculé).| |ymin\_type|integer|Méthode de calcul de la valeur minimale pour l'axe Y.<br><br>Valeurs possibles :<br>0 - *(par défaut)* calculé ;<br>1 - fixe ;<br>2 - élément.| |uuid|string|Identifiant unique universel, utilisé pour lier les graphiques importés à ceux déjà existants. Utilisé uniquement pour les graphiques de modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # graph.update # graph.update ### Group link The group link object links a host prototype with a host group and has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupid**<br>(required)|string|ID of the host group.| ### Lien de groupe L'objet de lien de groupe relie un prototype d'hôte à un groupe d'hôtes et possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupid**<br>(obligatoire)|string|ID du groupe d'hôtes.| #### GUI debugging Problems related to the frontend performance may be diagnosed using the frontend [debug mode](/manual/web_interface/debug_mode). #### Débogage de l'interface graphique Les problèmes liés aux performances de l'interface peuvent être diagnostiqués à l'aide de l'interface [en mode debug](/manual/web_interface/debug_mode). ### Handling of NaN values in Prometheus preprocessing There is a new behavior for handling (skipping) NaN values. So, if a dataset consists of valid numeric values and NaNs, then NaN values are skipped and: - 'avg', 'max', 'min', 'sum' return a result that is calculated from the valid values - 'count' returns the number of valid values If all values in a dataset are NaNs then 'avg', 'max', 'min', and 'sum' return a "no data (at least one value is required)" error, while 'count' returns 0. Previously, if NaN was the first value in a dataset then: - 'avg', 'max', 'min', 'sum' returned a "Value "NAN" of type "string" is not suitable for \ value type "Numeric (float)"" error - 'count' returned the number of values (including NaN values) Also previously, if NaN was not the first value in a dataset then: - 'avg', 'sum' returned a "Value "NAN" of type "string" is not suitable for \ value type "Numeric (float)"" error - 'max' returned the maximum of values until the first NaN was encountered - 'min' returned the minimum of values until the first NaN was encountered - 'count' returned the number of values (including NaN values) ### Gestion des valeurs NaN dans le prétraitement Prometheus Il existe un nouveau comportement pour la gestion (saut) des valeurs NaN. Ainsi, si un jeu de données est composé de valeurs numériques valides et NaN, les valeurs NaN sont ignorées et : - 'avg', 'max', 'min', 'sum' renvoient un résultat calculé à partir des valeurs valides - 'count' renvoie le nombre de valeurs valides Si toutes les valeurs d'un ensemble de données sont NaN, alors 'avg', 'max', 'min' et 'sum' renvoient un "no data (at least one value is required)", tandis que 'count' renvoie 0. Auparavant, si NaN était la première valeur d'un ensemble de données, alors : - 'avg', 'max', 'min', 'sum' renvoyaient une erreur "Value "NAN" of type "string" is not suitable for value type "Numeric (float)"" - 'count' renvoyait le nombre de valeurs (y compris les valeurs NaN) Précédemment également, si NaN n'était pas la première valeur d'un ensemble de données, alors : - · 'avg', 'sum' renvoyaient une erreur "Value "NAN" of type "string" is not suitable for value type "Numeric (float)"" - · 'max' renvoyait le maximum de valeurs jusqu'à ce que le premier NaN soit rencontré - · 'min' renvoyait le minimum de valeurs jusqu'à ce que le premier NaN soit rencontré - · 'count' renvoyait le nombre de valeurs (y compris les valeurs NaN) # hanode.get # hanode.get #### Hardware #### Matériel #### Hardware General advice on hardware: - Use fastest processor available - SCSI or SAS is better than IDE (performance of IDE disks may be significantly improved by using utility hdparm) and SATA - 15K RPM is better than 10K RPM which is better than 7200 RPM - Use fast RAID storage - Use fast Ethernet adapter - Having more memory is always better #### Matériel Conseils généraux sur le matériel : * Utilisez le processeur le plus rapide disponible * SCSI ou SAS est mieux qu'IDE (les performances des disques IDE peuvent être considérablement améliorées en utilisant l'utilitaire hdparm) et SATA * 15K RPM est mieux que 10K RPM qui est mieux que 7200 RPM * Utiliser un stockage RAID rapide * Utiliser un adaptateur Ethernet rapide * Avoir plus de mémoire, c'est toujours mieux #### Header processing The CSV file header line can be processed in two different ways: - If the *With header row* checkbox is marked - header line values are interpreted as column names. In this case the column names must be unique and the data row should not contain more columns than the header row; - If the *With header row* checkbox is not marked - the header line is interpreted as data. Column names are generated automatically (1,2,3,4...) CSV file example: Nr,Item name,Key,Qty 1,active agent item,agent.hostname,33 "2","passive agent item","agent.version","44" 3,"active,passive agent items",agent.ping,55 ::: noteclassic A quotation character within a quoted field in the input must be escaped by preceding it with another quotation character. ::: **Processing header line** JSON output when a header line is expected: ``` {.json} [ { "Nr":"1", "Item name":"active agent item", "Key":"agent.hostname", "Qty":"33" }, { "Nr":"2", "Item name":"passive agent item", "Key":"agent.version", "Qty":"44" }, { "Nr":"3", "Item name":"active,passive agent items", "Key":"agent.ping", "Qty":"55" } ] ``` **No header line processing** JSON output when a header line is not expected: ``` {.json} [ { "1":"Nr", "2":"Item name", "3":"Key" "4":"Qty" }, { "1":"1", "2":"active agent item", "3":"agent.hostname" "4":"33" }, { "1":"2", "2":"passive agent item", "3":"agent.version" "4":"44" }, { "1":"3", "2":"active,passive agent items", "3":"agent.ping" "4":"55" } ] ``` #### Traitement d'en-tête La ligne d'en-tête du fichier CSV peut être traitée de deux manières différentes : - Si la case *Avec ligne d'en-tête* est cochée, les valeurs de la ligne d'en-tête sont interprétées comme des noms de colonne. Dans ce cas, les noms de colonne doivent être uniques et la ligne de données ne doit pas contenir plus de colonnes que la ligne d'en-tête ; - Si la case *Avec ligne d'en-tête* n'est pas cochée, la ligne d'en-tête est interprétée comme des données. Les noms de colonnes sont générés automatiquement (1,2,3,4...) Exemple de fichier CSV : Nr,Item name,Key,Qty 1,active agent item,agent.hostname,33 "2","passive agent item","agent.version","44" 3,"active,passive agent items",agent.ping,55 ::: noteclassic Un guillemet dans un champ entre guillemets dans l'entrée doit être échappé en le faisant précéder d'un autre guillemet. ::: **Traitement de la ligne d'en-tête** Sortie JSON lorsqu'une ligne d'en-tête est attendue : ``` {.json} [ { "Nr":"1", "Item name":"active agent item", "Key":"agent.hostname", "Qty":"33" }, { "Nr":"2", "Item name":"passive agent item", "Key":"agent.version", "Qty":"44" }, { "Nr":"3", "Item name":"active,passive agent items", "Key":"agent.ping", "Qty":"55" } ] ``` **Pas de traitement de ligne d'en-tête** Sortie JSON lorsqu'une ligne d'en-tête n'est pas attendue : ``` {.json} [ { "1":"Nr", "2":"Item name", "3":"Key" "4":"Qty" }, { "1":"1", "2":"active agent item", "3":"agent.hostname" "4":"33" }, { "1":"2", "2":"passive agent item", "3":"agent.version" "4":"44" }, { "1":"3", "2":"active,passive agent items", "3":"agent.ping" "4":"55" } ] ``` ##### Hidden menu Even when the menu is hidden completely, a full menu is just one mouse click away, by clicking on the burger icon. Note that it reappears over page content; to move page content to the right you have to unhide the menu by clicking on the show sidebar button. ##### Menu caché Même lorsque le menu est complètement masqué, un menu complet n'est qu'à un clic de souris, en cliquant sur l'icône du hamburger. Notez qu'il réapparaît sur le contenu de la page ; pour déplacer le contenu de la page vers la droite, vous devez afficher le menu en cliquant sur le bouton Afficher la barre latérale. #### High availability cluster Retrieve a list of server nodes and their status. [High availability cluster API](/manual/api/reference/hanode) #### Cluster haute disponibilité Récupérez une liste de nœuds de serveur et leur état. [API Cluster Haute Disponibilité](/manual/api/reference/hanode) ### High availability node ::: noteclassic Nodes are created by the Zabbix server and cannot be modified via the API. ::: The High availability node object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |ha\_nodeid|string|ID of the node.| |name|string|Name assigned to the node, using the HANodeName configuration entry of zabbix\_server.conf. Empty for a server running in standalone mode.| |address|string|IP or DNS name where the node connects from.| |port|integer|Port on which the node is running.| |lastaccess|integer|Heartbeat time, t.i. time of last update from the node. UTC timestamp.| |status|integer|State of the node.<br><br>Possible values:<br>0 - standby;<br>1 - stopped manually;<br>2 - unavailable;<br>3 - active.| ### Nœud haute disponibilité ::: noteclassic Les nœuds sont créés par le serveur Zabbix et ne peuvent pas être modifiés via l'API. ::: L'objet nœud haute disponibilité possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |ha\_nodeid|string|ID du nœud.| |name|string|Nom attribué au nœud, à l'aide de l'entrée de configuration HANodeName du fichier zabbix\_server.conf. Vide pour un serveur exécuté en mode autonome.| |adresse|string|Nom IP ou DNS à partir duquel le nœud se connecte.| |port|integer|Port sur lequel le nœud s'exécute.| |lastaccess|integer|Heartbeat, heure de la dernière mise à jour à partir du nœud. Horodatage UTC.| |status|integer|État du nœud.<br><br>Valeurs possibles :<br>0 - standby ;<br>1 - arrêté manuellement ;<br>2 - indisponible ;<br>3 - actif.| # history.clear # history.clear # history.get # history.get #### History Retrieve historical values gathered by Zabbix monitoring processes for presentation or further processing. [History API](/manual/api/reference/history) #### Historique Récupérez les valeurs historiques collectées par les processus de surveillance Zabbix pour présentation ou traitement ultérieur. [API Historique](/manual/api/reference/history) ### HMAC function for JavaScript A new function has been added to the JavaScript engine allowing to return HMAC hash: - `hmac('<hash type>',key,string)` This is useful for cases when hash-based message authentication code (HMAC) is required for signing requests. MD5 and SHA256 hash types are supported, e. g.: - `hmac('md5',key,string)` - `hmac('sha256',key,string)` ### fonction HMAC pour JavaScript Une nouvelle fonction a été ajoutée au moteur JavaScript permettant de calculer le hachage HMAC : - · `hmac('<hash type>',key,string)` Ceci est utile dans les cas où un code d'authentification de message basé sur le hachage (HMAC) est requis pour signer les demandes. Les types de hachage MD5 et SHA256 sont pris en charge, par exemple : · - · `hmac('md5',key,string)` · - · `hmac('sha256',key,string)` #### Host access from several user groups A user may belong to any number of user groups. These groups may have different access permissions to hosts. Therefore, it is important to know what hosts an unprivileged user will be able to access as a result. For example, let us consider how access to host **X** (in Hostgroup 1) will be affected in various situations for a user who is in user groups A and B. - If Group A has only *Read* access to Hostgroup 1, but Group B *Read-write* access to Hostgroup 1, the user will get **Read-write** access to 'X'. ::: noteimportant “Read-write” permissions have precedence over “Read” permissions starting with Zabbix 2.2. ::: - In the same scenario as above, if 'X' is simultaneously also in Hostgroup 2 that is **denied** to Group A or B, access to 'X' will be **unavailable**, despite a *Read-write* access to Hostgroup 1. - If Group A has no permissions defined and Group B has a *Read-write* access to Hostgroup 1, the user will get **Read-write** access to 'X'. - If Group A has *Deny* access to Hostgroup 1 and Group B has a *Read-write* access to Hostgroup 1, the user will get access to 'X' **denied**. #### Accès hôte de plusieurs groupes d'utilisateurs Un utilisateur peut appartenir à n'importe quel nombre de groupes d'utilisateurs. Ces groupes peuvent avoir des autorisations d'accès différentes aux hôtes. Par conséquent, il est important de savoir à quels hôtes un utilisateur non privilégié pourra accéder. Par exemple, examinons comment l'accès à l'hôte **X** (dans le groupe d'hôtes 1) sera affecté dans diverses situations pour un utilisateur qui se trouve dans les groupes d'utilisateurs A et B. - Si le groupe A n'a qu'un accès en *lecture* au groupe d'hôtes 1, mais que le groupe B a un accès en *lecture-écriture* au groupe d'hôtes 1, l'utilisateur obtiendra un accès en **lecture-écriture** à 'X'. ::: noteimportant Les autorisations "Lecture-écriture" ont priorité sur les autorisations "Lecture" à partir de Zabbix 2.2. ::: - Dans le même scénario que ci-dessus, si 'X' est simultanément également dans le groupe d'hôtes 2 qui est **refusé** au groupe A ou B, l'accès à 'X' sera **indisponible**, malgré un accès en *lecture-écriture* au groupe d'hôtes 1. - Si le groupe A n'a pas d'autorisation définie et que le groupe B a un accès *Lecture-écriture* au groupe d'hôtes 1, l'utilisateur obtiendra un accès en **Lecture-écriture** à 'X'. - Si le groupe A a un accès *Refusé* au groupe d'hôtes 1 et que le groupe B a un accès *Lecture-écriture* au groupe d'hôtes 1, l'utilisateur aura accès à 'X' **refusé**. ##### Host configuration A host must be configured to process IPMI checks. An IPMI interface must be added, with the respective IP and port numbers, and IPMI authentication parameters must be defined. See the [configuration of hosts](/manual/config/hosts/host) for more details. ##### Configuration de l'hôte Un hôte doit être configuré pour traiter les vérifications IPMI. Une interface IPMI doit être ajoutée, avec les adresses IP et les numéros de port respectifs, et les paramètres d'authentification IPMI doivent être définis. Voir la [configuration des hôtes](/fr/manual/config/hosts/host) pour plus de détails. #### Host configuration To use VMware simple checks the host must have the following user macros defined: - **{$VMWARE.URL}** - VMware service (vCenter or ESX hypervisor) SDK URL (<https://servername/sdk>) - **{$VMWARE.USERNAME}** - VMware service user name - **{$VMWARE.PASSWORD}** - VMware service {$VMWARE.USERNAME} user password #### Paramétrage de l'hôte Pour utiliser les vérifications simples VMware, l'hôte doit avoir défini les macros utilisateur suivantes : - **{$VMWARE.URL}** - URL du SDK du service VMware (hyperviseur vCenter ou ESX) (<https://servername/sdk>) - **{$VMWARE.USERNAME}** - Nom d'utilisateur du service VMware - **{$VMWARE.PASSWORD}** - Mot de passe utilisateur du service VMware {$VMWARE.USERNAME} ##### Host configuration You can specify that an individual host should be monitored by a proxy in the [host configuration](/manual/config/hosts/host) form, using the *Monitored by proxy* field.  Host [mass update](/manual/config/hosts/hostupdate) is another way of specifying that hosts should be monitored by a proxy. ##### Configuration de l\'hôte Vous pouvez spécifier qu\'un hôte spécifique doit être surveillé par un proxy dans le formulaire de [configuration de l\'hôte](/manual/config/hosts/host), en utilisant le champ *Surveillé via le proxy*.  La [mise à jour groupée](/manual/config/hosts/hostupdate) des hôtes peut être une autre façon de spécifier que les hôtes doivent être surveillés par un proxy. # host.create # host.create # host.delete # host.delete # host.get # host.get ##### Host graph tags |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |name|x|`string`| |Graph name.| | |width|\-|`integer`|20-65535 (default: 900)|Graph width, in pixels. Used for preview and for pie/exploded graphs.| | |height|\-|`integer`|20-65535 (default: 200)|Graph height, in pixels. Used for preview and for pie/exploded graphs.| | |yaxismin|\-|`double`|Default: 0|Value of Y axis minimum.<br><br>Used if 'ymin\_type\_1' is FIXED.| | |yaxismax|\-|`double`|Default: 0|Value of Y axis maximum.<br><br>Used if 'ymax\_type\_1' is FIXED.| | |show\_work\_period|\-|`string`|0 - NO<br>1 - YES (default)|Highlight non-working hours.<br><br>Used by normal and stacked graphs.| | |show\_triggers|\-|`string`|0 - NO<br>1 - YES (default)|Display simple trigger values as a line.<br><br>Used by normal and stacked graphs.| | |type|\-|`string`|0 - NORMAL (default)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Graph type.| | |show\_legend|\-|`string`|0 - NO<br>1 - YES (default)|Display graph legend.| | |show\_3d|\-|`string`|0 - NO (default)<br>1 - YES|Enable 3D style.<br><br>Used by pie and exploded pie graphs.| | |percent\_left|\-|`double`|Default:0|Show the percentile line for left axis.<br><br>Used only for normal graphs.| | |percent\_right|\-|`double`|Default:0|Show the percentile line for right axis.<br><br>Used only for normal graphs.| | |ymin\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Minimum value of Y axis.<br><br>Used by normal and stacked graphs.| | |ymax\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Maximum value of Y axis.<br><br>Used by normal and stacked graphs.| |ymin\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymin\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |ymax\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymax\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |graph\_items| |x| | |Root element for graph items.| | |sortorder|\-|`integer`| |Draw order. The smaller value is drawn first. Can be used to draw lines or regions behind (or in front of) another.| | |drawtype|\-|`string`|0 - SINGLE\_LINE (default)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Draw style of the graph item.<br><br>Used only by normal graphs.| | |color|\-|`string`| |Element color (6 symbols, hex).| | |yaxisside|\-|`string`|0 - LEFT (default)<br>1 - RIGHT|Side of the graph where the graph item's Y scale will be drawn.<br><br>Used by normal and stacked graphs.| | |calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG (default)<br>4 - MAX<br>7 - ALL (minimum, average and maximum; used only by simple graphs)<br>9 - LAST (used only by pie and exploded pie graphs)|Data to draw if more than one value exists for an item.| | |type|\-|`string`|0 - SIMPLE (default)<br>2 - GRAPH\_SUM (value of the item represents the whole pie; used only by pie and exploded pie graphs)|Graph item type.| |item| |x| | |Individual item.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| ##### Tags de graphique d'hôte |Élément|Propriété de l'élément|Requis|Type|Plage^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Élément racine pour les graphiques.| | |name|x|`chaîne`| |Graph name.| | |width|\-|`entier`|20-65535 (par défaut : 900)|Largeur du graphique, en pixels. Utilisé pour l'aperçu et pour les graphiques à secteurs/éclatés.| | |height|\-|`entier`|20-65535 (par défaut : 200)|Hauteur du graphique, en pixels. Utilisé pour l'aperçu et pour les graphiques à secteurs/éclatés.| | |yaxismin|\-|`double`|Par défaut : 0|Valeur minimale de l'axe Y.<br><br>Utilisé si 'ymin\_type\_1' est FIXED.| | |yaxismax|\-|`double`|Par défaut : 0|Vvaleur maximale de l'axe Y.<br><br>Utilisé si 'ymax\type\_1' est FIXED.| | |show\_work\_period|\-|`chaîne`|0 - NO<br>1 - YES (par défaut)|Mettez en surbrillance les heures non travaillées.<br><br>Utilisé par les graphiques normaux et empilés.| | |show\_triggers|\-|`chaîne`|0 - NO<br>1 - YES (par défaut)|Afficher des valeurs de déclenchement simples sous forme de ligne.<br><br>Utilisé par les graphiques normaux et empilés.| | |type|\-|`chaîne`|0 - NORMAL (par défaut)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Type de graphique.| | |show\_legend|\-|`chaîne`|0 - NO<br>1 - YES (par défaut)|Afficher la légende du graphique.| | |show\_3d|\-|`chaîne`|0 - NO (par défaut)<br>1 - YES|Activer le style 3D.<br><br>Utilisé par les graphiques à secteurs et les graphiques à secteurs éclatés.| | |percent\_left|\-|`double`|Par défaut : 0|Afficher la ligne centile pour l'axe de gauche.<br><br>Utilisé uniquement pour les graphiques normaux.| | |percent\_right|\-|`double`|Par défaut : 0|Afficher la ligne centile pour l'axe de droite.<br><br>Utilisé uniquement pour les graphiques normaux.| | |ymin\_type\_1|\-|`chaîne`|0 - CALCULATED (par défaut)<br>1 - FIXED<br>2 - ITEM|Valeur minimale de l'axe Y.<br><br>Utilisé par les graphiques normaux et empilés.| | |ymax\_type\_1|\-|`chaîne`|0 - CALCULATED (par défaut)<br>1 - FIXED<br>2 - ITEM|Valeur maximale de l'axe Y.<br><br>Utilisé par les graphiques normaux et empilés.| |ymin\_item\_1| |\-| | |Détails de chaque élément.<br><br>Requis si 'ymin\_type\_1' est ITEM.| | |host|x|`chaîne`| |Hôte de l'élément.| | |key|x|`chaîne`| |Clé de l'élément.| |ymax\_item\_1| |\-| | |Détails de chaque élément.<br><br>Requis si 'ymax\_type\_1' est ITEM.| | |host|x|`chaîne`| |Hôte de l'élément.| | |key|x|`chaîne`| |Clé de l'élément.| |graph\_items| |x| | |Élément racine pour les éléments de graphique.| | |sortorder|\-|`entier`| |Ordre de tirage. La plus petite valeur est dessinée en premier. Peut être utilisé pour tracer des lignes ou des régions derrière (ou devant) une autre.| | |drawtype|\-|`chaîne`|0 - SINGLE\_LINE (par défaut)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Style de dessin de l'élément graphique.<br><br>Utilisé uniquement par les graphiques normaux.| | |color|\-|`chaîne`| |Couleur de l'élément (6 symboles, hexadécimal).| | |yaxisside|\-|`chaîne`|0 - LEFT (par défaut)<br>1 - RIGHT|Côté du graphique où l'échelle Y de l'élément de graphique sera dessinée.<br><br>Utilisé par les graphiques normaux et empilés.| | |calc\_fnc|\-|`chaîne`|1 - MIN<br>2 - AVG (par défaut)<br>4 - MAX<br>7 - ALL (minimum, moyenne et maximum; utilisé uniquement par des graphiques simples)<br>9 - LAST (utilisé uniquement par les camemberts et les camemberts éclatés)|Données à dessiner s'il existe plusieurs valeurs pour un élément.| | |type|\-|`chaîne`|0 - SIMPLE (par défaut)<br>2 - GRAPH\_SUM (la valeur de l'élément représente l'ensemble du secteur ; utilisé uniquement par les graphiques à secteurs et les graphiques à secteurs éclatés)|Type d'élément de graphique.| |item| |x| | |Élément individuel.| | |host|x|`chaîne`| |Hôte de l'élément.| | |key|x|`chaîne`| |Clé de l'élément.| # hostgroup.create # hostgroup.create # hostgroup.delete # hostgroup.delete # hostgroup.get # hostgroup.get # hostgroup.massadd # hostgroup.massadd # hostgroup.massremove # hostgroup.massremove # hostgroup.massupdate # hostgroup.massupdate ### Host group The host group object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groupid|string|*(readonly)* ID of the host group.| |**name**<br>(required)|string|Name of the host group.| |flags|integer|*(readonly)* Origin of the host group.<br><br>Possible values:<br>0 - a plain host group;<br>4 - a discovered host group.| |internal|integer|*(readonly)* Whether the group is used internally by the system. An internal group cannot be deleted.<br><br>Possible values:<br>0 - *(default)* not internal;<br>1 - internal.| |uuid|string|Universal unique identifier, used for linking imported host groups to already existing ones. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Groupe d'Hôte L'objet groupe d'hôtes a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groupid|string|*(lecture seule)* ID du groupe d'hôtes.| |**name**<br>(obligatoire)|string|Nom du groupe d'hôtes.| |flags|integer|*(lecture seule)* Origine du groupe d'hôtes.<br><br>Valeurs possibles :<br>0 - un groupe d'hôtes brut ;<br>4 - un groupe d'hôtes découvert.| |internal|integer|*(lecture seule)* Indique si le groupe est utilisé en interne par le système. Un groupe interne ne peut pas être supprimé.<br><br>Valeurs possibles :<br>0 - *(par défaut)* non interne ;<br>1 - interne.| |uuid|string|Identificateur universel unique, utilisé pour lier les groupes d'hôtes importés à ceux déjà existants. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # hostgroup.update # hostgroup.update # hostinterface.create # hostinterface.create # hostinterface.delete # hostinterface.delete # hostinterface.get # hostinterface.get # hostinterface.massadd # hostinterface.massadd # hostinterface.massremove # hostinterface.massremove # hostinterface.replacehostinterfaces # hostinterface.replacehostinterfaces # hostinterface.update # hostinterface.update ### Host inventory The host inventory object has the following properties. ::: notetip Each property has it's own unique ID number, which is used to associate host inventory fields with items. ::: |ID|Property|[Type](/manual/api/reference_commentary#data_types)|Description|Maximum length| |-|--|-|-----|-----| |4|alias|string|Alias.|128 characters| |11|asset\_tag|string|Asset tag.|64 characters| |28|chassis|string|Chassis.|64 characters| |23|contact|string|Contact person.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |32|contract\_number|string|Contract number.|64 characters| |47|date\_hw\_decomm|string|HW decommissioning date.|64 characters| |46|date\_hw\_expiry|string|HW maintenance expiry date.|64 characters| |45|date\_hw\_install|string|HW installation date.|64 characters| |44|date\_hw\_purchase|string|HW purchase date.|64 characters| |34|deployment\_status|string|Deployment status.|64 characters| |14|hardware|string|Hardware.|255 characters| |15|hardware\_full|string|Detailed hardware.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |39|host\_netmask|string|Host subnet mask.|39 characters| |38|host\_networks|string|Host networks.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |40|host\_router|string|Host router.|39 characters| |30|hw\_arch|string|HW architecture.|32 characters| |33|installer\_name|string|Installer name.|64 characters| |24|location|string|Location.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |25|location\_lat|string|Location latitude.|16 characters| |26|location\_lon|string|Location longitude.|16 characters| |12|macaddress\_a|string|MAC address A.|64 characters| |13|macaddress\_b|string|MAC address B.|64 characters| |29|model|string|Model.|64 characters| |3|name|string|Name.|128 characters| |27|notes|string|Notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |41|oob\_ip|string|OOB IP address.|39 characters| |42|oob\_netmask|string|OOB host subnet mask.|39 characters| |43|oob\_router|string|OOB router.|39 characters| |5|os|string|OS name.|128 characters| |6|os\_full|string|Detailed OS name.|255 characters| |7|os\_short|string|Short OS name.|128 characters| |61|poc\_1\_cell|string|Primary POC mobile number.|64 characters| |58|poc\_1\_email|string|Primary email.|128 characters| |57|poc\_1\_name|string|Primary POC name.|128 characters| |63|poc\_1\_notes|string|Primary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |59|poc\_1\_phone\_a|string|Primary POC phone A.|64 characters| |60|poc\_1\_phone\_b|string|Primary POC phone B.|64 characters| |62|poc\_1\_screen|string|Primary POC screen name.|64 characters| |68|poc\_2\_cell|string|Secondary POC mobile number.|64 characters| |65|poc\_2\_email|string|Secondary POC email.|128 characters| |64|poc\_2\_name|string|Secondary POC name.|128 characters| |70|poc\_2\_notes|string|Secondary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |66|poc\_2\_phone\_a|string|Secondary POC phone A.|64 characters| |67|poc\_2\_phone\_b|string|Secondary POC phone B.|64 characters| |69|poc\_2\_screen|string|Secondary POC screen name.|64 characters| |8|serialno\_a|string|Serial number A.|64 characters| |9|serialno\_b|string|Serial number B.|64 characters| |48|site\_address\_a|string|Site address A.|128 characters| |49|site\_address\_b|string|Site address B.|128 characters| |50|site\_address\_c|string|Site address C.|128 characters| |51|site\_city|string|Site city.|128 characters| |53|site\_country|string|Site country.|64 characters| |56|site\_notes|string|Site notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |55|site\_rack|string|Site rack location.|128 characters| |52|site\_state|string|Site state.|64 characters| |54|site\_zip|string|Site ZIP/postal code.|64 characters| |16|software|string|Software.|255 characters| |18|software\_app\_a|string|Software application A.|64 characters| |19|software\_app\_b|string|Software application B.|64 characters| |20|software\_app\_c|string|Software application C.|64 characters| |21|software\_app\_d|string|Software application D.|64 characters| |22|software\_app\_e|string|Software application E.|64 characters| |17|software\_full|string|Software details.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |10|tag|string|Tag.|64 characters| |1|type|string|Type.|64 characters| |2|type\_full|string|Type details.|64 characters| |35|url\_a|string|URL A.|255 characters| |36|url\_b|string|URL B.|255 characters| |37|url\_c|string|URL C.|255 characters| |31|vendor|string|Vendor.|64 characters| ### Inventaire d'hôte L'objet d'inventaire hôte a les propriétés suivantes. ::: notetip Chaque propriété a son propre numéro d'identification unique, utilisé pour associer des champs d'inventaire hôte à des éléments. ::: |ID|Propriété|[Type](/manual/api/reference_commentary#types-de-données)|Description| |-|--|-|-----|-----| |4|alias|string|Alias.|128 caractères| |11|asset\_tag|string|Tag caractéristique.|64 caractères| |28|chassis|string|Châssis.|64 caractères| |23|contact|string|Personne de contact.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |32|contract\_number|string|Numéro de contrat.|64 caractères| |47|date\_hw\_decomm|string|Matériel - Date de retrait.|64 caractères| |46|date\_hw\_expiry|string|Matériel - Date de fin de maintenance|64 caractères| |45|date\_hw\_install|string|Matériel - Date d'installation.|64 caractères| |44|date\_hw\_purchase|string|Matériel - Date d'achat.|64 caractères| |34|deployment\_status|string|État du déploiement.|64 caractères| |14|hardware|string|Matériel.|255 caractères| |15|hardware\_full|string|Matériel Détails complet.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |39|host\_netmask|string|Masque de sous-réseau de l'hôte.|39 caractères| |38|host\_networks|string|Réseaux de l'hôte.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |40|host\_router|string|Hôte - Routeur.|39 caractères| |30|hw\_arch|string|Architecture matérielle.|32 caractères| |33|installer\_name|string|Nom de l'installeur.|64 caractères| |24|location|string|Emplacement.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |25|location\_lat|string|Latitude de l'emplacement.|16 caractères| |26|location\_lon|string|Longitude de l'emplacement.|16 caractères| |12|macaddress\_a|string|Adresse MAC A.|64 caractères| |13|macaddress\_b|string|Adresse MAC B.|64 caractères| |29|model|string|Modèle.|64 caractères| |3|name|string|Nom.|128 caractères| |27|notes|string|Notes.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |41|oob\_ip|string|Adresse IP OOB.|39 caractères| |42|oob\_netmask|string|Masque de sous-réseau OOB.|39 caractères| |43|oob\_router|string|Routeur OOB.|39 caractères| |5|os|string|OS.|128 caractères| |6|os\_full|string|Nom complet de l'OS.|255 caractères| |7|os\_short|string|Nom court de l'OS.|128 caractères| |61|poc\_1\_cell|string|Contact Principal - Mobile.|64 caractères| |58|poc\_1\_email|string|Contact Principal - Courriel.|128 caractères| |57|poc\_1\_name|string|Contact Principal - Nom.|128 caractères| |63|poc\_1\_notes|string|Contact Principal - Notes.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |59|poc\_1\_phone\_a|string|Contact Principal - Téléphone 1.|64 caractères| |60|poc\_1\_phone\_b|string|Contact Principal - Téléphone 2.|64 caractères| |62|poc\_1\_screen|string|Contact Principal - Identifiant.|64 caractères| |68|poc\_2\_cell|string|Contact Secondaire - Mobile.|64 caractères| |65|poc\_2\_email|string|Contact Secondaire - Courriel.|128 caractères| |64|poc\_2\_name|string|Contact Secondaire - Nom.|128 caractères| |70|poc\_2\_notes|string|Contact Secondaire - Notes.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |66|poc\_2\_phone\_a|string|Contact Secondaire - Téléphone 1.|64 caractères| |67|poc\_2\_phone\_b|string|Contact Secondaire - Téléphone 2.|64 caractères| |69|poc\_2\_screen|string|Contact Secondaire - Identifiant.|64 caractères| |8|serialno\_a|string|Numéro de série A.|64 caractères| |9|serialno\_b|string|Numéro de série B.|64 caractères| |48|site\_address\_a|string|Site - Adresse 1.|128 caractères| |49|site\_address\_b|string|Site - Adresse 2.|128 caractères| |50|site\_address\_c|string|Site - Adresse 3.|128 caractères| |51|site\_city|string|Site - Ville.|128 caractères| |53|site\_country|string|Site - Pays.|64 caractères| |56|site\_notes|string|Site - Notes.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |55|site\_rack|string|Site - Localisation baie.|128 caractères| |52|site\_state|string|Site - Etat / province.|64 caractères| |54|site\_zip|string|Site - Code postal.|64 caractères| |16|software|string|Logiciel.|255 caractères| |18|software\_app\_a|string|Application logicielle A.|64 caractères| |19|software\_app\_b|string|Application logicielle B.|64 caractères| |20|software\_app\_c|string|Application logicielle C.|64 caractères| |21|software\_app\_d|string|Application logicielle D.|64 caractères| |22|software\_app\_e|string|Application logicielle E.|64 caractères| |17|software\_full|string|Détails du logiciel.|Dépend de la base de données utilisée : <br>- 65535 caractères pour les bases de données SQL <br>- 2048 caractères pour les bases de données Oracle| |10|tag|string|Étiquette.|64 caractères| |1|type|string|Type.|64 caractères| |2|type\_full|string|Détails du type.|64 caractères| |35|url\_a|string|URL A.|255 caractères| |36|url\_b|string|URL B.|255 caractères| |37|url\_c|string|URL C.|255 caractères| |31|vendor|string|Fabricant.|64 caractères| ##### Host low-level discovery rule tags |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Root element for low-level discovery rules.| | |*For most of the element tag values, see element tag values for a regular item. Only the tags that are specific to low-level discovery rules, are described below.*| | | | | | |type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`string`|Default: 30d|Time period after which items that are no longer discovered will be deleted. Seconds, time unit with suffix or user macro.| |filter| | | | |Individual filter.| | |evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logic to use for checking low-level discovery rule filter conditions.| | |formula|\-|`string`| |Custom calculation formula for filter conditions.| |conditions| |\-| | |Root element for filter conditions.| | |macro|x|`string`| |Low-level discovery macro name.| | |value|\-|`string`| |Filter value: regular expression or global regular expression.| | |operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|Condition operator.| | |formulaid|x|`character`| |Arbitrary unique ID that is used to reference a condition from the custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |lld\_macro\_paths| |\-| | |Root element for LLD macro paths.| | |lld\_macro|x|`string`| |Low-level discovery macro name.| | |path|x|`string`| |Selector for value which will be assigned to the corresponding macro.| |preprocessing| |\-| | |LLD rule value preprocessing.| |step| |\-| | |Individual LLD rule value preprocessing step.| | |*For most of the element tag values, see element tag values for a host item value preprocessing. Only the tags that are specific to low-level discovery value preprocessing, are described below.*| | | | | | |type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|Type of the item value preprocessing step.| |trigger\_prototypes| |\-| | |Root element for trigger prototypes.| | |*For trigger prototype element tag values, see regular [host trigger](/manual/xml_export_import/hosts#host_trigger_tags) tags.*| | | | | |graph\_prototypes| |\-| | |Root element for graph prototypes.| | |*For graph prototype element tag values, see regular [host graph](/manual/xml_export_import/hosts#host_graph_tags) tags.*| | | | | |host\_prototypes| |\-| | |Root element for host prototypes.| | |*For host prototype element tag values, see regular [host](/manual/xml_export_import/hosts#host_tags) tags.*| | | | | |item\_prototypes| |\-| | |Root element for item prototypes.| | |*For item prototype element tag values, see regular [host item](/manual/xml_export_import/hosts#host_item_tags) tags.*| | | | | |master\_item| |\-| | |Individual item prototype master item/item prototype data.| | |key|x|`string`| |Dependent item prototype master item/item prototype key value.<br><br>Required for a dependent item.| ##### Tags de règle de découverte de bas niveau d'hôte |Élément|Propriété de l'élément|Obligatoire|Type|Plage^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Élément racine pour les règles de découverte de bas niveau.| | |*Pour la plupart des valeurs de tag d'élément, consultez les valeurs de tag d'élément pour un élément standard. Seuls les tags spécifiques aux règles de découverte de bas niveau sont décrites ci-dessous.*| | | | | | |type|\-|`chaîne`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`chaîne`|Par défaut : 30j|Période après laquelle les éléments qui ne sont plus découverts seront supprimés. Secondes, unité de temps avec suffixe ou macro utilisateur.| |filter| | | | |Filtre individuel.| | |evaltype|\-|`chaîne`|0 - AND\_OR (par défaut)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logique à utiliser pour vérifier les conditions de filtrage des règles de découverte de bas niveau.| | |formula|\-|`chaîne`| |Formule de calcul personnalisée pour les conditions de filtre.| |conditions| |\-| | |Élément racine pour les conditions de filtre.| | |macro|x|`chaîne`| |Nom de la macro de découverte de bas niveau.| | |value|\-|`chaîne`| |Valeur du filtre : expression régulière ou expression régulière globale.| | |operator|\-|`chaîne`|8 - MATCHES\_REGEX (par défaut)<br>9 - NOT\_MATCHES\_REGEX|Opérateur de condition.| | |formulaid|x|`caractère`| |ID unique arbitraire utilisé pour référencer une condition à partir de l'expression personnalisée. Ne peut contenir que des lettres majuscules. L'ID doit être défini par l'utilisateur lors de la modification des conditions de filtrage, mais sera généré à nouveau lors de sa demande ultérieure.| |lld\_macro\_paths| |\-| | |Élément racine pour les chemins de macro LLD.| | |lld\_macro|x|`chaîne`| |Nom de la macro de découverte de bas niveau.| | |path|x|`chaîne`| |Sélecteur de valeur qui sera affectée à la macro correspondante.| |preprocessing| |\-| | |Prétraitement de la valeur de la règle LLD.| |step| |\-| | |Étape de prétraitement de valeur de règle LLD individuelle.| | |*Pour la plupart des valeurs de tag d'élément, consultez Valeurs de tag d'élément pour un prétraitement de valeur d'élément hôte. Seuls les tags spécifiques au prétraitement de valeur de découverte de bas niveau sont décrites ci-dessous.*| | | | | | |type|x|`chaîne`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|Type d'étape de prétraitement de la valeur de l'élément.| |trigger\_prototypes| |\-| | |Élément racine pour les prototypes de déclencheur.| | |*Pour les valeurs de tag d'élément de prototype de déclencheur, voir les tags réguliers de [déclencheur d'hôte](/manual/xml_export_import/hosts#host_trigger_tags).*| | | | | |graph\_prototypes| |\-| | |Élément racine pour les prototypes de graphique.| | |*Pour les valeurs de tag d'élément de prototype de graphique, voir les tags réguliers de [graphique d'hôte](/manual/xml_export_import/hosts#host_graph_tags).*| | | | | |host\_prototypes| |\-| | |Élément racine pour les prototypes d'hôte.| | |*Pour les valeurs de tag d'élément de prototype d'hôte, voir les tags d'[hôte] régulières(/manual/xml_export_import/hosts#host_tags).*| | | | | |item\_prototypes| |\-| | |Élément racine pour les prototypes d'élément.| | |*Pour les valeurs de tag d'élément de prototype d'élément, consultez les tags d'[élément d'hôte](/manual/xml_export_import/hosts#host_item_tags).*| | | | | |master\_item| |\-| | |Prototype d'élément individuel Élément maître/Données de prototype d'élément.| | |key|x|`chaîne`| |Valeur clé de l'élément principal du prototype d'élément dépendant/prototype d'élément.<br><br>Requis pour un élément dépendant.| ### Host macro The host macro object defines a macro available on a host, host prototype or template. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostmacroid|string|*(readonly)* ID of the host macro.| |**hostid**<br>(required)|string|ID of the host that the macro belongs to.| |**macro**<br>(required)|string|Macro string.| |**value**<br>(required)|string|Value of the macro.| |type|integer|Type of macro.<br><br>Possible values:<br>0 - *(default)* Text macro;<br>1 - Secret macro;<br>2 - Vault secret.| |description|string|Description of the macro.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Macro d'hôte L'objet macro d'hôte définit une macro disponible sur un hôte, un prototype d'hôte ou un modèle. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostmacroid|string|*(lecture seule)* ID de la macro d'hôte.| |**hostid**<br>(obligatoire)|string|ID de l'hôte auquel appartient la macro.| |**macro**<br>(obligatoire)|string|Chaîne de la macro.| |**value**<br>(obligatoire)|string|Valeur de la macro.| |type|integer|Type de la macro.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Macro texte;<br>1 - Macro secrète ;<br>2 - Secret du coffre-fort.| |description|string|Description de la macro.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. Host markers displayed on the map have the color of the host's most serious problem and green color if a host has no problems. Clicking on a host marker allows viewing the host's visible name and the number of unresolved problems grouped by severity. Clicking on the visible name will open [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu). Hosts displayed on the map can be filtered by problem severity. Press on the filter icon in the widget's upper right corner and mark the required severities.  Les marqueurs d'hôte affichés sur la carte ont la couleur du problème le plus grave de l'hôte et la couleur verte si un hôte n'a aucun problème. Cliquer sur un marqueur d'hôte permet d'afficher le nom visible de l'hôte et le nombre de problèmes non résolus regroupés par sévérité. Cliquer sur le nom visible ouvrira le [menu hôte](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu). Les hôtes affichés sur la carte peuvent être filtrés par sévérité de problème. Appuyez sur l'icône de filtre dans le coin supérieur droit du widget et cochez les sévérités requises.  # host.massadd # host.massadd # host.massremove # host.massremove # host.massupdate # host.massupdate #### Host menu Clicking on a host in the *Problems* widget brings up the host menu. It includes links to host inventory, latest data, problems, graphs, dashboards, web scenarios and configuration. Note that host configuration is available for Admin and Superadmin users only.  [Global scripts](/manual/web_interface/frontend_sections/administration/scripts) can also be run from the host menu. These scripts need to have their scope defined as 'Manual host action' to be available in the host menu. The host menu is accessible by clicking on a host in several other frontend sections: - Monitoring → [Problems](problems) - Monitoring → [Problems](problems) → Event details - Monitoring → [Hosts](hosts) - Monitoring → Hosts → [Web Monitoring](/manual/web_interface/frontend_sections/monitoring/hosts/web) - Monitoring → [Latest data](latest_data) - Monitoring → [Maps](maps) - Reports → [Triggers top 100](/manual/web_interface/frontend_sections/reports/triggers_top) #### Menu Hôte Cliquer sur un hôte dans le widget *Problèmes* fait apparaître le menu de l'hôte. Il comprend des liens vers l'inventaire des hôtes, les dernières données, les problèmes, les graphiques, les tableaux de bord, les scénarios Web et la configuration. Notez que la configuration de l'hôte est disponible uniquement pour les utilisateurs Admin et Superadmin.  Les [scripts globaux](/manual/web_interface/frontend_sections/administration/scripts) peuvent également être exécutés à partir du menu hôte. Ces scripts doivent avoir leur portée définie comme 'Action manuelle de l'hôte' pour être disponibles dans le menu de l'hôte. Le menu hôte est accessible en cliquant sur un hôte dans plusieurs autres sections de l'interface : - Surveillance → [Problèmes](problems) - Surveillance → [Problèmes](problems) → Détails de l'événement - Surveillance → [Hôtes](hosts) - Surveillance → Hôtes→ [Web](/manual/web_interface/frontend_sections/monitoring/hosts/web) - Surveillance → [Dernières données](latest_data) - Surveillance → [Cartes](maps) - Rapports→ [Top 100 des déclencheurs](/manual/web_interface/frontend_sections/reports/triggers_top) ##### Host naming When adding hosts, a host name is the result of reverse DNS lookup or IP address if reverse lookup fails. Lookup is performed from the Zabbix server or Zabbix proxy, depending on which is doing the discovery. If lookup fails on the proxy, it is not retried on the server. If the host with such a name already exists, the next host would get **\_2** appended to the name, then **\_3** and so on. It is also possible to override DNS/IP lookup and instead use an item value for host name, for example: - You may discover multiple servers with Zabbix agent running using a Zabbix agent item for discovery and assign proper names to them automatically, based on the string value returned by this item - You may discover multiple SNMP network devices using an SNMP agent item for discovery and assign proper names to them automatically, based on the string value returned by this item If the host name has been set using an item value, it is not updated during the following discovery checks. If it is not possible to set host name using an item value, default value (DNS name) is used. If a host already exists with the discovered IP address, a new host is not created. However, if the discovery action contains operations (link template, add to host group, etc), they are performed on the existing host. ##### Nommage de l'hôte Lors de l'ajout d'hôtes, un nom d'hôte est le résultat d'une recherche DNS inversée (lookup) ou d'une adresse IP si la recherche inversée échoue. La recherche est effectuée à partir du serveur Zabbix ou du proxy Zabbix, en fonction de celui effectuant la découverte. Si la recherche échoue sur le proxy, elle n'est pas relancée sur le serveur. Si l'hôte avec un tel nom existe déjà, l'hôte suivant se verra ajouter **_2** au nom, puis **_3** et ainsi de suite. Il est également possible de remplacer la recherche DNS/IP et d'utiliser à la place une valeur d'élément pour le nom d'hôte, par exemple : - Vous pouvez découvrir plusieurs serveurs avec l'agent Zabbix en cours d'exécution à l'aide d'un élément d'agent Zabbix pour la découverte et leur attribuer automatiquement des noms propres, en fonction de la valeur de chaîne renvoyée par cet élément - Vous pouvez découvrir plusieurs périphériques réseau SNMP à l'aide d'un élément d'agent SNMP pour la découverte et leur attribuer automatiquement des noms propres, en fonction de la valeur de chaîne renvoyée par cet élément Si le nom d'hôte a été défini à l'aide d'une valeur d'élément, il n'est pas mis à jour lors des vérifications de découverte suivantes. S'il n'est pas possible de définir le nom d'hôte à l'aide d'une valeur d'élément, la valeur par défaut (nom DNS) est utilisée. Si un hôte existe déjà avec l'adresse IP découverte, aucun nouvel hôte n'est créé. Toutefois, si l'action de découverte contient des opérations (lien avec un modèle, ajout au groupe d'hôtes, etc.), elles sont effectuées sur l'hôte existant. # hostprototype.create # hostprototype.create # hostprototype.delete # hostprototype.delete # hostprototype.get # hostprototype.get #### Host prototypes Host prototypes can be created with the low-level discovery rule. When virtual machines are discovered, these prototypes become real hosts. Prototypes, before becoming discovered, cannot have their own items and triggers, other than those from the linked templates. Discovered hosts will belong to an existing host.  In order for hosts created from a prototype to have unique host names, the *Host name* field must contain at least one [low-level discovery macro](/manual/config/macros/lld_macros). Since Zabbix 5.2, discovered hosts may be configured with custom interfaces or inherit the IP of a host the discovery rule belongs to (default). To add one or more custom interface, switch the *Interface* selector from *Inherit* to *Custom* mode, then press  and select the required interface type from the drop-down menu that appears. All supported types of interfaces can be defined for a host prototype: Zabbix agent, SNMP, JMX, IPMI. Interface fields support low-level discovery macros and [user macros](/manual/config/macros/user_macros). If several custom interfaces are specified - use the *Default* column to specify the primary interface. Notes: - If *Custom* is selected, but no interfaces have been specified the hosts will be created without interfaces. - If *Inherit* is selected for a host prototype that belongs to a template, discovered hosts will inherit the interface of a host to which the template is linked to. ::: notewarning A host will not be created, if the host interface contains incorrect data :::  LLD macros can also be used for the visible name, host group prototype fields, tag values, or values of host prototype user macros. Other options that can be specified for a host prototype are: - Linkage to existing host groups - Template linkage - Encryption If *Create enabled* is checked, the host will be added in an enabled state. If unchecked, the host will be added, but in a disabled state. If *Discover* is checked (default), the host will be created. If unchecked, the host will not be created, unless this setting is overridden in the [discovery rule](/manual/discovery/low_level_discovery#override). This functionality provides additional flexibility when creating discovery rules. Discovered hosts are prefixed with the name of the discovery rule that created them, in the host list. Discovered hosts can be manually deleted. Discovered hosts will also be automatically deleted, based on the *Keep lost resources period (in days)* value of the discovery rule. Most of the configuration options are read-only, except for enabling/disabling the host and host inventory. Discovered hosts cannot have host prototypes of their own. #### Prototypes d'hôte Des prototypes d'hôte peuvent être créés avec la règle de découverte de bas niveau. Lorsque des machines virtuelles sont découvertes, ces prototypes deviennent de véritables hôtes. Les prototypes, avant d'être découverts, ne peuvent pas avoir leurs propres éléments et déclencheurs, autres que ceux des modèles liés. Les hôtes découverts appartiendront à un hôte existant.  Pour que les hôtes créés à partir d'un prototype aient des noms d'hôtes uniques, le champ *Nom d'hôte* doit contenir au moins une [macro de découverte de bas niveau](/manual/config/macros/lld_macros). Depuis Zabbix 5.2, les hôtes découverts peuvent être configurés avec des interfaces personnalisées ou hériter de l'adresse IP d'un hôte auquel appartient la règle de découverte (par défaut). Pour ajouter une ou plusieurs interfaces personnalisées, basculez le sélecteur *Interface* du mode *Hériter* au mode *Personnaliser*, puis appuyez sur  et sélectionnez le type d'interface requis dans le menu déroulant qui s'affiche. Tous les types d'interfaces pris en charge peuvent être définis pour un prototype d'hôte : agent Zabbix, SNMP, JMX, IPMI. Les champs d'interface prennent en charge les macros de découverte de bas niveau et les [macros utilisateur](/manual/config/macros/user_macros). Si plusieurs interfaces personnalisées sont spécifiées, utilisez la colonne *Par défaut* pour spécifier l'interface principale. Remarques : - Si *Personnaliser* est sélectionné, mais qu'aucune interface n'a été spécifiée, les hôtes seront créés sans interfaces. - Si *Hériter* est sélectionné pour un prototype d'hôte qui appartient à un modèle, les hôtes découverts hériteront de l'interface d'un hôte auquel le modèle est lié. ::: notewarning Un hôte ne sera pas créé si l'interface hôte contient des données incorrectes :::  Les macros LLD peuvent également être utilisées pour le nom visible, les champs de prototype de groupe d'hôtes, les valeurs de tag ou les valeurs des macros d'utilisateur de prototype d'hôte. Les autres options pouvant être spécifiées pour un prototype hôte sont : - Lien avec les groupes d'hôtes existants - Liaison de modèles - Chiffrement Si *Créer activé* est coché, l'hôte sera ajouté dans un état activé. Si elle n'est pas cochée, l'hôte sera ajouté, mais dans un état désactivé. Si *Découvrir* est coché (par défaut), l'hôte sera créé. Si cette case n'est pas cochée, l'hôte ne sera pas créé, sauf si ce paramètre est remplacé dans la [règle de découverte](/manual/discovery/low_level_discovery#override). Cette fonctionnalité offre une flexibilité supplémentaire lors de la création de règles de découverte. Les hôtes découverts sont précédés du nom de la règle de découverte qui les a créés, dans la liste des hôtes. Les hôtes découverts peuvent être supprimés manuellement. Les hôtes découverts seront également automatiquement supprimés, en fonction de la valeur *Période de conservation des ressources perdues (en jours)* de la règle de découverte. La plupart des options de configuration sont en lecture seule, à l'exception de l'activation/désactivation de l'hôte et de l'inventaire de l'hôte. Les hôtes découverts ne peuvent pas avoir leurs propres prototypes d'hôte. ### Host prototype tag The host prototype tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Host prototype tag name.| |value|string|Host prototype tag value.| ### Tag de prototype d'hôte L'objet de tag de prototype d'hôte possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nom de tag du prototype d'hôte.| |value|string|Valeur de tag du prototype d'hôte.| ### Host prototype The host prototype object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostid|string|*(readonly)* ID of the host prototype.| |**host**<br>(required)|string|Technical name of the host prototype.| |name|string|Visible name of the host prototype.<br><br>Default: `host` property value.| |status|integer|Status of the host prototype.<br><br>Possible values are:<br>0 - *(default)* monitored host;<br>1 - unmonitored host.| |inventory\_mode|integer|Host inventory population mode.<br><br>Possible values are:<br>-1 - *(default)* disabled;<br>0 - manual;<br>1 - automatic.| |templateid|string|*(readonly)* ID of the parent template host prototype.| |discover|integer|Host prototype discovery status.<br><br>Possible values:<br>0 - *(default)* new hosts will be discovered;<br>1 - new hosts will not be discovered and existing hosts will be marked as lost.| |custom\_interfaces|integer|Source of interfaces for hosts created by the host prototype.<br><br>Possible values:<br>0 - *(default)* inherit interfaces from parent host;<br>1 - use host prototypes custom interfaces.| |uuid|string|Universal unique identifier, used for linking imported host prototypes to already existing ones. Used only for host prototypes on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Prototype d'hôte L'objet prototype d'hôte a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostid|string|*(lecture seule)* ID du prototype d'hôte.| |**host**<br>(obligatoire)|string|Nom technique du prototype d'hôte.| |name|string|Nom visible du prototype d'hôte.<br><br>Par défaut : valeur de la propriété `host`.| |status|integer|Statut du prototype d'hôte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* hôte surveillé ;<br>1 - hôte non surveillé.| |inventory\_mode|integer|Mode de remplissage de l'inventaire de l'hôte.<br><br>Les valeurs possibles sont :<br>-1 - *(par défaut)* désactivé ;<br>0 - manuel ;<br>1 - automatique.| |templateid|string|*(lecture seul)* ID du modèle parent du prototype d'hôte.| |discover|integer|Statut de découverte du prototype d'hôte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* de nouveaux hôtes seront découverts ;<br>1 - de nouveaux hôtes ne seront pas découverts et les hôtes existants seront marqués comme perdus.| |custom\_interfaces|integer|Source des interfaces pour les hôtes créés par le prototype d'hôte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* hérite des interfaces de l'hôte parent ;<br>1 - utilise les interfaces personnalisées des prototypes d'hôte.| |uuid|string|Identifiant unique universel, utilisé pour lier les prototypes d'hôtes importés à ceux déjà existants. Utilisé uniquement pour les prototypes hôtes sur les modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # hostprototype.update # hostprototype.update ##### Host removal Hosts discovered by a network discovery rule are removed automatically from *Monitoring* → *Discovery* if a discovered entity is not in the rule's IP range any more. Hosts are removed immediately. ##### Suppression d'un hôte Les hôtes découverts par une règle de découverte du réseau sont automatiquement supprimés de *Surveillance* → *Découverte* si une entité découverte ne se trouve plus dans la plage IP de la règle. Les hôtes sont supprimés immédiatement. #### Hosts and host groups Manage host groups, hosts and everything related to them, including host interfaces, host macros and maintenance periods. [Host API](/manual/api/reference/host) | [Host group API](/manual/api/reference/hostgroup) | [Host interface API](/manual/api/reference/hostinterface) | [User macro API](/manual/api/reference/usermacro) | [Value map API](/manual/api/reference/valuemap) | [Maintenance API](/manual/api/reference/maintenance) #### Hôtes et groupes d'hôtes Gérez les groupes d'hôtes, les hôtes et tout ce qui s'y rapporte, y compris les interfaces des hôtes, les macros hôtes et les périodes de maintenance. [API Hôte](/manual/api/reference/host) | [API Groupe d'hôte](/manual/api/reference/hostgroup) | [API Interface d'hôte](/manual/api/reference/hostinterface) | [API Macro utilisateur API](/manual/api/reference/usermacro) | [API Table de correspondance(/manual/api/reference/valuemap) | [API Maintenance](/manual/api/reference/maintenance) #### Hosts/host prototypes In a [host](/manual/config/hosts/host) and [host prototype](/manual/vm_monitoring#host_prototypes) configuration, user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Interface IP/DNS|<|DNS only| |Interface port|<|no| |*SNMP v1, v2*|<|<| | |SNMP community|yes| |*SNMP v3*|<|<| | |Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |*IPMI*|<|<| | |Username|yes| |^|Password|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes| #### Hôtes/prototypes d'hôtes Dans une configuration d'[hôte](/manual/config/hosts/host) et de [prototype d'hôte](/manual/vm_monitoring#host_prototypes), les macros utilisateur peuvent être utilisées dans les champs suivants : |Emplacement|<|Plusieurs macros/mix avec du texte^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Interface IP/DNS|<|DNS seulement| |Port d'Interface|<|non| |*SNMP v1, v2*|<|<| | |Communauté SNMP|oui| |*SNMP v3*|<|<| | |Nom du contexte|oui| |^|Nom de sécurité|oui| |^|Phrase secrète d'authentification|oui| |^|Phrase secrète de confidentialité|oui| |*IPMI*|<|<| | |Nom d'utilisateur|oui| |^|Mot de passe|oui| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Noms de Tag|oui| |^|Valeurs de Tag|oui| ##### Host tags |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |-------|----------------|--------|----|--------------------------|-----------| |groups|<|x|<|<|Root element for host groups.| |<|name|x|`string`|<|Host group name.| |hosts|<|\-|<|<|Root element for hosts.| |<|host|x|`string`|<|Unique host name.| |<|name|\-|`string`|<|Visible host name.| |<|description|\-|`text`|<|Host description.| |<|status|\-|`string`|0 - ENABLED (default)<br>1 - DISABLED|Host status.| |<|ipmi\_authtype|\-|`string`|-1 - DEFAULT (default)<br>0 - NONE<br>1 - MD2<br>2 - MD5<br>4 - STRAIGHT<br>5 - OEM<br>6 - RMCP\_PLUS|IPMI session authentication type.| |<|ipmi\_privilege|\-|`string`|1 - CALLBACK<br>2 - USER (default)<br>3 - OPERATOR<br>4 - ADMIN<br>5 - OEM|IPMI session privilege level.| |<|ipmi\_username|\-|`string`|<|Username for IPMI checks.| |<|ipmi\_password|\-|`string`|<|Password for IPMI checks.| |proxy|<|\-|<|<|Proxy.| |<|name|x|`string`|<|Name of the proxy (if any) that monitors the host.| |templates|<|\-|<|<|Root element for linked templates.| |<|name|x|`string`|<|Template name.| |interfaces|<|\-|<|<|Root element for host interfaces.| |<|default|\-|`string`|0 - NO<br>1 - YES (default)|Whether this is the primary host interface.<br>There can be only one primary interface of one type on a host.| |<|type|\-|`string`|1 - ZABBIX (default)<br>2 - SNMP<br>3 - IPMI<br>4 - JMX|Interface type.| |<|useip|\-|`string`|0 - NO<br>1 - YES (default)|Whether to use IP as the interface for connecting to the host (if not, DNS will be used).| |<|ip|\-|`string`|<|IP address, can be either IPv4 or IPv6.<br><br>Required if the connection is made via IP.| |<|dns|\-|`string`|<|DNS name.<br><br>Required if the connection is made via DNS.| |<|port|\-|`string`|<|Port number. Supports user macros.| |<|interface\_ref|x|`string`|Format: `if<N>`|Interface reference name to be used in items.| |details|<|\-|<|<|Root element for interface details.| |<|version|\-|`string`|1 - SNMPV1<br>2 - SNMP\_V2C (default)<br>3 - SNMP\_V3|Use this SNMP version.| |<|community|\-|`string`|<|SNMP community.<br><br>Required by SNMPv1 and SNMPv2 items.| |<|contextname|\-|`string`|<|SNMPv3 context name.<br><br>Used only by SNMPv3 items.| |<|securityname|\-|`string`|<|SNMPv3 security name.<br><br>Used only by SNMPv3 items.| |<|securitylevel|\-|`string`|0 - NOAUTHNOPRIV (default)<br>1 - AUTHNOPRIV<br>2 - AUTHPRIV|SNMPv3 security level.<br><br>Used only by SNMPv3 items.| |<|authprotocol|\-|`string`|0 - MD5 (default)<br>1 - SHA1<br>2 - SHA224<br>3 - SHA256<br>4 - SHA384<br>5 - SHA512|SNMPv3 authentication protocol.<br><br>Used only by SNMPv3 items.| |<|authpassphrase|\-|`string`|<|SNMPv3 authentication passphrase.<br><br>Used only by SNMPv3 items.| |<|privprotocol|\-|`string`|0 - DES (default)<br>1 - AES128<br>2 - AES192<br>3 - AES256<br>4 - AES192C<br>5 - AES256C|SNMPv3 privacy protocol.<br><br>Used only by SNMPv3 items.| |<|privpassphrase|\-|`string`|<|SNMPv3 privacy passphrase.<br><br>Used only by SNMPv3 items.| |<|bulk|\-|`string`|0 - NO<br>1 - YES (default)|Use bulk requests for SNMP.| |items|<|\-|<|<|Root element for items.| |<|*For item element tag values, see host [item](/manual/xml_export_import/hosts#host_item_tags) tags.*|<|<|<|<| |tags|<|\-|<|<|Root element for host tags.| |<|tag|x|`string`|<|Tag name.| |<|value|\-|`string`|<|Tag value.| |macros|<|\-|<|<|Root element for macros.| |<|macro|x|<|<|User macro name.| |<|type|\-|`string`|0 - TEXT (default)<br>1 - SECRET\_TEXT<br>2 - VAULT|Type of the macro.| |<|value|\-|`string`|<|User macro value.| |<|description|\-|`string`|<|User macro description.| |inventory|<|\-|<|<|Root element for host inventory.| |<|<inventory\_property>|\-|<|<|Individual inventory property.<br><br>All available inventory properties are listed under the respective tags, e.g. <type>, <name>, <os> (see example above).| |inventory\_mode|<|\-|`string`|-1 - DISABLED<br>0 - MANUAL (default)<br>1 - AUTOMATIC|Inventory mode.| |valuemaps|<|\-|<|<|Root element for host value maps.| |<|name|x|`string`|<|Value map name.| |<|mapping|\-|<|<|Root element for mappings.| |<|value|x|`string`|<|Value of a mapping.| |<|newvalue|x|`string`|<|New value of a mapping.| ##### Tags d'hôte |Element|Propriété d'élément|Requis|Type|Intervalle^**[1](#note de bas de page)**^|Description| |-------|----------------|--------|----|--------------------------|-----------| |groups|<|x|<|<|Élément racine pour les groupes d'hôtes.| |<|name|x|`string`|<|Nom du groupe d'hôtes.| |hosts|<|\-|<|<|Élément racine pour les hôtes.| |<|host|x|`string`|<|Nom unique de l'hôte. |<|name|\-|`string`|<|Nom visible de l'hôte.| |<|description|\-|`text`|<|Description de l'hôte.| |<|status|\-|`string`|0 - ACTIVE (par défaut)<br>1 - DESACTIVE|Statut de l'hôte.| |<|ipmi\_authtype|\-|`string`|-1 - DEFAULT (par défaut)<br>0 - AUCUN<br>1 - MD2<br>2 - MD5<br>4 - DROIT<br>5 - OEM<br>6 - RMCP\_PLUS|Type d'authentification de session IPMI.| |<|ipmi\_privilege|\-|`string`|1 - RAPPEL<br>2 - UTILISATEUR (par défaut)<br>3 - OPERATEUR<br>4 - ADMIN<br>5 - OEM|Niveau de privilège de session IPMI.| |<|ipmi\_username|\-|`string`|<|Nom d'utilisateur pour les vérifications IPMI.| |<|ipmi\_password|\-|`string`|<|Mot de passe pour les vérifications IPMI.| |proxy|<|\-|<|<|Proxy.| |<|name|x|`string`|<|Nom du proxy (le cas échéant) qui supervise l'hôte.| |templates|<|\-|<|<|Élément racine pour les modèles liés.| |<|name|x|`string`|<|Nom du modèle.| |interfaces|<|\-|<|<|Élément racine pour les interfaces d'hôtes. |<|default|\-|`string`|0 - NON<br>1 - OUI (par défaut)|S'il s'agit de l'interface hôte principale.<br>Il ne peut y avoir qu'une seule interface principale d'un type sur un hôte .| |<|type|\-|`string`|1 - ZABBIX (par défaut)<br>2 - SNMP<br>3 - IPMI<br>4 - JMX|type d'interface.| |<|useip|\-|`string`|0 - NON<br>1 - oui (par défaut)|Utilise IP comme interface pour se connecter à l'hôte (sinon, DNS sera utilisé).| |<|ip|\-|`string`|<|Adresse IP, peut être IPv4 ou IPv6.<br><br>Requis si la connexion se fait via l'adresse IP.| |<|dns|\-|`string`|<|Nom DNS.<br><br>Requis si la connexion se fait via DNS.| |<|port|\-|`string`|<|Numéro de port. Supporte les macros utilisateurs.| |<|interface\_ref|x|`string`|Format : `si<N>`|Nom de référence de l'interface à utiliser dans les éléments.| |details|<|\-|<|<|Élément racine pour les détails de l'interface.| |<|version|\-|`string`|1 - SNMPV1<br>2 - SNMP\_V2C (par défaut)<br>3 - SNMP\_V3|Utilise cette version de SNMP.| |<|community|\-|`string`|<|Communauté SNMP.<br><br>Requis par les éléments SNMPv1 et SNMPv2.| |<|contextname|\-|`string`|<|Nom du contexte SNMPv3.<br><br>Utilié uniquement pour les éléments SNMPv3.| |<|securityname|\-|`string`|<|Nom de la sécurité SNMPv3.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|securitylevel|\-|`string`|0 - NOAUTHNOPRIV (par défaut)<br>1 - AUTHNOPRIV<br>2 - AUTHPRIV|Niveau de sécurité SNMPv3.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|authprotocol|\-|`string`|0 - MD5 (par défaut)<br>1 - SHA1<br>2 - SHA224<br>3 - SHA256<br>4 - SHA384<br>5 - SHA512|Protocole d'authentification SNMPv3.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|authpassphrase|\-|`string`|<|Passphrase d'authentification SNMPv3.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|privprotocol|\-|`string`|0 - DES (default)<br>1 - AES128<br>2 - AES192<br>3 - AES256<br>4 - AES192C<br>5 - AES256C|SNMPv3 privacy protocol.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|privpassphrase|\-|`string`|<|SNMPv3 privacy passphrase.<br><br>Utilisé uniquement pour les éléments SNMPv3.| |<|bulk|\-|`string`|0 - NO<br>1 - YES (par défaut)|Utilise les requêtes groupées pour SNMP.| |items|<|\-|<|<|Elément racine pour les éléments.| |<|*Pour les valeurs des tags d'élément, consultez les [tags d'élément d'hôte](/manual/xml_export_import/hosts#host_item_tags).*|<|<|<|<| |tags|<|\-|<|<|Elément racine pour les tags d'hôtes.| |<|tag|x|`string`|<|Nom de tag.| |<|value|\-|`string`|<|Valeur du tag.| |macros|<|\-|<|<|Elément racine pour les macros.| |<|macro|x|<|<|Nom de la macro utilisateur.| |<|type|\-|`string`|0 - TEXT (par défaut)<br>1 - SECRET\_TEXT<br>2 - VAULT|Type de macro.| |<|value|\-|`string`|<|Valeur de la macro utilisateur.| |<|description|\-|`string`|<|Description de la macro utilisateur.| |inventory|<|\-|<|<|Elément racine pour l'inventaire d'hôte.| |<|<inventory\_property>|\-|<|<|Propriété d'inventaire individuelle.<br><br>Toutes les propriétés d'inventaire disponibles sont répertoriées sous les tags respectifs, par ex. <type>, <nom>, <os> (voir exemple ci-dessus).| |inventory\_mode|<|\-|`string`|-1 - DESACTIVE<br>0 - MANUEL (par défaut)<br>1 - AUTOMATIQUE|Mode d'inventaire.| |valuemaps|<|\-|<|<|Elément racine pour la correspondance de valeur de l'hôte.| |<|name|x|`string`|<|Nom de la correspondance de valeur.| |<|mapping|\-|<|<|Elément racine pour la correspondance.| |<|value|x|`string`|<|Valeur de la correspondance.| |<|newvalue|x|`string`|<|Nouvelle valeur de la correspondance.| ### Host tag The host tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Host tag name.| |value|string|Host tag value.| ### Tag d'hôte L'objet tag d'hôte a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nom du tag d'hôte.| |value|string|Valeur du tag d'hôte.| # host.update # host.update # housekeeping.get # housekeeping.get ### Housekeeping The settings object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hk\_events\_mode|integer|Enable internal housekeeping for events and alerts.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_events\_trigger|string|Trigger data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 365d.| |hk\_events\_service|string|Service data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 1d.| |hk\_events\_internal|string|Internal data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 1d.| |hk\_events\_discovery|string|Network discovery data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 1d.| |hk\_events\_autoreg|string|Autoregistration data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 1d.| |hk\_services\_mode|integer|Enable internal housekeeping for services.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_services|string|Services data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 365d.| |hk\_audit\_mode|integer|Enable internal housekeeping for audit.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_audit|string|Audit data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 365d.| |hk\_sessions\_mode|integer|Enable internal housekeeping for sessions.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_sessions|string|Sessions data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 365d.| |hk\_history\_mode|integer|Enable internal housekeeping for history.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_history\_global|integer|Override item history period.<br><br>Possible values:<br>0 - Do not override;<br>1 - *(default)* Override.| |hk\_history|string|History data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 90d.| |hk\_trends\_mode|integer|Enable internal housekeeping for trends.<br><br>Possible values:<br>0 - Disable;<br>1 - *(default)* Enable.| |hk\_trends\_global|integer|Override item trend period.<br><br>Possible values:<br>0 - Do not override;<br>1 - *(default)* Override.| |hk\_trends|string|Trends data storage period. Accepts seconds and time unit with suffix.<br><br>Default: 365d.| |db\_extension|string|*(readonly)* Configuration flag DB extension. If this flag is set to "timescaledb" then the server changes its behavior for housekeeping and item deletion.| |compression\_status|integer|Enable TimescaleDB compression for history and trends.<br><br>Possible values:<br>0 - *(default)* Off;<br>1 - On.| |compress\_older|string|Compress history and trends records older than specified period. Accepts seconds and time unit with suffix.<br><br>Default: 7d.| |compression\_availability|integer|*(readonly)* Compression availability.<br><br>Possible values:<br>0 - Unavailable;<br>1 - Available.| ### Nettoyage L'objet de paramètres a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hk\_events\_mode|integer|Activer la maintenance interne pour les événements et les alertes.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_events\_trigger|string|Période de déclenchement du stockage des données. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 365d.| |hk\_events\_service|string|Période de stockage des données de service. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 1d.| |hk\_events\_internal|string|Période de stockage des données internes. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 1d.| |hk\_events\_discovery|string|Période de stockage des données de découverte du réseau. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 1d.| |hk\_events\_autoreg|string|Période de stockage des données d'enregistrement automatique. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 1d.| |hk\_services\_mode|integer|Activer le nettoyage interne pour les services.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_services|string|Période de stockage des données des services. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 365d.| |hk\_audit\_mode|integer|Activer la maintenance interne pour l'audit.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_audit|string|Période de stockage des données d'audit. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 365d.| |hk\_sessions\_mode|integer|Activer le nettoyage interne pour les sessions.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_sessions|string|Période de stockage des données de session. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 365d.| |hk\_history\_mode|integer|Activer la maintenance interne pour l'historique.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_history\_global|integer|Remplacer la période d'historique des éléments.<br><br>Valeurs possibles :<br>0 - Ne pas remplacer ;<br>1 - *(par défaut)* Remplacer.| |hk\_history|string|Période de stockage des données de l'historique. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 90d.| |hk\_trends\_mode|integer|Activer le nettoyage interne pour les tendances.<br><br>Valeurs possibles :<br>0 - Désactiver ;<br>1 - *(par défaut)* Activer.| |hk\_trends\_global|integer|Remplacer la période de tendance de l'élément.<br><br>Valeurs possibles :<br>0 - Ne pas remplacer ;<br>1 - *(par défaut)* Remplacer.| |hk\_trends|string|Période de stockage des données de tendance. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 365d.| |db\_extension|string|*(lecture seule)* Flag de configuration de l'extension de base de données. Si cet indicateur est défini sur "timescaledb", le serveur modifie son comportement pour le nettoyage et la suppression d'éléments.| |compression\_status|integer|Activer la compression TimescaleDB pour l'historique et les tendances.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Désactiver ;<br>1 - Activer.| |compress\_older|string|Compresser les enregistrements d'historique et de tendances antérieurs à la période spécifiée. Accepte les secondes et l'unité de temps avec suffixe.<br><br>Par défaut : 7d.| |compression\_availability|integer|*(lecture seule)* Disponibilité de la compression.<br><br>Valeurs possibles :<br>0 - Indisponible ;<br>1 - Disponible.| # housekeeping.update # housekeeping.update #### How it works In log monitoring you may encounter lines similar to these: Line1: Application 1 stopped Line2: Application 2 stopped Line3: Application 1 was restarted Line4: Application 2 was restarted The idea of event correlation is to be able to match the problem event from Line1 to the resolution from Line3 and the problem event from Line2 to the resolution from Line4, and close these problems one by one: Line1: Application 1 stopped Line3: Application 1 was restarted #problem from Line 1 closed Line2: Application 2 stopped Line4: Application 2 was restarted #problem from Line 2 closed To do this you need to tag these related events as, for example, "Application 1" and "Application 2". That can be done by applying a regular expression to the log line to extract the tag value. Then, when events are created, they are tagged "Application 1" and "Application 2" respectively and problem can be matched to the resolution. #### Comment cela fonctionne Dans la surveillance des journaux, vous pouvez rencontrer des lignes similaires à celles-ci : Ligne1: Application 1 stopped Ligne2: Application 2 stopped Ligne3: Application 1 was restarted Ligne4: Application 2 was restarted L'idée de la corrélation d'événements est de pouvoir faire correspondre l'événement problème de Ligne1 à la résolution de Ligne3 et l'événement problème de Ligne2 à la résolution de Ligne4, et fermer ces problèmes un par un : Ligne1: Application 1 stopped Ligne3: Application 1 was restarted #problem from Line 1 closed Ligne2: Application 2 stopped Ligne4: Application 2 was restarted #problem from Line 2 closed Pour ce faire, vous devez tagger ces événements associés comme, par exemple, "Application 1" et "Application 2". Cela peut être fait en appliquant une expression régulière à la ligne de journal pour extraire la valeur de tag. Ensuite, lorsque des événements sont créés, ils sont taggés respectivement "Application 1" et "Application 2" et le problème peut être associé à la résolution. #### HP OpenView Zabbix can be configured to send messages to OpenView server. The following steps must be performed: #### HP OpenView Zabbix peut être configuré pour envoyer des messages au serveur OpenView. Les étapes suivantes doivent être effectuées : ### HTTP field The HTTP field object defines a name and value that is used to specify variable, HTTP header, POST form field data of query field data. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Name of header / variable / POST or GET field.| |**value**<br>(required)|string|Value of header / variable / POST or GET field.| ### Champ HTTP L'objet de champ HTTP définit un nom et une valeur utilisés pour spécifier une variable, un en-tête HTTP, des données de champ de formulaire POST ou des données de champ de requête. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(obligatoire)|string|Nom de l'en-tête / variable / champ POST ou GET.| |**value**<br>(obligatoire)|string|Valeur de l'en-tête / variable / champ POST ou GET..| #### HTTPS checks Web scenarios and HTTP agent items using the https protocol, Zabbix agent checks `net.tcp.service[https...]` and `net.tcp.service.perf[https...]` may fail if the target server is configured to disallow TLS v1.0 protocol or below. Please see [ZBX-9879](https://support.zabbix.com/browse/ZBX-9879) for more information and available workarounds. #### Vérifications HTTPS Scénarios Web et éléments HTTP agent utilisant le protocole https, les vérifications de l'agent Zabbix `net.tcp.service[https...]` et `net.tcp.service.perf[https...]` peuvent échouer si le serveur cible est configuré pour interdire le protocole TLS v1.0 ou inférieur. Veuillez consulter [ZBX-9879](https://support.zabbix.com/browse/ZBX-9879) pour plus d'informations et les solutions de contournement disponibles. # HTTP template operation Steps to ensure correct operation of templates that collect metrics with [HTTP agent](/manual/config/items/itemtypes/http): 1\. Create a host in Zabbix and specify an IP address or DNS name of the monitoring target as the main interface. This is needed for the {HOST.CONN} macro to resolve properly in the template items.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to the host created in step 1 (if the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\ 3. Adjust the values of mandatory macros as needed.\ 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column. ::: notetip This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name). ::: |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[Apache by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/apache_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$APACHE.STATUS.HOST}** - the hostname or IP address of Apache status page (default: 127.0.0.1).<br>**{$APACHE.STATUS.PATH}** - the URL path (default: server-status?auto).<br>**{$APACHE.STATUS.PORT}** - the port of Apache status page (default: 80).<br>**{$APACHE.STATUS.SCHEME}** - the request scheme. Supported: http (default), https.|Apache module mod\_status should be set (see Apache [documentation](https://httpd.apache.org/docs/current/mod/mod_status.html) for details).<br>To check availability, run:<br>`httpd -M 2>/dev/null \| grep status_module`<br><br>Apache configuration example:<br>`<Location "/server-status">`<br>`SetHandler server-status`<br>`Require host example.com`<br>`</Location>`| |[Asterisk by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/tel/asterisk_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$AMI.PORT}** - AMI port number for checking service availability (default: 8088).<br>**{$AMI.SECRET}** - the Asterisk Manager secret (default: zabbix).<br>**{$AMI.URL}** - the Asterisk Manager API URL in the format<br>`<scheme>://<host>:<port>/<prefix>/rawman`<br>(default: http://asterisk:8088/asterisk/rawman).<br>**{$AMI.USERNAME}** - the Asterisk Manager name.|1\. Enable the [mini-HTTP Server](https://wiki.asterisk.org/wiki/display/AST/Asterisk+Builtin+mini-HTTP+Server).<br><br>2. Add the option `webenabled=yes` to the general section of *manager.conf* file.<br><br>3. Create *Asterisk Manager* user in the Asterisk instance.| |[ClickHouse by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/clickhouse_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$CLICKHOUSE.PORT}** - the port of ClickHouse HTTP endpoint (default: 8123).<br>**{$CLICKHOUSE.SCHEME}** - the request scheme. Supported: http (default), https.<br>**{$CLICKHOUSE.USER}**, **{$CLICKHOUSE.PASSWORD}** - ClickHouse login credentials (default username: zabbix, password: zabbix\_pass).<br>If you don't need authentication, remove headers from HTTP agent type items.|Create a ClickHouse user with a 'web' profile and permission to view databases (see ClickHouse [documentation](https://clickhouse.tech/docs/en/operations/settings/settings-users/) for details).<br><br>See template's *Readme.md* file for a ready-to-use zabbix.xml file configuration.| |[Cloudflare by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/cloudflare_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$CLOUDFLARE.API.TOKEN}** - Cloudflare API token value (default: \`<change>\`).<br>**{$CLOUDFLARE.ZONE\_ID}** - Cloudflare Site Zone ID (default: \`<change>\`).|Cloudflare API Tokens are available in the Cloudflare account under *My Profile→ API Tokens*.<br>Zone ID is available in the Cloudflare account under *Account Home → Site*.| |[CockroachDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cockroachdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$COCKROACHDB.API.PORT}** - the port of CockroachDB API and Prometheus endpoint. (default: 8080).<br>**{$COCKROACHDB.API.SCHEME}** - the request scheme. Supported: http (default), https.|Internal node metrics are collected from Prometheus `/_status/vars` endpoint. <br> Node health metrics are collected from `/health` and `/health?ready=1` endpoints. <br><br>The template doesn't require usage of session token. <br><br> Depending on your CockroachDB version and configuration, some metrics may not be collected.| |[DELL PowerEdge R720 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r720_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R740 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r740_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R820 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r820_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R840 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r840_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$API.URL}** - Dell iDRAC Redfish API URL in the format `<scheme>://<host>:<port>` (default: <Put your URL here>)<br>**{$API.USER}**, **{$API.PASSWORD}** - Dell iDRAC login credentials (default: not set).|In the Dell iDRAC interface of your server:<br>1. Enable Redfish API .<br>2. Create a user for monitoring with read-only permissions.| |[Elasticsearch Cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/elasticsearch_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$ELASTICSEARCH.PORT}** - the port of the Elasticsearch host (default: 9200).<br>**{$ELASTICSEARCH.SCHEME}** - the request scheme. Supported: http (default), https.<br>**{$ELASTICSEARCH.USERNAME}**, **{$ELASTICSEARCH.PASSWORD}** - login credentials, required only if used for Elasticsearch authentication.| | |[Envoy Proxy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/envoy_proxy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$ENVOY.METRICS.PATH}** - the path from where to retrieve metrics in the Prometheus format (default: `/stats/prometheus`).<br>**{$ENVOY.URL}** - Envoy Proxy instance URL (default: http://localhost:9901)| Depending on your Envoy Proxy instance version and configuration, some metrics may not be collected. | |[Etcd by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/etcd_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$ETCD.PORT}**- the port used by Etcd API endpoint (default: 2379).<br>**{$ETCD.SCHEME}** - the request scheme. Supported: http (default), https.<br>**{$ETCD.USER}**, **{$ETCD.PASSWORD}** - login credentials, required only if used for Etcd authentication.|Metrics are collected from /metrics endpoint; to specify the endpoint's location use `--listen-metrics-urls` flag (see Etcd [documentation](https://github.com/etcd-io/website/blob/master/content/docs/v3.4.0/op-guide/configuration.md#--listen-metrics-urls) for details).<br><br>To verify, whether Etcd is configured to allow metric collection, run:<br>`curl -L http://localhost:2379/metrics`<br><br>To check, if Etcd is accessible from Zabbix proxy or Zabbix server run:<br>`curl -L http:%%//<etcd_node_adress>:2379/metrics%%`<br><br>The template should be added to each node with Etcd.| |[GitLab by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/gitlab_http)|**{$GITLAB.PORT}** - the port of GitLab web endpoint (default: 80)<br>**{$GITLAB.URL}** - GitLab instance URL (default: localhost)|This template works with self-hosted GitLab instances; metrics are collected from the `/metrics` endpoint.<br><br>To access the metrics, the client IP address must be explicitly allowed (see [GitLab documentation](https://docs.gitlab.com/ee/administration/monitoring/ip_whitelist.html) for details).<br><br>Note, that certain metrics may not be available for a particular GitLab instance version and configuration.| |[Hadoop by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/hadoop_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HADOOP.NAMENODE.HOST}** - the Hadoop NameNode host IP address or FQDN (default: NameNode).<br>**{$HADOOP.NAMENODE.PORT}** - the Hadoop NameNode web-UI port (default: 9870).<br>**{$HADOOP.RESOURCEMANAGER.HOST}** - the Hadoop ResourceManager host IP address or FQDN (default: ResourceManager).<br>**{$HADOOP.RESOURCEMANAGER.PORT}** - the Hadoop ResourceManager web-UI port (default: 8088).|Metrics are collected by polling the Hadoop API remotely using an HTTP agent and JSONPath preprocessing. Zabbix server (or proxy) executes direct requests to ResourceManager, NodeManagers, NameNode, DataNodes APIs.| |[HAProxy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/haproxy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HAPROXY.STATS.PATH}** - the path of HAProxy Stats page (default: stats).<br>**{$HAPROXY.STATS.PORT}** - the port of the HAProxy Stats host or container (default: 8404).<br>**{$HAPROXY.STATS.SCHEME}** - the request scheme. Supported: http (default), https.|HAProxy Stats page should be set up (see HAProxy [blog post](https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/) for details or template's Readme.md for configuration example).| |[HashiCorp Consul Cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/consul_http/consul_cluster_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$CONSUL.API.PORT}** - Consul API port, used in node LLD (default: 8500).<br>**{$CONSUL.API.SCHEME}** - Consul API scheme, used in node LLD (default: http).<br>**{$CONSUL.CLUSTER.URL}** - Consul cluster URL (default: http://localhost:8500).<br>**{$CONSUL.TOKEN}** - Consul authorization token (default: <PUT YOUR AUTH TOKEN>).| | |[HashiCorp Consul Node by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/consul_http/consul_node_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$CONSUL.NODE.API.URL}** - Consul instance URL (default: http://localhost:8500).<br>**{$CONSUL.TOKEN}** - Consul authorization token (default: <PUT YOUR AUTH TOKEN>).|Internal service metrics are collected from `/v1/agent/metrics` endpoint.<br><br> Prometheus format must be enabled for export metrics. See Consul [documentation](https://www.consul.io/docs/agent/options#telemetry-prometheus_retention_time) for details.| |[HashiCorp Vault by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/vault_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$VAULT.API.PORT}** - the port on which the Vault listens for API requests (default: 8200).<br>**{$VAULT.API.SCHEME}** - the API request scheme. Supported: http (default), https.<br>**{$VAULT.HOST}** - Vault host name (default: <PUT YOUR VAULT HOST>).<br>**{$VAULT.TOKEN}** - Vault authorization token (default: <PUT YOUR AUTH TOKEN>).|1\. Configure the Vault API (see [official documentation](https://www.vaultproject.io/docs/configuration) for details).<br>2. Create a Vault service token, then copy and paste it into {$VAULT.TOKEN} macro value in Zabbix.| |[Hikvision camera by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cctv/hikvision/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HIKVISION\_ISAPI\_PORT}** - ISAPI port on a device (default: 80).<br>**{$USER}**, **{$PASSWORD}** - camera login credentials (default username: admin, password: 1234).| | |[InfluxDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/influxdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$INFLUXDB.API.TOKEN}** - InfluxDB API authorization token (default: \`\`).<br>**{$INFLUXDB.URL}** - InfluxDB instance URL in the format `<scheme>://<host>:<port>` (default: http://localhost:8086).|This template collects internal service metrics from the InfluxDB /metrics endpoint of self-hosted InfluxDB instances.<br><br>See InfluxDB [documentation](https://docs.influxdata.com/influxdb/v2.0/security/tokens/) for details.| |[HPE MSA 2040 Storage by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_msa2040_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)/[HPE MSA 2060 Storage by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_msa2060_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HPE.MSA.API.PORT}** - connection port for API (default: 443) <br> **{$HPE.MSA.API.SCHEME}** - connection scheme for API. Supported: http, https (default)<br> **{$HPE.MSA.API.USERNAME}**, **{$HPE.MSA.API.PASSWORD}** - API credentials (default username: zabbix, password:\`\`). |Create a separate Storage user (for example, *zabbix*) with monitor role and specify username and password in template macros. | |[HPE Primera by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_primera_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HPE.PRIMERA.API.PORT}** - connection port for API (default: 443) <br> **{$HPE.PRIMERA.API.SCHEME}** - connection scheme for WSAPI. Supported: http, https (default)<br> **{$HPE.PRIMERA.API.USERNAME}**, **{$HPE.PIMERA.API.PASSWORD}** - WSAPI credentials (default username: zabbix, password:\`\`). |Create a separate Storage user (for example, *zabbix*) with browse role and enable it for all domains. <br><br> To start WSAPI server, log in to the CLI as a user whose role has the `wsapi_set` right, then run:<br> `startwsapi` <br><br> To check WSAPI state, run:<br> `showwsapi`| |[HPE Synergy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/hpe_synergy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$HPE.SYNERGY.API.PORT}** - connection port for API (default: 443) <br> **{$HPE.SYNERGY.API.SCHEME}** - connection scheme for API. Supported: http, https (default)<br> **{$HPE.SYNERGY.API.USERNAME}**, **{$HPE.SYNERGY.API.PASSWORD}** - API credentials (default username: zabbix, password:\`\`). | | |[InfluxDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/influxdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$INFLUXDB.API.TOKEN}** - InfluxDB API authorization token (default: \`\`).<br>**{$INFLUXDB.URL}** - InfluxDB instance URL in the format `<scheme>://<host>:<port>` (default: http://localhost:8086).|This template collects internal service metrics from the InfluxDB /metrics endpoint of self-hosted InfluxDB instances.<br><br>See InfluxDB [documentation](https://docs.influxdata.com/influxdb/v2.0/security/tokens/) for details.| |[Jenkins by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jenkins/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$JENKINS.API.KEY}** - API key to access Metrics Servlet; required for common metrics (default: \`\`).<br>**{$JENKINS.API.TOKEN}** - API token for HTTP BASIC authentication; required for monitoring computers and builds (default: \`\`).<br>**{$JENKINS.URL}** - Jenkins URL in the format `<scheme>://<host>:<port>`; required for monitoring computers and builds (default: \`\`).<br>**{$JENKINS.USER}** - username for HTTP BASIC authentication; required for monitoring computers and builds (default: zabbix).|Metrics are collected by requests to Metrics API.<br><br>For common metrics: install and configure Metrics plugin parameters according to the [official documentation](https://plugins.jenkins.io/metrics/). Issue an API key for access to the Metrics Servlet, then use it as {$JENKINS.API.KEY} macro value.<br><br>For monitoring computers and builds: create an API token for the Jenkins user that will be used for monitoring, then use it as {$JENKINS.API.TOKEN} macro value. See Jenkins [documentation](https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/) for details.| |[Kubernetes API server by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_api_server_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.API.SERVER.URL}** - instance URL (default: http://localhost:8086/metrics).<br>**{$KUBE.API.TOKEN}** - API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> Internal metrics are collected from the /metrics endpoint. <br><br> Use bearer API token for authorization. See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details. | |[Kubernetes Controller manager by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_controller_manager_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.CONTROLLER.SERVER.URL}** - instance URL (default: http://localhost:10252/metrics).<br>**{$KUBE.CONTROLLER.TOKEN}** - API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> Internal metrics are collected from the /metrics endpoint. <br><br> Use bearer API token for authorization. See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details. | |[Kubernetes kubelet by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_kubelet_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.KUBELET.URL}** - instance URL (default: https://localhost:10250).<br>**{$KUBE.API.TOKEN}** - API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> Internal metrics are collected from the /metrics endpoint. <br><br> Use bearer API token for authorization. See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details. | |[Kubernetes nodes by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_nodes_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.API.ENDPOINT}** - Kubernetes API endpoint in the format <scheme>://<host>:<port>/api (default: not set).<br>**{$KUBE.API.TOKEN}** - API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> To generate a service account token, run: <br> `kubectl get secret zabbix-service-account -n zabbix -o jsonpath={.data.token} | base64 -d` <br><br> See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details.<br><br> The template contains additional macros, which can be used to filter out certain metrics of discovered worker nodes. | |[Kubernetes Scheduler by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_scheduler_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.SCHEDULER.SERVER.URL}** - instance URL (default: http://localhost:10251/metrics).<br>**{$KUBE.SCHEDULER.TOKEN}** - Scheduler API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> Internal metrics are collected from the /metrics endpoint. <br><br> Use bearer API token for authorization. See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details. | |[Kubernetes cluster state by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_state_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{$KUBE.API.HOST}** - Kubernetes API host (default: not set).<br>**{$KUBE.API.PORT}**- Kubernetes API port (default:6443). <br> **{$KUBE.API.TOKEN}** - API authorization token (default: \`\`).| The template requires [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) to be installed in your Kubernetes cluster. <br><br> Internal service metrics are collected from the kube-state-metrics endpoint. <br><br> Use bearer API token for authorization. See Kubernetes [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) for details.<br><br> The template contains additional macros, which can be used to filter out certain metrics of discovered worker nodes. | |[Microsoft SharePoint by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/sharepoint_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$SHAREPOINT.URL}** - portal page URL, for example *http://sharepoint.companyname.local/* (default: \`\`).<br>**{$SHAREPOINT.ROOT}** - a root directory; only the specified directory and all its subfolders will be monitored (default: /Shared Documents)<br>**{$SHAREPOINT.USER}**, **{$SHAREPOINT.PASSWORD}** - SharePoint login credentials (default: not set).|The template contains additional macros, which can be used to filter out certain dictionaries and types during LLD process (see template's [Readme.md](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/sharepoint_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) for the description of available filter macros).| |[NetApp AFF A700 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/netapp_aff_a700_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$URL}** - AFF700 cluster URL address (default: ' ' )<br>**{$USERNAME}**, **{PASSWORD}** - AFF700 login credentials (default: not set).|Create a host for AFF A700 with cluster management IP as the Zabbix agent interface.| |[NGINX by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$NGINX.STUB\_STATUS.HOST}** - the hostname or IP address of NGINX stub\_status host or container (default: localhost).<br>**{$NGINX.STUB\_STATUS.PATH}** - the path of NGINX stub\_status page (default: basic\_status).<br>**{$NGINX.STUB\_STATUS.PORT}** - the port of NGINX stub\_status host or container (default: 80).<br>**{$NGINX.STUB\_STATUS.SCHEME}** - the request scheme. Supported: http (default), https.|`'ngx_http_stub_status_module` should be set up (see NGINX [documentation](https://nginx.org/en/docs/http/ngx_http_stub_status_module.html) for details or template's Readme.md for configuration example).<br>To check availability, run:<br>`nginx -V 2>&1 \| grep -o with-http_stub_status_module`| |[NGINX Plus by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_plus_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$NGINX.API.ENDPOINT}** - NGINX Plus API URL in the format `<scheme>://<host>:<port>/<location>/` (default: ' ').|1\. Enable NGINX Plus API (see NGINX [documentation](https://www.nginx.com/products/nginx/live-activity-monitoring/) for details).<br>2. Set the macro {$NGINX.API.ENDPOINT}<br>3. If required, use other template macros to filter out discovery operations and discover only required zones and upstreams.| |[OpenWeatherMap by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/openweathermap_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$OPENWEATHERMAP.API.ENDPOINT}** - OpenWeatherMap API endpoint (default: api.openweathermap.org/data/2.5/weather?).<br>**{$OPENWEATHERMAP.API.TOKEN}** - OpenWeatherMap API key (default:' ')<br>**{$LOCATION}** - locations for which to retrieve the metrics (default: Riga) |For instructions on getting the API key, see OpenWeatherMap [documentation](https://home.openweathermap.org/api_key). <br><br> **{$LOCATION}** macro supports the following formats: <br> *geo coordinates* - for example, `56.95,24.0833`<br> *location name* - for example, `Chicago`<br> *OpenWeatherMap location ID* - [download the ID list](http://bulk.openweathermap.org/sample/city.list.json.gz)<br>*zip/postal code with a country code* - for example, `94040,us`<br> To specify multiple locations, use the \| delimiter. <br> Example:<br>`43.81821,7.76115|Riga|2643743|94040,us` | |[PHP-FPM by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/php-fpm_agent/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$PHP\_FPM.HOST}** - a hostname or an IP of PHP-FPM status host or container (default: localhost).<br>**{$PHP\_FPM.PING.PAGE}** - PHP-FPM ping page path (default:ping).<br>**{$PHP\_FPM.PORT}** - the port of PHP-FPM status host or container (default: 80).<br>**{$PHP\_FPM.PROCESS\_NAME}** - PHP-FPM process name (default: php-fpm).<br>**{$PHP\_FPM.SCHEME}** - the request scheme. Supported: http (default), https.<br>**{$PHP\_FPM.STATUS.PAGE}** - PHP-FPM status page path (default:`status`).|1\. Open the php-fpm configuration file and enable the status page:<br>`pm.status_path = /status`<br>`ping.path = /ping`<br><br>2. Validate the syntax: `$ php-fpm7 -t`<br><br>3. Reload the php-fpm service.<br><br>4. In the Nginx Server Block (virtual host) configuration file, add (see template's *Readme.md* for an expanded example with comments):<br>`location ~ ^/(status\|ping)$ {`<br>`access_log off;`<br>`fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;`<br>`fastcgi_index index.php;`<br>`include fastcgi_params;`<br>`fastcgi_pass 127.0.0.1:9000;`<br>`}`<br><br>5. Check the syntax: `$ nginx -t`<br><br>6. Reload Nginx<br><br>7. Verify: `curl -L 127.0.0.1/status`| |[Proxmox VE by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/proxmox/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$PVE.TOKEN.ID}** - API token that allows stateless access to most parts of the REST API (default: not set). <br> **{$PVE.TOKEN.SECRET}** - secret key (default: not set). <br> **{$PVE.URL.PORT}** - the port the server listens to (default: 8006). |Create a separate user for monitoring, then generate an API token for this user. <br> Grant the following access levels to the token and user: <br>``Check: ["perm","/",["Sys.Audit"]]``<br>``Check: ["perm","/nodes/{node}",["Sys.Audit"]]``<br>``Check: ["perm","/vms/{vmid}",["VM.Audit"]]`` | |[RabbitMQ cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/rabbitmq_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$RABBITMQ.API.CLUSTER\_HOST}** - the hostname or IP address of RabbitMQ cluster API endpoint (default: 127.0.0.1).<br>**{$RABBITMQ.API.SCHEME}** - the request scheme. Supported: http (default), https.<br>**{$RABBITMQ.API.USER}**, **{$RABBITMQ.API.PASSWORD}** - RabbitMQ login credentials (default username: zbx\_monitor, password: zabbix).|Enable RabbitMQ management plugin (see [RabbitMQ documentation](https://www.rabbitmq.com/management.html)).<br><br>To create a RabbitMQ user with necessary permissions for monitoring, run:<br>'' rabbitmqctl add\_user zbx\_monitor <PASSWORD> ''<br>`rabbitmqctl set_permissions -p / zbx_monitor %% "" "" ".*"%%`<br>`rabbitmqctl set_user_tags zbx_monitor monitoring`<br><br>If the cluster consists of several nodes, it is recommended to assign the cluster template to a separate balancing host. In case of a single-node installation, the cluster template can be assigned to the host with a node template.| |[TiDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_tidb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$TIDB.PORT}** - The port of TiDB server metrics web endpoint (default: 10080)<br>**{$TIDB.URL}** - TiDB server URL (default: localhost).|This template works with TiDB server of PingCAP TiDB cluster.<br>Internal service metrics are collected from TiDB /metrics endpoint and TiDB monitoring API.| |[TiDB PD by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_pd_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$TIDB.PORT}** - The port of TiDB server metrics web endpoint (default: 2379)<br>**{$TIDB.URL}** - TiDB server URL (default: localhost).|This template works with PD server of PingCAP TiDB cluster.<br>Internal service metrics are collected from PD /metrics endpoint and TiDB monitoring API.| |[TiDB TiKV by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_tikv_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$TIDB.PORT}** - The port of TiDB server metrics web endpoint (default: 20180)<br>**{$TIDB.URL}** - TiDB server URL (default: localhost).|This template works with TiKV server of PingCAP TiDB cluster.<br>Internal service metrics are collected from TiKV /metrics endpoint.| |[Travis CI by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/travis_ci_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$TRAVIS.API.TOKEN}** - Travis API Token (default: not set)<br>**{$TRAVIS.API.URL}** - Travis API URL (default: api.travis-ci.com).|Travis API authentication token can be found in the *User → Settings → API authentication* section.<br>{$TRAVIS.API.URL} format for a private project is *api.travis-ci.com*.<br>{$TRAVIS.API.URL} format for an enterprise project is *api.example.com* (replace example.com with the domain Travis CI is running on).| |[VMWare SD-WAN VeloCloud by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/velocloud_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$VELOCLOUD.TOKEN}** - VMware SD-WAN Orchestrator API Token (default: \`\`).<br>**{$VELOCLOUD.URL}** - VMware SD-WAN Orchestrator URL, for example, *velocloud.net* (default: \`\`).|API token should be created in the VMware SD-WAN Orchestrator (see [VMware documentation](https://docs.vmware.com/en/VMware-SD-WAN/4.0/vmware-sd-wan-operator-guide/GUID-C150D536-A75F-47C1-8AFF-17C417F40C1D.html) for details).| |[ZooKeeper by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/zookeeper_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{$ZOOKEEPER.COMMAND\_URL}** - admin.commandURL; the URL for listing and issuing commands relative to the root URL (default: commands).<br>**{ZOOKEEPER.PORT}** - admin.serverPort; the port the embedded Jetty server listens on (default: 8080).<br>**{$ZOOKEEPER.SCHEME}** - the request scheme. Supported: http (default), https.|Metrics are collected from each ZooKeeper node by requests to AdminServer (enabled by default). See [ZooKeeper documentation](https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_adminserver_config) to enable or configure AdminServer.| # Opération de modèle HTTP Étapes pour garantir le bon fonctionnement des modèles qui collectent des métriques avec [l'agent HTTP](/manual/config/items/itemtypes/http) : 1. Créez un hôte dans Zabbix et spécifiez une adresse IP ou un nom DNS de la cible de surveillance comme interface principale. Cela est nécessaire pour que la macro {HOST.CONN} se résolve correctement dans les éléments de modèle.\ 2. [Liez](/manual/config/templates/linking#linking_a_template) le modèle à l'hôte créé à l'étape 1 (si le modèle n'est pas disponible dans votre installation Zabbix, vous devrez peut-être d'abord importer le fichier .xml du modèle - voir la section [Modèles prêts à l'emploi](/manual/config/templates_out_of_the_box) pour les instructions).\ 3. Ajustez les valeurs des macros obligatoires selon vos besoins.\ 4. Configurez l'instance surveillée pour autoriser le partage de données avec Zabbix - voir les instructions dans la colonne *Étapes supplémentaires/commentaires*. ::: notetip Cette page ne contient qu'un ensemble minimal de macros et d'étapes de configuration nécessaires au bon fonctionnement du modèle. Une description détaillée d'un modèle, y compris la liste complète des macros, des éléments et des déclencheurs, est disponible dans le fichier Readme.md du modèle (accessible en cliquant sur un nom de modèle). ::: |Modèle|Macros obligatoires|Étapes supplémentaires/commentaires| |--------|----------------|-------------------------| |[Apache by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/apache_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$APACHE.STATUS.HOST}** - le nom d'hôte ou l'adresse IP de la page d'état d'Apache (par défaut : 127.0.0.1).<br>**{\$APACHE.STATUS.PATH}** - le chemin de l'URL (par défaut : server-status?auto).<br>**{\$APACHE.STATUS.PORT}** - le port de la page d'état d'Apache (par défaut : 80).<br>**{\$APACHE.STATUS.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.|Apache module mod\_status doit être défini (voir la [documentation](https://httpd.apache.org/docs/current/mod/mod_status.html) Apache pour plus de détails).<br>Pour vérifier la disponibilité, exécutez :<br>`httpd -M 2>/dev/null \| grep status_module`<br><br>Exemple de configuration Apache :<br>`<Location "/server-status">`<br>`SetHandler server-status`<br>`Require host example.com`<br>`</Location>`| |[Asterisk by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/tel/asterisk_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$AMI.PORT}** - Numéro de port AMI pour vérifier la disponibilité du service (par défaut : 8088).<br>**{\$AMI.SECRET}** - le secret Asterisk Manager (par défaut : zabbix).<br>**{\$AMI.URL}** - l'URL de l'API Asterisk Manager au format<br>`<scheme>://<host>:<port>/<prefix>/rawman`<br>(par défaut : http://asterisk:8088/asterisk/rawman).<br>**{\$AMI.USERNAME}** - le nom de Asterisk Manager.|1\. Activez le [serveur mini-HTTP](https://wiki.asterisk.org/wiki/display/AST/Asterisk+Builtin+mini-HTTP+Server).<br><br>2. Ajoutez l'option `webenabled=yes` à la section générale du fichier *manager.conf*.<br><br>3. Créez l'utilisateur *Asterisk Manager* dans l'instance Asterisk.| |[ClickHouse by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/clickhouse_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$CLICKHOUSE.PORT}** - le port du point de terminaison HTTP ClickHouse (par défaut : 8123).<br>**{\$CLICKHOUSE.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.<br>**{\$CLICKHOUSE.USER}**, **{\$CLICKHOUSE.PASSWORD}** - Identifiants de connexion ClickHouse (nom d'utilisateur par défaut : zabbix, mot de passe : zabbix\_pass).<br>Si vous n'avez pas besoin d'authentification, supprimez les en-têtes des éléments de type d'agent HTTP.|Créez un utilisateur ClickHouse avec un profil 'web' et l'autorisation d'afficher les bases de données (voir la [documentation](https://clickhouse.tech/docs/en/operations/settings/settings-users/) ClickHouse pour plus de détails).<br><br>Voir le fichier *Readme.md* du modèle pour une configuration de fichier zabbix.xml prête à l'emploi.| |[Cloudflare by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/cloudflare_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$CLOUDFLARE.API.TOKEN}** - Valeur du jeton d'API Cloudflare (par défaut : \`\<change\>\`).<br>**{\$CLOUDFLARE.ZONE\_ID}** - ID de zone de site Cloudflare (par défaut : \`\<change\>\`).|Les jetons d'API Cloudflare sont disponibles dans le compte Cloudflare sous *My Profile→ API Tokens*.<br>L'ID de zone est disponible dans le compte Cloudflare sous *Account Home → Site*.| |[CockroachDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cockroachdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$COCKROACHDB.API.PORT}** - le port de l'API CockroachDB et du point de terminaison Prometheus. (par défaut : 8080).<br>**{\$COCKROACHDB.API.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.|Les métriques de nœud interne sont collectées à partir du point de terminaison Prometheus `/_status/vars`. <br> Les métriques de santé des nœuds sont collectées à partir des points de terminaison `/health` et `/health?ready=1`.<br><br>Le modèle ne nécessite pas l'utilisation d'un jeton de session. <br><br> Selon la version et la configuration de votre CockroachDB, certaines métriques peuvent ne pas être collectées.| |[DELL PowerEdge R720 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r720_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R740 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r740_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R820 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r820_http/README.md?at=refs%2Fheads%2Frelease%2F6.0),<br>[DELL PowerEdge R840 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/dell/dell_r840_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$API.URL}** - URL de l'API Dell iDRAC Redfish au format `<scheme>://<host>:<port>` (par défaut : <Mettez votre URL ici>)<br>**{\$API.USER}**, **{\$API.PASSWORD}** - Identifiants de connexion Dell iDRAC (par défaut : non définis).|Dans l'interface Dell iDRAC de votre serveur :<br>1. Activez l'API Redfish.<br>2. Créez un utilisateur pour la surveillance avec des autorisations en lecture seule.| |[Elasticsearch Cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/elasticsearch_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$ELASTICSEARCH.PORT}** - le port de l'hôte Elasticsearch (par défaut : 9200).<br>**{\$ELASTICSEARCH.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.<br>**{\$ELASTICSEARCH.USERNAME}**, **{\$ELASTICSEARCH.PASSWORD}** - identifiants de connexion, requis uniquement s'ils sont utilisés pour l'authentification Elasticsearch.| | |[Envoy Proxy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/envoy_proxy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$ENVOY.METRICS.PATH}** - le chemin d'où récupérer les métriques au format Prometheus (par défaut : `/stats/prometheus`).<br>**{\$ENVOY.URL}** - URL de l'instance Envoy Proxy (par défaut : http://localhost:9901)| Selon la version et la configuration de votre instance Envoy Proxy, certaines métriques peuvent ne pas être collectées. | |[Etcd by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/etcd_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$ETCD.PORT}**- le port utilisé par le point de terminaison de l'API Etcd (par défaut : 2379).<br>**{\$ETCD.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.<br>**{\$ETCD.USER}**, **{\$ETCD.PASSWORD}** - informations d'identification de connexion, requises uniquement si elles sont utilisées pour l'authentification Etcd.|Les métriques sont collectées à partir du point de terminaison /metrics ; pour spécifier l'emplacement du point de terminaison, utilisez l'indicateur `--listen-metrics-urls` (voir la [documentation](https://github.com/etcd-io/website/blob/master/content/docs/v3.4.0/op-guide/configuration.md#--listen-metrics-urls) Etcd pour plus de détails).<br><br>Pour vérifier si Etcd est configuré pour autoriser la collecte de métriques, exécutez :<br>`curl -L http://localhost:2379/metrics`<br><br>Pour vérifier, si Etcd est accessible depuis le proxy Zabbix ou le serveur Zabbix, exécutez :<br>`curl -L http:%%//<etcd_node_adress>:2379/metrics%%`<br><br>Le modèle doit être ajouté à chaque nœud Etcd.| |[GitLab by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/gitlab_http)|**{\$GITLAB.PORT}** - le port du point de terminaison Web GitLab (par défaut : 80)<br>**{\$GITLAB.URL}** - URL de l'instance GitLab (par défaut : localhost)|Ce modèle fonctionne avec les instances GitLab auto-hébergées ; les métriques sont collectées à partir du point de terminaison `/metrics`.<br><br>Pour accéder aux métriques, l'adresse IP du client doit être explicitement autorisée (voir la [documentation GitLab](https://docs.gitlab.com/ee/administration/monitoring/ip_whitelist.html) pour plus de détails).<br><br>Notez que certaines métriques peuvent ne pas être disponibles pour une version et une configuration d'instance GitLab particulières.| |[Hadoop by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/hadoop_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HADOOP.NAMENODE.HOST}** - l'adresse IP ou le FQDN de l'hôte Hadoop NameNode (par défaut : NameNode).<br>**{\$HADOOP.NAMENODE.PORT}** - le port de l'interface utilisateur Web Hadoop NameNode (par défaut : 9870).<br>**{\$HADOOP.RESOURCEMANAGER.HOST}** - l'adresse IP ou le FQDN de l'hôte Hadoop ResourceManager (par défaut : ResourceManager).<br>**{\$HADOOP.RESOURCEMANAGER.PORT}** - le port de l'interface utilisateur Web Hadoop ResourceManager (par défaut : 8088).|Les métriques sont collectées en interrogeant l'API Hadoop à distance à l'aide d'un agent HTTP et du prétraitement JSONPath. Le serveur Zabbix (ou proxy) exécute des requêtes directes aux API ResourceManager, NodeManagers, NameNode, DataNodes.| |[HAProxy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/haproxy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HAPROXY.STATS.PATH}** - le chemin de la page HAProxy Stats (par défaut : stats).<br>**{\$HAPROXY.STATS.PORT}** - le port de l'hôte ou du conteneur HAProxy Stats (par défaut : 8404).<br>**{\$HAPROXY.STATS.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.|La page de statistiques HAProxy doit être configurée (voir le [post du blog HAProxy](https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/) pour plus de détails ou le fichier Readme.md du modèle pour un exemple de configuration).| |[HashiCorp Consul Cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/consul_http/consul_cluster_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$CONSUL.API.PORT}** - Port API Consul, utilisé dans le nœud LLD (par défaut : 8500).<br>**{\$CONSUL.API.SCHEME}** - Schéma API Consul, utilisé dans le nœud LLD (par défaut : http).<br>**{\$CONSUL.CLUSTER.URL}** - URL du cluster Consul (par défaut : http://localhost:8500).<br>**{\$CONSUL.TOKEN}** - Jeton d'autorisation du Consul (par défaut : \<PUT YOUR AUTH TOKEN\>).| | |[HashiCorp Consul Node by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/consul_http/consul_node_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$CONSUL.NODE.API.URL}** - URL de l'instance Consul (par défaut : http://localhost:8500).<br>**{\$CONSUL.TOKEN}** - Jeton d'autorisation de Consul (par défaut : \<PUT YOUR AUTH TOKEN\>).|Les métriques de service interne sont collectées à partir du point de terminaison `/v1/agent/metrics`.<br><br> Le format Prometheus doit être activé pour les métriques d'exportation. Voir la [documentation](https://www.consul.io/docs/agent/options#telemetry-prometheus_retention_time) Consul pour plus de détails.| |[HashiCorp Vault by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/vault_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$VAULT.API.PORT}** - le port sur lequel Vault écoute les requêtes API (par défaut : 8200).<br>**{\$VAULT.API.SCHEME}** - le schéma de requête API. Pris en charge : http (par défaut), https.<br>**{\$VAULT.HOST}** - Nom d'hôte Vault (par défaut : \<PUT YOUR VAULT HOST\>).<br>**{\$VAULT.TOKEN}** - Jeton d'autorisation Vault (par défaut : \<PUT YOUR AUTH TOKEN\>).|1\. Configurez l'API Vault (voir la [documentation officielle](https://www.vaultproject.io/docs/configuration) pour plus de détails).<br>2. Créez un jeton de service Vault, puis copiez-le et collez-le dans la valeur de la macro {\$VAULT.TOKEN} dans Zabbix.| |[Hikvision camera by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cctv/hikvision/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HIKVISION\_ISAPI\_PORT}** - Port ISAPI sur un périphérique (par défaut : 80).<br>**{\$USER}**, **{\$PASSWORD}** - identifiants de connexion à la caméra (nom d'utilisateur par défaut : admin, mot de passe : 1234).| | |[InfluxDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/influxdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$INFLUXDB.API.TOKEN}** - Jeton d'autorisation de l'API InfluxDB (par défaut : \`\`).<br>**{\$INFLUXDB.URL}** - URL de l'instance InfluxDB au format `<scheme>://<host>:<port>` (par défaut : http://localhost:8086).|Ce modèle collecte des métriques de service internes à partir du point de terminaison InfluxDB /metrics des instances InfluxDB auto-hébergées.<br><br>Voir la [documentation](https://docs.influxdata.com/influxdb/v2.0/security/tokens/) InfluxDB pour plus de détails.| |[HPE MSA 2040 Storage by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_msa2040_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)/[HPE MSA 2060 Storage by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_msa2060_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HPE.MSA.API.PORT}** - port de connexion pour l'API (par défaut : 443)<br> **{\$HPE.MSA.API.SCHEME}** - schéma de connexion pour l'API. Pris en charge : http, https (par défaut)<br> **{\$HPE.MSA.API.USERNAME}**, **{\$HPE.MSA.API.PASSWORD}** - Informations d'identification de l'API (nom d'utilisateur par défaut : zabbix, mot de passe : \`\`). |Créez un utilisateur de stockage distinct (par exemple, *zabbix*) avec un rôle de moniteur et spécifiez le nom d'utilisateur et le mot de passe dans les macros de modèle. | |[HPE Primera by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/hpe_primera_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HPE.PRIMERA.API.PORT}** - port de connexion pour l'API (par défaut : 443) <br> **{\$HPE.PRIMERA.API.SCHEME}** - schéma de connexion pour WSAPI. Pris en charge : http, https (par défaut)<br> **{\$HPE.PRIMERA.API.USERNAME}**, **{\$HPE.PIMERA.API.PASSWORD}** - Informations d'identification WSAPI (nom d'utilisateur par défaut : zabbix, mot de passe : \`\`). |Créez un utilisateur de stockage distinct (par exemple, *zabbix*) avec un rôle de navigation et activez-le pour tous les domaines. <br><br> Pour démarrer le serveur WSAPI, connectez-vous à la CLI en tant qu'utilisateur dont le rôle dispose du droit `wsapi_set`, puis exécutez :<br> `startwsapi` <br><br> Pour vérifier l'état de WSAPI, exécutez : <br> `showwsapi`| |[HPE Synergy by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/hpe_synergy_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$HPE.SYNERGY.API.PORT}** - port de connexion pour l'API (par défaut : 443)<br> **{\$HPE.SYNERGY.API.SCHEME}** - schéma de connexion pour l'API. Pris en charge : http, https (par défaut)<br> **{\$HPE.SYNERGY.API.USERNAME}**, **{\$HPE.SYNERGY.API.PASSWORD}** - Informations d'identification de l'API (nom d'utilisateur par défaut : zabbix, mot de passe : \`\`). | | |[InfluxDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/influxdb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$INFLUXDB.API.TOKEN}** - Jeton d'autorisation de l'API InfluxDB (par défaut : \`\`).<br>**{\$INFLUXDB.URL}** - URL de l'instance InfluxDB au format `<scheme>://<host>:<port>` (par défaut : http://localhost:8086).|Ce modèle collecte des métriques de service internes à partir du point de terminaison InfluxDB /metrics des instances InfluxDB auto-hébergées.<br><br>Voir la [documentation](https://docs.influxdata.com/influxdb/v2.0/security/tokens/) InfluxDB pour plus de détails.| |[Jenkins by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jenkins/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$JENKINS.API.KEY}** - Clé API pour accéder à Metrics Servlet ; requis pour les métriques courantes (par défaut : \`\`).<br>**{\$JENKINS.API.TOKEN}** - Jeton API pour l'authentification HTTP BASIC ; requis pour surveiller les ordinateurs et les builds (par défaut : \`\`).<br>**{\$JENKINS.URL}** - URL Jenkins au format `<scheme>://<host>:<port>` ; requis pour surveiller les ordinateurs et les builds (par défaut : \`\`).<br>**{\$JENKINS.USER}** - nom d'utilisateur pour l'authentification HTTP BASIC ; requis pour surveiller les ordinateurs et les builds (par défaut : zabbix).|Les métriques sont collectées par des requêtes à l'API Metrics.<br><br>Pour les métriques courantes : installez et configurez les paramètres du plugin Metrics conformément à la [documentation officielle](https://plugins.jenkins.io/metrics/). Émettez une clé API pour accéder au servlet Metrics, puis utilisez-la comme valeur de macro {\$JENKINS.API.KEY}.<br><br>Pour surveiller les ordinateurs et les builds : créez un jeton API pour l'utilisateur Jenkins qui sera utilisé pour la surveillance, puis utilisez-le comme valeur de macro {\$JENKINS.API.TOKEN}. Voir la [documentation](https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/) Jenkins pour plus de détails.| |[Kubernetes API server by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_api_server_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.API.SERVER.URL}** - URL de l'instance (par défaut : http://localhost:8086/metrics).<br>**{\$KUBE.API.TOKEN}** - Jeton d'autorisation d'API (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes.<br><br> Les métriques internes sont collectées à partir du point de terminaison /metrics. <br><br> Utiliser le jeton d'API du porteur pour l'autorisation. Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails. | |[Kubernetes Controller manager by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_controller_manager_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.CONTROLLER.SERVER.URL}** - URL de l'instance (par défaut : http://localhost:10252/metrics).<br>**{\$KUBE.CONTROLLER.TOKEN}** - Jeton d'autorisation d'API (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes. <br><br> Les métriques internes sont collectées à partir du point de terminaison /metrics. <br><br> Utiliser le jeton d'API du porteur pour l'autorisation. Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails. | |[Kubernetes kubelet by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_kubelet_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.KUBELET.URL}** - URL de l'instance (par défaut : https://localhost:10250).<br>**{\$KUBE.API.TOKEN}** - Jeton d'autorisation d'API (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes. <br><br> Les métriques internes sont collectées à partir du point de terminaison /metrics. <br><br>Utiliser le jeton d'API du porteur pour l'autorisation. Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails. | |[Kubernetes nodes by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_nodes_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.API.ENDPOINT}** - Point de terminaison de l'API Kubernetes au format <scheme>://<host>:<port>/api (par défaut : non défini).<br>**{\$KUBE.API.TOKEN}** - Jeton d'autorisation d'API (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes. <br><br> Pour générer un jeton de compte de service, exécutez : <br> `kubectl get secret zabbix-service-account -n zabbix -o jsonpath={.data.token} | base64 -d` <br><br> Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails.<br><br> Le modèle contient des macros supplémentaires, qui peuvent être utilisées pour filtrer certaines mesures des nœuds de travail découverts. | |[Kubernetes Scheduler by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_scheduler_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.SCHEDULER.SERVER.URL}** - URL de l'instance (par défaut : http://localhost:10251/metrics).<br>**{\$KUBE.SCHEDULER.TOKEN}** - Jeton d'autorisation de l'API du planificateur (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes. <br><br> Les métriques internes sont collectées à partir du point de terminaison /metrics. <br><br> Utiliser le jeton d'API du porteur pour l'autorisation. Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails. | |[Kubernetes cluster state by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kubernetes_http/kubernetes_state_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) |**{\$KUBE.API.HOST}** - Hôte d'API Kubernetes (par défaut : non défini).<br>**{\$KUBE.API.PORT}**- Port de l'API Kubernetes (par défaut : 6443). <br> **{\$KUBE.API.TOKEN}** - Jeton d'autorisation d'API (par défaut : \`\`).| Le modèle nécessite [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0) pour être installé dans votre cluster Kubernetes. <br><br> Les métriques de service internes sont collectées à partir du point de terminaison kube-state-metrics. <br><br> Utiliser le jeton d'API du porteur pour l'autorisation. Voir la [documentation](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/) Kubernetes pour plus de détails.<br><br> Le modèle contient des macros supplémentaires, qui peuvent être utilisées pour filtrer certaines métriques des noeuds worker découverts. | |[Microsoft SharePoint by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/sharepoint_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$SHAREPOINT.URL}** - URL de la page du portail, par exemple *http://sharepoint.companyname.local/* (par défaut : \`\`).<br>**{\$SHAREPOINT.ROOT}** - un répertoire racine ; seul le répertoire spécifié et tous ses sous-dossiers seront surveillés (par défaut : /Shared Documents)<br>**{\$SHAREPOINT.USER}**, **{\$SHAREPOINT.PASSWORD}** - Identifiants de connexion SharePoint (par défaut : non définis).|Le modèle contient des macros supplémentaires, qui peuvent être utilisées pour filtrer certains dictionnaires et types pendant le processus LLD (voir [Readme.md](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates /app/sharepoint_http/README.md?at=refs%2Fheads%2Frelease%2F6.0) du modèle pour la description des macros de filtre disponibles).| |[NetApp AFF A700 by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/netapp_aff_a700_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$URL}** - Adresse URL du cluster AFF700 (par défaut : ' ' )<br>**{\$USERNAME}**, **{PASSWORD}** - Identifiants de connexion AFF700 (par défaut : non définis).|Créez un hôte pour AFF A700 avec l'IP de gestion du cluster comme interface de l'agent Zabbix.| |[NGINX by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$NGINX.STUB\_STATUS.HOST}** - le nom d'hôte ou l'adresse IP de l'hôte ou du conteneur NGINX stub\_status (par défaut : localhost).<br>**{\$NGINX.STUB\_STATUS.PATH}** - le chemin de la page NGINX stub\_status (par défaut : basic\_status).<br>**{\$NGINX.STUB\_STATUS.PORT}** - le port de l'hôte ou du conteneur NGINX stub\_status (par défaut : 80).<br>**{\$NGINX.STUB\_STATUS.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.|`'ngx_http_stub_status_module` doit être configuré (voir la [documentation](https://nginx.org/en/docs/http/ngx_http_stub_status_module.html) NGINX pour plus de détails ou le Readme.md du modèle pour un exemple de configuration).<br>Pour vérifier la disponibilité, exécutez : <br>`nginx -V 2>&1 \| grep -o avec-http_stub_status_module`| |[NGINX Plus by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_plus_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$NGINX.API.ENDPOINT}** - URL de l'API NGINX Plus au format `<scheme>://<host>:<port>/<location>/` (par défaut : ' ').|1\. Activez l'API NGINX Plus (voir la [documentation](https://www.nginx.com/products/nginx/live-activity-monitoring/) NGINX pour plus de détails).<br>2. Définissez la macro {\$NGINX.API.ENDPOINT}<br>3. Si nécessaire, utilisez d'autres macros de modèle pour filtrer les opérations de découverte et découvrir uniquement les zones et les zones en amont requises.| |[OpenWeatherMap by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/openweathermap_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$OPENWEATHERMAP.API.ENDPOINT}** - Point de terminaison de l'API OpenWeatherMap (par défaut : api.openweathermap.org/data/2.5/weather?).<br>**{\$OPENWEATHERMAP.API.TOKEN}** - Clé API OpenWeatherMap (par défaut : ' ')<br>**{\$LOCATION}** - emplacements pour lesquels récupérer les métriques (par défaut : Riga) |Pour obtenir des instructions sur l'obtention de la clé API, consultez la [documentation](https://home.openweathermap.org/api_key) OpenWeatherMap. <br><br> **{\$LOCATION}** prend en charge les formats suivants : <br> *coordonnées géographiques* - par exemple, `56.95,24.0833`<br> *nom de l'emplacement* - par exemple, `Chicago`<br> *ID de l'emplacement OpenWeatherMap* - [télécharger la liste des ID](http://bulk.openweathermap.org/sample/city.list.json.gz)<br>*zip/code postal avec un code de pays* - par exemple, `94040,us`<br> Pour spécifier plusieurs emplacements, utilisez le délimiteur \|. <br> Exemple :<br>`43.81821,7.76115|Riga|2643743|94040,us` | |[PHP-FPM by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/php-fpm_agent/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$PHP\_FPM.HOST}** -un nom d'hôte ou une IP d'hôte ou de conteneur de statut PHP-FPM (par défaut : localhost).<br>**{\$PHP\_FPM.PING.PAGE}** - Chemin de la page de ping PHP-FPM (par défaut : ping).<br>**{\$PHP\_FPM.PORT}** - le port de l'hôte ou du conteneur de statut PHP-FPM (par défaut : 80).<br>**{\$PHP\_FPM.PROCESS\_NAME}** - Nom du processus PHP-FPM (par défaut : php-fpm).<br>**{\$PHP\_FPM.SCHEME}** - le schema de la demande. Pris en charge : http (par défaut), https.<br>**{\$PHP\_FPM.STATUS.PAGE}** - Chemin de la page d'état PHP-FPM (par défaut : `status`).|1\. Ouvrez le fichier de configuration php-fpm et activez la page d'état :<br>`pm.status_path = /status`<br>`ping.path = /ping`<br><br>2. Validez la syntaxe : `$ php-fpm7 -t`<br><br>3. Rechargez le service php-fpm.<br><br>4. Dans le fichier de configuration Nginx Server Block (hôte virtuel), ajoutez (voir *Readme.md* du modèle pour un exemple développé avec des commentaires) :<br>`location ~ ^/(status\|ping)$ {`<br>` access_log off;`<br>`fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;`<br>`fastcgi_index index.php;`<br>`include fastcgi_params;`<br>`fastcgi_pass 127.0.0.1:9000;`<br>` }`<br><br>5. Vérifiez la syntaxe : `$ nginx -t`<br><br>6. Rechargez Nginx<br><br>7. Vérifiez : `curl -L 127.0.0.1/status`| |[Proxmox VE by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/proxmox/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$PVE.TOKEN.ID}** - Jeton d'API qui permet un accès sans état à la plupart des parties de l'API REST (par défaut : non défini). <br> **{\$PVE.TOKEN.SECRET}** - clé secrète (par défaut : non définie). <br> **{\$PVE.URL.PORT}** - le port sur lequel le serveur écoute (par défaut : 8006). |Créez un utilisateur distinct pour la surveillance, puis générez un jeton d'API pour cet utilisateur. <br> Accordez les niveaux d'accès suivants au jeton et à l'utilisateur : <br>``Check: ["perm","/",["Sys.Audit"]]``<br>``Check: ["perm","/nodes/{node}",["Sys.Audit"]]``<br>``Check: ["perm","/vms/{vmid}",["VM.Audit"]]`` | |[RabbitMQ cluster by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/rabbitmq_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$RABBITMQ.API.CLUSTER\_HOST}** - le nom d'hôte ou l'adresse IP du point de terminaison de l'API du cluster RabbitMQ (par défaut : 127.0.0.1).<br>**{\$RABBITMQ.API.SCHEME}** - le régime de la demande. Pris en charge : http (par défaut), https.<br>**{\$RABBITMQ.API.USER}**, **{\$RABBITMQ.API.PASSWORD}** - Identifiants de connexion RabbitMQ (nom d'utilisateur par défaut : zbx\_monitor, mot de passe : zabbix).|Activez le plug-in de gestion RabbitMQ (voir [documentation RabbitMQ](https://www.rabbitmq.com/management.html)).<br><br>Pour créer un utilisateur RabbitMQ avec les autorisations nécessaires pour la surveillance, exécutez :<br>`rabbitmqctl add\_user zbx\_monitor <PASSWORD> `<br>`rabbitmqctl set_permissions -p / zbx_monitor %% "" "" ".*"%%`<br>`rabbitmqctl set_user_tags zbx_monitor monitoring`<br><br>Si le cluster se compose de plusieurs nœuds, il est recommandé d'attribuer le modèle de cluster à un hôte d'équilibrage distinct. Dans le cas d'une installation à nœud unique, le modèle de cluster peut être attribué à l'hôte avec un modèle de nœud.| |[TiDB by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_tidb_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$TIDB.PORT}** - Le port du point de terminaison Web des métriques du serveur TiDB (par défaut : 10080)<br>**{\$TIDB.URL}** - URL du serveur TiDB (par défaut : localhost).|Ce modèle fonctionne avec le serveur TiDB du cluster PingCAP TiDB.<br>Les métriques de service internes sont collectées à partir du point de terminaison TiDB /metrics et de l'API de surveillance TiDB.| |[TiDB PD by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_pd_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$TIDB.PORT}** - Le port du point de terminaison Web des métriques du serveur TiDB (par défaut : 2379)<br>**{\$TIDB.URL}** - URL du serveur TiDB (par défaut : localhost).|Ce modèle fonctionne avec le serveur PD du cluster PingCAP TiDB.<br>Les métriques de service internes sont collectées à partir du point de terminaison PD /metrics et de l'API de surveillance TiDB.| |[TiDB TiKV by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/tidb_http/tidb_tikv_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$TIDB.PORT}** - Le port du point de terminaison Web des métriques du serveur TiDB (par défaut : 20180)<br>**{\$TIDB.URL}** - URL du serveur TiDB (par défaut : localhost).|Ce modèle fonctionne avec le serveur TiKV du cluster PingCAP TiDB.<br>Les métriques de service interne sont collectées à partir du point de terminaison TiKV /metrics.| |[Travis CI by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/travis_ci_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$TRAVIS.API.TOKEN}** - Jeton API Travis (par défaut : non défini)<br>**{\$TRAVIS.API.URL}** - URL API Travis (par défaut : api.travis-ci.com).|Le jeton d'authentification API Travis se trouve dans la section *Utilisateur → Paramètres → Authentification API*.<br>Le format {\$TRAVIS.API.URL} pour un projet privé est *api.travis-ci.com*.<br>Le format {\$TRAVIS.API.URL} pour un projet d'entreprise est *api.example.com* (remplacez example.com par le domaine sur lequel Travis CI s'exécute).| |[VMWare SD-WAN VeloCloud by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/velocloud_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$VELOCLOUD.TOKEN}** - Jeton d'API VMware SD-WAN Orchestrator (par défaut : \`\`).<br>**{\$VELOCLOUD.URL}** - URL de VMware SD-WAN Orchestrator, par exemple, *velocloud.net* (par défaut : \`\`).|Le jeton d'API doit être créé dans VMware SD-WAN Orchestrator (voir la [documentation VMware](https://docs.vmware.com/en/VMware-SD-WAN/4.0/vmware-sd-wan-operator-guide/GUID-C150D536-A75F-47C1-8AFF-17C417F40C1D.html) pour plus de détails).| |[ZooKeeper by HTTP](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/zookeeper_http/README.md?at=refs%2Fheads%2Frelease%2F6.0)|**{\$ZOOKEEPER.COMMAND\_URL}** - admin.commandURL ; l'URL pour lister et émettre des commandes relatives à l'URL racine (par défaut : commands).<br>**{ZOOKEEPER.PORT}** - admin.serverPort ; le port sur lequel le serveur Jetty intégré écoute (par défaut : 8080).<br>**{\$ZOOKEEPER.SCHEME}** - le schéma de requête. Pris en charge : http (par défaut), https.|Les métriques sont collectées à partir de chaque nœud ZooKeeper par des requêtes adressées à AdminServer (activé par défaut). Voir la [Documentation ZooKeeper](https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_adminserver_config) pour activer ou configurer AdminServer.| # httptest.create # httptest.create # httptest.delete # httptest.delete # httptest.get # httptest.get # httptest.update # httptest.update #### Hysteresis Sometimes an interval is needed between problem and recovery states, rather than a simple threshold. For example, if we want to define a trigger that reports a problem when server room temperature goes above 20°C and we want it to stay in the problem state until the temperature drops below 15°C, a simple trigger threshold at 20°C will not be enough. Instead, we need to define a trigger expression for the problem event first (temperature above 20°C). Then we need to define an additional recovery condition (temperature below 15°C). This is done by defining an additional *Recovery expression* parameter when [defining](/manual/config/triggers/trigger) a trigger. In this case, problem recovery will take place in two steps: - First, the problem expression (temperature above 20°C) will have to evaluate to FALSE - Second, the recovery expression (temperature below 15°C) will have to evaluate to TRUE The recovery expression will be evaluated only when the problem event is resolved first. ::: notewarning The recovery expression being TRUE alone does not resolve a problem if the problem expression is still TRUE! ::: #### Hystérésis Parfois, un intervalle est nécessaire entre les états problème et récupération, plutôt qu'un simple seuil. Par exemple, si nous voulons définir un déclencheur signalant un problème lorsque la température de la salle des serveurs dépasse 20°C et que nous souhaitons qu'il reste dans l'état du problème jusqu'à ce que la température descende sous 15°C, un seuil de déclenchement simple à 20°C ne suffira pas. Au lieu de cela, nous devons d'abord définir une expression de déclenchement pour l'événement problématique (température supérieure à 20°C). Ensuite, nous devons définir une condition de récupération supplémentaire (température inférieure à 15°C). Pour ce faire, vous définissez un paramètre *Expression de récupération* supplémentaire lors de la [définition](/manual/config/triggers/trigger) du déclencheur. Dans ce cas, la récupération du problème se fera en deux étapes : - Tout d’abord, l’expression du problème (température supérieure à 20°C) devra être évaluée à FAUX - Deuxièmement, l'expression de récupération (température inférieure à 15°C) devra être évaluée à VRAI L'expression de récupération sera évaluée uniquement lorsque l'événement posant problème est résolu en premier. ::: notewarning L'expression de récupération seule à VRAI ne résout pas le problème si l'expression du problème est toujours VRAI ! ::: ##### Icon highlighting If a map element is in problem status, it is highlighted with a round circle. The fill color of the circle corresponds to the severity color of the problem. Only problems on or above the selected severity level will be displayed with the element. If all problems are acknowledged, a thick green border around the circle is displayed. Additionally: - a host in [maintenance](/manual/maintenance) is highlighted with an orange, filled square. Note that maintenance highlighting has priority over the problem severity highlighting (since Zabbix 6.0.5, only if the map element is host). - a disabled (not-monitored) host is highlighted with a gray, filled square. Highlighting is displayed if the *Icon highlighting* check-box is marked in map [configuration](/manual/config/visualization/maps/map#creating_a_map). ##### Icône en surbrillance Si un élément de la carte est en état de problème, il est mis en surbrillance avec un cercle. La couleur de remplissage du cercle correspond à la couleur de sévérité du problème. Seuls les problèmes au niveau de sévérité sélectionné ou au-dessus seront affichés avec l'élément. Si tous les problèmes sont acquittés, une bordure verte épaisse autour du cercle s'affiche. En outre: - un hôte en [maintenance](/manual/maintenance) est mis en évidence avec un carré orange plein. Notez que la mise en surbrillance de maintenance a priorité sur la mise en évidence de la sévérité du problème (depuis Zabbix 6.0.5, uniquement si l'élément de la carte est un hôte). - un hôte désactivé (non surveillé) est mis en surbrillance avec un carré gris rempli. La surbrillance s'affiche si la case à cocher *Icône en surbrillance* est cochée sur la [configuration](/manual/config/visualization/maps/map#creating_a_map) de la carte. # iconmap.create # iconmap.create # iconmap.delete # iconmap.delete # iconmap.get # iconmap.get ### Icon mapping The icon mapping object defines a specific icon to be used for hosts with a certain inventory field value. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |iconmappingid|string|*(readonly)* ID of the icon map.| |**iconid**<br>(required)|string|ID of the icon used by the icon mapping.| |**expression**<br>(required)|string|Expression to match the inventory field against.| |**inventory\_link**<br>(required)|integer|ID of the host inventory field.<br><br>Refer to the [host inventory object](/manual/api/reference/host/object#host_inventory) for a list of supported inventory fields.| |iconmapid|string|*(readonly)* ID of the icon map that the icon mapping belongs to.| |sortorder|integer|*(readonly)* Position of the icon mapping in the icon map.| ### Mappage d'icône L'objet de mappage d'icône définit une icône spécifique à utiliser pour les hôtes ayant une certaine valeur de champ d'inventaire. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |iconmappingid|string|*(lecture seule)* ID de la correspondance d'icônes.| |**iconid**<br>(obligatoire)|string|ID de l'icône utilisée par le mappage d'icône.| |**expression**<br>(obligatoire)|string|Expression pour faire correspondre le champ d’inventaire.| |**inventory\_link**<br>(obligatoire)|integer|ID du champ d'inventaire de l'hôte.<br><br>Se référer à l'[objet Inventaire d'hôte](/manual/api/reference/host/object#host_inventory) pour une liste des champs d'inventaire supportés.| |iconmapid|string|*(lecture seule)* Identifiant de la correspondance d'icône à laquelle appartient le mappage.| |sortorder|integer|*(lecture seule)* Position du mappage d'icône dans la correspondance d'icônes.| # iconmap.update # iconmap.update If access rights to persistent storage files are removed during agent operation or other errors occur (e.g. disk full) then errors are logged into the agent log file but the log item does not become NOTSUPPORTED. Si les droits d'accès aux fichiers de stockage persistants sont supprimés pendant le fonctionnement de l'agent ou si d'autres erreurs se produisent (par exemple, disque plein), les erreurs sont consignées dans le fichier journal de l'agent mais l'élément de journal ne devient NON SUPPORTÉ. ##### If the webhook test fails - *"Media type test failed."* message is displayed, followed by additional failure details. ##### Si le test du webhook échoue - Le message *"Échec du test du type de support."* s'affiche, suivi de détails supplémentaires sur l'échec. ##### If the webhook test is successful - *"Media type test successful."* message is displayed - Server response appears in the gray *Response* field - Response type (JSON or String) is specified below the *Response* field ##### Si le test du webhook est réussi - Le message *"Test du type de support réussi."* s'affiche - La réponse du serveur apparaît dans le champ gris *Réponse* - Le type de réponse (JSON ou String) est spécifié sous le champ *Réponse* # image.create # image.create # image.delete # image.delete # image.get # image.get ### Image The image object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |imageid|string|*(readonly)* ID of the image.| |**name**<br>(required)|string|Name of the image.| |imagetype|integer|Type of image.<br><br>Possible values:<br>1 - *(default)* icon;<br>2 - background image.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Image L'objet image possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |imageid|string|*(lecture seule)* ID de l'image.| |**name**<br>(obligatoire)|string|Nom de l'image.| |imagetype|integer|Type d'image.<br><br>Valeurs possibles:<br>1 - *(par défaut)* icône;<br>2 - image de fond.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # image.update # image.update ### Implementation details The high availability (HA) cluster is an opt-in solution and it is supported for Zabbix server. The native HA solution is designed to be simple in use, it will work across sites and does not have specific requirements for the databases that Zabbix recognizes. Users are free to use the native Zabbix HA solution, or a third-party HA solution, depending on what best suits the high availability requirements in their environment. The solution consists of multiple zabbix\_server instances or nodes. Every node: - is configured separately - uses the same database - may have several modes: active, standby, unavailable, stopped Only one node can be active (working) at a time. A standby node runs only one process - the HA manager. A standby node does no data collection, processing or other regular server activities; they do not listen on ports; they have minimum database connections. Both active and standby nodes update their last access time every 5 seconds. Each standby node monitors the last access time of the active node. If the last access time of the active node is over 'failover delay' seconds, the standby node switches itself to be the active node and assigns 'unavailable' status to the previously active node. The active node monitors its own database connectivity - if it is lost for more than `failover delay-5` seconds, it must stop all processing and switch to standby mode. The active node also monitors the status of the standby nodes - if the last access time of a standby node is over 'failover delay' seconds, the standby node is assigned the 'unavailable' status. The nodes are designed to be compatible across minor Zabbix versions. ### Détails d'implémentation Le cluster haute disponibilité (HA) est une solution opt-in et il est pris en charge pour le serveur Zabbix. La solution HA native est conçue pour être simple à utiliser, elle fonctionnera sur tous les sites et n'a pas d'exigences spécifiques pour les bases de données reconnues par Zabbix. Les utilisateurs sont libres d'utiliser la solution HA native Zabbix ou une solution HA tierce, selon ce qui convient le mieux aux exigences de haute disponibilité de leur environnement. La solution consiste en plusieurs instances ou nœuds zabbix\_server. Chaque nœud : - est configuré séparément - utilise la même base de données - peut avoir plusieurs modes : active, standby, unavailable, stopped Un seul nœud peut être actif à la fois. Un nœud standby n'exécute qu'un seul processus : le gestionnaire HA. Un nœud standby n'effectue pas de collecte de données, de traitement ou d'autres activités habituelles du serveur ; ils n'écoutent pas sur les ports ; ils ont un minimum de connexions à la base de données. Les nœuds actifs et standby mettent à jour leur heure de dernier accès toutes les 5 secondes. Chaque nœud standby surveille l'heure du dernier accès du nœud actif. Si le dernier temps d'accès du nœud actif est supérieur à « délai de basculement » secondes, le nœud standby devient le nœud actif et attribue l'état 'unavailable' au nœud précédemment actif. Le nœud actif surveille sa propre connectivité à la base de données - s'il est perdu pendant plus de `délai de basculement-5` secondes, il doit arrêter tout traitement et passer en mode standby. Le nœud actif surveille également l'état des nœuds standby - si le dernier temps d'accès d'un nœud standby dépasse le « délai de basculement » secondes, le nœud standby se voit attribuer l'état 'unavailable'. Les nœuds sont conçus pour être compatibles entre les versions mineures de Zabbix. #### Important notes - Database monitoring items will become unsupported if no *odbc poller* processes are started in the server or proxy configuration. To activate ODBC pollers, set *StartODBCPollers* parameter in Zabbix [server](/manual/appendix/config/zabbix_server) configuration file or, for checks performed by proxy, in Zabbix [proxy](/manual/appendix/config/zabbix_proxy) configuration file. - Zabbix does not limit the query execution time. It is up to the user to choose queries that can be executed in a reasonable amount of time. - The [Timeout](/manual/appendix/config/zabbix_server) parameter value from Zabbix server is used as the ODBC login timeout (note that depending on ODBC drivers the login timeout setting might be ignored). - The SQL command must return a result set like any query with `select ...`. The query syntax will depend on the RDBMS which will process them. The syntax of request to a storage procedure must be started with `call` keyword. #### Remarques importantes - Les éléments de surveillance de la base de données ne seront plus pris en charge si aucun processus *odbc poller* n'est démarré dans la configuration du serveur ou du proxy. Pour activer les pollers ODBC, définissez le paramètre *StartODBCPollers* dans le fichier de configuration [serveur](/manual/appendix/config/zabbix_server) Zabbix ou, pour les vérifications effectuées par proxy, dans le fichier de configuration [proxy](/manual/appendix/config/zabbix_proxy) Zabbix. - Zabbix ne limite pas le temps d'exécution des requêtes. Il appartient à l'utilisateur de choisir des requêtes pouvant être exécutées dans un délai raisonnable. - La valeur du paramètre [Timeout](/manual/appendix/config/zabbix_server) du serveur Zabbix est utilisée comme délai de connexion ODBC (notez que selon les pilotes ODBC, le paramètre de délai de connexion peut être ignoré). - La commande SQL doit retourner un jeu de résultats comme n'importe quelle requête avec `select ...`. La syntaxe des requêtes dépendra du SGBDR qui les traitera. La syntaxe de requête à une procédure de stockage doit être démarrée avec le mot-clé `call`. #### Important notes - If more than one user macro with context exists, Zabbix will try to match the simple context macros first and then context macros with regular expressions in an undefined order. ::: notewarning Do not create different context macros matching the same string to avoid undefined behavior. ::: - If a macro with its context is not found on host, linked templates or globally, then the macro without context is searched for. - Only low-level discovery macros are supported in the context. Any other macros are ignored and treated as plain text. Technically, macro context is specified using rules similar to [item key](/manual/config/items/item/key) parameters, except macro context is not parsed as several parameters if there is a `,` character: - Macro context must be quoted with `"` if the context contains a `}` character or starts with a `"` 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:"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. #### Notes importantes - S'il existe plusieurs macros utilisateur avec contexte, Zabbix essaiera d'abord de faire correspondre les macros de contexte simples, puis les macros de contexte avec des expressions régulières dans un ordre indéfini. ::: notewarning Ne créez pas de macros de contexte différentes correspondant à la même chaîne pour éviter un comportement indéfini. ::: - Si une macro avec son contexte n'est pas trouvée sur l'hôte, sur les modèles liés ou globalement, la macro sans contexte est recherchée. - Seules les macros de découverte de bas niveau sont prises en charge dans le contexte. Toutes les autres macros sont ignorées et traitées comme du texte brut. Techniquement, le contexte de la macro est spécifié à l'aide de règles similaires aux paramètres de la [clé d'élément](/manual/config/items/item/key), sauf que le contexte de la macro n'est pas analysé comme plusieurs paramètres s'il y a un caractère `,` : - Le contexte de la macro doit être entre guillemets avec `"` si le contexte contient un caractère `}` ou commence par un caractère `"`. Les guillemets à l'intérieur du contexte entre guillemets doivent être échappés avec le caractère `\`. - Le caractère `\` lui-même n'est pas échappé, ce qui signifie qu'il est impossible d'avoir un contexte entre guillemets se terminant par le caractère `\` - la macro {$MACRO:"a:\\b\\c\\"} est invalide. - Les espaces de début dans le contexte sont ignorés, les espaces de fin ne le sont pas : - Par exemple {\$MACRO:A} est identique à {\$MACRO: A}, mais pas à {$MACRO:A }. - Tous les espaces avant les guillemets de début et après les guillemets de fin sont ignorés, mais tous les espaces à l'intérieur des guillemets ne le sont pas : - Les macros {\$MACRO:"A"}, {\$MACRO: "A"}, {\$MACRO:"A" } et {\$MACRO: "A" } sont identiques, mais les macros {\$MACRO:"A"} et {\$MACRO:" A "} ne le sont pas. Les macros suivantes sont toutes équivalentes, car elles ont le même contexte : {\$MACRO:A}, {\$MACRO:A} et {\$MACRO:"A"}. Cela contraste avec les clés d'élément, où 'key\[a\]', 'key\[ a\]' et 'key\["a"\]' sont sémantiquement identiques, mais différents à des fins d'unicité. #### Importing a template Import the template configuration contained in the XML string. If any items or triggers in the XML string are missing, they will be deleted from the database, and everything else will be left unchanged. Request: ```json { "jsonrpc": "2.0", "method": "configuration.import", "params": { "format": "xml", "rules": { "templates": { "createMissing": true, "updateExisting": true }, "items": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "triggers": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "valueMaps": { "createMissing": true, "updateExisting": false } }, "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:00:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter>&lt;dt&gt;Server uptime: (.*)&lt;/dt&gt;</parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>6805d4c39a624a8bab2cc8ab63df1ab3</uuid><name>CPU load</name><key>system.cpu.load</key><value_type>FLOAT</value_type><triggers><trigger><uuid>ab4c2526c2bc42e48a633082255ebcb3</uuid><expression>avg(/New template/system.cpu.load,3m)&gt;2</expression><name>CPU load too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": true, "id": 1 } ``` #### Importation d'un modèle Importe la configuration d'un modèle contenue dans la chaîne XML. S'il manque des éléments ou des déclencheurs dans la chaîne XML, ils seront supprimés de la base de données et tout le reste restera inchangé. Requête : ```json { "jsonrpc": "2.0", "method": "configuration.import", "params": { "format": "xml", "rules": { "templates": { "createMissing": true, "updateExisting": true }, "items": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "triggers": { "createMissing": true, "updateExisting": true, "deleteMissing": true }, "valueMaps": { "createMissing": true, "updateExisting": false } }, "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>6.0</version><date>2023-01-01T12:00:00Z</date><groups><group><uuid>7df96b18c230490a9a0a9e2307226338</uuid><name>Templates</name></group></groups><templates><template><uuid>5aef0444a82a4d8cb7a95dc4c0c85330</uuid><template>New template</template><name>New template</name><groups><group><name>Templates</name></group></groups><items><item><uuid>7f1e6f1e48aa4a128e5b6a958a5d11c3</uuid><name>Zabbix agent ping</name><key>agent.ping</key></item><item><uuid>77ba228662be4570830aa3c503fcdc03</uuid><name>Apache server uptime</name><type>DEPENDENT</type><key>apache.server.uptime</key><delay>0</delay><trends>0</trends><value_type>TEXT</value_type><preprocessing><step><type>REGEX</type><parameters><parameter><dt>Server uptime: (.*)</dt></parameter><parameter>\\1</parameter></parameters></step></preprocessing><master_item><key>web.page.get[127.0.0.1/server-status]</key></master_item></item><item><uuid>6805d4c39a624a8bab2cc8ab63df1ab3</uuid><name>CPU load</name><key>system.cpu.load</key><value_type>FLOAT</value_type><triggers><trigger><uuid>ab4c2526c2bc42e48a633082255ebcb3</uuid><expression>avg(/New template/system.cpu.load,3m)>2</expression><name>CPU load too high on 'New host' for 3 minutes</name><priority>WARNING</priority></trigger></triggers></item><item><uuid>590efe5731254f089265c76ff9320726</uuid><name>Apache server status</name><key>web.page.get[127.0.0.1/server-status]</key><trends>0</trends><value_type>TEXT</value_type></item></items><valuemaps><valuemap><uuid>8fd5814c45d44a00a15ac6eaae1f3946</uuid><name>Zabbix agent ping</name><mappings><mapping><value>1</value><newvalue>Available</newvalue></mapping><mapping><value>0</value><newvalue>Not available</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>\n" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": true, "id": 1 } ``` ##### Importing data Import initial schema: # cat /usr/share/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix For proxy with PostgreSQL (or SQLite): # cat /usr/share/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix # cat /usr/share/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db ##### Importation de données Importer le schéma initial : # cat /usr/share/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix Pour un proxy avec PostgreSQL (ou SQLite) : # cat /usr/share/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix # cat /usr/share/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db #### Importing data with Timescale DB With TimescaleDB, in addition to the import command for PostgreSQL, also run: # cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix ::: notewarning TimescaleDB is supported with Zabbix server only. ::: #### Importation de données avec Timescale DB Avec TimescaleDB, en plus de la commande d'importation pour PostgreSQL, exécuter également : # cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix ::: notewarning TimescaleDB est pris en charge uniquement avec le serveur Zabbix. ::: #### Importing To import hosts, do the following: - Go to: *Configuration* → *Hosts* - Click on *Import* to the right - Select the import file - Mark the required options in import rules - Click on *Import*  A success or failure message of the import will be displayed in the frontend. Import rules: |Rule|Description| |----|-----------| |*Update existing*|Existing elements will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new elements using data from the import file. Otherwise it will not add them.| |*Delete missing*|The import will remove existing elements not present in the import file. Otherwise it will not remove them.<br>If *Delete missing* is marked for template linkage, existing template linkage not present in the import file will be removed from the host along with all entities inherited from the potentially unlinked templates (items, triggers, etc).| #### Import Pour importer des hôtes, procédez comme suit : - Allez dans : *Configuration* → *Hôtes* - Cliquez sur *Importer* à droite - Sélectionnez le fichier d'importation - Marquez les options requises dans les règles d'importation - Cliquez sur *Importer*  Un message de réussite ou d'échec de l'importation s'affichera dans l'interface web. Règles d'importation : |Règle|Description| |----|-----------| |*Mettre à jour l'existant*|Les éléments existants seront mis à jour avec les données extraites du fichier d'import. Sinon, ils ne seront pas mis à jour.| |*Create new*|L'import ajoutera de nouveaux éléments en utilisant les données du fichier d'import. Sinon, il ne les ajoutera pas.| |*Supprimer manquant*|L'import supprimera les éléments existants non présents dans le fichier d'importation. Sinon, il ne les supprimera pas.<br>Si *Supprimer manquant* est marqué pour modèle lié, le modèle lié existant non présent dans le fichier d'import sera supprimé de l'hôte avec toutes les entités héritées des modèles potentiellement non liés (éléments, déclencheurs , etc.).| #### Importing To import media types, do the following: - Go to: *Administration* → *Media types* - Click on *Import* to the right - Select the import file - Mark the required options in import rules - Click on *Import*  A success or failure message of the import will be displayed in the frontend. Import rules: |Rule|Description| |----|-----------| |*Update existing*|Existing elements will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new elements using data from the import file. Otherwise it will not add them.| |*Delete missing*|The import will remove existing elements not present in the import file. Otherwise it will not remove them.| #### Importing Pour importer des types de médias, procéder comme suit : - Aller dans : *Administration* → *Types de médias* - Cliquer sur *Importer* sur la droite - Sélectionner le fichier à importer - Cocher les options requises dans les règles d'importation - Cliquer sur *Importer*  Un message de réussite ou d'échec de l'importation sera affiché dans l'interface. Règles d'importation : |Règle|Description| |----|-----------| |*Mettre à jour l'existant*|Les éléments existants seront mis à jour avec les données extraites du fichier d'importation. Sinon, ils ne seront pas mis à jour.| |*Créer le nouveau*|L'importation ajoutera de nouveaux éléments à l'aide des données du fichier d'importation. Sinon, il ne les ajoutera pas.| |*Supprimer le manquant*|L'importation supprimera les éléments existants non présents dans le fichier d'importation. Sinon, il ne les supprimera pas.| #### Importing To import network maps, do the following: - Go to: *Monitoring* → *Maps* - Click on *Import* to the right - Select the import file - Mark the required options in import rules - Click on *Import*  All mandatory input fields are marked with a red asterisk. A success or failure message of the import will be displayed in the frontend. Import rules: |Rule|Description| |----|-----------| |*Update existing*|Existing maps will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new maps using data from the import file. Otherwise it will not add them.| If you uncheck both map options and check the respective options for images, images only will be imported. Image importing is only available to Super Admin users. ::: notewarning If replacing an existing image, it will affect all maps that are using this image. ::: #### Import Pour importer des cartes du réseau, procéder comme suit : - Aller dans : *Surveillance* → *cartes* - Cliquer sur *Importer* sur la droite - Sélectionner le fichier à importer - Cocher les options requises dans les règles d'importation - Cliquer sur *Importer*  Tous les champs obligatoires sont marqués par un astérisque rouge. Un message de réussite ou d'échec de l'import sera affiché dans l'interface. Règles d'import : |Règle|Description| |----|-----------| |*Mettre à jour l'existant*|Les éléments existants seront mis à jour avec les données extraites du fichier d'import. Sinon, ils ne seront pas mis à jour.| |*Créer le nouveau*|L'importation ajoutera de nouveaux éléments à l'aide des données du fichier d'import. Sinon, il ne les ajoutera pas.| |*Supprimer le manquant*|L'importation supprimera les éléments existants non présents dans le fichier d'importation. Sinon, il ne les supprimera pas.| Si vous décochez les deux options de carte et cochez les options respectives pour les images, seules les images seront importées. L'importation d'images n'est disponible que pour les utilisateurs super administrateurs. ::: notewarning Si vous remplacez une image existante, cela affectera toutes les cartes qui utilisent cette image. ::: ### Improved performance of history syncers The performance of history syncers has been improved by introducing a new read-write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only by the configuration syncer performing a configuration cache reload. ### Amélioration des performances des synchroniseurs d'historique Les performances des synchroniseurs d'historique ont été améliorées en introduisant un nouveau verrou en lecture-écriture. Cela réduit le verrouillage entre les synchroniseurs d'historique, les trappers et les pollers proxy en utilisant un verrou de lecture partagé lors de l'accès au cache de configuration. Le nouveau verrou ne peut être verrouillé en écriture que par le synchroniseur de configuration effectuant un rechargement du cache de configuration. ### Improved performance of history syncers The performance of history syncers has been improved by introducing a new read-write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only by the configuration syncer performing a configuration cache reload. ### Amélioration des performances des synchroniseurs d'historique Les performances des synchroniseurs d'historique ont été améliorées en introduisant un nouveau verrou en lecture-écriture. Cela réduit le verrouillage entre les synchroniseurs d'historique, les trappers et les pollers proxy en utilisant un verrou de lecture partagé lors de l'accès au cache de configuration. Le nouveau verrou ne peut être verrouillé en écriture que par le synchroniseur de configuration effectuant un rechargement du cache de configuration. ##### In accepting-side log: ...failed to accept an incoming connection: from 127.0.0.1: support for TLS was not compiled in ##### Dans le journal côté serveur/proxy : ...failed to accept an incoming connection: from 127.0.0.1: support for TLS was not compiled in In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets, you may set the following specific options: | | | |--|--------| |*Host groups*|Select host groups to be displayed on the map. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove selected groups. <br>If nothing is selected in both *Host groups* and *Hosts* fields, all hosts with valid coordinates will be displayed.| |*Hosts*|Select hosts to be displayed all the map. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove selected hosts. <br>If nothing is selected in both *Host groups* and *Hosts* fields, all hosts with valid coordinates will be displayed.| |*Tags*|Specify tags to limit the number of hosts displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Initial view*|Comma-separated center coordinates and an optional zoom level to display when the widget is initially loaded in the format `<latitude>,<longitude>,<zoom>`<br>If initial zoom is specified, the Geomap widget is loaded at the given zoom level. Otherwise, initial zoom is calculated as half of the [max zoom](/manual/web_interface/frontend_sections/administration/general#geographical_maps) for the particular tile provider.<br>The initial view is ignored if the default view is set (see below).<br>Examples:<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891| Outre les paramètres qui sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets, vous pouvez définir les options spécifiques suivantes : | | | |--|--------| |*Groupes d'hôtes*|Sélectionnez les groupes d'hôtes à afficher sur la carte. Ce champ est auto-complété, donc commencer à taper le nom d'un groupe offrira une liste déroulante des groupes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer les groupes sélectionnés. <br>Si rien n'est sélectionné dans les champs *Groupes d'hôtes* et *Hôtes*, tous les hôtes avec des coordonnées valides seront affichés.| |*Hôtes*|Sélectionnez les hôtes à afficher sur toute la carte. Ce champ est auto-complété, donc commencer à taper le nom d'un hôte offrira une liste déroulante des hôtes correspondants. Faites défiler vers le bas pour sélectionner. Cliquez sur 'x' pour supprimer les hôtes sélectionnés. <br>Si rien n'est sélectionné dans les champs *Groupes d'hôtes* et *Hôtes*, tous les hôtes avec des coordonnées valides seront affichés.| |*Tags*|Spécifiez des tags pour limiter le nombre d'hôtes affichés dans le widget. Il est possible d'inclure et d'exclure des tags et des valeurs de tag spécifiques. Plusieurs conditions peuvent être définies. La correspondance des noms de tag est toujours sensible à la casse.<br>Plusieurs opérateurs sont disponibles pour chaque condition :<br>**Existe** - inclut les noms de tag spécifiés<br>**Égal** - inclut les noms de tag spécifiés et valeurs (sensible à la casse)<br>**Contient** - inclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie (correspondance de sous-chaîne, insensible à la casse)<br>**N'existe pas** - exclut les valeurs spécifiées noms de tag<br>**N'est pas égal** - exclut les noms et valeurs de tag spécifiés (sensible à la casse)<br>**Ne contient pas** - exclut les noms de tag spécifiés où les valeurs de tag contiennent la chaîne saisie ( correspondance de sous-chaîne, insensible à la casse)<br>Il existe deux types de calcul pour les conditions :<br>**Et/Ou** - toutes les conditions doivent être remplies, les conditions ayant le même nom de tag seront regroupées par la condition Ou<br >**Ou** - suffisant si une condition est remplie| |*Vue initiale*|Coordonnées du centre séparées par des virgules et un niveau de zoom facultatif à afficher lorsque le widget est initialement chargé au format `<latitude>,<longitude>,<zoom>`<br>Si le zoom initial est spécifié, le widget Géocarte est chargé au niveau de zoom donné. Sinon, le zoom initial est calculé comme la moitié du [zoom max](/manual/web_interface/frontend_sections/administration/general#geographical_maps) pour le fournisseur de tuiles particulier.<br>La vue initiale est ignorée si la vue par défaut est définie (voir ci-dessous).<br>Exemples :<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891| In addition, Zabbix provides the zabbix-selinux-policy package as part of source RPM packages for [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) and [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). This package provides a basic default policy for SELinux and makes zabbix components work out-of-the-box by allowing Zabbix to create and use sockets and enabling httpd connection to PostgreSQL (used by frontend). The source *zabbix_policy.te* file contains the following rules: module zabbix_policy 1.2; require { type zabbix_t; type zabbix_port_t; type zabbix_var_run_t; type postgresql_port_t; type httpd_t; class tcp_socket name_connect; class sock_file { create unlink }; class unix_stream_socket connectto; } #============= zabbix_t ============== allow zabbix_t self:unix_stream_socket connectto; allow zabbix_t zabbix_port_t:tcp_socket name_connect; allow zabbix_t zabbix_var_run_t:sock_file create; allow zabbix_t zabbix_var_run_t:sock_file unlink; allow httpd_t zabbix_port_t:tcp_socket name_connect; #============= httpd_t ============== allow httpd_t postgresql_port_t:tcp_socket name_connect; This package has been created to prevent users from turning off SELinux because of the configuration complexity. It contains the default policy that is sufficient to speed up Zabbix deployment and configuration. For maximum security level, it is recommended to set custom SELinux settings. De plus, Zabbix fournit le package zabbix-selinux-policy dans le cadre des packages RPM source pour [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) et [RHEL 7] (http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). Ce package fournit une politique par défaut de base pour SELinux et permet aux composants zabbix de fonctionner immédiatement en permettant à Zabbix de créer et d'utiliser des sockets et en activant la connexion httpd à PostgreSQL (utilisé par le frontend). Le fichier source *zabbix_policy.te* contient les règles suivantes : module zabbix_policy 1.2; require { type zabbix_t; type zabbix_port_t; type zabbix_var_run_t; type postgresql_port_t; type httpd_t; class tcp_socket name_connect; class sock_file { create unlink }; class unix_stream_socket connectto; } #============= zabbix_t ============== allow zabbix_t self:unix_stream_socket connectto; allow zabbix_t zabbix_port_t:tcp_socket name_connect; allow zabbix_t zabbix_var_run_t:sock_file create; allow zabbix_t zabbix_var_run_t:sock_file unlink; allow httpd_t zabbix_port_t:tcp_socket name_connect; #============= httpd_t ============== allow httpd_t postgresql_port_t:tcp_socket name_connect; Ce package a été créé pour empêcher les utilisateurs de désactiver SELinux en raison de la complexité de la configuration. Il contient la politique par défaut suffisante pour accélérer le déploiement et la configuration de Zabbix. Pour un niveau de sécurité maximal, il est recommandé de définir des paramètres SELinux personnalisés. In addition, Zabbix provides the zabbix-selinux-policy package as part of source RPM packages for [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) and [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). This package provides a basic default policy for SELinux and makes zabbix components work out-of-the-box by allowing Zabbix to create and use sockets and enabling httpd connection to PostgreSQL (used by frontend). The source *zabbix_policy.te* file contains the following rules: module zabbix_policy 1.2; require { type zabbix_t; type zabbix_port_t; type zabbix_var_run_t; type postgresql_port_t; type httpd_t; class tcp_socket name_connect; class sock_file { create unlink }; class unix_stream_socket connectto; } #============= zabbix_t ============== allow zabbix_t self:unix_stream_socket connectto; allow zabbix_t zabbix_port_t:tcp_socket name_connect; allow zabbix_t zabbix_var_run_t:sock_file create; allow zabbix_t zabbix_var_run_t:sock_file unlink; allow httpd_t zabbix_port_t:tcp_socket name_connect; #============= httpd_t ============== allow httpd_t postgresql_port_t:tcp_socket name_connect; This package has been created to prevent users from turning off SELinux because of the configuration complexity. It contains the default policy that is sufficient to speed up Zabbix deployment and configuration. For maximum security level, it is recommended to set custom SELinux settings. De plus, Zabbix fournit le package zabbix-selinux-policy dans le cadre des packages RPM source pour [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) et [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). Ce package fournit une politique par défaut de base pour SELinux et permet aux composants zabbix de fonctionner immédiatement en permettant à Zabbix de créer et d'utiliser des sockets et en activant la connexion httpd à PostgreSQL (utilisé par le frontend). Le fichier source *zabbix_policy.te* contient les règles suivantes : module zabbix_policy 1.2; require { type zabbix_t; type zabbix_port_t; type zabbix_var_run_t; type postgresql_port_t; type httpd_t; class tcp_socket name_connect; class sock_file { create unlink }; class unix_stream_socket connectto; } #============= zabbix_t ============== allow zabbix_t self:unix_stream_socket connectto; allow zabbix_t zabbix_port_t:tcp_socket name_connect; allow zabbix_t zabbix_var_run_t:sock_file create; allow zabbix_t zabbix_var_run_t:sock_file unlink; allow httpd_t zabbix_port_t:tcp_socket name_connect; #============= httpd_t ============== allow httpd_t postgresql_port_t:tcp_socket name_connect; Ce package a été créé pour empêcher les utilisateurs de désactiver SELinux en raison de la complexité de la configuration. Il contient la politique par défaut suffisante pour accélérer le déploiement et la configuration de Zabbix. Pour un niveau de sécurité maximal, il est recommandé de définir des paramètres SELinux personnalisés. ##### In connecting-side log: Linux: ...In zbx_tls_init_child() ...OpenSSL library (version OpenSSL 1.1.1 11 Sep 2018) initialized ... ...In zbx_tls_connect(): psk_identity:"PSK test sender" ...End of zbx_tls_connect():FAIL error:'connection closed by peer' ...send value error: TCP successful, cannot establish TLS to [[localhost]:10051]: connection closed by peer Windows: ...OpenSSL library (version OpenSSL 1.1.1a 20 Nov 2018) initialized ... ...In zbx_tls_connect(): psk_identity:"PSK test sender" ...zbx_psk_client_cb() requested PSK identity "PSK test sender" ...End of zbx_tls_connect():FAIL error:'SSL_connect() I/O error: [0x00000000] The operation completed successfully.' ...send value error: TCP successful, cannot establish TLS to [[192.168.1.2]:10051]: SSL_connect() I/O error: [0x00000000] The operation completed successfully. ##### Dans le journal côté connexion : Linux : ...In zbx_tls_init_child() ...OpenSSL library (version OpenSSL 1.1.1 11 Sep 2018) initialized ... ...In zbx_tls_connect(): psk_identity:"PSK test sender" ...End of zbx_tls_connect():FAIL error:'connection closed by peer' ...send value error: TCP successful, cannot establish TLS to [[localhost]:10051]: connection closed by peer Windows : ...OpenSSL library (version OpenSSL 1.1.1a 20 Nov 2018) initialized ... ...In zbx_tls_connect(): psk_identity:"PSK test sender" ...zbx_psk_client_cb() requested PSK identity "PSK test sender" ...End of zbx_tls_connect():FAIL error:'SSL_connect() I/O error: [0x00000000] The operation completed successfully.' ...send value error: TCP successful, cannot establish TLS to [[192.168.1.2]:10051]: SSL_connect() I/O error: [0x00000000] The operation completed successfully. #### Incorrect request method parameter in items The request method parameter, used only in HTTP checks, may be incorrectly set to '1', a non-default value for all items as a result of upgrade from a pre-4.0 Zabbix version. For details on how to fix this situation, see [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308). #### Paramètre de méthode de requête incorrect dans les éléments Le paramètre de méthode de requête, utilisé uniquement dans les vérifications HTTP, peut être incorrectement défini sur "1", une valeur autre que la valeur par défaut pour tous les éléments à la suite d'une mise à niveau à partir d'une version antérieure à la version 4.0 de Zabbix. Pour plus de détails sur la façon de résoudre ce problème, consultez [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308). #### Indexed macros The indexed macro syntax of {MACRO**<1-9>**} works only in the context of **trigger expressions**. It can be used to reference hosts or functions in the order in which they appear in the expression. Macros like {HOST.IP1}, {HOST.IP2}, {HOST.IP3} will resolve to the IP of the first, second, and third host in the trigger expression (providing the trigger expression contains those hosts). Macros like {FUNCTION.VALUE1}, {FUNCTION.VALUE2}, {FUNCTION.VALUE3} will resolve to the value of the first, second, and third item-based function in the trigger expression at the time of the event (providing the trigger expression contains those functions). Additionally the {HOST.HOST<1-9>} macro is also supported within the `{?func(/host/key,param)}` expression macro in **graph names**. For example, `{?func(/{HOST.HOST2}/key,param)}` in the graph name will refer to the host of the second item in the graph. ::: notewarning Indexed macros will not resolve in any other context, except the two cases mentioned here. For other contexts, use macros **without** index (i. e.{HOST.HOST}, {HOST.IP}, etc) instead. ::: #### Macros indexées La syntaxe de macro indexée de {MACRO**<1-9\>**} ne fonctionne que dans le contexte des **expressions de déclenchement**. Il peut être utilisé pour référencer des hôtes ou des fonctions dans l'ordre dans lequel ils apparaissent dans l'expression. Les macros telles que {HOST.IP1}, {HOST.IP2}, {HOST.IP3} résoudront l'adresse IP du premier, du deuxième et du troisième hôte dans l'expression du déclencheur (à condition que l'expression du déclencheur contienne ces hôtes). Les macros telles que {FUNCTION.VALUE1}, {FUNCTION.VALUE2}, {FUNCTION.VALUE3} résoudront la valeur de la première, de la deuxième et de la troisième fonction basée sur l'élément dans l'expression du déclencheur au moment de l'événement (à condition que le déclencheur expression contient ces fonctions). De plus, la macro {HOST.HOST<1-9>} est également prise en charge dans la macro d'expression `{?func(/host/key,param)}` dans les **noms de graphiquess**. Par exemple, `{?func(/{HOST.HOST2}/key,param)}` dans le nom du graphique fera référence à l'hôte du deuxième élément du graphique. ::: notewarning Les macros indexées ne seront résolues dans aucun autre contexte, à l'exception des deux cas mentionnés ici. Pour les autres contextes, utilisez plutôt des macros **sans** index (c'est-à-dire {HOST.HOST}, {HOST.IP}, etc.). ::: #### Index lookup caching When a dynamic index item is requested, Zabbix retrieves and caches whole SNMP table under base OID for index, even if a match would be found sooner. This is done in case another item would refer to the same base OID later - Zabbix would look up index in the cache, instead of querying the monitored host again. Note that each poller process uses separate cache. In all subsequent value retrieval operations only the found index is verified. If it has not changed, value is requested. If it has changed, cache is rebuilt - each poller that encounters a changed index walks the index SNMP table again. #### Mise en cache de la recherche d'index Lorsqu'un élément d'index dynamique est demandé, Zabbix récupère et met en cache toute la table SNMP sous l'OID de base pour l'indexation, même si une correspondance a été trouvée plus tôt. Ceci est fait dans le cas où un autre élément se rapporterait au même OID de base plus tard - Zabbix rechercherait l'index dans le cache, au lieu d'interroger à nouveau l'hôte surveillé. Notez que chaque processus poller utilise un cache distinct. Dans toutes les opérations de récupération de valeur ultérieures, seul l'index trouvé est vérifié. Si cela n'a pas changé, la valeur est demandée. Si elle a été modifiée, le cache est reconstruit. Chaque poller qui rencontre un index modifié parcourt à nouveau la table d'index SNMP. ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [EXAMPLES](#lbAF) [SEE ALSO](#lbAG) ------------------------------------------------------------------------ This document was created on: 21:23:35 GMT, March 18, 2020 ## Index [NOM](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [EXEMPLES](#lbAF) [VOIR EGALEMENT](#lbAG) ------------------------------------------------------------------------ Ce document a été créé le : 21:23:35 GMT, March 18, 2020 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [EXAMPLES](#lbAG) [SEE ALSO](#lbAH) [AUTHOR](#lbAI) ------------------------------------------------------------------------ This document was created on: 08:42:29 GMT, June 11, 2021 ## Index [NOM](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [EXEMPLES](#lbAG) [VOIR EGALEMENT](#lbAH) [AUTEUR](#lbAI) ------------------------------------------------------------------------ Ce document a été créé le : 08:42:29 GMT, June 11, 2021 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [FILES](#lbAG) [SEE ALSO](#lbAH) [AUTHOR](#lbAI) ------------------------------------------------------------------------ This document was created on: 14:07:57 GMT, November 22, 2021 ## Index [NOM](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [FICHIERS](#lbAG) [VOIR ÉGALEMENT](#lbAH) [AUTEUR](#lbAI) ------------------------------------------------------------------------ Ce document a été créé le : 22 Novembre 2021 à 14:07:57 GMT ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created on: 16:12:22 GMT, September 04, 2020 ## Index [NOM](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FICHIERS](#lbAH) [VOIR EGALEMENT](#lbAI) [AUTEUR](#lbAJ) ------------------------------------------------------------------------ Ce document a été créé le : 16:12:22 GMT, September 04, 2020 ## Index [NAME](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FILES](#lbAH) [SEE ALSO](#lbAI) [AUTHOR](#lbAJ) ------------------------------------------------------------------------ This document was created on: 20:50:13 GMT, November 22, 2021 ## Index [NOM](#lbAB) [SYNOPSIS](#lbAC) [DESCRIPTION](#lbAD) [OPTIONS](#lbAE) [](#lbAF) [](#lbAG) [FICHIERS](#lbAH) [VOIR EGALEMENT](#lbAI) [AUTEUR](#lbAJ) ------------------------------------------------------------------------ Ce document a été créé le : 22 Novembre 2021 à 20:50:13 GMT #### Individual migration of history tables * Prepare directories for Data Pump for each history table. Data Pump must have read and write permissions to these directories. Example: ``` {.bash} mkdir -pv /export/history /export/history_uint /export/history_str /export/history_log /export/history_text chown -R oracle:oracle /export ``` * Create a directory object and grant read and write permissions to this object to the user used for Zabbix authentication ('zabbix' in the example below). Under *sysdba* role, run: ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; create directory history_uint as '/export/history_uint'; grant read,write on directory history_uint to zabbix; create directory history_str as '/export/history_str'; grant read,write on directory history_str to zabbix; create directory history_log as '/export/history_log'; grant read,write on directory history_log to zabbix; create directory history_text as '/export/history_text'; grant read,write on directory history_text to zabbix; ``` * Export and import each table. Replace N with the desired thread count. ``` {.bash} expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old REMAP_TABLE=history_old:history data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old REMAP_TABLE=history_uint_old:history_uint data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old REMAP_TABLE=history_str_old:history_str data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old REMAP_TABLE=history_log_old:history_log data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old REMAP_TABLE=history_text_old:history_text data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ``` * Follow [post-migration instructions](#post-migration) to drop the old tables. #### Migration individuelle des tables d'historique * Préparer des répertoires pour Data Pump pour chaque table d'historique. Data Pump doit disposer d'autorisations de lecture et d'écriture sur ces répertoires. Exemple : ``` {.bash} mkdir -pv /export/history /export/history_uint /export/history_str /export/history_log /export/history_text chown -R oracle:oracle /export ``` * Créer un objet répertoire et accorder des autorisations de lecture et d'écriture sur cet objet à l'utilisateur utilisé pour l'authentification Zabbix ("zabbix" dans l'exemple ci-dessous). Sous le rôle *sysdba*, exécuter : ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; create directory history_uint as '/export/history_uint'; grant read,write on directory history_uint to zabbix; create directory history_str as '/export/history_str'; grant read,write on directory history_str to zabbix; create directory history_log as '/export/history_log'; grant read,write on directory history_log to zabbix; create directory history_text as '/export/history_text'; grant read,write on directory history_text to zabbix; ``` * Exporter et importer chaque table. Remplacer N par le nombre de thread souhaité. ``` {.bash} expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old REMAP_TABLE=history_old:history data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old REMAP_TABLE=history_uint_old:history_uint data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old REMAP_TABLE=history_str_old:history_str data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old REMAP_TABLE=history_log_old:history_log data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old REMAP_TABLE=history_text_old:history_text data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ``` * Suivre les [instructions post-migration](#post-migration) pour supprimer les anciennes tables. ### Informational ### Informel ##### Informix Standard Informix utility **onstat** can be used for monitoring of virtually every aspect of Informix database. Also, Zabbix can retrieve information provided by Informix SNMP agent. ##### Informix L'utilitaire standard Informix **onstat** peut être utilisé pour surveiller pratiquement tous les aspects de la base de données Informix. De plus, Zabbix peut extraire les informations fournies par l'agent SNMP Informix. ##### Installation After this is done use the following command to install Zabbix agent as Windows service: C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i Now you should be able to configure "Zabbix agent" service normally as any other Windows service. See [more details](/manual/appendix/install/windows_agent#installing_agent_as_windows_service) on installing and running Zabbix agent on Windows. ##### Installation Une fois que les étapes précédentes sont réalisées, exécutez la commande suivante pour installer l’agent Zabbix en tant que service : C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i Maintenant vous devriez être capable de configurer le service “Agent Zabbix” comme les autres services Windows. Voir [plus de details](/manual/appendix/install/windows_agent#installing_agent_as_windows_service) sur l'installation et l'exécution de l'agent Zabbix sur Windows. #### Installation from packages It has been observed that it is impossible to install a specific frontend version by running, e.g.: yum install -v zabbix-web-mysql-scl-5.0.0 As a workaround to this issue, if you wish to install a specific frontend version, specify version for all components, e.g.: yum install zabbix-web-mysql-scl-5.0.0 zabbix-apache-conf-scl-5.0.0 zabbix-web-5.0.0 zabbix-web-deps-scl-5.0.0 #### Installation à partir de packages Il a été observé qu'il est impossible d'installer une version spécifique du frontend en exécutant, par exemple : yum install -v zabbix-web-mysql-scl-5.0.0 Pour contourner ce problème, si vous souhaitez installer une version d'interface spécifique, spécifiez la version de tous les composants, par exemple : yum install zabbix-web-mysql-scl-5.0.0 zabbix-apache-conf-scl-5.0.0 zabbix-web-5.0.0 zabbix-web-deps-scl-5.0.0 #### Installation Please always read the installation manual for a particular module. It is recommended to install new modules one by one to catch failures easily. Just before you install a module: - Make sure you have downloaded the module from a trusted source. Installation of harmful code may lead to consequences, such as data loss - Different versions of the same module (same ID) can be installed in parallel, but only a single version can be enabled at once Steps to install a module: - Unpack your module within its own folder in the `modules` folder of the Zabbix frontend - Ensure that your module folder contains at least the manifest.json file - Navigate to [Module administration](/manual/web_interface/frontend_sections/administration/general#modules) and click the *Scan directory* button - New module will appear in the list along with its version, author, description and status - Enable module by clicking on its status Troubleshooting: |Problem|Solution| |---------|----------------------------------------| |*Module did not appear in the list*|Make sure that the manifest.json file exists in `modules/your-module/` folder of the Zabbix frontend. If it does that means the module does not suit the current Zabbix version. If manifest.json file does not exist, you have probably unpacked in the wrong directory.| |*Frontend crashed*|The module code is not compatible with the current Zabbix version or server configuration. Please delete module files and reload the frontend. You'll see a notice that some modules are absent. Go to [Module administration](/manual/web_interface/frontend_sections/administration/general#modules) and click *Scan directory* again to remove non-existent modules from the database.| |*Error message about identical namespace, ID or actions appears*|New module tried to register a namespace, ID or actions which are already registered by other enabled modules. Disable the conflicting module (mentioned in error message) prior to enabling the new one.| |*Technical error messages appear*|Report errors to the developer of the module.| #### Installation Veuillez toujours lire le manuel d'installation d'un module particulier. Il est recommandé d'installer les nouveaux modules un par un pour gérer facilement les pannes. Juste avant d'installer un module : - Assurez-vous d'avoir téléchargé le module à partir d'une source fiable. L'installation de code nuisible peut entraîner des conséquences, telles que la perte de données - Différentes versions d'un même module (même ID) peuvent être installées en parallèle, mais une seule version peut être activée à la fois Étapes pour installer un module : - Décompressez votre module dans son propre dossier dans le dossier `modules` de l'interface Zabbix - Assurez-vous que votre dossier de module contient au moins le fichier manifest.json - Accédez à l'[Administration du module](/manual/web_interface/frontend_sections/administration/general#modules) et cliquez sur le bouton *Analyser le répertoire* - Le nouveau module apparaîtra dans la liste avec sa version, son auteur, sa description et son statut - Activer le module en cliquant sur son statut Dépannage |Problème|Solution|: |Problem|Solution| |---------|----------------------------------------| |*Le module n'apparait pas dans la liste*|Assurez-vous que le fichier manifest.json existe dans le dossier `modules/your-module/` de l'interface Zabbix. Si c'est le cas, cela signifie que le module ne convient pas à la version actuelle de Zabbix. Si le fichier manifest.json n'existe pas, vous avez probablement décompressé dans le mauvais répertoire.| |*L'interface s'est crashée*|Le code du module n'est pas compatible avec la version actuelle de Zabbix ou la configuration du serveur. Veuillez supprimer les fichiers du module et recharger l'interface. Vous verrez un avis indiquant que certains modules sont absents. Allez dans l'[Administration du module](/manual/web_interface/frontend_sections/administration/general#modules) et cliquez une nouvelle fois sur le bouton *Analyser le répertoire* pour supprimer les modules inexistants de la base de données.| |*Un message d'erreur concernant un namespadce, un ID ou des actions identiques s'affiche*|Le nouveau module a essayé d'enregistrer un namespace, un ID ou des actions qui sont déjà enregistrés par d'autres modules activés. Désactivez le module en conflit (mentionné dans le message d'erreur) avant d'activer le nouveau.| |*Des messages d'erreur technique apparaissent*|Signalez les erreurs au développeur du module.| ##### Installation See the [package installation](/manual/installation/install_from_packages) section for instructions on how to install Zabbix agent as package. Alternatively see instructions for [manual installation](/manual/installation/install#installing_zabbix_daemons) if you do not want to use packages. ::: noteimportant In general, 32bit Zabbix agents will work on 64bit systems, but may fail in some cases. ::: ##### Installation Voir la section [installation des packages](/manual/installation/install_from_packages) pour voir les instructions d’installation de l’agent Zabbix sous forme de package. Sinon référez-vous aux instructions d’[installation manuelle](/manual/installation/install#installing_zabbix_daemons) si vous ne voulez pas utiliser de packages. ::: noteimportant En général, les agents Zabbix 32bits fonctionnent sur les systèmes 64bits, mais cela peut ne pas fonctionner dans certains cas. ::: ||Installation size<br>(dedicated servers/on-prem/virtual/clouds)|<|<|<|Containers base|Large/very large installations<br>(dedicated servers/on-prem/virtual/clouds)|<|<|<| |--|-|-|-|-|-|-|-|-|-| | |Small|Medium|Large|Very large|All|Database|Server|Frontend|Proxy| |**Hardware examples**|<|<|<|<|<|<|<|<|<| |*CPU (2018+ m.y.)*| |2 core| | | | |8 core|4+ core^**2**^|4 core| |*CPU High clock frequency (2018+ m.y.)*|1 core|8 core| |16+ core| |8+ core| | | | |*RAM*|1 GB|2 GB|16 GB|64+ GB| |32+ GB|16 GB|8+ GB^**2**^|4 GB| |*NUMA (check/setup if >2 sockets or >8 cores VM)*| | |+|+| |+|+| | | |*Storage/SAN*| | |RAID|vRAID| |vRAID| | | | |*Flash storage/SAN*| | |+|vRAID| |vRAID| | | | |*SSD write-intensive or mixed usage*|+|+|+| | | | | | | |*NVME*| | |+|+| |+| | | | |*Any storage for OS and logs*| | | | | | |+|+|+| |*Hosts*|100|500|>1000|>10000| | | | | | |**Database examples**|<|<|<|<|<|<|<|<|<| |*Oracle Database*| | |+|+|+|+| | | | |*Percona Server*|+|+|+|+|+|+| | | | |*MariaDB Enterprise/Community Server*|+|+|+|+|+|+| | | | |*MySQL Community Edition/Commercial*|+|+|+|+|+|+| | | | |*PostgreSQL/PostgreSQL Pro/EnterpriseDB*|+|+|+|+|+|+| | | | |*TimescaleDB*|+|+|+|+|+|+|| | | |**Filesystem examples**|<|<|<|<|<|<|<|<|<| |*BTRFS*|+|+| | | | | | | | |*EXT4*|+|+|+|+| |+|+|+|+| |*XFS*|+|+|+|+| |+|+|+|+| |*ZFS*| | |+|+| |+| | | | |**Networking examples**|<|<|<|<|<|<|<|<|<| |*Synchronous cluster (RTT/Latency)*| | | | | |Single DC| | | | |*Asynchronous replication (RTT/Latency)*| | | | | |<5 seconds| | | | |*NIC Teaming/Bonding*| | |Recommended|Recommended| |Recommended|Recommended|Recommended| | |*Bandwidth*|10mbits/sec+|100mbits/sec+|100mbits/sec+|1000mbits/sec+| |1000mbits/sec+|1000mbits/sec+|1000mbits/sec+|1mbit/sec+^**3**^| ^**1**^ For adoption and testing<br> ^**2**^ According to the amount of users<br> ^**3**^ Depending on the workload and requirements ::: noteclassic Actual configuration depends on the number of active items and refresh rates very much (see [database size](/manual/installation/requirements#Database_size) section of this page for details). It is highly recommended to run the database on a separate box for large installations. ::: ||Taille de l'installation<br>(serveurs dédiés/on-prem/virtuel/clouds)|<|<|<|Base de conteneurs|Grandes/très grandes installations<br>(serveurs dédiés/on-prem/virtuel/clouds)|<|<|<| |--|-|-|-|-|-|-|-|-|-| | |Petit|Moyen|Grand|Très grand|Tous|Base de données|Serveur|Frontend|Proxy| |**Exemples de matériel**|<|<|<|<|<|<|<|<|<| |*CPU (2018+ m.y.)*| |2 core| | | | |8 core|4+ core^**2**^|4 core| |*CPU High clock frequency (2018+ m.y.)*|1 core|8 core| |16+ core| |8+ core| | | | |*RAM*|1 GB|2 GB|16 GB|64+ GB| |32+ GB|16 GB|8+ GB^**2**^|4 GB| |*NUMA (check/setup if >2 sockets or >8 cores VM)*| | |+|+| |+|+| | | |*Storage/SAN*| | |RAID|vRAID| |vRAID| | | | |*Flash storage/SAN*| | |+|vRAID| |vRAID| | | | |*SSD utilisation intensive en écriture ou mixte*|+|+|+| | | | | | | |*NVME*| | |+|+| |+| | | | |*Tout stockage pour le système d'exploitation et les journaux*| | | | | | |+|+|+| |*Hôtes*|100|500|>1000|>10000| | | | | | |**Exemples de base de données**|<|<|<|<|<|<|<|<|<| |*Base de données Oracle*| | |+|+|+|+| | | | |*Percona Server*|+|+|+|+|+|+| | | | |*MariaDB Enterprise/Community Server*|+|+|+|+|+|+| | | | |*MySQL Community Edition/Commercial*|+|+|+|+|+|+| | | | |*PostgreSQL/PostgreSQL Pro/EnterpriseDB*|+|+|+|+|+|+| | | | |*TimescaleDB*|+|+|+|+|+|+|| | | |**Exemples de systèmes de fichiers**|<|<|<|<|<|<|<|<|<| |*BTRFS*|+|+| | | | | | | | |*EXT4*|+|+|+|+| |+|+|+|+| |*XFS*|+|+|+|+| |+|+|+|+| |*ZFS*| | |+|+| |+| | | | |**Exemples de mise en réseau**|<|<|<|<|<|<|<|<|<| |*Cluster synchrone (RTT/Latency)*| | | | | |Single DC| | | | |*Réplication asynchrone (RTT/Latency)*| | | | | |<5 seconds| | | | |*NIC Teaming/Bonding*| | |Recommandé|Recommandé| |Recommandé|Recommandé|Recommandé| | |*Bande passante*|10mbits/sec+|100mbits/sec+|100mbits/sec+|1000mbits/sec+| |1000mbits/sec+|1000mbits/sec+|1000mbits/sec+|1mbit/sec+^**3**^| ^**1**^ Pour adoption et test<br> ^**2**^ Selon le nombre d'utilisateurs<br> ^**3**^En fonction de la charge de travail et des besoins ::: noteclassic La configuration réelle dépend beaucoup du nombre d'éléments actifs et des taux de rafraîchissement (voir la section [taille de la base de données](/manual/installation/requirements#Database_size) de cette page pour plus de détails). Il est fortement recommandé d'exécuter la base de données sur un boîtier séparé pour les grandes installations. ::: #### Installation steps To install, double-click the downloaded MSI file.   Accept the license to proceed to the next step.  Specify the following parameters. |Parameter|Description| |--|--------| |*Host name*|Specify host name.| |*Zabbix server IP/DNS*|Specify IP/DNS of Zabbix server.| |*Agent listen port*|Specify agent listen port (10050 by default).| |*Server or Proxy for active checks*|Specify IP/DNS of Zabbix server/proxy for active agent checks.| |*Enable PSK*|Mark the checkbox to enable TLS support via pre-shared keys.| |*Add agent location to the PATH*|Add agent location to the PATH variable.|  Enter pre-shared key identity and value. This step is only available if you checked *Enable PSK* in the previous step.  Select Zabbix components to install - [Zabbix agent daemon](/manual/concepts/agent), [Zabbix sender](/manual/concepts/sender), [Zabbix get](/manual/concepts/get).  Zabbix components along with the configuration file will be installed in a *Zabbix Agent* folder in Program Files. zabbix\_agentd.exe will be set up as Windows service with automatic startup.  #### Étapes d'installation Pour installer, double-cliquez sur le fichier MSI téléchargé.   Acceptez la licence pour passer à l'étape suivante.  Spécifiez les paramètres suivants. |Paramètre|Description| |--|--------| |*Host name*|Spécifiez le nom d'hôte.| |*Zabbix server IP/DNS*|Spécifiez l'IP/DNS du serveur Zabbix.| |*Agent listen port*|Spécifiez le port d'écoute de l'agent (10050 par défaut).| |*Server or Proxy for active checks*|Spécifiez l'IP/DNS du serveur/proxy Zabbix pour les vérifications actives de l'agent.| |*Enable PSK*|Cochez la case pour activer la prise en charge TLS via des clés pré-partagées.| |*Add agent location to the PATH*|Ajouter l'emplacement de l'agent à la variable PATH.|  Entrez l'identité et la valeur de la clé pré-partagée. Cette étape n'est disponible que si vous avez coché *Enable PSK* à l'étape précédente.  Sélectionnez les composants Zabbix à installer - [Zabbix agent daemon](/manual/concepts/agent), [Zabbix sender](/manual/concepts/sender), [Zabbix get](/manual/concepts/get).  Les composants Zabbix ainsi que le fichier de configuration seront installés dans un dossier * Zabbix Agent * dans Program Files. zabbix\_agentd.exe sera configuré en tant que service Windows avec démarrage automatique.  #### Install If installing Zabbix from sources, download the configuration file and place it under conf/ in the webserver HTML documents subdirectory where you copied Zabbix PHP files to. {width="550"} {width="350"} ::: notetip Providing the webserver user has write access to conf/ directory the configuration file would be saved automatically and it would be possible to proceed to the next step right away. ::: Finish the installation. {width="550"} #### Installation Si vous installez Zabbix à partir des sources, téléchargez le fichier de configuration et placez-le sous conf/ dans le sous-répertoire des documents HTML du serveur Web dans lequel vous avez copié les fichiers PHP de Zabbix. {width="550"} {width="350"} ::: notetip Si l'utilisateur du serveur Web dispose d'un accès en écriture au répertoire conf/, le fichier de configuration sera enregistré automatiquement et il sera possible de passer immédiatement à l'étape suivante. ::: Terminez l'installation. {width="550"} #### Installing agent as Windows service To install a single instance of Zabbix agent with the default configuration file `c:\zabbix_agentd.conf`: zabbix_agentd.exe --install ::: noteimportant On a 64-bit system, a 64-bit Zabbix agent version is required for all checks related to running 64-bit processes to work correctly. ::: If you wish to use a configuration file other than `c:\zabbix_agentd.conf`, you should use the following command for service installation: zabbix_agentd.exe --config <your_configuration_file> --install A full path to the configuration file should be specified. Multiple instances of Zabbix agent can be installed as services like this: zabbix_agentd.exe --config <configuration_file_for_instance_1> --install --multiple-agents zabbix_agentd.exe --config <configuration_file_for_instance_2> --install --multiple-agents ... zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents The installed service should now be visible in Control Panel. #### Installation de l'agent en tant que service Windows Pour installer une seule instance de l'agent Zabbix avec la valeur par défaut du fichier de configuration `c:\zabbix_agentd.conf` : zabbix_agentd.exe --install ::: note importante Sur un système 64 bits, une version 64 bits de l'agent Zabbix est requise pour que toutes les vérifications liées à l'exécution de processus 64 bits fonctionnent correctement. ::: Si vous souhaitez utiliser un fichier de configuration autre que `c:\zabbix_agentd.conf`, vous devez utiliser la commande suivante pour la mise en place des services : zabbix_agentd.exe --config <votre_fichier_de_configuration> --install Un chemin d'accès complet au fichier de configuration doit être spécifié. Plusieurs instances de l'agent Zabbix peuvent être installées en tant que services comme ceci : zabbix_agentd.exe --config <fichier_de_configuration_pour_instance_1> --install --multiple-agents zabbix_agentd.exe --config <fichier_de_configuration_pour_instance_2> --install --multiple-agents ... zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents Le service installé devrait maintenant être visible dans le Panneau de configuration. #### Installing agent The agent can be installed using the graphical user interface or from the command line, for example: sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target / Make sure to use the correct Zabbix package version in the command. It must match the name of the downloaded package. #### Installation de l'agent L'agent peut être installé à l'aide de l'interface utilisateur graphique ou à partir de la ligne de commande, par exemple : sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target / Assurez-vous d'utiliser la bonne version du package Zabbix dans la commande. Il doit correspondre au nom du package téléchargé. ### Installing debuginfo packages :::noteclassic Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5. ::: To enable debuginfo repository, edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository. [zabbix-debuginfo] name=Zabbix Official Repository debuginfo - $basearch baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/ enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 gpgcheck=1 This will allow you to install the zabbix-debuginfo package. # yum install zabbix-debuginfo This single package contains debug information for all binary Zabbix components. ### Installation des packages debuginfo :::noteclassic Les packages Debuginfo sont actuellement disponibles pour les versions 7, 6 et 5 de RHEL/CentOS. ::: Pour activer le dépôt debuginfo, modifiez le fichier */etc/yum.repos.d/zabbix.repo*. Remplacez `enabled=0` par `enabled=1` pour le référentiel zabbix-debuginfo. [zabbix-debuginfo] name=Zabbix Official Repository debuginfo - $basearch baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/ enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 gpgcheck=1 Cela vous permettra d'installer le package zabbix-debuginfo. # yum install zabbix-debuginfo Ce package unique contient des informations de débogage pour tous les composants binaires Zabbix. ##### Installing frontend Please see [Web interface installation](/manual/installation/frontend) page for information about Zabbix frontend installation wizard. ##### Installation de l'interface Veuillez consulter la page [Installation de l'interface Web](/manual/installation/frontend) pour plus d'informations sur l'assistant d'installation du frontend Zabbix. #### Installing locales To list all installed languages, run: locale -a If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset. Now, run: locale-gen Restart the web server. The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear. #### Installation des paramètres régionaux Pour lister toutes les langues installées, exécutez : locale -a Si certaines langues nécessaires ne sont pas répertoriées, ouvrez le fichier */etc/locale.gen* et décommentez les paramètres régionaux requis. Étant donné que Zabbix utilise l'encodage UTF-8, vous devez sélectionner des paramètres régionaux avec le jeu de caractères UTF-8. Maintenant, exécutez : locale-gen Redémarrez le serveur Web. Les paramètres régionaux devraient maintenant être installées. Il peut être nécessaire de recharger la page du frontal Zabbix dans le navigateur en utilisant Ctrl + F5 pour que de nouvelles langues apparaissent. #### Installing MinGW Compiler 1\. Download MinGW-w64 with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2. Extract and move to *c:\\mingw*\ 3. Setup environmental variable @echo off set PATH=%PATH%;c:\mingw\bin cmd When compiling use Windows prompt instead of MSYS terminal provided by MinGW #### Installation du compilateur MinGW 1\. Télécharger MinGW-w64 avec SJLJ (set jump/long jump) Gestion des exceptions et threads Windows (par exemple *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2\. Extraire et déplacer vers *c:\\mingw*\ 3\. Configurer la variable d'environnement @echo off set PATH=%PATH%;c:\mingw\bin cmd Lors de la compilation, utilisez l'invite Windows au lieu du terminal MSYS fourni par MinGW. #### Installing Zabbix If installing Zabbix directly from [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), translation files should be generated manually. To generate translation files, run: make gettext locale/make_mo.sh This step is not needed when installing Zabbix from packages or source tar.gz files. #### Installer Zabbix Si vous installez Zabbix directement depuis le [repository git Zabbix](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), les fichiers de traduction doivent être générés manuellement. Pour générer des fichiers de traduction, exécutez : make gettext locale/make_mo.sh Cette étape n'est pas nécessaire lors de l'installation de Zabbix à partir de packages ou des fichiers source tar.gz. ### Integer history The integer history object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|integer|Received value.| ### Historique des entiers L'objet d'historique d'entier a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Heure à laquelle cette valeur a été reçue.| |itemid|string|ID de l'élément associé.| |ns|integer|Nanosecondes lorsque la valeur a été reçue.| |value|integer|Valeur reçue.| ### Integer trend The integer trend object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Timestamp of an hour for which the value was calculated. E. g. timestamp of 04:00:00 means values calculated for period 04:00:00-04:59:59.| |itemid|integer|ID of the related item.| |num|integer|Number of values that were available for the hour.| |value\_min|integer|Hourly minimum value.| |value\_avg|integer|Hourly average value.| |value\_max|integer|Hourly maximum value.| ### Tendance integer L'objet de tendance integer a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Horodatage d'une heure pour laquelle la valeur a été calculée. Par exemple. l'horodatage de 04:00:00 signifie des valeurs calculées pour la période 04:00:00-04:59:59.| |itemid|integer|ID de l'élément connexe.| |num|integer|Nombre de valeurs disponibles pour l'heure.| |value\_min|integer|Valeur horaire minimum.| |value\_avg|integer|Valeur horaire moyenne.| |value\_max|integer|Valeur horaire maximum.| #### Integrations The following integrations are available allowing to use predefined webhook media types for pushing Zabbix notifications to: - [brevis.one](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/brevis.one/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Discord](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/discord/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Express.ms messenger](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/express.ms/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Github issues](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/github/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [GLPi](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/glpi/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [iLert](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/ilert/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [iTop](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/itop/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Jira](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Jira Service Desk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [ManageEngine ServiceDesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/manageengine_servicedesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Mattermost](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/mattermost/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Microsoft Teams](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/msteams/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Opsgenie](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/opsgenie/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [OTRS](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/otrs/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Pagerduty](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pagerduty/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Pushover](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pushover/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Redmine](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/redmine/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Rocket.Chat](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/rocketchat/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [ServiceNow](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/servicenow/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SIGNL4](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/signl4/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Slack](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/slack/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SolarWinds](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/solarwinds/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SysAid](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/sysaid/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Telegram](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/telegram/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [TOPdesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/topdesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [VictorOps](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/victorops/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Zammad](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/zammad/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Zendesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/zendesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) ::: notetip In addition to the services listed here, Zabbix can be integrated with **Spiceworks** (no webhook is required). To convert Zabbix notifications into Spiceworks tickets, create an [email media type](/manual/config/notifications/media/email) and enter Spiceworks helpdesk email address (e.g. help\@zabbix.on.spiceworks.com) in the profile settings of a designated Zabbix user. ::: #### Intégrations Les intégrations suivantes sont disponibles, permettant d'utiliser des types de média Webhook prédéfinis pour envoyer les notifications Zabbix à : - [brevis.one](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/brevis.one/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Discord](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/discord/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Express.ms messenger](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/express.ms/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Github issues](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/github/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [GLPi](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/glpi/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [iLert](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/ilert/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [iTop](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/itop/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Jira](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Jira Service Desk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [ManageEngine ServiceDesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/manageengine_servicedesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Mattermost](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/mattermost/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Microsoft Teams](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/msteams/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Opsgenie](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/opsgenie/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [OTRS](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/otrs/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Pagerduty](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pagerduty/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Pushover](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pushover/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Redmine](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/redmine/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Rocket.Chat](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/rocketchat/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [ServiceNow](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/servicenow/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SIGNL4](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/signl4/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Slack](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/slack/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SolarWinds](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/solarwinds/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [SysAid](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/sysaid/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Telegram](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/telegram/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [TOPdesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/topdesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [VictorOps](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/victorops/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Zammad](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/zammad/README.md?at=refs%2Fheads%2Frelease%2F6.0) - [Zendesk](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/zendesk/README.md?at=refs%2Fheads%2Frelease%2F6.0) ::: notetip En plus des services répertoriés ici, Zabbix peut être intégré à **Spiceworks** (aucun webhook n'est requis). Pour convertir les notifications Zabbix en tickets Spiceworks, créez un [type de media e-mail](/manual/config/notifications/media/email) et entrez l'adresse e-mail du service d'assistance Spiceworks (par exemple, help\@zabbix.on.spiceworks.com) dans les paramètres du profil d'un utilisateur Zabbix désigné. ::: ##### Interface creation when adding hosts When hosts are added as a result of network discovery, they get interfaces created according to these rules: - the services detected - for example, if an SNMP check succeeded, an SNMP interface will be created - if a host responded both to Zabbix agent and SNMP requests, both types of interfaces will be created - if uniqueness criteria are Zabbix agent or SNMP-returned data, the first interface found for a host will be created as the default one. Other IP addresses will be added as additional interfaces. Action's conditions (such as Host IP) do not impact adding interfaces. *Note* that this will work if all interfaces are discovered by the same discovery rule. If a different discovery rule discovers a different interface of the same host, an additional host will be added. - if a host responded to agent checks only, it will be created with an agent interface only. If it would start responding to SNMP later, additional SNMP interfaces would be added. - if 3 separate hosts were initially created, having been discovered by the "IP" uniqueness criteria, and then the discovery rule is modified so that hosts A, B and C have identical uniqueness criteria result, B and C are created as additional interfaces for A, the first host. The individual hosts B and C remain. In *Monitoring → Discovery* the added interfaces will be displayed in the "Discovered device" column, in black font and indented, but the "Monitored host" column will only display A, the first created host. "Uptime/Downtime" is not measured for IPs that are considered to be additional interfaces. ##### Création d'interface lors de l'ajout d'hôtes Lorsque des hôtes sont ajoutés via la découverte du réseau, ils obtiennent des interfaces créées conformément à ces règles : - les services détectés - par exemple, si une vérification SNMP réussit, une interface SNMP sera créée - si un hôte répond à la fois à l'agent Zabbix et aux requêtes SNMP, les deux types d'interfaces seront créées - si les critères d'unicité sont l'agent Zabbix ou les données renvoyées par SNMP, la première interface trouvée pour un hôte sera créée comme interface par défaut. D'autres adresses IP seront ajoutées en tant qu'interfaces supplémentaires. Les conditions de l'action (telles que l'IP de l'hôte) n'ont pas d'incidence sur l'ajout d'interfaces. *Notez* que cela fonctionnera si toutes les interfaces sont découvertes par la même règle de découverte. Si une règle de découverte différente découvre une interface différente du même hôte, un hôte supplémentaire sera ajouté. - si un hôte a répondu uniquement aux vérifications d'agent, il sera créé avec une interface d'agent uniquement. S'il devait commencer à répondre à SNMP plus tard, des interfaces SNMP supplémentaires seraient ajoutées à ce moment là. - si 3 hôtes distincts ont été créés à l'origine, après avoir été découverts par le critère d'unicité "IP", puis la règle de découverte est modifiée de sorte que les hôtes A, B et C aient des critères d'unicité identiques, B et C sont créés en tant qu'interfaces supplémentaires pour A, le premier hôte. Les hôtes individuels B et C restent inchangés. Dans *Surveillance* → *Découverte*, les interfaces ajoutées sont affichées dans la colonne "Équipement découvert", en caractères noirs et en retrait, mais la colonne "Hôte surveillé" affiche uniquement A, le premier hôte créé. Le «temps de fonctionnement/Temp d'arrêt» n'est pas mesuré pour les adresses IP considérées comme des interfaces supplémentaires. ### Internal authentication The *Authentication* tab allows defining custom password complexity requirements for internal Zabbix users.  The following password policy options can be configured: |Parameter|Description| |--|--------| |*Minimum password length*|By default, the minimum password length is set to 8. Supported range: 1-70. Note that passwords longer than 72 characters will be truncated.| |*Password must contain*|Mark one or several checkboxes to require usage of specified characters in a password:<br>-an uppercase and a lowercase Latin letter<br>-a digit<br>-a special character<br><br>Hover over the question mark to see a hint with the list of characters for each option.| |*Avoid easy-to-guess passwords*|If marked, a password will be checked against the following requirements:<br>- must not contain user's name, surname, or username<br>- must not be one of the common or context-specific passwords.<br><br>The list of common and context-specific passwords is generated automatically from the list of NCSC "Top 100k passwords", the list of SecLists "Top 1M passwords" and the list of Zabbix context-specific passwords. Internal users will not be allowed to set passwords included in this list as such passwords are considered weak due to their common use.| Changes in password complexity requirements will not affect existing user passwords, but if an existing user chooses to change a password, the new password will have to meet current requirements. A hint with the list of requirements will be displayed next to the *Password* field in the [user profile](/manual/web_interface/user_profile) and in the [user configuration form](/manual/config/users_and_usergroups/user) accessible from the *Administration→Users* menu. ### Authentification interne L'onglet *Authentification* permet de définir des exigences de complexité de mot de passe personnalisées pour les utilisateurs internes de Zabbix.  Les options de stratégie de mot de passe suivantes peuvent être configurées : |Paramètre|Description| |--|--------| |*Longueur minimale du mot de passe*|Par défaut, la longueur minimale du mot de passe est définie sur 8. Plage prise en charge : 1-70. Notez que les mots de passe de plus de 72 caractères seront tronqués.| |*Le mot de passe doit contenir*|Cochez une ou plusieurs cases pour exiger l'utilisation des caractères spécifiés dans un mot de passe :<br>-une lettre latine majuscule et minuscule<br>-un chiffre<br>-un caractère spécial<br><br>Passez la souris sur le point d'interrogation pour voir un indice avec la liste des caractères pour chaque option.| |*Évitez les mots de passe faciles à deviner*|Si coché, un mot de passe sera vérifié par rapport aux exigences suivantes :<br>- ne doit pas contenir le nom, le prénom ou le nom d'utilisateur de l'utilisateur<br>- ne doit pas être l'un des mots de passe courants ou mots de passe spécifiques au contexte.<br><br>La liste des mots de passe communs et spécifiques au contexte est générée automatiquement à partir de la liste des NCSC "Top 100k passwords", de la liste des SecLists "Top 1M passwords" et de la liste des contextes Zabbix mots de passe spécifiques. Les utilisateurs internes ne seront pas autorisés à définir des mots de passe inclus dans cette liste car ces mots de passe sont considérés comme faibles en raison de leur utilisation courante.| Les modifications des exigences de complexité des mots de passe n'affecteront pas les mots de passe des utilisateurs existants, mais si un utilisateur existant choisit de modifier un mot de passe, le nouveau mot de passe devra répondre aux exigences actuelles. Un indice avec la liste des exigences sera affiché à côté du champ *Mot de passe* dans le [profil utilisateur](/manual/web_interface/user_profile) et dans le [formulaire de configuration utilisateur](/manual/config/users_and_usergroups/user) accessible depuis le menu *Administration→Utilisateurs*. #### Internal event actions The following conditions can be set for actions based on internal events: |Condition type|Supported operators|Description| |--|--|------| |*Event type*|equals|**Item in "not supported" state** - matches events where an item goes from a 'normal' to 'not supported' state<br>**Low-level discovery rule in "not supported" state** - matches events where a low-level discovery rule goes from a 'normal' to 'not supported' state<br>**Trigger in "unknown" state** - matches events where a trigger goes from a 'normal' to 'unknown' state| |*Host group*|equals<br>does not equal|Specify host groups or host groups to exclude.<br>**equals** - event belongs to this host group.<br>**does not equal** - event does not belong to this host group.| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag or event tag to exclude.<br>**equals** - event has this tag<br>**does not equal** - event does not have this tag<br>**contains** - event has a tag containing this string<br>**does not contain** - event does not have a tag containing this string| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag and value combination or tag and value combination to exclude.<br>**equals** - event has this tag and value<br>**does not equal** - event does not have this tag and value<br>**contains** - event has a tag and value containing these strings<br>**does not contain** - event does not have a tag and value containing these strings| |*Template*|equals<br>does not equal|Specify templates or templates to exclude.<br>**equals** - event belongs to an item/trigger/low-level discovery rule inherited from this template.<br>**does not equal** - event does not belong to an item/trigger/low-level discovery rule inherited from this template.| |*Host*|equals<br>does not equal|Specify hosts or hosts to exclude.<br>**equals** - event belongs to this host.<br>**does not equal** - event does not belong to this host.| #### Actions d'événements internes Les conditions suivantes peuvent être définies pour les actions basées sur des événements: |Type de condition|Opérateurs pris en charge|Description| |--|--|------| |*Type d'événement*|égal|**Élément dans l'état "non supporté"** - correspond aux événements où un élément passe d'un état 'normal' à 'non supporté'<br>**Règle de découverte bas niveau dans l'état "non supporté" ** : correspond aux événements où une règle de découverte de bas niveau passe d'un état 'normal' à 'non supporté'<br>**Déclencheur dans l'état "inconnu"** : correspond aux événements où un déclencheur passe d'un état 'normal' à 'inconnu'| |*Groupe d'hôtes*|égal<br>n'est pas égal|Spécifiez les groupes d'hôtes ou les groupes d'hôtes à exclure.<br>**égal** - l'événement appartient à ce groupe d'hôtes.<br>**n'est pas égal** - l'événement n'appartient pas à ce groupe d'hôtes.| |*Nom de tag*|égal<br>n'est pas égal<br>contient<br>ne contient pas|Spécifiez le tag d'événement ou le tag d'événement à exclure.<br>**égal** - l'événement a ce tag<br>* *n'est pas égal** - l'événement n'a pas ce tag<br>**contient** - l'événement a un tag contenant cette chaîne<br>**ne contient pas** - l'événement n'a pas de tag contenant cette chaîne| |*Valeur de tag*|égal<br>n'est pas égal<br>contient<br>ne contient pas|Spécifiez la combinaison de tag et de valeur de tag d'événement ou la combinaison de tag et de valeur de tag à exclure.<br>**égal** - l'événement a ce tag et cette valeur<br>**n'est pas égal** - l'événement n'a pas ce tag et cette valeur<br>**contient** - l'événement a un tag et une valeur contenant ces chaînes<br>**ne contient pas** - l'événement n'a pas de tag et de valeur contenant ces chaînes | |*Modèle*|égal<br>n'est pas égal|Spécifiez les modèles ou les modèles à exclure.<br>**égal** - l'événement appartient à un élément/déclencheur/règle de découverte de bas niveau héritée de ce modèle.<br> **n'est pas égal** - l'événement n'appartient pas à un élément/déclencheur/règle de découverte de bas niveau héritée de ce modèle.| |*Hôte*|égal<br>n'est pas égal|Spécifiez les hôtes ou les hôtes à exclure.<br>**égal** - l'événement appartient à cet hôte.<br>**n'est pas égal** - l'événement n'appartient pas à cet hôte.| #### Internal queue items There are also another two items specifically allowing to remote query internal queue stats on another Zabbix instance: - `zabbix[stats,<ip>,<port>,queue,<from>,<to>]` internal item - for direct internal queue queries to remote Zabbix server/proxy - `zabbix.stats[<ip>,<port>,queue,<from>,<to>]` agent item - for agent-based internal queue queries to remote Zabbix server/proxy See also: [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent) #### Éléments de la file d'attente interne Il existe également deux autres éléments permettant spécifiquement d'interroger à distance les statistiques de la file d'attente interne sur une autre instance Zabbix : - Elément interne `zabbix[stats,<ip>,<port>,queue,<from>,<to>]` - pour les requêtes de file d'attente internes directes vers le serveur/proxy Zabbix distant - Elément agent `zabbix.stats[<ip>,<port>,queue,<from>,<to>]` - pour les requêtes de file d'attente interne basées sur l'agent vers le serveur/proxy Zabbix distant Voir également : [Eléments internes](/manual/config/items/itemtypes/internal), [éléments agent Zabbix](/manual/config/items/itemtypes/zabbix_agent) #### Internal workings of bulk processing Starting from 2.2.3 Zabbix server and proxy query SNMP devices for multiple values in a single request. This affects several types of SNMP items: - regular SNMP items - SNMP items [with dynamic indexes](/manual/config/items/itemtypes/snmp/dynamicindex) - SNMP [low-level discovery rules](/manual/discovery/low_level_discovery/examples/snmp_oids) All SNMP items on a single interface with identical parameters are scheduled to be queried at the same time. The first two types of items are taken by pollers in batches of at most 128 items, whereas low-level discovery rules are processed individually, as before. On the lower level, there are two kinds of operations performed for querying values: getting multiple specified objects and walking an OID tree. For "getting", a GetRequest-PDU is used with at most 128 variable bindings. For "walking", a GetNextRequest-PDU is used for SNMPv1 and GetBulkRequest with "max-repetitions" field of at most 128 is used for SNMPv2 and SNMPv3. Thus, the benefits of bulk processing for each SNMP item type are outlined below: - regular SNMP items benefit from "getting" improvements; - SNMP items with dynamic indexes benefit from both "getting" and "walking" improvements: "getting" is used for index verification and "walking" for building the cache; - SNMP low-level discovery rules benefit from "walking" improvements. However, there is a technical issue that not all devices are capable of returning 128 values per request. Some always return a proper response, but others either respond with a "tooBig(1)" error or do not respond at all once the potential response is over a certain limit. In order to find an optimal number of objects to query for a given device, Zabbix uses the following strategy. It starts cautiously with querying 1 value in a request. If that is successful, it queries 2 values in a request. If that is successful again, it queries 3 values in a request and continues similarly by multiplying the number of queried objects by 1.5, resulting in the following sequence of request sizes: 1, 2, 3, 4, 6, 9, 13, 19, 28, 42, 63, 94, 128. However, once a device refuses to give a proper response (for example, for 42 variables), Zabbix does two things. First, for the current item batch it halves the number of objects in a single request and queries 21 variables. If the device is alive, then the query should work in the vast majority of cases, because 28 variables were known to work and 21 is significantly less than that. However, if that still fails, then Zabbix falls back to querying values one by one. If it still fails at this point, then the device is definitely not responding and request size is not an issue. The second thing Zabbix does for subsequent item batches is it starts with the last successful number of variables (28 in our example) and continues incrementing request sizes by 1 until the limit is hit. For example, assuming the largest response size is 32 variables, the subsequent requests will be of sizes 29, 30, 31, 32, and 33. The last request will fail and Zabbix will never issue a request of size 33 again. From that point on, Zabbix will query at most 32 variables for this device. If large queries fail with this number of variables, it can mean one of two things. The exact criteria that a device uses for limiting response size cannot be known, but we try to approximate that using the number of variables. So the first possibility is that this number of variables is around the device's actual response size limit in the general case: sometimes response is less than the limit, sometimes it is greater than that. The second possibility is that a UDP packet in either direction simply got lost. For these reasons, if Zabbix gets a failed query, it reduces the maximum number of variables to try to get deeper into the device's comfortable range, but (starting from 2.2.8) only up to two times. In the example above, if a query with 32 variables happens to fail, Zabbix will reduce the count to 31. If that happens to fail, too, Zabbix will reduce the count to 30. However, Zabbix will not reduce the count below 30, because it will assume that further failures are due to UDP packets getting lost, rather than the device's limit. If, however, a device cannot handle bulk requests properly for other reasons and the heuristic described above does not work, since Zabbix 2.4 there is a "Use bulk requests" setting for each interface that allows to disable bulk requests for that device. #### Fonctionnement interne du traitement en masse À partir de 2.2.3, le serveur Zabbix et le proxy interrogent les périphériques SNMP pour plusieurs valeurs en une seule requête. Cela affecte plusieurs types d'éléments SNMP : - éléments SNMP réguliers - Éléments SNMP [avec index dynamiques](/manual/config/items/itemtypes/snmp/dynamicindex) - [Règles de découverte de bas niveau](/manual/discovery/low_level_discovery/examples/snmp_oids) SNMP Tous les éléments SNMP sur une seule interface avec des paramètres identiques sont programmés pour être interrogés en même temps. Les deux premiers types d'éléments sont pris par les pollers par lots d'au plus 128 éléments, tandis que les règles de découverte de bas niveau sont traitées individuellement, comme auparavant. Au niveau inférieur, il existe deux types d'opérations effectuées pour interroger des valeurs : obtenir plusieurs objets spécifiés et parcourir une arborescence d'OID. Pour le SNMP "get", une GetRequest-PDU est utilisée avec au plus 128 liaisons de variables. Pour le SNMP "walk", un GetNextRequest-PDU est utilisé pour SNMPv1 et GetBulkRequest avec un champ "max-repetitions" d'au plus 128 est utilisé pour SNMPv2 et SNMPv3. Ainsi, les avantages du traitement en bloc pour chaque type d'élément SNMP sont décrits ci-dessous : - Les éléments SNMP réguliers bénéficient d'améliorations "get" ; - Les éléments SNMP avec des index dynamiques bénéficient à la fois des améliorations "get" et "walk": "get" est utilisé pour la vérification de l'index et "walk" pour la construction du cache ; - Les règles de découverte de bas niveau SNMP bénéficient d'améliorations "walk". Cependant, il existe un problème technique qui fait que tous les appareils ne sont pas capables de renvoyer 128 valeurs par requête. Certains renvoient toujours une réponse appropriée, mais d'autres répondent avec une erreur "tooBig(1)" ou ne répondent pas du tout une fois que la réponse potentielle dépasse une certaine limite. Afin de trouver un nombre optimal d'objets à interroger pour un appareil donné, Zabbix utilise la stratégie suivante. Il commence prudemment en interrogeant 1 valeur dans une requête. Si cela réussit, il interroge 2 valeurs dans une requête. Si cela réussit à nouveau, il interroge 3 valeurs dans une requête et continue de la même manière en multipliant le nombre d'objets interrogés par 1,5, ce qui donne la séquence suivante de tailles de requête : 1, 2, 3, 4, 6, 9, 13, 19 , 28, 42, 63, 94, 128. Cependant, une fois qu'un appareil refuse de donner une réponse appropriée (par exemple, pour 42 variables), Zabbix fait deux choses. Tout d'abord, pour le lot d'éléments en cours, il divise par deux le nombre d'objets dans une seule requête et interroge 21 variables. Si l'appareil est actif, la requête devrait fonctionner dans la grande majorité des cas, car 28 variables étaient connues pour fonctionner et 21, c'est nettement moins que cela. Cependant, si cela échoue toujours, Zabbix revient à interroger les valeurs une par une. S'il échoue toujours à ce stade, l'appareil ne répond définitivement pas et la taille de la demande n'est pas un problème. La deuxième chose que Zabbix fait pour les lots d'éléments suivants est qu'il commence par le dernier nombre de variables réussi (28 dans notre exemple) et continue d'incrémenter les tailles de requête de 1 jusqu'à ce que la limite soit atteinte. Par exemple, en supposant que la plus grande taille de réponse est de 32 variables, les requêtes suivantes seront de tailles 29, 30, 31, 32 et 33. La dernière requête échouera et Zabbix n'émettra plus jamais de requête de taille 33. À partir de ce moment, Zabbix interrogera au plus 32 variables pour cet appareil. Si de grandes requêtes échouent avec ce nombre de variables, cela peut signifier deux choses. Les critères exacts qu'un appareil utilise pour limiter la taille de la réponse ne peuvent pas être connus, mais nous essayons d'en faire une approximation en utilisant le nombre de variables. Ainsi, la première possibilité est que ce nombre de variables se situe autour de la limite de taille de réponse réelle de l'appareil dans le cas général : parfois la réponse est inférieure à la limite, parfois elle est supérieure à cela. La deuxième possibilité est qu'un paquet UDP dans l'une ou l'autre direction soit simplement perdu. Pour ces raisons, si Zabbix obtient une requête ayant échoué, il réduit le nombre maximum de variables pour essayer d'approfondir la plage confortable de l'appareil, mais (à partir de 2.2.8) jusqu'à deux fois seulement. Dans l'exemple ci-dessus, si une requête avec 32 variables échoue, Zabbix réduira le nombre à 31. Si cela échoue également, Zabbix réduira le nombre à 30. Cependant, Zabbix ne réduira pas le nombre en dessous de 30, car il supposera que d'autres échecs sont dus à la perte de paquets UDP, plutôt qu'à la limite du périphérique. Si, toutefois, un appareil ne peut pas gérer correctement les demandes groupées pour d'autres raisons et que l'heuristique décrite ci-dessus ne fonctionne pas, depuis Zabbix 2.4, il existe un paramètre "Utiliser les demandes groupées" pour chaque interface qui permet de désactiver les demandes groupées pour cet appareil. #### Introduction MIB stands for a Management Information Base. MIB files allow you to use textual representation of the OID (Object Identifier). For example, ifHCOutOctets is textual representation of OID 1.3.6.1.2.1.31.1.1.1.10 You can use either, when monitoring SNMP devices with Zabbix, but if you feel more comfortable when using textual representation you have to install MIB files. #### Introduction MIB signifie Management Information Base. Les fichiers MIB vous permettent d'utiliser une représentation textuelle de l'OID (Object Identifier). Par exemple, ifHCOutOctets est une représentation textuelle de l'OID 1.3.6.1.2.1.31.1.1.1.10 Vous pouvez utiliser l'un ou l'autre, lors de la surveillance des périphériques SNMP avec Zabbix, mais si vous vous sentez plus à l'aise lors de l'utilisation de la représentation textuelle, vous devez installer des fichiers MIB. Introduction of loadable plugins caused the following configuration parameter changes: - *Plugins.\<PluginName>.Path* parameter has been moved to *Plugins.\<PluginName>.System.Path*. - *Plugins.\<PluginName>.Capacity* parameter, while still supported, has been deprecated, please use *Plugins.\<PluginName>.System.Capacity* instead. L'introduction de plugins chargeables a entraîné les changements de paramètres de configuration suivants : - Le paramètre *Plugins.\<PluginName>.Path* a été déplacé vers *Plugins.\<PluginName>.System.Path*. - Le paramètre *Plugins.\<PluginName>.Capacity*, bien que toujours pris en charge, est obsolète, veuillez utiliser *Plugins.\<PluginName>.System.Capacity* à la place. #### Invalid regular expressions after switching to PCRE2 In Zabbix 6.0 support for PCRE2 has been added. Even though PCRE is still supported, Zabbix installation packages for RHEL 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer have been updated to use PCRE2. While providing many benefits, switching to PCRE2 may cause certain existing PCRE regexp patterns becoming invalid or behaving differently. In particular, this affects the pattern *\^[\\w-\\.]*. In order to make this regexp valid again without affecting semantics, change the expression to *\^[-\\w\\.]* . This happens due to the fact that PCRE2 treats the dash sign as a delimiter, creating a range inside a character class. The following Zabbix installation packages have been updated and now use PCRE2: RHEL 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer. #### Expressions régulières non valides après le passage à PCRE2 Dans Zabbix 6.0, la prise en charge de PCRE2 a été ajoutée. Même si PCRE est toujours pris en charge, les packages d'installation Zabbix pour RHEL 7 et versions ultérieures, SLES (toutes les versions), Debian 9 et versions ultérieures, Ubuntu 16.04 et versions ultérieures ont été mis à jour pour utiliser PCRE2. Tout en offrant de nombreux avantages, le passage à PCRE2 peut rendre invalides ou se comporter différemment certains modèles d'expressions régulières PCRE existants. En particulier, cela affecte le modèle *\^[\\w-\\.]*. Afin de rendre cette expression régulière à nouveau valide sans affecter la sémantique, remplacez l'expression par *\^[-\\w\\.]* . Cela est dû au fait que PCRE2 traite le tiret comme un délimiteur, créant une plage à l'intérieur d'une classe de caractères. Les packages d'installation Zabbix suivants ont été mis à jour et utilisent désormais PCRE2 : RHEL 7 et versions ultérieures, SLES (toutes les versions), Debian 9 et versions ultérieures, Ubuntu 16.04 et versions ultérieures. ##### Inventory mode selection Inventory mode can be selected in the host configuration form. Inventory mode by default for new hosts is selected based on the *Default host inventory mode* setting in *Administration* → *General* → *[Other](/manual/web_interface/frontend_sections/administration/general#other_parameters)*. For hosts added by network discovery or autoregistration actions, it is possible to define a *Set host inventory mode* operation selecting manual or automatic mode. This operation overrides the *Default host inventory mode* setting. ##### Sélection du mode d'inventaire Le mode d'inventaire peut être sélectionné dans le formulaire de configuration de l'hôte. Le mode d'inventaire par défaut pour les nouveaux hôtes est sélectionné en fonction du paramètre *Mode d'inventaire d'hôte par défaut* dans *Administration* → *Général* → *[Autre](/manual/web_interface/frontend_sections/administration/general#other_parameters)*. Pour les hôtes ajoutés par des actions de découverte de réseau ou d'enregistrement automatique, il est possible de définir une opération *Définir le mode d'inventaire des hôtes* en sélectionnant le mode manuel ou automatique. Cette opération remplace le paramètre *Mode d'inventaire de l'hôte par défaut*. #### Inventory overview The details of all existing inventory data are available in the *Inventory* menu. In *Inventory → Overview* you can get a host count by various fields of the inventory. In *Inventory → Hosts* you can see all hosts that have inventory information. Clicking on the host name will reveal the inventory details in a form. {width="600"} The **Overview** tab shows: |Parameter|Description| |--|--------| |*Host name*|Name of the host.<br>Clicking on the name opens a menu with the scripts defined for the host.<br>Host name is displayed with an orange icon, if the host is in maintenance.| |*Visible name*|Visible name of the host (if defined).| |*Host (Agent, SNMP, JMX, IPMI)<br>interfaces*|This block provides details of the interfaces configured for the host.| |*OS*|Operating system inventory field of the host (if defined).| |*Hardware*|Host hardware inventory field (if defined).| |*Software*|Host software inventory field (if defined).| |*Description*|Host description.| |*Monitoring*|Links to monitoring sections with data for this host: *Web*, *Latest data*, *Problems*, *Graphs*, *Dashboards*.| |*Configuration*|Links to configuration sections for this host: *Host*, *Applications*, *Items*, *Triggers*, *Graphs*, *Discovery*, *Web*.<br>The amount of configured entities is listed in parenthesis after each link.| The **Details** tab shows all inventory fields that are populated (are not empty). #### Aperçu de l'inventaire Les détails de toutes les données d'inventaire existantes sont disponibles dans le menu *Inventaire*. Dans *Inventaire → Aperçu*, vous pouvez obtenir un nombre d'hôtes par différents champs de l'inventaire. Dans *Inventaire → Hôtes*, vous pouvez voir tous les hôtes qui ont des informations d'inventaire. Cliquer sur le nom de l'hôte révélera les détails de l'inventaire dans un formulaire. {width="600"} L'onglet **Aperçu** affiche : |Paramètre|Description| |--|--------| |*Nom de l'hôte*|Nom de l'hôte.<br>Cliquer sur le nom ouvre un menu avec les scripts définis pour l'hôte.<br>Le nom de l'hôte s'affiche avec une icône orange, si l'hôte est en maintenance.| |*Nom visible*|Nom visible de l'hôte (si défini).| |*Interfaces de l'hôte<br>(Agent, SNMP, JMX, IPMI)*|Ce bloc fournit des détails sur les interfaces configurées pour l'hôte.| |*OS*|Champ d'inventaire du système d'exploitation de l'hôte (si défini).| |*Hardware*|Champ d'inventaire du matériel de l'hôte (si défini).| |*Logiciel*|Champ d'inventaire du logiciel hôte (si défini).| |*Description*|Description de l'hôte.| |*Surveillance*|Liens vers les sections de surveillance avec des données pour cet hôte : *Web*, *Dernières données*, *Problèmes*, *Graphiques*, *Tableaux de bord*.| |*Configuration*|Liens vers les sections de configuration pour cet hôte : *Host*, *Applications*, *Eléments*, *Déclencheurs*, *Graphiques*, *Découverte*, *Web*.<br>Le nombre d'entités configurées est entre parenthèses après chaque lien.| L'onglet **Détails** affiche tous les champs d'inventaire remplis (non vides). #### IPMI checks IPMI checks will not work with the standard OpenIPMI library package on Debian prior to 9 (stretch) and Ubuntu prior to 16.04 (xenial). To fix that, recompile OpenIPMI library with OpenSSL enabled as discussed in [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139). #### Vérifications IPMI Les vérifications IPMI ne fonctionneront pas avec le package de bibliothèque OpenIPMI standard sur Debian avant 9 (stretch) et Ubuntu avant 16.04 (xenial). Pour résoudre ce problème, recompilez la bibliothèque OpenIPMI avec OpenSSL activé, comme indiqué dans [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139). #### IPMI remote commands For IPMI remote commands the following syntax should be used: <command> [<value>] where - <command> - one of IPMI commands without spaces - <value> - 'on', 'off' or any unsigned integer. <value> is an optional parameter. #### Commandes à distance IPMI Pour les commandes distantes IPMI, la syntaxe suivante doit être utilisée : <command> [<value>] où - <command> - une des commandes IPMI sans espaces - <value> - 'on', 'off' ou tout entier non signé. <valeur> est un paramètre facultatif. #### IPv6 address issue in SNMPv3 traps Due to a net-snmp bug, IPv6 address may not be correctly displayed when using SNMPv3 in SNMP traps. For more details and a possible workaround, see [ZBX-14541](https://support.zabbix.com/browse/ZBX-14541). #### Problème d'adresse IPv6 dans les traps SNMPv3 En raison d'un bogue net-snmp, l'adresse IPv6 peut ne pas s'afficher correctement lors de l'utilisation de SNMPv3 dans les traps SNMP. Pour plus de détails et une solution de contournement possible, voir [ZBX-14541](https://support.zabbix.com/browse/ZBX-14541). #### Issues in Zabbix 6.0.11 ##### JSONPath parsing errors JSONPath parsing errors occur in case of leading whitespace and empty array/object. Fixed in Zabbix 6.0.12. ##### AND/OR evaluation in LLD filters The evaluation of AND/OR expressions in the low-level discovery filters/overrides may fail in this version. Fixed in Zabbix 6.0.12. #### Problèmes dans Zabbix 6.0.11 ##### Erreurs d'analyse JSONPath Des erreurs d'analyse JSONPath se produisent en cas d'espace blanc en tête et de tableau/objet vide. Corrigé dans Zabbix 6.0.12. ##### Évaluation ET/OU dans les filtres LLD L'évaluation des expressions ET/OU dans les filtres/substitutions de découverte de bas niveau peut échouer dans cette version. Corrigé dans Zabbix 6.0.12. #### Item changes Native support for the [items](/manual/config/items/itemtypes/zabbix_agent) **net.dns** and **net.dns.record** has been added to Zabbix agent 2. On Zabbix agent 2 for Windows, these items now allow custom DNS IP addresses in the `ip` parameter and no longer ignore `timeout` and `count` parameters. #### Modifications d'éléments La prise en charge native des [items](/manual/config/items/itemtypes/zabbix_agent) **net.dns** et **net.dns.record** a été ajoutée à l'agent Zabbix 2. Sur l'agent Zabbix 2 pour Windows , ces éléments autorisent désormais les adresses IP DNS personnalisées dans le paramètre `ip` et n'ignorent plus les paramètres `timeout` et `count`. ##### Item configuration Actual command(s) to be executed must be placed in the **Executed script** field in the item configuration. Multiple commands can be executed one after another by placing them on a new line. In this case returned values also will be formatted as multi lined.  All mandatory input fields are marked with a red asterisk. The fields that require specific information for SSH items are: |Parameter|Description|Comments| |--|------|------| |*Type*|Select **SSH agent** here.| | |*Key*|Unique (per host) item key in format **ssh.run\[<unique short description>,<ip>,<port>,<encoding>\]**|<unique short description> is required and should be unique for all SSH items per host<br>Default port is 22, not the port specified in the interface to which this item is assigned| |*Authentication method*|One of the "Password" or "Public key"| | |*User name*|User name to authenticate on remote host.<br>Required| | |*Public key file*|File name of public key if *Authentication method* is "Public key". Required|Example: *id\_rsa.pub* - default public key file name generated by a command [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen)| |*Private key file*|File name of private key if *Authentication method* is "Public key". Required|Example: *id\_rsa* - default private key file name| |*Password* or<br>*Key passphrase*|Password to authenticate or<br>Passphrase **if** it was used for the private key|Leave the *Key passphrase* field empty if passphrase was not used<br>See also [known issues](/manual/installation/known_issues#ssh_checks) regarding passphrase usage| |*Executed script*|Executed shell command(s) using SSH remote session|Examples:<br>*date +%s*<br>*service mysql-server status*<br>*ps auxww \| grep httpd \| wc -l*| ::: noteimportant libssh2 library may truncate executable scripts to \~32kB. ::: ##### Configuration de l’élément Les commandes réelles à exécuter doivent être placées dans le champ **Script exécuté** dans la configuration de l'élément. Plusieurs commandes peuvent être exécutées l'une après l'autre en les plaçant sur une nouvelle ligne. Dans ce cas, les valeurs renvoyées seront également formatées en plusieurs lignes.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les champs qui nécessitent des informations spécifiques pour les éléments SSH sont les suivants : |Paramètre|Description|Commentaires| |--|------|------|¶ |*Type*|Sélectionnez **Agent SSH** ici.| | |*Clé*|Clé d'élément unique (par hôte) au format **ssh.run\[<unique short description>,<ip>,<port>,<encoding>\]**|<unique short description > est obligatoire et doit être unique pour tous les éléments SSH par hôte.<br>Le port par défaut est 22, pas le port spécifié dans l'interface à laquelle cet élément est affecté| |*Méthode d'authentification*|Un parmi "Mot de passe" or "Clé publique"| | |*Nom d'utilisateur*|Nom de l'utilisateur permettant de s'authentifier sur l'hôte distant.<br>Obligatoire| | |*Fichier de clé publique*|Nom du fichier ou clé publique si la *Méthode d'authentification* est "Clé publique". Obligatoire|Exemple : *id\_rsa.pub* - par défaut le nom du fichier de la clé publique est généré via la commande [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen)| |*Fichier de clé privée*|Nom du fichier ou clé privée si la *Méthode d'authentification* est "Clé publique". Obligatoire|Exemple : *id\_rsa* - par défaut le nom de fichier de la clé privée| |*Mot de passe* ou<br>*Phrase de passe de la clé*|Mot de passe pour l'authentification ou<br>Phrase de passe de la clé **si** il était utilisé pour la clé privée|Laissez le champs *Phrase de passe de la clé* vide si la phrase secrete n'est pas utilisée<br>Voir aussi les [problèmes connus](/fr/manual/installation/known_issues#verifications_ssh) concernant l'utilisation de la phrase secrete| |*script exécuté*|Commande(s) shell exécutée(s) à l'aide de la session à distance SSH|Exemples :<br>*date +%s*<br>*service mysql-server status*<br>*ps auxww \| grep httpd \| wc -l*| ::: noteimportant La bibliothèque libssh2 peut tronquer les scripts exécutables à \~32 Ko. ::: #### Item configuration A dependent item depends on its master item for data. That is why the **master item** must be configured (or exist) first: - Go to: *Configuration* → *Hosts* - Click on *Items* in the row of the host - Click on *Create item* - Enter parameters of the item in the form  All mandatory input fields are marked with a red asterisk. Click on *Add* to save the master item. Then you can configure a **dependent item**.  All mandatory input fields are marked with a red asterisk. The fields that require specific information for dependent items are: | | | |--|--------| |*Type*|Select **Dependent item** here.| |*Key*|Enter a key that will be used to recognize the item.| |*Master item*|Select the master item. Master item value will be used to populate dependent item value.| |*Type of information*|Select the type of information that will correspond the format of data that will be stored.| You may use item value [preprocessing](/manual/config/items/item#item_value_preprocessing) to extract the required part of the master item value. {width="600"} Without preprocessing, the dependent item value will be exactly the same as the master item value. Click on *Add* to save the dependent item. A shortcut to creating a dependent item quicker is to use the wizard in the item list:  #### Configuration de l"élément Un élément dépendant dépend de son élément principal pour les données. C'est pourquoi l'**élément principal** doit d'abord être configuré (ou exister) : - Allez dans : *Configuration* → *Hôtes* - Cliquez sur *Éléments* dans la rangée de l'hôte - Cliquez sur *Créer un élément* - Saisissez les paramètres de l'élément dans le formulaire  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Cliquez sur *Ajouter* pour enregistrer l'élément principal. Ensuite, vous pouvez configurer un **élément dépendant**.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les champs qui nécessitent des informations spécifiques pour les éléments dépendants sont : | | | |--|--------| |*Type*|Sélectionnez **élément dépendant** ici.| |*Clé*|Entrez une clé qui sera utilisée pour reconnaître l'élément.| |*Élément principal*|Sélectionnez l'élément principal. La valeur de l'élément principal sera utilisée pour remplir la valeur de l'élément dépendant.| |*Type d'information*|Sélectionnez le type d'information qui correspondra au format des données qui seront stockées.| Vous pouvez utiliser le [prétraitement](/manual/config/items/item#item_value_preprocessing) de valeur d'éléméent pour extraire la partie requise de la valeur de l'élément principal. {width="600"} Sans prétraitement, la valeur de l'élément dépendant sera exactement la même que la valeur de l'élément principal. Cliquez sur *Ajouter* pour enregistrer l'élément dépendant. Un raccourci pour créer plus rapidement un élément dépendant consiste à utiliser l'assistant dans la liste des éléments :  ##### Item configuration When [configuring an item](/manual/config/items/item) on a host level: - Select 'IPMI agent' as the *Type* - Enter an item [key](/manual/config/items/item/key) that is unique within the host (say, ipmi.fan.rpm) - For *Host interface* select the relevant IPMI interface (IP and port). Note that an IPMI interface must exist on the host. - Specify the *IPMI sensor* (for example 'FAN MOD 1A RPM' on Dell Poweredge) to retrieve the metric from. By default, the sensor ID should be specified. It is also possible to use prefixes before the value: - `id:` - to specify sensor ID; - `name:` - to specify sensor full name. This can be useful in situations when sensors can only be distinguished by specifying the full name. - Select the respective type of information ('Numeric (float)' in this case; for discrete sensors - 'Numeric (unsigned)'), units (most likely 'rpm') and any other required item attributes ##### Configuration de l'élément Lors de la [configuration d'un élément](/fr/manual/config/items/item) au niveau de l'hôte : - Sélectionnez 'IPMI agent' comme *Type* - Saisissez une [clé](/manual/config/items/item/key) unique sur l'hôte (telle que, ipmi.fan.rpm) - Pour l'*interface hôte*, sélectionnez l'interface IPMI adéquate (IP et port). Notez que l'interface IPMI doit exister sur l'hôte. - Spécifiez le *capteur IPMI* (par exemple 'FAN MOD 1A RPM' sur Dell Poweredge) sur lequel récupérer la valeur. Par défaut, l'ID du capteur doit être spécifié. Il est aussi possible d'utiliser des préfixes avant la valeur : - `id:` - pour spécifier l'ID du capteur ; - `name:` - pour spécifier le nom complet du capteur. Cela peut être utile dans certaines situations quand les capteurs peuvent seulement être distingués en spécifiant le nom complet. - Sélectionnez le type d'information correspondant ('Numérique (flottant)' dans ce cas, pour les capteurs discrets - 'Numérique (non signé)'), les unités (très probablement 'rpm') et tout autre attribut d'élément requis # item.create # item.create # item.delete # item.delete # item.get # item.get #### Item key SQL queries are performed using a "Database monitor" item type. Therefore, most of the instructions on [ODBC monitoring](/manual/config/items/itemtypes/odbc_checks) page apply in order to get a working "Database monitor" discovery rule. Two item keys may be used in "Database monitor" discovery rules: - **db.odbc.discovery**\[<unique short description>,<dsn>,<connection string>\] - this item transforms the SQL query result into a JSON array, turning the column names from the query result into low-level discovery macro names paired with the discovered field values. These macros can be used in creating item, trigger, etc prototypes. See also: [Using db.odbc.discovery](#using_dbodbcdiscovery). ```{=html} <!-- --> ``` - **db.odbc.get**\[<unique short description>,<dsn>,<connection string>\] - this item transforms the SQL query result into a JSON array, keeping the original column names from the query result as a field name in JSON paired with the discovered values. Compared to `db.odbc.discovery[]`, this item does not create low-level discovery macros in the returned JSON, therefore there is no need to check if the column names can be valid macro names. The low-level discovery macros can be defined as an additional step as required, using the [custom LLD macro](/manual/discovery/low_level_discovery#custom_macros) functionality with JSONPath pointing to the discovered values in the returned JSON. See also: [Using db.odbc.get](#using_dbodbcget). #### Clé d'élément Les requêtes SQL sont effectuées à l'aide d'une élément de type "Surveillance base de données". Par conséquent, la plupart des instructions de la page [Surveillance ODBC](/manual/config/items/itemtypes/odbc_checks) s'appliquent afin d'obtenir une règle de découverte "Surveillance base de données" fonctionnelle. Deux clés d'éléments peuvent être utilisées dans les règles de découverte "Surveillance base de données" : - **db.odbc.discovery**\[<courte description unique>,<dsn>,<chaîne de connexion>\] - cet élément transforme le résultat de la requête SQL en un tableau JSON, transformant les noms de colonne du résultat de la requête en noms de macro de découverte de bas niveau associés aux valeurs de champ découvertes. Ces macros peuvent être utilisées pour créer des prototypes d'éléments, de déclencheurs, etc. Voir aussi : [Utilisation de odb.odbc.discovery](#using_dbodbcdiscovery). ```{=html} <!-- --> ``` - **db.odbc.get**\[<courte description unique>,<dsn>,<chaîne de connexion>\] - cet élément transforme le résultat de la requête SQL en un tableau JSON, en conservant les noms de colonne d'origine du résultat de la requête en tant que nom de champ dans JSON associé aux valeurs découvertes. Comparé à `db.odbc.discovery[]`, cet élément ne crée pas de macros de découverte de bas niveau dans le JSON renvoyé, il n'est donc pas nécessaire de vérifier si les noms de colonne peuvent être des noms de macro valides. Les macros de découverte de bas niveau peuvent être définies comme une étape supplémentaire si nécessaire, à l'aide de la fonctionnalité [macro LLD personnalisée](/manual/discovery/low_level_discovery#custom_macros) avec JSONPath pointant vers les valeurs découvertes dans le JSON renvoyé. Voir aussi : [Utilisation de db.odbc.get](#using_dbodbcget). #### Item keys The table provides details on the simple checks that can be used to monitor [VMware environments](/manual/vm_monitoring). |Key|<|<|<|<| |-|------|--|------|------| |<|Description|Return value|Parameters|Comments| |vmware.cl.perfcounter\[<url>,<id>,<path>,<instance>\]|<|<|<|<| |<|VMware cluster performance counter metrics.|Integer|**url** - VMware service URL<br>**id** - VMware cluster ID<br>**path** - performance counter path<br>**instance** - performance counter instance|`id` can be received from vmware.cluster.discovery\[\] as {\#CLUSTER.ID}| |vmware.cluster.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware clusters.|JSON object|**url** - VMware service URL|<| |vmware.cluster.status\[<url>, <name>\]|<|<|<|<| |<|VMware cluster status.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**name** - VMware cluster name|<| |vmware.datastore.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware datastores.|JSON object|**url** - VMware service URL|<| |vmware.datastore.hv.list\[<url>,<datastore>\]|<|<|<|<| |<|List of datastore hypervisors.|JSON object|**url** - VMware service URL<br>**datastore** - datastore name|<| |vmware.datastore.read\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|Amount of time for a read operation from the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - latency (average value, default), maxlatency (maximum value)|<| |vmware.datastore.size\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore space in bytes or in percentage from total.|Integer - for bytes<br>Float - for percentage|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - possible values:<br>total (default), free, pfree (free, percentage), uncommitted|<| |vmware.datastore.write\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|Amount of time for a write operation to the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - latency (average value, default), maxlatency (maximum value)|<| |vmware.dc.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware datacenters.|JSON object|**url** - VMware service URL|<| |vmware.eventlog\[<url>,<mode>\]|<|<|<|<| |<|VMware event log.|Log|**url** - VMware service URL<br>**mode** - *all* (default), *skip* - skip processing of older data|There must be only one vmware.eventlog\[\] item key per URL.<br><br>See also: [example of filtering](/manual/config/items/preprocessing/examples#filtering_vmware_event_log_records) VMware event log records.| |vmware.fullname\[<url>\]|<|<|<|<| |<|VMware service full name.|String|**url** - VMware service URL|<| |vmware.hv.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor cluster name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage as a percentage during the interval.|Float|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.utilization\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage as a percentage during the interval, depends on power management or HT.|Float|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor datacenter name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware hypervisor datastores.|JSON object|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.list\[<url>,<uuid>\]|<|<|<|<| |<|List of VMware hypervisor datastores.|JSON object|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.multipath\[<url>,<uuid>,<datastore>,<partitionid>\]|<|<|<|<| |<|Number of available datastore paths.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**partitionid** - internal ID of physical device from vmware.hv.datastore.discovery|<| |vmware.hv.datastore.read\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|Average amount of time for a read operation from the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - latency (default)|<| |vmware.hv.datastore.size\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore space in bytes or in percentage from total.|Integer - for bytes<br>Float - for percentage|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - possible values:<br>total (default), free, pfree (free, percentage), uncommitted|<| |vmware.hv.datastore.write\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|Average amount of time for a write operation to the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - latency (default)|<| |vmware.hv.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware hypervisors.|JSON object|**url** - VMware service URL|<| |vmware.hv.fullname\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.freq\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor frequency (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor model.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of processor cores on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.threads\[<url>,<uuid>\]|<|<|<|<| |<|Number of processor threads on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.memory\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor total memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor model.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.uuid\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor BIOS UUID.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.vendor\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor vendor name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.maintenance\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor maintenance status.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|Returns '0' - not in maintenance or '1' - in maintenance| |vmware.hv.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor ballooned memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.memory.used\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor used memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.network.in\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor network input statistics (bytes per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**mode** - bps (default)|<| |vmware.hv.network.out\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor network output statistics (bytes per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**mode** - bps (default)|<| |vmware.hv.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware hypervisor performance counter value.|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**path** - performance counter path ^**[1](vmware_keys#footnotes)**^<br>**instance** - performance counter instance. Use empty instance for aggregate values (default)|<| |vmware.hv.power\[<url>,<uuid>,<max>\]|<|<|<|<| |<|VMware hypervisor power usage (W).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**max** - maximum allowed power usage|<| |vmware.hv.sensor.health.state\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor health state rollup sensor.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|The item might not work in the VMware vSphere 6.5 and newer, because VMware has deprecated the *VMware Rollup Health State* sensor. | |vmware.hv.sensors.get\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor HW vendor state sensors.|JSON|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.status\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor status.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|Uses the host system overall status property.| |vmware.hv.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor uptime (seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.version\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor version.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.vm.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of virtual machines on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.version\[<url>\]|<|<|<|<| |<|VMware service version.|String|**url** - VMware service URL|<| |vmware.vm.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.latency\[<url>,<uuid>\]|<|<|<|<| |<|Percentage of time the virtual machine is unable to run because it is contending for access to the physical CPU(s).|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of processors on VMware virtual machine.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.readiness\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical CPU.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - CPU instance|<| |vmware.vm.cpu.ready\[<url>,<uuid>\]|<|<|<|<| |<|Time (in milliseconds) that the virtual machine was ready, but could not get scheduled to run on the physical CPU. CPU ready time is dependent on the number of virtual machines on the host and their CPU loads (%).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.swapwait\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Percentage of CPU time spent waiting for swap-in.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - CPU instance|<| |vmware.vm.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine processor usage (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine processor usage as a percentage during the interval.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine datacenter name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware virtual machines.|JSON object|**url** - VMware service URL|<| |vmware.vm.guest.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|Amount of guest physical memory that is swapped out to the swap space (KB).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.guest.osuptime\[<url>,<uuid>\]|<|<|<|<| |<|Total time elapsed since the last operating system boot-up (in seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.hv.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine hypervisor name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine total memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine ballooned memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.compressed\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine compressed memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.consumed\[<url>,<uuid>\]|<|<|<|<| |<|Amount of host physical memory consumed for backing up guest physical memory pages (KB).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.private\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine private memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.shared\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine shared memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine swapped memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.usage.guest\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine guest memory usage (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.usage.host\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine host memory usage (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.usage\[<url>,<uuid>\]|<|<|<|<| |<|Percentage of host physical memory that has been consumed.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.net.if.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine network interfaces.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.net.if.in\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine network interface input statistics (bytes/packets per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance<br>**mode** - bps (default)/pps - bytes/packets per second|<| |vmware.vm.net.if.out\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine network interface output statistics (bytes/packets per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance<br>**mode** - bps (default)/pps - bytes/packets per second|<| |vmware.vm.net.if.usage\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|VMware virtual machine network utilization (combined transmit-rates and receive-rates) during the interval (KBps).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance|<| |vmware.vm.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware virtual machine performance counter value.|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**path** - performance counter path ^**[1](vmware_keys#footnotes)**^<br>**instance** - performance counter instance. Use empty instance for aggregate values (default)|<| |vmware.vm.powerstate\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine power state.|Integer:<br>0 - poweredOff;<br>1 - poweredOn;<br>2 - suspended|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.committed\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine committed storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.readoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Average number of outstanding read requests to the virtual disk during the collection interval.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.totalreadlatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|The average time a read from the virtual disk takes (milliseconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.totalwritelatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|The average time a write to the virtual disk takes (milliseconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.uncommitted\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine uncommitted storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.unshared\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine unshared storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.writeoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Average number of outstanding write requests to the virtual disk during the collection interval.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine uptime (seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.vfs.dev.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine disk devices.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.vfs.dev.read\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine disk device read statistics (bytes/operations per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.dev.write\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine disk device write statistics (bytes/operations per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.fs.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine file systems.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|VMware Tools must be installed on the guest virtual machine.| |vmware.vm.vfs.fs.size\[<url>,<uuid>,<fsname>,<mode>\]|<|<|<|<| |<|VMware virtual machine file system statistics (bytes/percentages).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**fsname** - file system name<br>**mode** - total/free/used/pfree/pused|VMware Tools must be installed on the guest virtual machine.| #### Clés d'élément Le tableau fournit des détails sur les vérifications simples qui peuvent être utilisées pour surveiller [les environnements VMware](/manual/vm_monitoring). |Clé|<|<|<|<| |-|------|--|------|------| |<|Description|Valeur de retour|Paramètres|Commentaires| |vmware.cl.perfcounter\[\<url\>,\<id\>,\<path\>,\<instance\>\]|<|<|<|<| |<|Métriques du compteur de performances du cluster VMware.|Entier|**url** - URL du service VMware<br>**id** - ID du cluster VMware<br>**path** - chemin du compteur de performances<br>**instance** - l'instance de compteur de performance|`id` peut être reçue de vmware.cluster.discovery\[\] en tant que {\#CLUSTER.ID}| |vmware.cluster.discovery\[\<url\>\]|<|<|<|<| |<|Découverte des clusters VMware.|Objet JSON|**url** - URL du service VMware|<| |vmware.cluster.status\[\<url\>, \<name\>\]|<|<|<|<| |<|État du cluster VMware.|Entier :<br>0 - gris ;<br>1 - vert ;<br>2 - jaune ;<br>3 - rouge|**url** - URL du service VMware<br> **name** - Nom du cluster VMware|<| |vmware.datastore.discovery\[\<url\>\]|<|<|<|<| |<|Découverte des datastores VMware.|Objet JSON|**url** - URL du service VMware|<| |vmware.datastore.hv.list\[\<url\>,\<datastore\>\]|<|<|<|<| |<|Liste des hyperviseurs de magasins de données.|Objet JSON|**url** - URL du service VMware<br>**datastore** - nom du magasin de données|<| |vmware.datastore.read\[\<url\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Durée d'une opération de lecture à partir du magasin de données (millisecondes).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**datastore** - nom du magasin de données<br>**mode** - latency (valeur moyenne, par défaut), maxlatency (valeur maximale)|<| |vmware.datastore.size\[\<url\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Espace de la banque de données VMware en octets ou en pourcentage du total.|Entier - pour les octets<br>Flottant - pour le pourcentage|**url** - URL du service VMware<br>**datastore** - nom de la banque de données<br> **mode** - valeurs possibles :<br>total (par défaut), free, pfree (libre, pourcentage), uncommitted|<| |vmware.datastore.write\[\<url\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Durée d'une opération d'écriture dans le magasin de données (millisecondes).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**datastore** - nom de la banque de données<br>**mode** - latency (valeur moyenne, par défaut), maxlatency (valeur maximale)|<| |vmware.dc.discovery\[\<url\>\]|<|<|<|<| |<|Découverte des datacenters VMware.|Objet JSON|**url** - URL du service VMware|<| |vmware.eventlog\[\<url\>,\<mode\>\]|<|<|<|<| |<|Journal des événements VMware.|Journal|**url** - URL du service VMware<br>**mode** - *all* (par défaut), *skip* - ignore le traitement des données plus anciennes|Il ne doit y en avoir qu'une vlé d'élément vmware.eventlog\[\] par URL.<br><br>Voir aussi : [exemple de filtrage](/manual/config/items/preprocessing/examples#filtering_vmware_event_log_records) Enregistrements du journal des événements VMware.| |vmware.fullname\[\<url\>\]|<|<|<|<| |<|Nom complet du service VMware.|Chaîne|**url** - URL du service VMware|<| |vmware.hv.cluster.name\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom du cluster de l'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom de l'hôte de l'hyperviseur VMware|<| |vmware.hv.cpu.usage\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation du processeur de l'hyperviseur VMware (Hz).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.cpu.usage.perf\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation du processeur de l'hyperviseur VMware en pourcentage pendant l'intervalle.|Flottant|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.cpu.utilization\[\<url\>,\<uuid\>\]|<|<|<|<| |<|L'utilisation du processeur de l'hyperviseur VMware en pourcentage pendant l'intervalle, dépend de la gestion de l'alimentation ou de HT.|Flottant|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.datacenter.name\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom du centre de données de l'hyperviseur VMware.|String|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.datastore.discovery\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Découverte des datastores de l'hyperviseur VMware.|Objet JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.datastore.list\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Liste des datastores de l'hyperviseur VMware.|Objet JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.datastore.multipath\[\<url\>,\<uuid\>,\<datastore\>,\<partitionid\>\]|<|<|<|<| |<|Nombre de chemins de magasins de données disponibles.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware<br>**datastore** - Nom du magasin de données<br>**partitionid** - ID interne du périphérique physique de vmware.hv.datastore.discovery|<| |vmware.hv.datastore.read\[\<url\>,\<uuid\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Durée moyenne d'une opération de lecture à partir du magasin de données (millisecondes).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware<br>**datastore** - Nom de la banque de données<br>**mode** - latency (par défaut)|<| |vmware.hv.datastore.size\[\<url\>,\<uuid\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Espace de la banque de données VMware en octets ou en pourcentage du total.|Entier - pour les octets<br>Flottant - pour le pourcentage|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware< br>**datastore** - nom du datastore<br>**mode** - valeurs possibles :<br>total (par défaut), free, pfree (libre, pourcentage), uncommitted|<| |vmware.hv.datastore.write\[\<url\>,\<uuid\>,\<datastore\>,\<mode\>\]|<|<|<|<| |<|Durée moyenne d'une opération d'écriture dans le datastore (millisecondes).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware<br>**datastore** - Nom de la banque de données<br>**mode** - latency (par défaut)|<| |vmware.hv.discovery\[\<url\>\]|<|<|<|<| |<|Découverte des hyperviseurs VMware.|Objet JSON|**url** - URL du service VMware|<| |vmware.hv.nomcomplet\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom de l'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.cpu.freq\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Fréquence du processeur de l'hyperviseur VMware (Hz).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.cpu.model\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Modèle de processeur de l'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.cpu.num\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nombre de cœurs de processeur sur l'hyperviseur VMware.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.cpu.threads\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nombre de threads de processeur sur l'hyperviseur VMware.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.memory\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille totale de la mémoire de l'hyperviseur VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.model\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Modèle d'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.uuid\[\<url\>,\<uuid\>\]|<|<|<|<| |<|UUID du BIOS de l'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.hw.vendor\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom du fournisseur de l'hyperviseur VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom de l'hôte de l'hyperviseur VMware|<| |vmware.hv.maintenance\[\<url\>,\<uuid\>\]|<|<|<|<| |<|État de maintenance de l'hyperviseur VMware.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|Renvoie '0' - pas en maintenance ou '1' - en maintenance| |vmware.hv.memory.size.ballooned\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille mémoire gonflée de l'hyperviseur VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.memory.used\[\<url\>,\<uuid\>\]|<|<|<|<| |<|L'hyperviseur VMware a utilisé la taille de la mémoire (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.network.in\[\<url\>,\<uuid\>,\<mode\>\]|<|<|<|<| |<|Statistiques d'entrée réseau de l'hyperviseur VMware (octets par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - VMware nom d'hôte de l'hyperviseur<br>**mode** - bps (par défaut)|<| |vmware.hv.network.out\[\<url\>,\<uuid\>,\<mode\>\]|<|<|<|<| |<|Statistiques de sortie du réseau de l'hyperviseur VMware (octets par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - VMware nom d'hôte de l'hyperviseur<br>**mode** - bps (par défaut)|<| |vmware.hv.perfcounter\[\<url\>,\<uuid\>,\<path\>,\<instance\>\]|<|<|<|<| |<|Valeur du compteur de performances de l'hyperviseur VMware.|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware<br>**path** - chemin du compteur de performances ^**[1](vmware_keys#footnotes)**^<br>**instance** - instance du compteur de performances. Utiliser une instance vide pour les valeurs agrégées (par défaut)|<| |vmware.hv.power\[\<url\>,\<uuid\>,\<max\>\]|<|<|<|<| |<|Consommation d'énergie de l'hyperviseur VMware (W).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware<br>**max** - Consommation d'énergie maximale autorisée| <| |vmware.hv.sensor.health.state\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Capteur de cumul de l'état de santé de l'hyperviseur VMware.|Entier :<br>0 - gris ;<br>1 - vert ;<br>2 - jaune ;<br>3 - rouge|**url** - URL du service VMware <br>**uuid** - Nom d'hôte de l'hyperviseur VMware|L'élément peut ne pas fonctionner dans VMware vSphere 6.5 et versions ultérieures, car VMware a déprécié le capteur *VMware Rollup Health State*. | |vmware.hv.sensors.get\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Capteurs d'état du fournisseur matériel de l'hyperviseur VMware.|JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.status\[\<url\>,\<uuid\>\]|<|<|<|<| |<|État de l'hyperviseur VMware.|Entier :<br>0 - gris ;<br>1 - vert ;<br>2 - jaune ;<br>3 - rouge|**url** - URL du service VMware<br> **uuid** - Nom d'hôte de l'hyperviseur VMware|Utilise la propriété d'état général du système hôte.| |vmware.hv.uptime\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Temps de disponibilité de l'hyperviseur VMware (secondes).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.version\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Version de l'hyperviseur VMware.|String|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l'hyperviseur VMware|<| |vmware.hv.vm.num\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nombre de machines virtuelles sur l'hyperviseur VMware.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de l\'hyperviseur VMware|<| |vmware.version\[\<url\>\]|<|<|<|<| |<|Version du service VMware.|Chaîne|**url** - URL du service VMware|<| |vmware.vm.cluster.name\[\<url\>,\<uuid>\]|<|<|<|<| |<|Nom de la machine virtuelle VMware.|String|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.cpu.latency\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Pourcentage de temps pendant lequel la machine virtuelle est incapable de s'exécuter car elle est en conflit pour accéder au(x) CPU physique(s).|Flottant|**url** - URL du service VMware<br>**uuid** - VMware virtuel nom d'hôte de la machine|<| |vmware.vm.cpu.num\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nombre de processeurs sur la machine virtuelle VMware.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.cpu.readiness\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Pourcentage de temps pendant lequel la machine virtuelle était prête, mais n'a pas pu être planifiée pour s'exécuter sur le CPU physique.|Float|**url** - URL du service VMware<br>**uuid** - Hôte de la machine virtuelle VMware nom<br>**instance** - instance CPU|<| |vmware.vm.cpu.ready\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Durée (en millisecondes) pendant laquelle la machine virtuelle était prête, mais n'a pas pu être planifiée pour s'exécuter sur le CPU physique. Le temps de disponibilité du processeur dépend du nombre de machines virtuelles sur l'hôte et de leurs charges de processeur (%).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br >**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.cpu.swapwait\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Pourcentage de temps CPU passé à attendre l'échange.|Flottant|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance CPU|<| |vmware.vm.cpu.usage\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation du processeur de la machine virtuelle VMware (Hz).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.cpu.usage.perf\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation du processeur de la machine virtuelle VMware en pourcentage pendant l'intervalle.|Flottant|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.datacenter.name\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom du centre de données de la machine virtuelle VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.discovery\[\<url\>\]|<|<|<|<| |<|Découverte des machines virtuelles VMware.|Objet JSON|**url** - URL du service VMware|<| |vmware.vm.guest.memory.size.swapped\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Quantité de mémoire physique de l'invité qui est échangée vers l'espace d'échange (Ko).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.guest.osuptime\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Temps total écoulé depuis le dernier démarrage du système d'exploitation (en secondes).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.hv.name\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Nom de l'hyperviseur de la machine virtuelle VMware.|Chaîne|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille totale de la mémoire de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.ballooned\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille mémoire gonflée de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.compressed\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille de la mémoire compressée de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.consumed\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Quantité de mémoire physique de l'hôte consommée pour la sauvegarde des pages de mémoire physique de l'invité (Ko).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.private\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille de la mémoire privée de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.shared\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille de la mémoire partagée de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.swapped\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Taille de la mémoire échangée de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.usage.guest\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation de la mémoire de l'invité de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.size.usage.host\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Utilisation de la mémoire de l'hôte de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom de l'hôte de la machine virtuelle VMware|<| |vmware.vm.memory.usage\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Pourcentage de mémoire physique de l'hôte qui a été consommée.|Flottant|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.net.if.discovery\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Découverte des interfaces réseau des machines virtuelles VMware.|Objet JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.net.if.in\[\<url\>,\<uuid\>,\<instance\>,\<mode\>\]|<|<|<|<| |<|Statistiques d'entrée de l'interface réseau de la machine virtuelle VMware (octets/paquets par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de l'interface réseau<br>**mode** - bps (par défaut)/pps - octets/paquets par seconde|<| |vmware.vm.net.if.out\[\<url\>,\<uuid\>,\<instance\>,\<mode\>\]|<|<|<|<| |<|Statistiques de sortie de l'interface réseau de la machine virtuelle VMware (octets/paquets par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** \- instance de l'interface réseau<br>**mode** - bps (par défaut)/pps - octets/paquets par seconde|<| |vmware.vm.net.if.usage\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Utilisation du réseau de la machine virtuelle VMware (taux de transmission et de réception combinés) pendant l'intervalle (Ko/s).|Entier|**url** - URL du service VMware<br>**uuid** - Hôte de la machine virtuelle VMware nom<br>**instance** - instance d'interface réseau|<| |vmware.vm.perfcounter\[\<url\>,\<uuid\>,\<path\>,\<instance\>\]|<|<|<|<| |<|Valeur du compteur de performances de la machine virtuelle VMware.|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware <br>**path** - chemin du compteur de performances ^**[1](vmware_keys#footnotes)**^<br>**instance** - instance du compteur de performances. Utiliser une instance vide pour les valeurs agrégées (par défaut)|<| |vmware.vm.powerstate\[\<url\>,\<uuid\>\]|<|<|<|<| |<|État d'alimentation de la machine virtuelle VMware.|Entier :<br>0 - mis hors tension ;<br>1 - sous tension ;<br>2 - suspendu|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.storage.committed\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Espace de stockage dédié de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.storage.readoio\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Nombre moyen de demandes de lecture en attente sur le disque virtuel pendant l'intervalle de collecte.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque (obligatoire)|<| |vmware.vm.storage.totalreadlatency\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Durée moyenne d'une lecture à partir du disque virtuel (millisecondes).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque (obligatoire)|<| |vmware.vm.storage.totalwritelatency\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Durée moyenne d'une écriture sur le disque virtuel (millisecondes).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque (obligatoire)|<| |vmware.vm.storage.uncommitted\[<url>,<uuid>\]|<|<|<|<| |<|Espace de stockage non engagé de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.storage.unshared\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Espace de stockage non partagé de la machine virtuelle VMware (octets).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.storage.writeoio\[\<url\>,\<uuid\>,\<instance\>\]|<|<|<|<| |<|Nombre moyen de demandes d'écriture en attente sur le disque virtuel pendant l'intervalle de collecte.|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque (obligatoire)|<| |vmware.vm.uptime\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Temps de disponibilité de la machine virtuelle VMware (secondes).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.vfs.dev.discovery\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Découverte des périphériques de disque de la machine virtuelle VMware.|Objet JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|<| |vmware.vm.vfs.dev.read\[\<url\>,\<uuid\>,\<instance\>,\<mode\>\]|<|<|<|<| |<|Statistiques de lecture du périphérique de disque de la machine virtuelle VMware (octets/opérations par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid ** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque<br>**mode** - bps (par défaut)/ops - octets/opérations par seconde|<| |vmware.vm.vfs.dev.write\[\<url\>,\<uuid\>,\<instance\>,\<mode\>\]|<|<|<|<| |<|Statistiques d'écriture du périphérique de disque de la machine virtuelle VMware (octets/opérations par seconde).|Entier ^**[2](vmware_keys#footnotes)**^|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**instance** - instance de périphérique de disque<br>**mode** - bps (par défaut)/ops - octets/opérations par seconde|<| |vmware.vm.vfs.fs.discovery\[\<url\>,\<uuid\>\]|<|<|<|<| |<|Découverte des systèmes de fichiers de la machine virtuelle VMware.|Objet JSON|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware|VMware Tools doit être installé sur la machine virtuelle invitée. | |vmware.vm.vfs.fs.size\[\<url\>,\<uuid\>,\<fsname\>,\<mode\>\]|<|<|<|<| |<|Statistiques du système de fichiers de la machine virtuelle VMware (octets/pourcentages).|Entier|**url** - URL du service VMware<br>**uuid** - Nom d'hôte de la machine virtuelle VMware<br>**fsname** - nom du système de fichiers<br>**mode** - total/free/used/pfree/pused|VMware Tools doit être installé sur la machine virtuelle invitée.| #### Item key The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is net.if.discovery This item is supported since Zabbix agent 2.0. #### Clé d'élément La clé d'élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#discovery_rule) est net.if.discovery Cet élément est pris en charge depuis l'agent Zabbix 2.0. #### Item key The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is system.cpu.discovery This item is supported since Zabbix agent 2.4. #### Clé d'élément a clé d’élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#discovery_rule) est system.cpu.discovery Cet élément est pris en charge depuis l'agent Zabbix 2.4. #### Item key The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is vfs.dev.discovery This item is supported on Linux platforms only, since Zabbix agent 4.4. You may create discovery rules using this discovery item and: - filter: **{\#DEVNAME} matches `sd[\D]$`** - to discover devices named "sd0", "sd1", "sd2", ... - filter: **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match `^loop.*`** - to discover disk type devices whose name does not start with "loop" #### Clé d'élément La clé d'élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#discovery_rule) est ``` vfs.dev.discovery ``` Cet élément est pris en charge sur les plateformes Linux uniquement, depuis l'agent Zabbix 4.4. Vous pouvez créer des règles de découverte à l'aide de cet élément de découverte et : - filtre : **{\#DEVNAME} matches `sd[\D]$`** - pour découvrir les périphériques nommés "sd0", "sd1", "sd2", ... - filtre : **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match `^loop.*`** - pour découvrir les périphériques de type disque dont le nom ne commence pas par "loop" #### Item key The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is service.discovery This item is supported since Zabbix Windows agent 3.0. #### Clé d'élément L'élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#discovery_rule) est ``` service.discovery ``` Cet élément est supporté depuis l'agent Windows Zabbix 3.0. ### Item key The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the systemd.unit.discovery ::: noteimportant This [item](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) key is only supported in Zabbix agent 2. ::: This item returns a JSON with information about systemd units, for example: [{ "{#UNIT.NAME}": "mysqld.service", "{#UNIT.DESCRIPTION}": "MySQL Server", "{#UNIT.LOADSTATE}": "loaded", "{#UNIT.ACTIVESTATE}": "active", "{#UNIT.SUBSTATE}": "running", "{#UNIT.FOLLOWED}": "", "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice", "{#UNIT.JOBID}": 0, "{#UNIT.JOBTYPE}": "", "{#UNIT.JOBPATH}": "/", "{#UNIT.UNITFILESTATE}": "enabled" }, { "{#UNIT.NAME}": "systemd-journald.socket", "{#UNIT.DESCRIPTION}": "Journal Socket", "{#UNIT.LOADSTATE}": "loaded", "{#UNIT.ACTIVESTATE}": "active", "{#UNIT.SUBSTATE}": "running", "{#UNIT.FOLLOWED}": "", "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket", "{#UNIT.JOBID}": 0, "{#UNIT.JOBTYPE}": "", "{#UNIT.JOBPATH}": "/", "{#UNIT.UNITFILESTATE}": "enabled" }] ### Clé d'élément L'élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#discovery_rule) est systemd.unit.discovery ::: noteimportant Cette clé d'[élément](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) n'est prise en charge que dans l'agent Zabbix 2. ::: Cet élément renvoie un JSON avec des informations sur les unités systemd, par exemple : [{ "{#UNIT.NAME}": "mysqld.service", "{#UNIT.DESCRIPTION}": "MySQL Server", "{#UNIT.LOADSTATE}": "loaded", "{#UNIT.ACTIVESTATE}": "active", "{#UNIT.SUBSTATE}": "running", "{#UNIT.FOLLOWED}": "", "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice", "{#UNIT.JOBID}": 0, "{#UNIT.JOBTYPE}": "", "{#UNIT.JOBPATH}": "/", "{#UNIT.UNITFILESTATE}": "enabled" }, { "{#UNIT.NAME}": "systemd-journald.socket", "{#UNIT.DESCRIPTION}": "Journal Socket", "{#UNIT.LOADSTATE}": "loaded", "{#UNIT.ACTIVESTATE}": "active", "{#UNIT.SUBSTATE}": "running", "{#UNIT.FOLLOWED}": "", "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket", "{#UNIT.JOBID}": 0, "{#UNIT.JOBTYPE}": "", "{#UNIT.JOBPATH}": "/", "{#UNIT.UNITFILESTATE}": "enabled" }] #### Item key The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the zabbix[host,discovery,interfaces] internal item. This item is supported since Zabbix server 3.4. This item returns a JSON with the description of interfaces, including: - IP address/DNS hostname (depending on the “Connect to” host setting) - Port number - Interface type (Zabbix agent, SNMP, JMX, IPMI) - If it is the default interface or not - If the bulk request feature is enabled - for SNMP interfaces only. For example: [{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}] With multiple interfaces their records in JSON are ordered by: - Interface type, - Default - the default interface is put before non-default interfaces, - Interface ID (in ascending order). #### Clé d'élément L'élément à utiliser dans la [règle de découverte](/manual/discovery/low_level_discovery#regle-de-decouverte) est l'élément interne ``` zabbix[host,discovery,interfaces] ``` Cet élément est supporté depuis le serveur Zabbix 3.4. Cet élément renvoie un JSON avec la description des interfaces, notamment : - Adresse IP/nom d'hôte DNS (selon le paramètre d'hôte "Connecter à") - Numéro de port - Type d'interface (agent Zabbix, SNMP, JMX, IPMI) - Si c'est l'interface par défaut ou non - Si la fonctionnalité de requête de masse est activée - pour les interfaces SNMP uniquement. Par exemple : ``` {"data":[{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}]} ``` Avec plusieurs interfaces, leurs enregistrements en JSON sont classés par : - Type d'interface, - Défaut - l'interface par défaut est placée avant les interfaces autres que celles par défaut, - ID d'interface (dans l'ordre croissant). #### Item key Unlike with file system and network interface discovery, the item does not necessarily has to have an "snmp.discovery" key - item type of SNMP agent is sufficient. To configure the discovery rule, do the following: - Go to: *Configuration* → *Templates* - Click on *Discovery* in the row of an appropriate template  - Click on *Create discovery rule* in the upper right corner of the screen - Fill in the discovery rule form with the required details as in the screenshot below  All mandatory input fields are marked with a red asterisk. The OIDs to discover are defined in SNMP OID field in the following format: `discovery[{#MACRO1}, oid1, {#MACRO2}, oid2, …,]` where *{\#MACRO1}*, *{\#MACRO2}* … are valid lld macro names and *oid1*, *oid2*... are OIDs capable of generating meaningful values for these macros. A built-in macro *{\#SNMPINDEX}* containing index of the discovered OID is applied to discovered entities. The discovered entities are grouped by *{\#SNMPINDEX}* macro value. To understand what we mean, let us perform few snmpwalks on our switch: $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifDescr IF-MIB::ifDescr.1 = STRING: WAN IF-MIB::ifDescr.2 = STRING: LAN1 IF-MIB::ifDescr.3 = STRING: LAN2 $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifPhysAddress IF-MIB::ifPhysAddress.1 = STRING: 8:0:27:90:7a:75 IF-MIB::ifPhysAddress.2 = STRING: 8:0:27:90:7a:76 IF-MIB::ifPhysAddress.3 = STRING: 8:0:27:2b:af:9e And set SNMP OID to: `discovery[{#IFDESCR}, ifDescr, {#IFPHYSADDRESS}, ifPhysAddress]` Now this rule will discover entities with {\#IFDESCR} macros set to **WAN**, **LAN1** and **LAN2**, {\#IFPHYSADDRESS} macros set to **8:0:27:90:7a:75**, **8:0:27:90:7a:76**, and **8:0:27:2b:af:9e**, {\#SNMPINDEX} macros set to the discovered OIDs indexes **1**, **2** and **3**: ``` {.java} [ { "{#SNMPINDEX}": "1", "{#IFDESCR}": "WAN", "{#IFPHYSADDRESS}": "8:0:27:90:7a:75" }, { "{#SNMPINDEX}": "2", "{#IFDESCR}": "LAN1", "{#IFPHYSADDRESS}": "8:0:27:90:7a:76" }, { "{#SNMPINDEX}": "3", "{#IFDESCR}": "LAN2", "{#IFPHYSADDRESS}": "8:0:27:2b:af:9e" } ] ``` If an entity does not have the specified OID, then the corresponding macro will be omitted for this entity. For example if we have the following data: ifDescr.1 "Interface #1" ifDescr.2 "Interface #2" ifDescr.4 "Interface #4" ifAlias.1 "eth0" ifAlias.2 "eth1" ifAlias.3 "eth2" ifAlias.5 "eth4" Then in this case SNMP discovery `discovery[{#IFDESCR}, ifDescr, {#IFALIAS}, ifAlias]` will return the following structure: ``` {.java} [ { "{#SNMPINDEX}": 1, "{#IFDESCR}": "Interface #1", "{#IFALIAS}": "eth0" }, { "{#SNMPINDEX}": 2, "{#IFDESCR}": "Interface #2", "{#IFALIAS}": "eth1" }, { "{#SNMPINDEX}": 3, "{#IFALIAS}": "eth2" }, { "{#SNMPINDEX}": 4, "{#IFDESCR}": "Interface #4" }, { "{#SNMPINDEX}": 5, "{#IFALIAS}": "eth4" } ] ``` #### Clé d'élément Contrairement à la découverte du système de fichiers et de l'interface réseau, l'élément n'a pas nécessairement besoin d'une clé "snmp.discovery" - le type d'élément agent SNMP est suffisant. Pour configurer la règle de découverte, procéder comme suit : - Aller dans : *Configuration* → *Modèles* - Cliquer sur *Découverte* sur la ligne du modèle approprié  - Cliquer sur *Créer une règle de découverte* dans le coin supérieur droit de l'écran. - Remplissez le formulaire de règle de découverte avec les détails requis comme dans la capture d'écran ci-dessous  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. Les OID à découvrir sont définis dans le champ SNMP OID au format suivant : `discovery[{#MACRO1}, oid1, {#MACRO2}, oid2, ...,]` où *{#MACRO1}*, *{#MACRO2}* ... sont des noms de macro lld valides et *oid1*, *oid2*... sont des OID capables de générer des valeurs significatives pour ces macros. Une macro intégrée *{#SNMPINDEX}* contenant l'index de l'OID découvert est appliquée aux entités découvertes. Les entités découvertes sont regroupées par la valeur de macro *{#SNMPINDEX}*. Pour comprendre ce que nous voulons dire, exécutons quelques commandes snmpwalks sur notre switch : $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifDescr IF-MIB::ifDescr.1 = STRING: WAN IF-MIB::ifDescr.2 = STRING: LAN1 IF-MIB::ifDescr.3 = STRING: LAN2 $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifPhysAddress IF-MIB::ifPhysAddress.1 = STRING: 8:0:27:90:7a:75 IF-MIB::ifPhysAddress.2 = STRING: 8:0:27:90:7a:76 IF-MIB::ifPhysAddress.3 = STRING: 8:0:27:2b:af:9e Et définissons l'OID SNMP sur : `discovery[{#IFDESCR}, ifDescr, {#IFPHYSADDRESS}, ifPhysAddress]` Cette règle détecte désormais les entités avec les macros {#IFDESCR} définies sur **WAN**, **LAN1** et **LAN2**, les macros {#IFPHYSADDRESS} sont définies sur **8:0:27:90:7a:75**, **8:0:27:90:7a:76**, et **8:0:27:2b:af:9e**, les macros {#SNMPINDEX} sont définies sur les index OID découverts **1**, **2** and **3** : ``` {.java} [ { "{#SNMPINDEX}": "1", "{#IFDESCR}": "WAN", "{#IFPHYSADDRESS}": "8:0:27:90:7a:75" }, { "{#SNMPINDEX}": "2", "{#IFDESCR}": "LAN1", "{#IFPHYSADDRESS}": "8:0:27:90:7a:76" }, { "{#SNMPINDEX}": "3", "{#IFDESCR}": "LAN2", "{#IFPHYSADDRESS}": "8:0:27:2b:af:9e" } ] ``` Si une entité ne possède pas l'OID spécifié, la macro correspondante sera omise pour cette entité. Par exemple si nous avons les données suivantes : ifDescr.1 "Interface #1" ifDescr.2 "Interface #2" ifDescr.4 "Interface #4" ifAlias.1 "eth0" ifAlias.2 "eth1" ifAlias.3 "eth2" ifAlias.5 "eth4" Dans ce cas, la découverte SNMP de `discovery[{#IFDESCR}, ifDescr, {#IFALIAS}, ifAlias]` renverra la structure suivante : ``` {.java} [ { "{#SNMPINDEX}": 1, "{#IFDESCR}": "Interface #1", "{#IFALIAS}": "eth0" }, { "{#SNMPINDEX}": 2, "{#IFDESCR}": "Interface #2", "{#IFALIAS}": "eth1" }, { "{#SNMPINDEX}": 3, "{#IFALIAS}": "eth2" }, { "{#SNMPINDEX}": 4, "{#IFDESCR}": "Interface #4" }, { "{#SNMPINDEX}": 5, "{#IFALIAS}": "eth4" } ] ``` #### Item net.tcp.service parameters **ftp** Creates a TCP connection and expects the first 4 characters of the response to be "220 ", then sends "QUIT\\r\\n". Default port 21 is used if not specified. **http** Creates a TCP connection without expecting and sending anything. Default port 80 is used if not specified. **https** Uses (and only works with) libcurl, does not verify the authenticity of the certificate, does not verify the host name in the SSL certificate, only fetches the response header (HEAD request). Default port 443 is used if not specified. **imap** Creates a TCP connection and expects the first 4 characters of the response to be "\* OK", then sends "a1 LOGOUT\\r\\n". Default port 143 is used if not specified. **ldap** Opens a connection to an LDAP server and performs an LDAP search operation with filter set to (objectClass=\*). Expects successful retrieval of the first attribute of the first entry. Default port 389 is used if not specified. **nntp** Creates a TCP connection and expects the first 3 characters of the response to be "200" or "201", then sends "QUIT\\r\\n". Default port 119 is used if not specified. **pop** Creates a TCP connection and expects the first 3 characters of the response to be "+OK", then sends "QUIT\\r\\n". Default port 110 is used if not specified. **smtp** Creates a TCP connection and expects the first 3 characters of the response to be "220", followed by a space, the line ending or a dash. The lines containing a dash belong to a multiline response and the response will be re-read until a line without the dash is received. Then sends "QUIT\\r\\n". Default port 25 is used if not specified. **ssh** Creates a TCP connection. If the connection has been established, both sides exchange an identification string (SSH-major.minor-XXXX), where major and minor are protocol versions and XXXX is a string. Zabbix checks if the string matching the specification is found and then sends back the string "SSH-major.minor-zabbix\_agent\\r\\n" or "0\\n" on mismatch. Default port 22 is used if not specified. **tcp** Creates a TCP connection without expecting and sending anything. Unlike the other checks requires the port parameter to be specified. **telnet** Creates a TCP connection and expects a login prompt (':' at the end). Default port 23 is used if not specified. #### Paramètres de l'élément net.tcp.service **ftp** Crée une connexion TCP et attend que les 4 premiers caractères de la réponse soient "220 ", puis envoie "QUIT\\r\\n". Le port 21 par défaut est utilisé s'il n'est pas spécifié. **http** Crée une connexion TCP sans rien attendre ni rien envoyer. Le port par défaut 80 est utilisé s'il n'est pas spécifié. **https** Utilise (et fonctionne uniquement avec) libcurl, ne vérifie pas l'authenticité du certificat, ne vérifie pas le nom d'hôte dans le certificat SSL, récupère uniquement l'en-tête de la réponse (requête HEAD). Le port par défaut 443 est utilisé s'il n'est pas spécifié. **imap** Crée une connexion TCP et s’attend à ce que les 4 premiers caractères de la réponse soient "\* OK", puis envoie "a1 LOGOUT\\r\\n". Le port par défaut 143 est utilisé s'il n'est pas spécifié. **ldap** Ouvre une connexion à un serveur LDAP et effectue une opération de recherche LDAP avec le filtre défini sur (objectClass=\*). Attend une récupération réussie du premier attribut de la première entrée. Le port par défaut 389 est utilisé s'il n'est pas spécifié. **nntp** Crée une connexion TCP et s'attend à ce que les 3 premiers caractères de la réponse soient "200" ou "201", puis envoie "QUIT\\r\\n". Le port par défaut 119 est utilisé s'il n'est pas spécifié. **pop** Crée une connexion TCP et s'attend à ce que les 3 premiers caractères de la réponse soient "+OK", puis envoie "QUIT\\r\\n". Le port par défaut 110 est utilisé s'il n'est pas spécifié. **smtp** Creates a TCP connection and expects the first 3 characters of the response to be "220", followed by a space, the line ending or a dash. The lines containing a dash belong to a multiline response and the response will be re-read until a line without the dash is received. Then sends "QUIT\\r\\n". Default port 25 is used if not specified. **ssh** Crée une connexion TCP. Si la connexion a été établie, les deux côtés échangent une chaîne d'identification (SSH-major.minor-XXXX), où major et minor sont des versions de protocole et XXXX est une chaîne. Zabbix vérifie si la chaîne correspondant à la spécification est trouvée, puis renvoie la chaîne "SSH-major.minor-zabbix\_agent\\r\\n" ou "0\\n" en cas de non concordance. Le port par défaut 22 est utilisé s'il n'est pas spécifié. **tcp** Crée une connexion TCP sans rien attendre ni rien envoyer. Contrairement aux autres vérifications, le paramètre de port doit être spécifié. **telnet** Crée une connexion TCP et attend une invite de connexion (':' à la fin). Le port par défaut 23 est utilisé s'il n'est pas spécifié. #### Item net.udp.service parameters **ntp** Sends an SNTP packet over UDP and validates the response according to [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5). Default port 123 is used if not specified. #### Paramètres de l'élément net.udp.service **ntp** Envoie un paquet SNTP sur UDP et valide la réponse conformément à la [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5). Le port par défaut 123 est utilisé s'il n'est pas spécifié. ### Item ::: noteclassic Web items cannot be directly created, updated or deleted via the Zabbix API. ::: The item object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the item.| |**delay**<br>(required)|string|Update interval of the item. Accepts seconds or a time unit with suffix (30s,1m,2h,1d).<br>Optionally one or more [custom intervals](/manual/config/items/item/custom_intervals) can be specified either as flexible intervals or scheduling.<br>Multiple intervals are separated by a semicolon.<br>User macros may be used. A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Flexible intervals may be written as two macros separated by a forward slash (e.g. `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host or template that the item belongs to.<br><br>For update operations this field is *readonly*.| |**interfaceid**<br>(required)|string|ID of the item's host interface.<br><br>Used only for host items. Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, calculated, dependent, database monitor and script items. Optional for HTTP agent items.| |**key\_**<br>(required)|string|Item key.| |**name**<br>(required)|string|Name of the item.| |**type**<br>(required)|integer|Type of the item.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - Simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>9 - Web item;<br>10 - External check;<br>11 - Database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - Telnet agent;<br>15 - Calculated;<br>16 - JMX agent;<br>17 - SNMP trap;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script| |**url**<br>(required)|string|URL string, required only for HTTP agent item type. Supports user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(required)|integer|Type of information of the item.<br><br>Possible values:<br>0 - numeric float;<br>1 - character;<br>2 - log;<br>3 - numeric unsigned;<br>4 - text.| |allow\_traps|integer|HTTP agent item field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent items or HTTP agent items.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM<br>3 - Kerberos| |description|string|Description of the item.| |error|string|*(readonly)* Error text if there are problems updating the item.| |flags|integer|*(readonly)* Origin of the item.<br><br>Possible values:<br>0 - a plain item;<br>4 - a discovered item.| |follow\_redirects|integer|HTTP agent item field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent item field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |history|string|A time unit of how long the history data should be stored. Also accepts user macro.<br><br>Default: 90d.| |http\_proxy|string|HTTP agent item field. HTTP(S) proxy connection string.| |inventory\_link|integer|ID of the host inventory field that is populated by the item.<br><br>Refer to the [host inventory page](/manual/api/reference/host/object#host_inventory) for a list of supported host inventory fields and their IDs.<br><br>Default: 0.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI items.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lastclock|timestamp|*(readonly)* Time when the item was last updated.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |lastns|integer|*(readonly)* Nanoseconds when the item was last updated.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |lastvalue|string|*(readonly)* Last value of the item.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |logtimefmt|string|Format of the time in log entries. Used only by log items.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and maximum count of dependent items equal to 29999 are allowed.<br><br>Required by dependent items.| |output\_format|integer|HTTP agent item field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the item:<br>- executed script for SSH and Telnet items;<br>- SQL query for database monitor items;<br>- formula for calculated items;<br>- the script for script item.| |parameters|array|Additional parameters for script items. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent items.<br>When used by JMX, username should also be specified together with password or both properties should be left blank.| |post\_type|integer|HTTP agent item field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent item field. HTTP(S) request body data. Used with post\_type.| |prevvalue|string|*(readonly)* Previous value of the item.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent item field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent item field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent item field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent item field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent item field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent item field. Password for SSL Key file.| |state|integer|*(readonly)* State of the item.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - not supported.| |status|integer|Status of the item.<br><br>Possible values:<br>0 - *(default)* enabled item;<br>1 - disabled item.| |status\_codes|string|HTTP agent item field. Ranges of required HTTP status codes separated by commas. Also supports user macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template item.<br><br>*Hint*: Use the `hostid` property to specify the template that the item belongs to.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script items. Supports user macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper items or HTTP agent items.| |trends|string|A time unit of how long the trends data should be stored. Also accepts user macro.<br><br>Default: 365d.| |units|string|Value units.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent items.<br><br>Required by SSH and Telnet items.<br>When used by JMX, password should also be specified together with username or both properties should be left blank.| |uuid|string|Universal unique identifier, used for linking imported item to already existing ones. Used only for items on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |valuemapid|string|ID of the associated value map.| |verify\_host|integer|HTTP agent item field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |verify\_peer|integer|HTTP agent item field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Élément ::: noteclassic Les éléments Web ne peuvent pas être directement créés, mis à jour ou supprimés via l'API Zabbix. ::: L'objet élément possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(lecture seule)* ID de l'élément.| |**delay**<br>(obligatoire)|string|Intervalle de mise à jour de l'élément. Accepte les secondes ou une unité de temps avec suffixe (30s, 1m, 2h, 1j).<br> En option, un ou plusieurs [intervalles personnalisés](/manual/config/items/item/custom_intervals) peuvent être spécifiés soit comme intervalles flexibles, soit comme planification .<br>Plusieurs intervalles sont séparés par un point-virgule.<br>Des macros utilisateur peuvent être utilisées. Une seule macro doit remplir tout le champ. Les macros multiples dans un champ ou les macros mélangées avec du texte ne sont pas prises en charge.<br>Les intervalles flexibles peuvent être écrits sous la forme de deux macros séparées par une barre oblique (par exemple, `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br >Facultatif pour le trappeur Zabbix, les éléments dépendants et pour l'agent Zabbix (actif) avec la clé `mqtt.get`.| |**hostid**<br>(obligatoire)|string|ID de l'hôte ou du modèle auquel appartient l'élément.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |**interfaceid**<br>(obligatoire)|string|ID de l'interface hôte de l'élément.<br><br>Utilisé uniquement pour les éléments hôtes. Non requis pour les éléments d'agent Zabbix (actif), Zabbix interne, trapper Zabbix, calculé, dépendant, moniteur de base de données et script. Facultatif pour les éléments d'agent HTTP.| |**key\_**<br>(obligatoire)|string|Clé de l'élément.| |**name**<br>(obligatoire)|string|Nom de l'élément.| |**type**<br>(obligatoire)|integer|Type de l'élément<br><br>Valeurs possibles :<br>0 - Agent Zabbix ;<br>2 - Trapper Zabbix ;<br>3 - Vérification simple ;<br>5 - Zabbix interne ;<br>7 - Agent Zabbix (actif) ;<br>9 - Élément Web ;<br>10 - Vérification externe ;<br>11 - Moniteur de base de données ;<br>12 - Agent IPMI ;<br>13 - Agent SSH ;<br>14 - Agent Telnet ;<br>15 - Calculé ;<br>16 - Agent JMX ;<br>17 - Interruption SNMP ;<br>18 - Élément dépendant ;<br>19 - Agent HTTP ;<br>20 - Agent SNMP ;<br>21 - Script| |**url**<br>(obligatoire)|string|Chaîne d'URL, requise uniquement pour le type d'élément d'agent HTTP. Prend en charge les macros utilisateur, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(obligatoire)|integer|Type d'information de l'élément.<br><br>Valeurs possibles :<br>0 - nombre flottant ;<br>1 - caractère ;<br>2 - journal ;<br>3 - numérique non signé ;<br>4 - texte.| |allow\_traps|integer|Champ d'élément d'agent HTTP. Autoriser également le remplissage de la valeur comme dans le type d'élément du trappeur.<br><br>0 - *(par défaut)* Ne pas autoriser l'acceptation des données entrantes.<br>1 - Autoriser l'acceptation des données entrantes.| |authtype|integer|Utilisé uniquement par les éléments d'agent SSH ou les éléments d'agent HTTP.<br><br>Valeurs possibles de la méthode d'authentification de l'agent SSH :<br>0 - mot de passe *(par défaut)* ;<br>1 - clé publique.<br><br> Valeurs possibles de la méthode d'authentification de l'agent HTTP :<br>0 - *(par défaut)* aucune<br>1 - de base<br>2 - NTLM<br>3 - Kerberos| |description|string|Description de l'élément.| |error|string|*(lecture seule)* Texte d'erreur en cas de problèmes de mise à jour de l'élément.| |flags|integer|*(lecture seule)* Origine de l'objet.<br><br>Valeurs possibles :<br>0 - un objet ordinaire ;<br>4 - un objet découvert.| |follow\_redirects|integer|Champ d'élément d'agent HTTP. Suivre les redirections de réponse tout en regroupant les données.<br><br>0 - Ne pas suivre les redirections.<br>1 - *(par défaut)* Suivre les redirections.| |headers|object|Champ d'élément d'agent HTTP. Objet avec en-têtes de requête HTTP(S), où le nom de l'en-tête est utilisé comme clé et la valeur de l'en-tête comme valeur.<br><br>Exemple :<br>{ "User-Agent": "Zabbix" }| |history|string|Une unité de temps indiquant combien de temps les données d'historique doivent être stockées. Accepte également les macros utilisateur.<br><br>Par défaut : 90d.| |http\_proxy|string|Champ d'élément d'agent HTTP. Chaîne de connexion proxy HTTP(S).| |inventory\_link|integer|ID du champ d'inventaire d'hôte rempli par l'élément.<br><br>Reportez-vous à la [page d'inventaire d'hôte](/manual/api/reference/host/object#host_inventory) pour obtenir la liste des champs d'inventaire d'hôte pris en charge et leurs identifiants.<br><br>Par défaut : 0.| |ipmi\_sensor|string|Capteur IPMI. Utilisé uniquement par les éléments IPMI.| |jmx\_endpoint|string|Chaîne de connexion personnalisée de l'agent JMX.<br><br>Valeur par défaut :<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN} :{HOST.PORT}/jmxrmi| |lastclock|timestamp|*(lecture seule)* Heure à laquelle l'élément a été mis à jour pour la dernière fois.<br><br>Par défaut, seules les valeurs des dernières 24 heures sont affichées. Vous pouvez prolonger cette période en modifiant la valeur du paramètre *Période d'affichage maximale de l'historique* dans la section de menu *[Administration → Général](/manual/web_interface/frontend_sections/administration/general#gui)*.| |lastns|integer|*(lecture seule)* Nanosecondes de la dernière mise à jour de l'élément.<br><br>Par défaut, seules les valeurs des dernières 24 heures sont affichées. Vous pouvez prolonger cette période en modifiant la valeur du paramètre *Période d'affichage maximale de l'historique* dans la section de menu *[Administration → Général](/manual/web_interface/frontend_sections/administration/general#gui)*.| |lastvalue|string|*(lecture seule)* Dernière valeur de l'élément.<br><br>Par défaut, seules les valeurs des dernières 24 heures sont affichées. Vous pouvez prolonger cette période en modifiant la valeur du paramètre *Période d'affichage maximale de l'historique* dans la section de menu *[Administration → Général](/manual/web_interface/frontend_sections/administration/general#gui)*.| |logtimefmt|string|Format de l'heure dans les entrées de journal. Utilisé uniquement par les éléments de journal.| |master\_itemid|integer|ID de l'élément principal.<br>La récursivité jusqu'à 3 éléments dépendants et le nombre maximal d'éléments dépendants égal à 29 999 sont autorisés.<br><br>Requis par les éléments dépendants.| |output\_format|integer|Champ d'élément d'agent HTTP. La réponse doit-elle être convertie en JSON.<br><br>0 - *(par défaut)* Stocker brut.<br>1 - Convertir en JSON.| |params|string|Paramètres supplémentaires en fonction du type d'élément :<br>- script exécuté pour les éléments SSH et Telnet ;<br>- requête SQL pour les éléments de surveillance de base de données ;<br>- formule pour les éléments calculés ;<br>- le script pour un élément script.| |parameters|array|Paramètres supplémentaires pour les éléments de script. Tableau d'objets avec les propriétés 'name' et 'value', où name doit être unique.| |password|string|Mot de passe pour l'authentification. Utilisé par vérification simple, SSH, Telnet, moniteur de base de données, éléments d'agent JMX et HTTP.<br>Lorsqu'il est utilisé par JMX, le nom d'utilisateur doit également être spécifié avec le mot de passe ou les deux propriétés doivent être laissées vides.| |post\_type|integer|Champ d'élément d'agent HTTP. Type de corps de données post stocké dans la propriété posts.<br><br>0 - *(par défaut)* Données brutes.<br>2 - Données JSON.<br>3 - Données XML.| |posts|string|Champ d'élément d'agent HTTP. Données du corps de la requête HTTP(S). Utilisé avec post\_type.| |prevvalue|string|*(lecture seule)* Valeur précédente de l'élément.<br><br>Par défaut, seules les valeurs des dernières 24 heures sont affichées. Vous pouvez prolonger cette période en modifiant la valeur du paramètre *Période d'affichage maximale de l'historique* dans la section de menu *[Administration → Général](/manual/web_interface/frontend_sections/administration/general#gui)*.| |privatekey|string|Nom du fichier de clé privée.| |publickey|string|Nom du fichier de clé publique.| |query\_fields|array|Champ d'élément d'agent HTTP. Paramètres de requête. Tableau d'objets avec des paires 'clé':'valeur', où la valeur peut être une chaîne vide.| |request\_method|integer|Champ d'élément d'agent HTTP. Type de méthode de requête.<br><br>0 - *(par défaut)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|Champ d'élément d'agent HTTP. Quelle partie de la réponse doit être stockée.<br><br>0 - *(par défaut)* Corps.<br>1 - En-têtes.<br>2 - Le corps et les en-têtes seront stockés.<br><br>Pour request\_method HEAD seul 1 est la valeur autorisée.| |snmp\_oid|string|OID SNMP.| |ssl\_cert\_file|string|Champ d'élément d'agent HTTP. Chemin d'accès au fichier de clé SSL publique.| |ssl\_key\_file|string|Champ d'élément d'agent HTTP. Chemin d'accès au fichier de clé SSL privée.| |ssl\_key\_password|string|Champ d'élément d'agent HTTP. Mot de passe pour le fichier de clé SSL.| |state|integer|*(lecture seule)* État de l'élément.<br><br>Valeurs possibles :<br>0 - *(par défaut)* normal ;<br>1 - non pris en charge.| |status|integer|Statut de l'élément.<br><br>Valeurs possibles :<br>0 - élément activé *(par défaut)* ;<br>1 - élément désactivé.| |status\_codes|string|Champ d'élément d'agent HTTP. Plages de codes d'état HTTP requis séparés par des virgules. Prend également en charge les macros utilisateur dans le cadre d'une liste séparée par des virgules.<br><br>Exemple : 200,200-{$M},{$M},200-400| |templateid|string|(lecture seule) ID de l'élément du modèle parent.<br><br>*Conseil* : utilisez la propriété `hostid` pour spécifier le modèle auquel appartient l'élément.| |timeout|string|Délai d'expiration de la demande d'interrogation des données d'élément. Utilisé pour l'agent HTTP et les éléments de script. Prend en charge les macros utilisateur.<br><br>par défaut : 3s<br>valeur maximale : 60s| |trapper\_hosts|string|Hôtes autorisés. Utilisé par les éléments de trappeur ou les éléments d'agent HTTP.| |trends|string|Une unité de temps de combien de temps les données de tendances doivent être stockées. Accepte également les macros utilisateur.<br><br>Par défaut : 365d.| |units|string|Unités de valeur.| |username|string|Nom d'utilisateur pour l'authentification. Utilisé par simple vérification, SSH, Telnet, moniteur de base de données, éléments d'agent JMX et HTTP.<br><br>Requis par les éléments SSH et Telnet.<br>Lorsqu'il est utilisé par JMX, le mot de passe doit également être spécifié avec le nom d'utilisateur ou les deux propriétés doit rester vide.| |uuid|string|Identifiant unique universel, utilisé pour lier un élément importé à des éléments déjà existants. Utilisé uniquement pour les éléments de modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |valuemapid|string|ID de la table. de correspondance de valeurs associée.| |verify\_host|integer|Champ d'élément d'agent HTTP. Valider que le nom d'hôte dans l'URL se trouve dans le champ Nom commun ou dans un champ Autre nom du sujet du certificat d'hôte.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| |verify\_peer|integer|Champ d'élément d'agent HTTP. Valider si le certificat de l'hôte est authentique.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # itemprototype.create # itemprototype.create # itemprototype.delete # itemprototype.delete # itemprototype.get # itemprototype.get #### Item prototypes The following screenshot illustrates how we can use these macros in item prototypes:  You can create as many item prototypes as needed: {width="600"} #### Prototypes d'élément La capture d'écran suivante illustre comment nous pouvons utiliser ces macros dans les prototypes d'éléments :  Vous pouvez créer autant de prototypes d'articles que nécessaire : {width="600"} ### Item prototype tag The item prototype tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Item prototype tag name.| |value|string|Item prototype tag value.| ### Tag de prototype d'élément L'objet de tag de prototype d'élément a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nom du tag du prototype d'élément.| |value|string|Valeur du tag du prototype d'élément.| ### Item prototype The item prototype object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the item prototype.| |**delay**<br>(required)|string|Update interval of the item prototype. Accepts seconds or a time unit with suffix (30s,1m,2h,1d).<br>Optionally one or more [custom intervals](/manual/config/items/item/custom_intervals) can be specified either as flexible intervals or scheduling.<br>Multiple intervals are separated by a semicolon.<br>User macros and LLD macros may be used. A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Flexible intervals may be written as two macros separated by a forward slash (e.g. `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host that the item prototype belongs to.<br><br>For update operations this field is *readonly*.| |**ruleid**<br>(required)|string|ID of the LLD rule that the item belongs to.<br><br>For update operations this field is *readonly*.| |**interfaceid**<br>(required)|string|ID of the item prototype's host interface. Used only for host item prototypes.<br><br>Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, calculated, dependent, database monitor and script item prototypes. Optional for HTTP agent item prototypes.| |**key\_**<br>(required)|string|Item prototype key.| |**name**<br>(required)|string|Name of the item prototype.| |**type**<br>(required)|integer|Type of the item prototype.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>10 - external check;<br>11 - database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - TELNET agent;<br>15 - calculated;<br>16 - JMX agent;<br>17 - SNMP trap;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script.| |**url**<br>(required)|string|URL string required only for HTTP agent item prototypes. Supports LLD macros, user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(required)|integer|Type of information of the item prototype.<br><br>Possible values:<br>0 - numeric float;<br>1 - character;<br>2 - log;<br>3 - numeric unsigned;<br>4 - text.| |allow\_traps|integer|HTTP agent item prototype field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent item prototypes or HTTP agent item prototypes.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM<br>3 - Kerberos| |description|string|Description of the item prototype.| |follow\_redirects|integer|HTTP agent item prototype field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent item prototype field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |history|string|A time unit of how long the history data should be stored. Also accepts user macro and LLD macro.<br><br>Default: 90d.| |http\_proxy|string|HTTP agent item prototype field. HTTP(S) proxy connection string.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI item prototypes.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |logtimefmt|string|Format of the time in log entries. Used only by log item prototypes.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and item prototypes and maximum count of dependent items and item prototypes equal to 29999 are allowed.<br><br>Required by Dependent items.| |output\_format|integer|HTTP agent item prototype field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the item prototype:<br>- executed script for SSH and Telnet item prototypes;<br>- SQL query for database monitor item prototypes;<br>- formula for calculated item prototypes.| |parameters|array|Additional parameters for script item prototypes. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent item prototypes.| |post\_type|integer|HTTP agent item prototype field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent item prototype field. HTTP(S) request body data. Used with post\_type.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent item prototype field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent item prototype field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent item prototype field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent item prototype field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent item prototype field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent item prototype field. Password for SSL Key file.| |status|integer|Status of the item prototype.<br><br>Possible values:<br>0 - *(default)* enabled item prototype;<br>1 - disabled item prototype;<br>3 - unsupported item prototype.| |status\_codes|string|HTTP agent item prototype field. Ranges of required HTTP status codes separated by commas. Also supports user macros or LLD macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template item prototype.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script item prototypes. Supports user macros and LLD macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper item prototypes or HTTP item prototypes.| |trends|string|A time unit of how long the trends data should be stored. Also accepts user macro and LLD macro.<br><br>Default: 365d.| |units|string|Value units.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent item prototypes.<br><br>Required by SSH and Telnet item prototypes.| |uuid|string|Universal unique identifier, used for linking imported item prototypes to already existing ones. Used only for item prototypes on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |valuemapid|string|ID of the associated value map.| |verify\_host|integer|HTTP agent item prototype field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.<br>| |verify\_peer|integer|HTTP agent item prototype field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |discover|integer|Item prototype discovery status.<br><br>Possible values:<br>0 - *(default)* new items will be discovered;<br>1 - new items will not be discovered and existing items will be marked as lost.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Prototype d'élément L'objet prototype d'élément possède les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(lecture seule)* ID du prototype d'élément.| |**delay**<br>(obligatoire)|string|Intervalle de mise à jour du prototype d'élément. Accepte les secondes ou une unité de temps avec suffixe (30s, 1m, 2h, 1j).<br> En option, un ou plusieurs [intervalles personnalisés](/manual/config/items/item/custom_intervals) peuvent être spécifiés soit comme intervalles flexibles, soit comme planification .<br>Plusieurs intervalles sont séparés par un point-virgule.<br>Des macros utilisateur peuvent être utilisées. Une seule macro doit remplir tout le champ. Les macros multiples dans un champ ou les macros mélangées avec du texte ne sont pas prises en charge.<br>Les intervalles flexibles peuvent être écrits sous la forme de deux macros séparées par une barre oblique (par exemple, `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br >Facultatif pour le trappeur Zabbix, les éléments dépendants et pour l'agent Zabbix (actif) avec la clé `mqtt.get`.| |**hostid**<br>(obligatoire)|string|ID de l'hôte ou du modèle auquel appartient le prorotype d'élément.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |**ruleid**<br>(obligatoire)|string|ID de la règle LLD à laquelle appartient l'élément.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |**interfaceid**<br>(obligatoire)|string|ID de l'interface hôte du prototype d'élément.<br><br>Utilisé uniquement pour les prototypes d' élément hôtes. Non requis pour les prototypes d'éléments d'agent Zabbix (actif), Zabbix interne, trapper Zabbix, calculé, dépendant, moniteur de base de données et script. Facultatif pour les prototypes d'éléments d'agent HTTP.| |**key\_**<br>(obligatoire)|string|Clé du prototype d'élément.| |**name**<br>(obligatoire)|string|Nom du prototype d'élément.| |**type**<br>(obligatoire)|integer|Type du prototype d'élément<br><br>Valeurs possibles :<br>0 - Agent Zabbix ;<br>2 - Trapper Zabbix ;<br>3 - Vérification simple ;<br>5 - Zabbix interne ;<br>7 - Agent Zabbix (actif) ;<br>9 - Élément Web ;<br>10 - Vérification externe ;<br>11 - Moniteur de base de données ;<br>12 - Agent IPMI ;<br>13 - Agent SSH ;<br>14 - Agent Telnet ;<br>15 - Calculé ;<br>16 - Agent JMX ;<br>17 - Interruption SNMP ;<br>18 - Élément dépendant ;<br>19 - Agent HTTP ;<br>20 - Agent SNMP ;<br>21 - Script| |**url**<br>(obligatoire)|string|Chaîne d'URL, requise uniquement pour le type de prototype d'élément d'agent HTTP. Prend en charge les macros utilisateur, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(obligatoire)|integer|Type d'information du prototype d'élément.<br><br>Valeurs possibles :<br>0 - nombre flottant ;<br>1 - caractère ;<br>2 - journal ;<br>3 - numérique non signé ;<br>4 - texte.| |allow\_traps|integer|Champ de prototype d'élément d'agent HTTP. Autoriser également le remplissage de la valeur comme dans le type d'élément du trappeur.<br><br>0 - *(par défaut)* Ne pas autoriser l'acceptation des données entrantes.<br>1 - Autoriser l'acceptation des données entrantes.| |authtype|integer|Utilisé uniquement par les prototypes d'élément d'agent SSH ou les éléments d'agent HTTP.<br><br>Valeurs possibles de la méthode d'authentification de l'agent SSH :<br>0 - mot de passe *(par défaut)* ;<br>1 - clé publique.<br><br> Valeurs possibles de la méthode d'authentification de l'agent HTTP :<br>0 - *(par défaut)* aucune<br>1 - de base<br>2 - NTLM<br>3 - Kerberos| |description|string|Description du prototype d'élément.| |follow\_redirects|integer|Champ du prototype d'élément d'agent HTTP. Suivre les redirections de réponse tout en regroupant les données.<br><br>0 - Ne pas suivre les redirections.<br>1 - *(par défaut)* Suivre les redirections.| |headers|object|Champ du prototype d'élément d'agent HTTP. Objet avec en-têtes de requête HTTP(S), où le nom de l'en-tête est utilisé comme clé et la valeur de l'en-tête comme valeur.<br><br>Exemple :<br>{ "User-Agent": "Zabbix" }| |history|string|Une unité de temps indiquant combien de temps les données d'historique doivent être stockées. Accepte également les macros utilisateur.<br><br>Par défaut : 90d.| |http\_proxy|string|Champ du prototype d'élément d'agent HTTP. Chaîne de connexion proxy HTTP(S).| |ipmi\_sensor|string|Capteur IPMI. Utilisé uniquement par les prototype d'élément IPMI.| |jmx\_endpoint|string|Chaîne de connexion personnalisée de l'agent JMX.<br><br>Valeur par défaut :<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN} :{HOST.PORT}/jmxrmi| |logtimefmt|string|Format de l'heure dans les entrées de journal. Utilisé uniquement par les prototypes d'élément de journal.| |master\_itemid|integer|ID de l'élément principal.<br>La récursivité jusqu'à 3 éléments dépendants et le nombre maximal d'éléments et de prototypes d'éléments dépendants égal à 29 999 sont autorisés.<br><br>Requis par les éléments dépendants.| |output\_format|integer|Champ du prototype d'élément d'agent HTTP. La réponse doit-elle être convertie en JSON.<br><br>0 - *(par défaut)* Stocker brut.<br>1 - Convertir en JSON.| |params|string|Paramètres supplémentaires en fonction du type de prototype d'élément :<br>- script exécuté pour les prototypes d'élément SSH et Telnet ;<br>- requête SQL pour les prototypes d'élément de surveillance de base de données ;<br>- formule pour les prototypes d'élément calculés.| |parameters|array|Paramètres supplémentaires pour les prototypes d'élément de script. Tableau d'objets avec les propriétés 'name' et 'value', où name doit être unique.| |password|string|Mot de passe pour l'authentification. Utilisé par vérification simple, SSH, Telnet, moniteur de base de données, prototypes d'élément d'agent JMX et HTTP.| |post\_type|integer|Champ de prototype d'élément d'agent HTTP. Type de corps de données post stocké dans la propriété posts.<br><br>0 - *(par défaut)* Données brutes.<br>2 - Données JSON.<br>3 - Données XML.| |posts|string|Champ de prototype d'élément d'agent HTTP. Données du corps de la requête HTTP(S). Utilisé avec post\_type.| |privatekey|string|Nom du fichier de clé privée.| |publickey|string|Nom du fichier de clé publique.| |query\_fields|array|Champ de prototype d'élément d'agent HTTP. Paramètres de requête. Tableau d'objets avec des paires 'clé':'valeur', où la valeur peut être une chaîne vide.| |request\_method|integer|Champ de prototype d'élément d'agent HTTP. Type de méthode de requête.<br><br>0 - *(par défaut)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|Champ de prototype d'élément d'agent HTTP. Quelle partie de la réponse doit être stockée.<br><br>0 - *(par défaut)* Corps.<br>1 - En-têtes.<br>2 - Le corps et les en-têtes seront stockés.<br><br>Pour request\_method HEAD seul 1 est la valeur autorisée.| |snmp\_oid|string|OID SNMP.| |ssl\_cert\_file|string|Champ de prototype d'élément d'agent HTTP. Chemin d'accès au fichier de clé SSL publique.| |ssl\_key\_file|string|Champ de prototype d'élément d'agent HTTP. Chemin d'accès au fichier de clé SSL privée.| |ssl\_key\_password|string|Champ de prototype d'élément d'agent HTTP. Mot de passe pour le fichier de clé SSL.| |status|integer|Statut du prototype d'élément.<br><br>Valeurs possibles :<br>0 - prototype d'élément activé *(par défaut)* ;<br>1 - prototype d'élément désactivé ;<br>2 - prototype d'élément non supporté.| |status\_codes|string|Champ de prototype d'élément d'agent HTTP. Plages de codes d'état HTTP requis séparés par des virgules. Prend également en charge les macros utilisateur dans le cadre d'une liste séparée par des virgules.<br><br>Exemple : 200,200-{$M},{$M},200-400| |templateid|string|(lecture seule) ID du prototype d'élément du modèle parent.| |timeout|string|Délai d'expiration de la demande d'interrogation des données d'élément. Utilisé pour l'agent HTTP et les prototypes d'élément de script. Prend en charge les macros utilisateur.<br><br>par défaut : 3s<br>valeur maximale : 60s| |trapper\_hosts|string|Hôtes autorisés. Utilisé par les prototypes d'élément de trappeur ou les prototypes d'élément d'agent HTTP.| |trends|string|Une unité de temps de combien de temps les données de tendances doivent être stockées. Accepte également les macros utilisateur.<br><br>Par défaut : 365d.| |units|string|Unités de valeur.| |username|string|Nom d'utilisateur pour l'authentification. Utilisé par simple vérification, SSH, Telnet, moniteur de base de données, prototypes d'élément d'agent JMX et HTTP.<br><br>Requis par les prototypes d'élément SSH et Telnet.| |uuid|string|Identifiant unique universel, utilisé pour lier un prototype d'élément importé à des prototypes d'élément déjà existants. Utilisé uniquement pour les prototypes d'élément de modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |valuemapid|string|ID de la table. de correspondance de valeurs associée.| |verify\_host|integer|Champ de prototype d'élément d'agent HTTP. Valider que le nom d'hôte dans l'URL se trouve dans le champ Nom commun ou dans un champ Autre nom du sujet du certificat d'hôte.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| |verify\_peer|integer|Champ de prototype d'élément d'agent HTTP. Valider si le certificat de l'hôte est authentique.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| |discover|integer|Statut de découverte du prototype d'élément.<br><br>Valeurs possibles :<br>0 - *(par défaut)* les nouveaux éléments seront découverts ;<br>1 - les nouveaux éléments ne seront pas découverts et les éléments existants seront marqués comme perdus.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # itemprototype.update # itemprototype.update ##### Item prototype You may want to create an item prototype like this:  with preprocessing options:  ##### Prototype d'élément Vous voudrez peut-être créer un prototype d'élément comme celui-ci :  avec options de prétraitement :  #### Items Define items to monitor. [Item API](/manual/api/reference/item) #### Eléments Définissez les éléments à surveiller. [API Elément](/manual/api/reference/item) #### Items To configure querying of internal stats on another Zabbix instance, you may use two items: - `zabbix[stats,<ip>,<port>]` internal item - for direct remote queries of Zabbix server/proxy. <ip> and <port> are used to identify the target instance. - `zabbix.stats[<ip>,<port>]` agent item - for agent-based remote queries of Zabbix server/proxy. <ip> and <port> are used to identify the target instance. See also: [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent) The following diagram illustrates the use of either item depending on the context.  -  - Server → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -  - Server → proxy → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -  - Server → agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) -  - Server → proxy → agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) To make sure that the target instance allows querying it by the external instance, list the address of the external instance in the 'StatsAllowedIP' parameter on the target instance. #### Eléments Pour configurer l'interrogation des statistiques internes sur une autre instance Zabbix, vous pouvez utiliser deux éléments : - L'élément interne `zabbix[stats,<ip>,<port>]` - pour des requêtes directes à distance du serveur/proxy Zabbix. <ip> et <port> sont utilisés pour identifier l'instance cible. - L'élément agent `zabbix.stats[<ip>,<port>]` - pour des requêtes basées sur l'agent du serveur/proxy Zabbix. <ip> et <port> sont utilisés pour identifier l'instance cible. Voir aussi : [Éléments internes](/manual/config/items/itemtypes/internal), [Éléments agent Zabbix](/manual/config/items/itemtypes/zabbix_agent) Le schéma suivant illustre l'utilisation de l'un ou l'autre élément en fonction du contexte.  -  - Serveur → instance Zabbix externe (`zabbix[stats,<ip>,<port>]`) -  - Serveur → proxy → instance Zabbix externe (`zabbix[stats,<ip>,<port>]`) -  - Serveur → agent → instance Zabbix externe (`zabbix.stats[<ip>,<port>]`) -  - Serveur → proxy → agent → instance Zabbix externe (`zabbix.stats[<ip>,<port>]`) Pour vous assurer que l'instance cible permet de l'interroger par l'instance externe, indiquez l'adresse de l'instance externe dans le paramètre 'StatsAllowedIP' sur l'instance cible. ### Item tag The item tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Item tag name.| |value|string|Item tag value.| ### Tag d'élément L'objet tag d'élément a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nom du tag de l'élément.| |value|string|Valeur du tag de l'élément.| ##### Item To begin with, you may want to set up an item that monitors a log file, for example: log[/var/log/syslog]  With the item set up, wait a minute for the configuration changes to be picked up and then go to [Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) to make sure that the item has started collecting data. ##### Elément Pour commencer, vous souhaiterez peut-être configurer un élément qui surveille un fichier journal, par exemple : log[/var/log/syslog]  Une fois l'élément configuré, attendez une minute que les modifications de configuration soient récupérées, puis accédez aux [Dernières données](/manual/web_interface/frontend_sections/monitoring/latest_data) pour vous assurer que l'élément a commencé à collecter des données. # item.update # item.update ##### Item value preprocessing The **Preprocessing** tab allows to define [transformation rules](/manual/config/items/preprocessing) for the received values. ##### Prétraitement de la valeur de l'élément L'onglet **Prétraitement ** permet de définir des [règles de transformation](/manual/config/items/preprocessing) pour les valeurs reçues. #### Item value preprocessing To visualize the data preprocessing process, we can use the following simplified diagram:  The diagram above shows only processes, objects and main actions related to item value preprocessing in a **simplified** form. The diagram does not show conditional direction changes, error handling or loops. Only one preprocessing worker is shown on this diagram (multiple preprocessing workers can be used in real-life scenarios), only one item value is being processed and we assume that this item requires to execute at least one preprocessing step. The aim of this diagram is to show the idea behind item value preprocessing pipeline. - Item data and item value is passed to preprocessing manager using socket-based IPC mechanism. - Item is placed in the preprocessing queue. ::: noteclassic Item can be placed at the end or at the beginning of the preprocessing queue. Zabbix internal items are always placed at the beginning of preprocessing queue, while other item types are enqueued at the end. ::: - At this point data flow stops until there is at least one unoccupied (that is not executing any tasks) preprocessing worker. - When preprocessing worker is available, preprocessing task is being sent to it. - After preprocessing is done (both failed and successful execution of preprocessing steps), preprocessed value is being passed back to preprocessing manager. - Preprocessing manager converts result to desired format (defined by item value type) and places result in preprocessing queue. If there are dependent items for current item, then dependent items are added to preprocessing queue as well. Dependent items are enqueued in preprocessing queue right after the master item, but only for master items with value set and not in NOT SUPPORTED state. #### Prétraitement de la valeur de l'élément Pour visualiser le processus de prétraitement des données, nous pouvons utiliser le schéma simplifié suivant :  Le diagramme ci-dessus montre uniquement les processus, les objets et les actions principales liés au prétraitement de la valeur de l'élément sous une forme **simplifiée**. Le diagramme ne montre pas les changements de direction conditionnels, la gestion des erreurs ou les boucles. Un seul agent de prétraitement est affiché sur ce diagramme (plusieurs agents de prétraitement peuvent être utilisés dans des scénarios réels), une seule valeur d'élément est en cours de traitement et nous supposons que cet élément nécessite l'exécution d'au moins une étape de prétraitement. Le but de ce diagramme est de montrer l'idée derrière le pipeline de prétraitement de la valeur de l'élément. - Les données d'élément et la valeur de l'élément sont transmises au gestionnaire de prétraitement à l'aide du mécanisme IPC basé sur les sockets. - L'élément est placé dans la file d'attente de prétraitement. ::: noteclassic L'élément peut être placé à la fin ou au début de la file d'attente de prétraitement. Les éléments internes de Zabbix sont toujours placés au début de la file d'attente de prétraitement, tandis que les autres types d'éléments sont mis en file d'attente à la fin. ::: - À ce stade, le flux de données s'arrête jusqu'à ce qu'il y ait au moins un agent de prétraitement inoccupé (qui n'exécute aucune tâche). - Lorsque le worker de prétraitement est disponible, la tâche de prétraitement lui est envoyée. - Une fois le prétraitement terminé (échec et exécution réussie des étapes de prétraitement), la valeur prétraitée est renvoyée au gestionnaire de prétraitement. - Le gestionnaire de prétraitement convertit le résultat au format souhaité (défini par le type de valeur d'élément) et place le résultat dans la file d'attente de prétraitement. S'il existe des éléments dépendants pour l'élément actuel, les éléments dépendants sont également ajoutés à la file d'attente de prétraitement. Les éléments dépendants sont mis en file d'attente dans la file d'attente de prétraitement juste après l'élément principal, mais uniquement pour les éléments principaux avec une valeur définie et non dans l'état NON SUPPORTÉ. #### Item value processing To visualize the data flow from data source to the Zabbix database, we can use the following simplified diagram:  The diagram above shows only processes, objects and actions related to item value processing in a **simplified** form. The diagram does not show conditional direction changes, error handling or loops. Local data cache of preprocessing manager is not shown either because it doesn't affect data flow directly. The aim of this diagram is to show processes involved in item value processing and the way they interact. - Data gathering starts with raw data from a data source. At this point, data contains only ID, timestamp and value (can be multiple values as well) - No matter what type of data gatherer is used, the idea is the same for active or passive checks, for trapper items and etc, as it only changes the data format and the communication starter (either data gatherer is waiting for a connection and data, or data gatherer initiates the communication and requests the data). Raw data is validated, item configuration is retrieved from configuration cache (data is enriched with the configuration data). - Socket-based IPC mechanism is used to pass data from data gatherers to preprocessing manager. At this point data gatherer continue to gather data without waiting for the response from preprocessing manager. - Data preprocessing is performed. This includes execution of preprocessing steps and dependent item processing. ::: noteclassic Item can change its state to NOT SUPPORTED while preprocessing is performed if any of preprocessing steps fail. ::: - History data from local data cache of preprocessing manager is being flushed into history cache. - At this point data flow stops until the next synchronization of history cache (when history syncer process performs data synchronization). - Synchronization process starts with data normalization storing data in Zabbix database. Data normalization performs conversions to desired item type (type defined in item configuration), including truncation of textual data based on predefined sizes allowed for those types (HISTORY\_STR\_VALUE\_LEN for string, HISTORY\_TEXT\_VALUE\_LEN for text and HISTORY\_LOG\_VALUE\_LEN for log values). Data is being sent to Zabbix database after normalization is done. ::: noteclassic Item can change its state to NOT SUPPORTED if data normalization fails (for example, when textual value cannot be converted to number). ::: - Gathered data is being processed - triggers are checked, item configuration is updated if item becomes NOT SUPPORTED, etc. - This is considered the end of data flow from the point of view of item value processing. #### Traitement de la valeur de l'élément Pour visualiser le flux de données de la source de données vers la base de données Zabbix, nous pouvons utiliser le schéma simplifié suivant :  Le diagramme ci-dessus montre uniquement les processus, les objets et les actions liés au traitement de la valeur de l'élément sous une forme **simplifiée**. Le diagramme ne montre pas les changements de direction conditionnels, la gestion des erreurs ou les boucles. Le cache de données local du gestionnaire de prétraitement n'est pas affiché non plus car il n'affecte pas directement le flux de données. L'objectif de ce diagramme est de montrer les processus impliqués dans le traitement de la valeur des éléments et la façon dont ils interagissent. - La collecte de données commence par des données brutes provenant d'une source de données. À ce stade, les données ne contiennent que l'ID, l'horodatage et la valeur (il peut également s'agir de plusieurs valeurs) - Quel que soit le type de collecteur de données utilisé, l'idée est la même pour les vérifications actives ou passives, pour les éléments de trappeur, etc., car cela ne modifie que le format des données et le démarreur de communication (soit le collecteur de données attend une connexion et des données, ou le collecteur de données initie la communication et demande les données). Les données brutes sont validées, la configuration des éléments est extraite du cache de configuration (les données sont enrichies avec les données de configuration). - Le mécanisme IPC basé sur les sockets est utilisé pour transmettre les données des collecteurs de données au gestionnaire de prétraitement. À ce stade, le collecteur de données continue de collecter des données sans attendre la réponse du gestionnaire de prétraitement. - Un prétraitement des données est effectué. Cela inclut l'exécution des étapes de prétraitement et le traitement des éléments dépendants. ::: noteclassic L'élément peut changer son état en NON SUPPORTÉ pendant le prétraitement si l'une des étapes de prétraitement échoue. ::: - Les données d'historique du cache de données local du gestionnaire de prétraitement sont vidées dans le cache d'historique. - À ce stade, le flux de données s'arrête jusqu'à la prochaine synchronisation du cache de l'historique (lorsque le processus de synchronisation de l'historique effectue la synchronisation des données). - Le processus de synchronisation commence par la normalisation des données en stockant les données dans la base de données Zabbix. La normalisation des données effectue des conversions vers le type d'élément souhaité (type défini dans la configuration de l'élément), y compris la troncature des données textuelles en fonction des tailles prédéfinies autorisées pour ces types (HISTORY\_STR\_VALUE\_LEN pour la chaîne, HISTORY\_TEXT\_VALUE\_LEN pour le texte et HISTORY\_LOG\_VALUE\_LEN pour les valeurs de journal). Les données sont envoyées à la base de données Zabbix après la normalisation. ::: noteclassic L'élément peut changer son état en NON SUPPORTÉ si la normalisation des données échoue (par exemple, lorsque la valeur textuelle ne peut pas être convertie en nombre). ::: - Les données collectées sont en cours de traitement - les déclencheurs sont vérifiés, la configuration de l'élément est mise à jour si l'élément devient NON SUPPORTÉ, etc. - Ceci est considéré comme la fin du flux de données du point de vue du traitement de la valeur de l'élément. #### Item values The following information is exported for a collected item value: |Field|<|Type|Description| |-|---------|---------|---------------------------| |*host*|<|object|Host name of the item host.| | |host|string|Host name.| |^|name|string|Visible host name.| |*groups*|<|array|List of host groups of the item host; there should be at least one element in array.| | |\-|string|Host group name.| |*itemid*|<|number|Item ID.| |*name*|<|string|Visible item name.| |*clock*|<|number|Number of seconds since Epoch to the moment when value was collected (integer part).| |*ns*|<|number|Number of nanoseconds to be added to `clock` to get a precise value collection time.| |*timestamp*<br>(*Log* only)|<|number|0 if not available.| |*source*<br>(*Log* only)|<|string|Empty string if not available.| |*severity*<br>(*Log* only)|<|number|0 if not available.| |*eventid*<br>(*Log* only)|<|number|0 if not available.| |*value*|<|number (for numeric items) or<br>string (for text items)|Collected item value.| |*type*|<|number|Collected value type:<br>0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text| #### Valeurs d'élément The following information is exported for a collected item value: |Champ|<|Type|Description| |-|---------|---------|--------------------------- | |*host*|<|object|Nom d'hôte de l'hôte de l'élément.| | |host|string|Nom d'hôte.| |^|name|string|Nom d'hôte visible.| |*groups*|<|array|Liste des groupes d'hôtes de l'hote de l'élément ; il doit y avoir au moins un élément dans le tableau.| | |\-|string|Nom du groupe d'hôtes.| |*itemid*|<|number|ID de l'article.| |*name*|<|string|Nom de l'élément visible.| |*clock*|<|number|Nombre de secondes depuis Epoch jusqu'au moment où la valeur a été collectée (partie entière).| |*ns*|<|number|Nombre de nanosecondes à ajouter à `clock` pour obtenir une heure de collecte de valeur précise.| |*timestamp*<br>(*Journal* uniquement)|<|number|0 si non disponible.| |*source*<br>(*Journal* uniquement)|<|string|Chaîne vide si non disponible.| |*severity*<br>(*Journal* uniquement)|<|number|0 si non disponible.| |*eventid*<br>(*Journal* uniquement)|<|number|0 si non disponible.| |*value*|<|number (pour les éléments numériques) ou<br>string (pour les éléments de texte)|Valeur de l'élément collecté.| |*type*|<|number|Type de valeur collectée :<br>0 - nombre flottant, 1 - caractère, 2 - journal, 3 - numérique non signé, 4 - texte| It is possible to zoom in and out the map by using the plus and minus buttons in the widget's upper left corner or by using the mouse scroll wheel or touchpad. To set the current view as default, right-click anywhere on the map and select *Set this view as default*. This setting will override *Initial view* widget parameter for the current user. To undo this action, right-click anywhere on the map again and select *Reset the initial view*. When *Initial view* or *Default view* is set, you can return to this view at any time by pressing on the home icon on the left.  Il est possible d'effectuer un zoom avant et arrière sur la carte en utilisant les boutons plus et moins dans le coin supérieur gauche du widget ou en utilisant la molette de la souris ou le pavé tactile. Pour définir la vue actuelle par défaut, cliquez avec le bouton droit n'importe où sur la carte et sélectionnez *Définir cette vue par défaut*. Ce paramètre remplacera le paramètre de widget *Vue initiale* pour l'utilisateur actuel. Pour annuler cette action, faites à nouveau un clic droit n'importe où sur la carte et sélectionnez *Réinitialiser la vue initiale*. Lorsque *Vue initiale* ou *Vue par défaut* est définie, vous pouvez revenir à cette vue à tout moment en appuyant sur l'icône d'accueil à gauche.  ### Java gateway installation It is required to install [Java gateway](/manual/concepts/java) only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database. Once the required repository is added, you can install Zabbix Java gateway by running: # dnf install zabbix-java-gateway Proceed to [setup](/manual/concepts/java/from_rhel_centos) for more details on configuring and running Java gateway. ###Installation de la passerelle Java Il est nécessaire d'installer la [passerelle Java](/manual/concepts/java) uniquement si vous souhaitez surveiller les applications JMX. La passerelle Java est légère et ne nécessite pas de base de données. Une fois le dépôt requis ajouté, vous pouvez installer la passerelle Java Zabbix en exécutant : # dnf install zabbix-java-gateway¶ Passez à la [configuration](/manual/concepts/java/from_rhel_centos) pour plus de détails sur la configuration et l'exécution de la passerelle Java. #### JMX item keys in more detail #### Clés d’élément JMX plus en détails #### JMX monitoring See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details. #### Supervision JMX Voir la page [Supervision JMX](/fr/manual/config/items/itemtypes/jmx_monitoring) pour plus de détails. #### JMX monitoring See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details. #### Supervision JMX Voir la page [Supervision JMX](/fr/manual/config/items/itemtypes/jmx_monitoring) pour plus de détails. #### JMX monitoring See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details. #### Supervision JMX Voir la page [Supervision JMX](/fr/manual/config/items/itemtypes/jmx_monitoring) pour plus de détails. #### JMX monitoring See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details. #### Supervision JMX Voir la page [Supervision JMX](/manual/config/items/itemtypes/jmx_monitoring) pour plus de détails. ### JMX monitoring The template *Generic Java JMX* now contains discovery rules for low-level discovery of memory pools and garbage collectors. ### Surveillance JMX Le modèle *Generic Java JMX* contient désormais des règles de découverte pour la découverte de bas niveau des pools de mémoire et des récupérateurs de mémoire. # JMX template operation Steps to ensure correct operation of templates that collect metrics by [JMX](/manual/config/items/itemtypes/jmx_monitoring): 1\. Make sure Zabbix [Java gateway](/manual/concepts/java#getting_java_gateway) is installed and set up properly.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to the target host. The host should have JMX interface set up.\ If the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions.\ 3. Adjust the values of mandatory macros as needed.\ 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column. ::: notetip This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items, and triggers, is available in the template's Readme.md file (accessible by clicking on a template name). ::: |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[Apache ActiveMQ by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/activemq_jmx/README.md)|**{$ACTIVEMQ.PORT}** - port for JMX (default: 1099).<br>**{$ACTIVEMQ.USERNAME}**, **{$ACTIVEMQ.PASSWORD}** - login credentials for JMX<br>(default username: admin, password: activemq).|JMX access to Apache ActiveMQ should be enabled and configured per instructions in [the official documentation](https://activemq.apache.org/jmx.html).| |[Apache Cassandra by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cassandra_jmx/README.md)|**{$CASSANDRA.USER}**, **{$CASSANDRA.PASSWORD}** - Apache Cassandra login credentials<br>(default username: zabbix, password: zabbix)|JMX access to Apache Cassandra should be enabled and configured per instructions in [the official documentation](https://cassandra.apache.org/doc/latest/operating/security.html#jmx-access).| |[Apache Kafka by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kafka_jmx/README.md)|**{$KAFKA.USER}**, **{$KAFKA.PASSWORD}** - Apache Kafka login credentials<br>(default username: zabbix, password: zabbix)|JMX access to Apache Kafka should be enabled and configured per instructions in [the official documentation](https://kafka.apache.org/documentation/#remote_jmx).| |[Apache Tomcat by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/tomcat_jmx/README.md)|**{$TOMCAT.USER}**, **{$TOMCAT.PASSWORD}** - Apache Tomcat login credentials; leave blank if Tomcat installation does not require authentication<br>(default: not set).|JMX access to Apache Tomcat should be enabled and configured per instructions in [the official documentation](https://tomcat.apache.org/tomcat-10.0-doc/monitoring.html#Enabling_JMX_Remote) (choose the correct version).| |[GridGain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/gridgain_jmx/README.md)|**{$GRIDGAIN.USER}**, **{$GRIDGAIN.PASSWORD}** - GridGain login credentials (default username: zabbix, password: <secret>).|JMX access to GridGain In-Memory Computing Platform should be enabled and configured per instructions in [the documentation](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html).| |[Ignite by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/ignite_jmx/README.md)|**{$IGNITE.USER}**, **{$IGNITE.PASSWORD}** - Apache Ignite login credentials (default username: zabbix, password: <secret>).|Enable and configure JMX access to Apache Ignite.<br><br>JMX tree hierarchy contains ClassLoader by default. Adding the following Java Virtual Machine option `-DIGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false` will exclude one level with ClassLoader name.<br><br>Cache and Data Region metrics can be configured as needed - see [Ignite documentation](https://ignite.apache.org/docs/latest/monitoring-metrics/configuring-metrics) for details.<br><br>See also: [Monitoring and Management Using JMX Technology](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)| |[WildFly Domain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_domain_jmx/README.md)|**{$WILDFLY.JMX.PROTOCOL}** - JMX scheme (default: remote+http)<br>**{$WILDFLY.USER}**, **{$WILDFLY.PASSWORD}** - WildFly login credentials (default username: zabbix, password: zabbix).|1\. Enable and configure JMX access to WildFly according to instructions in [the official documentation](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copy *jboss-client.jar* from `/(wildfly,EAP,Jboss,AS)/bin/client` into directory `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Restart Zabbix Java gateway.| |[WildFly Server by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_server_jmx/README.md)|**{$WILDFLY.JMX.PROTOCOL}** - JMX scheme (default: remote+http)<br>**{$WILDFLY.USER}**, **{$WILDFLY.PASSWORD}** - WildFly login credentials (default username: zabbix, password: zabbix).|1\. Enable and configure JMX access to WildFly according to instructions in [the official documentation](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copy *jboss-client.jar* from `/(wildfly,EAP,Jboss,AS)/bin/client` into directory `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Restart Zabbix Java gateway.| # Fonctionnement du modèle JMX Étapes pour garantir le bon fonctionnement des modèles qui collectent des métriques par [JMX](/manual/config/items/itemtypes/jmx_monitoring): 1\. Assurez-vous que la [passerelle Java](/manual/concepts/java#getting_java_gateway) Zabbix est installée et configurée correctement.\ 2. [Liez](/manual/config/templates/linking#linking_a_template) le modèle à l'hôte cible. L'hôte doit avoir une interface JMX configurée.\ Si le modèle n'est pas disponible dans votre installation Zabbix, vous devrez peut-être d'abord importer le fichier .xml du modèle - voir la section [Modèles prêts à l'emploi](/manual/config/templates_out_of_the_box) pour obtenir les instructions.\ 3. Ajustez les valeurs des macros obligatoires selon vos besoins.\ 4. Configurez l'instance surveillée pour autoriser le partage de données avec Zabbix - voir les instructions dans la colonne *Étapes supplémentaires/commentaires*. ::: notetip Cette page ne contient qu'un ensemble minimal de macros et d'étapes de configuration nécessaires au bon fonctionnement du modèle. Une description détaillée d'un modèle, y compris la liste complète des macros, des éléments et des déclencheurs, est disponible dans le fichier Readme.md du modèle (accessible en cliquant sur un nom de modèle). ::: |Modèle|Macros obligatoires|Étapes/commentaires supplémentaires| |--------|----------------|-------------------------| |[Apache ActiveMQ by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/activemq_jmx/README.md)|**{\$ACTIVEMQ.PORT}** - port pour JMX (par défaut : 1099).<br>**{\$ACTIVEMQ.USERNAME}**, **{\$ACTIVEMQ.PASSWORD}** - identifiants de connexion pour JMX<br>(nom d'utilisateur par défaut : admin, mot de passe : activemq).|L'accès JMX à Apache ActiveMQ doit être activé et configuré conformément aux instructions de [la documentation officielle](https://activemq.apache.org/jmx.html).| |[Apache Cassandra by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cassandra_jmx/README.md)|**{\$CASSANDRA.USER}**, **{\$CASSANDRA.PASSWORD}** - Identifiants de connexion Apache Cassandra<br>(nom d'utilisateur par défaut : zabbix, mot de passe : zabbix)|L'accès JMX à Apache Cassandra doit être activé et configuré conformément aux instructions de [la documentation officielle](https://cassandra.apache.org/doc/latest/operating/security.html#jmx-access).| |[Apache Kafka by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kafka_jmx/README.md)|**{\$KAFKA.USER}**, **{\$KAFKA.PASSWORD}** - Identifiants de connexion Apache Kafka<br>(nom d'utilisateur par défaut : zabbix, mot de passe : zabbix)|L'accès JMX à Apache Kafka doit être activé et configuré conformément aux instructions de [la documentation officielle](https://kafka.apache.org/documentation/#remote_jmx).| |[Apache Tomcat by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/tomcat_jmx/README.md)|**{\$TOMCAT.USER}**, **{\$TOMCAT.PASSWORD}** - Identifiants de connexion Apache Tomcat ; laissez vide si l'installation de Tomcat ne nécessite pas d'authentification<br>(par défaut : non défini).|L'accès JMX à Apache Tomcat doit être activé et configuré conformément aux instructions de [la documentation officielle](https://tomcat.apache.org/tomcat-10.0-doc/monitoring.html#Enabling_JMX_Remote) (choisissez la bonne version).| |[GridGain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/gridgain_jmx/README.md)|**{\$GRIDGAIN.USER}**, **{\$GRIDGAIN.PASSWORD}** - Identifiants de connexion à GridGain (nom d'utilisateur par défaut : zabbix, mot de passe : \<secret\>).|L'accès JMX à GridGain In-Memory Computing Platform doit être activé et configuré conformément aux instructions de [la documentation](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html).| |[Ignite by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/ignite_jmx/README.md)|**{\$IGNITE.USER}**, **{\$IGNITE.PASSWORD}** - Identifiants de connexion Apache Ignite (nom d'utilisateur par défaut : zabbix, mot de passe : \<secret\>).|Activez et configurez l'accès JMX à Apache Ignite.<br><br>La hiérarchie de l'arborescence JMX contient ClassLoader par défaut. L'ajout de l'option de machine virtuelle Java suivante `-DIGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false` exclura un niveau avec le nom de ClassLoader.<br><br>Les métriques de cache et de région de données peuvent être configurées selon les besoins - voir la [documentation Ignite](https://ignite.apache.org/docs/latest/monitoring-metrics/configuring-metrics) pour plus de détails.<br><br>Voir aussi : [Surveillance et gestion à l'aide de la technologie JMX](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)| |[WildFly Domain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_domain_jmx/README.md)|**{\$WILDFLY.JMX.PROTOCOL}** - Schéma JMX (par défaut : remote+http)<br>**{\$WILDFLY.USER}**, **{\$WILDFLY.PASSWORD}** - Identifiants de connexion WildFly (nom d'utilisateur par défaut : zabbix, mot de passe : zabbix).|1\. Activez et configurez l'accès JMX à WildFly conformément aux instructions de [la documentation officielle](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copiez *jboss-client.jar* de `/(wildfly,EAP,Jboss,AS)/bin/client` dans le répertoire `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Redémarrez la passerelle Java Zabbix.| |[WildFly Server by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_server_jmx/README.md)|**{\$WILDFLY.JMX.PROTOCOL}** - Schéma JMX (par défaut : remote+http)<br>**{\$WILDFLY.USER}**, **{\$WILDFLY.PASSWORD}** - Identifiants de connexion WildFly (nom d'utilisateur par défaut : zabbix, mot de passe : zabbix).|1\. Activez et configurez l'accès JMX à WildFly conformément aux instructions de [la documentation officielle](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copiez *jboss-client.jar* de `/(wildfly,EAP,Jboss,AS)/bin/client` dans le répertoire `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Redémarrez la passerelle Java Zabbix.| ### JSONPath parsing errors JSONPath parsing errors occur in this version in case of leading whitespace and empty array/object. Fixed in Zabbix 6.0.12. ### Erreurs d'analyse JSONPath Des erreurs d'analyse JSONPath se produisent dans cette version en cas d'espace en tête et de tableau/objet vide. Corrigé dans Zabbix 6.0.12. #### Keeping history You can set for how many days history will be kept: - in the item properties [form](/manual/config/items/item) - when mass-updating items - when [setting up](/manual/web_interface/frontend_sections/administration/general#housekeeper) housekeeper tasks Any older data will be removed by the housekeeper. The general strong advice is to keep history for the smallest possible number of days and that way not to overload the database with lots of historical values. Instead of keeping a long history, you can keep longer data of trends. For example, you could keep history for 14 days and trends for 5 years. You can get a good idea of how much space is required by history versus trends data by referring to the [database sizing page](/manual/installation/requirements#database_size). While keeping shorter history, you will still be able to review older data in graphs, as graphs will use trend values for displaying older data. ::: noteimportant If history is set to '0', the item will update only dependent items and inventory. No trigger functions will be evaluated because trigger evaluation is based on history data only. ::: ::: notetip As an alternative way to preserve history consider to use [history export](/manual/config/items/loadablemodules#providing_history_export_callbacks) functionality of loadable modules. ::: #### Conserver l'historique Vous pouvez définir pendant combien de jours l'historique sera conservé :: - dans le formulaire des propriétés de l'[élément](/manual/config/items/item) - lors de la mise à jour en masse d'éléments - lors de la [configuration](/manual/web_interface/frontend_sections/administration/general#housekeeper) des tâches de nettoyage Toutes les données plus anciennes seront supprimées par le nettoyage. Le conseil général est de conserver l'historique pendant le plus petit nombre de jours possible et de ne pas surcharger la base de données avec de nombreuses valeurs historiques. Au lieu de conserver un long historique, vous pouvez conserver des données plus longues sur les tendances. Par exemple, vous pouvez conserver l'historique pendant 14 jours et les tendances pendant 5 ans. Vous pouvez avoir une bonne idée de l'espace requis par les données d'historique par rapport aux données de tendances en vous référant à la [page de dimensionnement de la base de données](/manual/installation/requirements#database_size). Tout en conservant un historique plus court, vous pourrez toujours revoir les données plus anciennes dans les graphiques, car les graphiques utiliseront les valeurs de tendance pour afficher les données plus anciennes. ::: noteimportant Si l'historique est défini sur '0', l'élément ne mettra à jour que les éléments dépendants et l'inventaire. Aucune fonction de déclencheur ne sera évaluée car l'évaluation du déclencheur est basée uniquement sur les données d'historique. ::: ::: notetip Comme autre moyen de préserver l'histoire, envisagez d'utiliser la fonctionnalité d'[exportation d'historique](/manual/config/items/loadablemodules#providing_history_export_callbacks) des modules chargeables. ::: #### Keeping trends Trends is a built-in historical data reduction mechanism which stores minimum, maximum, average and the total number of values per every hour for numeric data types. You can set for how many days trends will be kept: - in the item properties [form](/manual/config/items/item) - when mass-updating items - when setting up Housekeeper tasks Trends usually can be kept for much longer than history. Any older data will be removed by the housekeeper. Zabbix server accumulates trend data in runtime in the trend cache, as the data flows in. Server flushes **previous hour** trends of every item into the database (where frontend can find them) in these situations: - server receives the first current hour value of the item - 5 or less minutes of the current hour left and still no current hour values of the item - server stops To see trends on a graph you need to wait at least to the beginning of the next hour (if item is updated frequently) and at most to the end of the next hour (if item is updated rarely), which is 2 hours maximum. When server flushes trend cache and there are already trends in the database for this hour (for example, server has been restarted mid-hour), server needs to use update statements instead of simple inserts. Therefore on a bigger installation if restart is needed it is desirable to stop server in the end of one hour and start in the beginning of the next hour to avoid trend data overlap. History tables do not participate in trend generation in any way. ::: noteimportant If trends are set to '0', Zabbix server does not calculate or store trends at all. ::: ::: noteclassic The trends are calculated and stored with the same data type as the original values. As a result the average value calculations of unsigned data type values are rounded and the less the value interval is the less precise the result will be. For example if item has values 0 and 1, the average value will be 0, not 0.5. Also restarting server might result in the precision loss of unsigned data type average value calculations for the current hour. ::: #### Garder les tendances Les tendances sont un mécanisme intégré de réduction des données historiques qui stocke le minimum, le maximum, la moyenne et le nombre total de valeurs par heure pour les types de données numériques. Vous pouvez définir pendant combien de jours les tendances seront conservées : - dans le [formulaire](/manual/config/items/item) des propriétés de l'élément - lors de la mise à jour en masse d'éléments - lors de la configuration des tâches de Nettoyage Les tendances peuvent généralement être conservées beaucoup plus longtemps que l'historique. Toutes les données plus anciennes seront supprimées par le nettoyage. Le serveur Zabbix accumule les données de tendance lors de l'exécution dans le cache de tendance, au fur et à mesure que les données arrivent. Le serveur vide les tendances de l'**heure précédente** de chaque élément dans la base de données (où l'interface peut les trouver) dans ces situations : - le serveur reçoit la première valeur d'heure actuelle de l'élément - Il reste 5 minutes ou moins de l'heure actuelle et toujours aucune valeur d'heure actuelle pour l'élément - le serveur s'arrête Pour voir les tendances sur un graphique, vous devez attendre au moins jusqu'au début de l'heure suivante (si l'élément est mis à jour fréquemment) et au plus jusqu'à la fin de l'heure suivante (si l'élément est mis à jour rarement), soit 2 heures maximum. Lorsque le serveur vide le cache des tendances et qu'il existe déjà des tendances dans la base de données pour cette heure (par exemple, le serveur a été redémarré en milieu d'heure), le serveur doit utiliser des instructions de mise à jour au lieu de simples insertions. Par conséquent, sur une installation plus importante, si un redémarrage est nécessaire, il est souhaitable d'arrêter le serveur au bout d'une heure et de démarrer au début de l'heure suivante pour éviter le chevauchement des données de tendance. Les tables d'historique ne participent en aucune façon à la génération de tendance. ::: noteimportant Si les tendances sont définies sur '0', le serveur Zabbix ne calcule ni ne stocke les tendances du tout. ::: ::: noteclassic Les tendances sont calculées et stockées avec le même type de données que les valeurs d'origine. En conséquence, les calculs de valeur moyenne des valeurs de type de données non signées sont arrondis et moins l'intervalle de valeurs est faible, moins le résultat sera précis. Par exemple, si l'élément a les valeurs 0 et 1, la valeur moyenne sera 0 et non 0,5. Le redémarrage du serveur peut également entraîner la perte de précision des calculs de la valeur moyenne des types de données non signés pour l'heure en cours. ::: ##### Kernel data |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**kernel.maxfiles**|<|<|<| |Maximum number of opened files supported by OS.|Integer| | | |**kernel.maxproc**|<|<|<| |Maximum number of processes supported by OS.|Integer| | | |**kernel.openfiles**|<|<|<| |Return the number of currently open file descriptors.|Integer| |This item is supported since Zabbix 6.0.| ##### Données du noyau |Clé de l'élément|<|<|<| |--|--|------|------| |Description|Valeur de retour|Paramètres|Commentaires| |**kernel.maxfiles**|<|<|<| |Nombre maximum de fichiers ouverts pris en charge par le système d'exploitation.|Entier| | | |**kernel.maxproc**|<|<|<| |Nombre maximum de processus pris en charge par le système d'exploitation.|Entier| | | |**kernel.openfiles**|<|<|<| |Renvoie le nombre de descripteurs de fichiers actuellement ouverts.|Entier| |Cet élément est pris en charge depuis Zabbix 6.0.| ### Keyboard navigation Keyboard control has been implemented for info icons in the frontend. Thus it is now possible to focus on info icons, and open the hints, using the keyboard. ### Navigation au clavier Le contrôle du clavier a été implémenté pour les icônes d'informations dans l'interface. Ainsi il est maintenant possible de se concentrer sur les icônes d'information et d'ouvrir les astuces à l'aide du clavier. ##### Key file authentication To use key based authentication for SSH items, certain changes to the server configuration are required. Open the Zabbix server configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) as `root` and look for the following line: # SSHKeyLocation= Uncomment it and set full path to a folder where public and private keys will be located: SSHKeyLocation=/home/zabbix/.ssh Save the file and restart zabbix\_server afterwards. */home/zabbix* here is the home directory for the *zabbix* user account and *.ssh* is a directory where by default public and private keys will be generated by a [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen) command inside the home directory. Usually installation packages of zabbix-server from different OS distributions create *zabbix* user account with a home directory in not very well-known places (as for system accounts), e. g. */var/lib/zabbix*. Before starting to generate the keys, an approach to reallocate the home directory to a better known place (intuitively expected) could be considered. This will correspond with the *SSHKeyLocation* Zabbix server configuration parameter mentioned above. These steps can be skipped if *zabbix* account has been added manually according to the [installation section](/manual/installation/install#create_user_account) because in this case most likely the home directory is already located at */home/zabbix*. To change the setting for the *zabbix* user account all working processes which are using it have to be stopped: # service zabbix-agent stop # service zabbix-server stop To change the home directory location with an attempt to move it (if it exists) a command should be executed: # usermod -m -d /home/zabbix zabbix It's absolutely possible that a home directory did not exist in the old place, so it should be created at the new place. A safe attempt to do that is: # test -d /home/zabbix || mkdir /home/zabbix To be sure that all is secure, additional commands could be executed to set permissions to the home directory: # chown zabbix:zabbix /home/zabbix # chmod 700 /home/zabbix Previously stopped processes now can be started again: # service zabbix-agent start # service zabbix-server start Now steps to generate public and private keys can be performed by a command: # sudo -u zabbix ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/zabbix/.ssh/id_rsa): Created directory '/home/zabbix/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/zabbix/.ssh/id_rsa. Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub. The key fingerprint is: 90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0 The key's randomart image is: +--[ RSA 2048]----+ | | | . | | o | | . o | |+ . S | |.+ o = | |E . * = | |=o . ..* . | |... oo.o+ | +-----------------+ Note: public and private keys (*id\_rsa.pub* and *id\_rsa* respectively) have been generated by default in the */home/zabbix/.ssh* directory which corresponds to the Zabbix server *SSHKeyLocation* configuration parameter. ::: noteimportant Key types other than "rsa" may be supported by the ssh-keygen tool and SSH servers but they may not be supported by libssh2, used by Zabbix. ::: ##### Authentification par fichier clé Pour utiliser l'authentification par clé pour les éléments SSH, certaines modifications de la configuration du serveur sont requises. Ouvrez le fichier de configuration du serveur Zabbix ([zabbix\_server.conf](/fr/manual/appendix/config/zabbix_server)) en tant qu'utilisateur `root` et recherchez la ligne suivante : # SSHKeyLocation= Décommentez-le et définissez le chemin d'accès complet à un dossier où se trouvent les clés publiques et privées : SSHKeyLocation=/home/zabbix/.ssh Enregistrez le fichier et redémarrez zabbix\_server ensuite. */home/zabbix* ici est le répertoire de base du compte utilisateur *zabbix* et .ssh est un répertoire où, par défaut, les clés publiques et privées seront générées par une commande [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen) dans le répertoire home. Habituellement, les paquets d'installation de zabbix-server provenant de différentes distributions du système d'exploitation créent le compte utilisateur *zabbix* avec un répertoire personnel dans des endroits peu connus (comme les comptes systèmes), par exemple */var/lib/zabbix*. Avant de commencer à générer les clés, une approche pour réattribuer le répertoire de base à un endroit mieux connu (plus intuitif) pourrait être envisagée. Cela correspondra au paramètre de configuration du serveur Zabbix *SSHKeyLocation* mentionné ci-dessus. Ces étapes peuvent être ignorées si le compte *zabbix* a été ajouté manuellement en fonction de la [section d'installation](/fr/manual/installation/install#create_user_account) car, dans ce cas, le répertoire home est probablement déjà situé dans */home/zabbix*. Pour modifier le paramètre du compte utilisateur *zabbix*, tous les processus qui l'utilisent doivent être arrêtés : # service zabbix-agent stop # service zabbix-server stop Pour changer l'emplacement du répertoire personnel en le déplaçant (s'il existe), la commande suivante devrait être exécutée : # usermod -m -d /home/zabbix zabbix Il est tout à fait possible qu'un répertoire personnel n'existe pas à l'ancien emplacement, il devrait donc être créé au nouvel endroit. Une tentative sûre de faire cela est : # test -d /home/zabbix || mkdir /home/zabbix Pour être sûr que tout est sécurisé, des commandes supplémentaires peuvent être exécutées pour définir des autorisations sur le répertoire de base : # chown zabbix:zabbix /home/zabbix # chmod 700 /home/zabbix Les processus précédemment arrêtés peuvent maintenant être redémarrés : # service zabbix-agent start # service zabbix-server start Maintenant, les étapes pour générer des clés publiques et privées peuvent être effectuées par la commande : # sudo -u zabbix ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/zabbix/.ssh/id_rsa): Created directory '/home/zabbix/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/zabbix/.ssh/id_rsa. Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub. The key fingerprint is: 90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0 The key's randomart image is: --[ RSA 2048]----+ | | | . | | o | | . o | |+ . S | |.+ o = | |E . * = | |=o . ..* . | |... oo.o+ | +-----------------+ Remarque : les clés publique et privée (*id\_rsa.pub* et *id\_rsa* respectivement) ont été générées par défaut dans le répertoire */home/zabbix/.ssh* qui correspond au paramètre de configuration du serveur Zabbix *SSHKeyLocation*. ::: noteimportant Les types de clé autres que "rsa" peuvent être pris en charge par l'outil ssh-keygen et les serveurs SSH, mais ils peuvent ne pas être pris en charge par libssh2, utilisé par Zabbix. ::: #### Key name The key name itself has a limited range of allowed characters, which just follow each other. Allowed characters are: 0-9a-zA-Z_-. Which means: - all numbers; - all lowercase letters; - all uppercase letters; - underscore; - dash; - dot.  #### Nom de la clé Le nom de la clé elle-même a une gamme limitée de caractères autorisés, qui se suivent les uns les autres. Les caractères autorisés sont : 0-9a-zA-Z_-. Ce qui signifie : - tous les nombres ; - toutes les lettres minuscules ; - toutes les lettres majuscules ; - underscore ; - tiret ; - point.  #### Kiosk mode The kiosk mode in supported frontend pages can be activated using URL parameters. For example, in dashboards: - `/zabbix.php?action=dashboard.view&kiosk=1` - activate kiosk mode - `/zabbix.php?action=dashboard.view&kiosk=0` - activate normal mode #### Mode kiosque Le mode kiosque dans les pages frontend prises en charge peut être activé à l'aide des paramètres d'URL. Par exemple, dans les tableaux de bord : - `/zabbix.php?action=dashboard.view&kiosk=1` - active le mode kiosque - `/zabbix.php?action=dashboard.view&kiosk=0` - active le mode normal #### Known issues See [known issues](/manual/installation/known_issues#graphs) for graphs. #### Problèmes connus Voir les [problèmes connus](/manual/installation/known_issues#graphs) pour les graphiques. ##### Large file support Zabbix has large file support for SNMP trapper files. The maximum file size that Zabbix can read is 2\^63 (8 EiB). Note that the filesystem may impose a lower limit on the file size. ##### Prise en charge des fichiers volumineux Zabbix prend en charge les fichiers volumineux pour les fichiers de trapper SNMP. La taille limite maximum que Zabbix peut lire est 2\^63 (8 EiB). Notez que le système de fichier peut imposer une limite inférieure sur la taille du fichier. ### Latest data link for hosts shows numbers The latest data link for hosts in [*Monitoring* -> *Hosts*](/manual/web_interface/frontend_sections/monitoring/hosts) now shows the number of items with latest data. ### Le lien des dernières données pour les hôtes affiche des chiffres Le lien des dernières données pour les hôtes dans [*Surveillance* -> *Hôtes*](/manual/web_interface/frontend_sections/monitoring/hosts) affiche désormais le nombre d'éléments avec les dernières données. ##### Limitations - Only same host (template) dependencies are allowed - An item prototype can depend on another item prototype or regular item from the same host - Maximum count of dependent items for one master item is limited to 29999 (regardless of the number of dependency levels) - Maximum 3 dependency levels allowed - Dependent item on a host with master item from template will not be exported to XML ##### Limites - · Seules les dépendances du même hôte (modèle) sont autorisées - · Un prototype d'élément peut dépendre d'un autre prototype d'élément ou d'un élément standard du même hôte - · Le nombre maximum d'éléments dépendants pour un élément principal est limité à 29999 (quel que soit le nombre de niveaux de dépendance) - · Maximum 3 niveaux de dépendance autorisés - · L'élément dépendant d'un hôte avec l'élément principal du modèle ne sera pas exporté en XML #### Limitations - Private keys are stored in plain text in files readable by Zabbix components during startup - Pre-shared keys are entered in Zabbix frontend and stored in Zabbix database in plain text - Built-in encryption does not protect communications: - Between the web server running Zabbix frontend and user web browser - Between Zabbix frontend and Zabbix server - Currently each encrypted connection opens with a full TLS handshake, no session caching and tickets are implemented - Adding encryption increases the time for item checks and actions, depending on network latency: - For example, if packet delay is 100ms then opening a TCP connection and sending unencrypted request takes around 200ms. With encryption about 1000 ms are added for establishing the TLS connection; - Timeouts may need to be increased, otherwise some items and actions running remote scripts on agents may work with unencrypted connections, but fail with timeout with encrypted. - Encryption is not supported by [network discovery](/manual/discovery/network_discovery). Zabbix agent checks performed by network discovery will be unencrypted and if Zabbix agent is configured to reject unencrypted connections such checks will not succeed. #### Limitations - Les clés privées sont stockées en texte brut dans des fichiers lisibles par les composants Zabbix lors du démarrage - Les clés pré-partagées sont saisies dans l'interface Zabbix et stockées dans la base de données Zabbix en texte brut - Le cryptage intégré ne protège pas les communications : - Entre le serveur Web exécutant l'interface Zabbix et le navigateur Web de l'utilisateur - Entre l'interface Zabbix et le serveur Zabbix - Actuellement, chaque connexion cryptée s'ouvre avec une vérification TLS complète, aucune mise en cache de session et les tickets ne sont implémentés - L'ajout du chiffrement augmente le temps de vérification et d'action des éléments, en fonction de la latence du réseau : - Par exemple, si le délai de paquet est de 100 ms, l'ouverture d'une connexion TCP et l'envoi d'une requête non chiffrée prend environ 200 ms. Avec le cryptage, environ 1000 ms sont ajoutées pour établir la connexion TLS ; - Il peut être nécessaire d'augmenter les timeouts, sinon certains éléments et actions exécutant des scripts distants sur des agents peuvent fonctionner avec des connexions non chiffrées, mais échouer avec un délai d'expiration chiffré. - Le chiffrement n'est pas pris en charge par la [découverte du réseau](/manual/discovery/network_discovery). Les vérifications de l'agent Zabbix effectuées par la découverte du réseau ne seront pas chiffrées et si l'agent Zabbix est configuré pour rejeter les connexions non chiffrées, ces vérifications échoueront. #### Limitations Zabbix agent for Windows does not support non-standard Windows configurations where CPUs are distributed non-uniformly across NUMA nodes. If logical CPUs are distributed non-uniformly, then CPU performance metrics may not be available for some CPUs. For example, if there are 72 logical CPUs with 2 NUMA nodes, both nodes must have 36 CPUs each. #### Limitations L'agent Zabbix pour Windows ne prend pas en charge les configurations Windows non standard dans lesquelles les processeurs sont répartis de manière non uniforme sur les nœuds NUMA. Si les processeurs logiques ne sont pas distribués de manière uniforme, les métriques de performances du processeur peuvent ne pas être disponibles pour certains processeurs. Par exemple, s'il y a 72 CPU logiques avec 2 nœuds NUMA, les deux nœuds doivent avoir 36 CPU chacun. #### Limiting access to API Update role with ID "5", deny to call any "create", "update" or "delete" methods. Request: ```json { "jsonrpc": "2.0", "method": "role.update", "params": [ { "roleid": "5", "rules": { "api.access": "1", "api.mode": "0", "api": ["*.create", "*.update", "*.delete"] } } ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` #### Limiter l'accès à l'API Mettre à jour le rôle avec l'ID "5", refuser d'appeler les méthodes "create", "update" ou "delete". Requête : ```json { "jsonrpc": "2.0", "method": "role.update", "params": [ { "roleid": "5", "rules": { "api.access": "1", "api.mode": "0", "api": ["*.create", "*.update", "*.delete"] } } ], "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "roleids": [ "5" ] }, "id": 1 } ``` ### Limits for JavaScript objects in preprocessing The following limits for [JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects#additional-javascript-objects) in preprocessing have been introduced: - The total size of all messages that can be logged with the `log()` method has been limited to 8 MB per script execution. - The initialization of multiple `HttpRequest` objects has been limited to 10 per script execution. - The total length of header fields that can be added to a single `HttpRequest` object with the `addHeader()` method has been limited to 128 Kbytes (special characters and header names included). ### Limites pour les objets JavaScript dans le prétraitement Les limites suivantes pour les [objets JavaScript](/manual/config/items/preprocessing/javascript/javascript_objects#objets-javascript-supplémentaires) dans le prétraitement ont été introduites : - La taille totale de tous les messages pouvant être enregistrés avec la méthode `log()` a été limitée à 8 Mo par exécution de script. - L'initialisation de plusieurs objets `HttpRequest` a été limitée à 10 par exécution de script. - La longueur totale des champs d'en-tête pouvant être ajoutés à un seul objet `HttpRequest` avec la méthode `addHeader()` a été limitée à 128 Ko (caractères spéciaux et noms d'en-tête inclus). ### Limits for JavaScript objects in preprocessing The following limits for [JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects#additional-javascript-objects) in preprocessing have been introduced: - The total size of all messages that can be logged with the `log()` method has been limited to 8 MB per script execution. - The initialization of multiple `HttpRequest` objects has been limited to 10 per script execution. - The total length of header fields that can be added to a single `HttpRequest` object with the `addHeader()` method has been limited to 128 Kbytes (special characters and header names included). ### Limites pour les objets JavaScript dans le prétraitement Les limites suivantes pour les [objets JavaScript](/manual/config/items/preprocessing/javascript/javascript_objects#objets-javascript-supplémentaires) dans le prétraitement ont été introduites : - La taille totale de tous les messages pouvant être enregistrés avec la méthode `log()` a été limitée à 8 Mo par exécution de script. - L'initialisation de plusieurs objets `HttpRequest` a été limitée à 10 par exécution de script. - La longueur totale des champs d'en-tête pouvant être ajoutés à un seul objet `HttpRequest` avec la méthode `addHeader()` a été limitée à 128 Ko (caractères spéciaux et noms d'en-tête inclus). #### Link a group to templates Add host group "2" to two templates. Request: ```json { "jsonrpc": "2.0", "method": "template.massadd", "params": { "templates": [ { "templateid": "10085" }, { "templateid": "10086" } ], "groups": [ { "groupid": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Lier un groupe à des modèles Ajoutez le groupe d'hôtes "2" à deux modèles. Requête : ```json { "jsonrpc": "2.0", "method": "template.massadd", "params": { "templates": [ { "templateid": "10085" }, { "templateid": "10086" } ], "groups": [ { "groupid": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Link a two tempalates to a template Link templates "10106" and "10104" to template. Request: ```json { "jsonrpc": "2.0", "method": "template.massadd", "params": { "templates": [ { "templateid": "10073" } ], "templates_link": [ { "templateid": "10106" }, { "templateid": "10104" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10073" ] }, "id": 1 } ``` #### Liez deux modèles à un modèle Liez les modèles "10106" et "10104" au modèle "10073". Requête : ```json { "jsonrpc": "2.0", "method": "template.massadd", "params": { "templates": [ { "templateid": "10073" } ], "templates_link": [ { "templateid": "10106" }, { "templateid": "10104" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10073" ] }, "id": 1 } ``` #### Linking a template To link a template to the host, do the following: - Go to *Configuration → Hosts* - Click on the required host - Start typing the template name in the *Templates* field. A list of matching templates will appear; scroll down to select. - Alternatively, you may click on *Select* next to the field and select one or several templates from the list in a popup window - Click on *Add/Update* in the host attributes form The host will now have all the entities (items, triggers, graphs, etc) of the template. ::: noteimportant Linking multiple templates to the same host will fail if in those templates there are items with the same item key. And, as triggers and graphs use items, they cannot be linked to a single host from multiple templates either, if using identical item keys. ::: When entities (items, triggers, graphs etc.) are added from the template: - previously existing identical entities on the host are updated as entities of the template - entities from the template are added - any directly linked entities that, prior to template linkage, existed only on the host remain untouched In the lists, all entities from the template now are prefixed by the template name, indicating that these belong to the particular template. The template name itself (in gray text) is a link allowing to access the list of those entities on the template level. If some entity (item, trigger, graph etc.) is not prefixed by the template name, it means that it existed on the host before and was not added by the template. #### Lier un modèle Pour lier un modèle à l'hôte, procédez comme suit : - Allez dans *Configuration → Hôtes* - Cliquez sur l'hôte requis - Commencez à saisir le nom du modèle dans le champ *Modèles*. Une liste de modèles correspondants apparaîtra ; faites défiler vers le bas pour sélectionner. - Alternativement, vous pouvez cliquer sur *Sélectionner* à côté du champ et sélectionner un ou plusieurs modèles dans la liste dans une fenêtre contextuelle - Cliquez sur *Ajouter/Actualiser* dans le formulaire d'attributs de l'hôte L'hôte aura maintenant toutes les entités (éléments, déclencheurs, graphiques, etc.) du modèle. ::: noteimportant La liaison de plusieurs modèles au même hôte échouera si des éléments possèdent la même clé d’élément. Et, comme les déclencheurs et les graphiques utilisent des éléments, ils ne peuvent pas non plus être liés à un seul hôte à partir de plusieurs modèles, si des clés d'élément identiques sont utilisées. ::: Lorsque des entités (éléments, déclencheurs, graphiques, etc.) sont ajoutées à partir du modèle : - les entités identiques précédemment existantes sur l'hôte sont mises à jour en tant qu'entités du modèle - les entités du modèle sont ajoutées - toutes les entités directement liées qui, avant le couplage de modèle, n'existaient que sur l'hôte restent intactes Dans les listes, toutes les entités du modèle sont désormais préfixées par le nom du modèle, ce qui indique qu'elles appartiennent au modèle en question. Le nom du modèle lui-même (en gris) est un lien permettant d’accéder à la liste de ces entités au niveau du modèle. Si une entité (élément, déclencheur, graphique, etc.) n'est pas préfixée par le nom du modèle, cela signifie qu'elle existait auparavant sur l'hôte et n'a pas été ajoutée par le modèle. #### Linking elements Once you have put some elements on the map, it is time to start linking them. To link two elements you must first select them. With the elements selected, click on *Add* next to Link. With a link created, the single element form now contains an additional *Links* section. Click on *Edit* to edit link attributes. {width="600"} Link attributes: |Parameter|Description| |--|--------| |*Label*|Label that will be rendered on top of the link.<br>Expression [macros](/manual/appendix/macros/supported_by_location) are supported in this field, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).| |*Connect to*|The element that the link connects to.| |*Type (OK)*|Default link style:<br>**Line** - single line<br>**Bold line** - bold line<br>**Dot** - dots<br>**Dashed line** - dashed line| |*Color (OK)*|Default link color.| |*[Link indicators](links)*|List of triggers linked to the link. In case a trigger has status PROBLEM, its style is applied to the link.| #### Lier des éléments Une fois que vous avez mis certains éléments sur la carte, il est temps de commencer à les relier. Pour lier deux éléments, vous devez d'abord les sélectionner. Une fois les éléments sélectionnés, cliquez sur *Ajouter* à côté de Lien. Avec un lien créé, le formulaire à élément unique contient désormais une section *Liens* supplémentaire. Cliquez sur *Modifier* pour modifier les attributs du lien. {width="600"} Attributs du lien : |Paramètre|Description| |--|--------| |*Étiquette*|Étiquette qui sera rendue au-dessus du lien.<br>Les expressions [macros](/manual/appendix/macros/supported_by_location) sont prises en charge dans ce champ, mais uniquement avec les fonctions `avg`, `last`, `min` et `max`, avec le temps comme paramètre (par exemple, `{?avg(/host/key,1h)}`).| |*Se connecte à*|L'élément auquel le lien se connecte.| |*Type (OK)*|Style de lien par défaut :<br>**Ligne** - une seule ligne<br>**Ligne en gras** - ligne en gras<br>**Point** - points<br>** Ligne pointillée** - ligne pointillée| |*Couleur (OK)*|Couleur du lien par défaut.| |*[Indicateurs de lien](liens)*|Liste des déclencheurs liés au lien. Dans le cas où un déclencheur a le statut PROBLÈME, son style est appliqué au lien.| ##### Linking pre-defined templates to hosts As you may have noticed, Zabbix comes with a set of predefined templates for various OS, devices and applications. To get started with monitoring very quickly, you may link the appropriate one of them to a host, but beware that these templates need to be fine-tuned for your environment. Some checks may not be needed, and polling intervals may be way too frequent. More information about [templates](/manual/config/templates) is available. ##### Lier des modèles prédéfinis à des hôtes Comme vous l\'avez peut-être remarqué, Zabbix est fourni avec un ensemble de modèles prédéfinis pour divers systèmes d\'exploitation, équipements et applications. Pour commencer à surveiller très rapidement, vous pouvez associer le modèle le plus approprié à un hôte, mais attention, ces modèles doivent être adaptés à votre environnement. Certaines vérifications peuvent ne pas être nécessaires et les intervalles d\'interrogation peuvent être trop fréquents. Plus d\'informations sur les [modèles](/manual/config/templates) sont disponibles. #### Linking template to host With a template ready, it only remains to add it to a host. For that, go to *Configuration → Hosts*, click on 'New host' to open its property form and find the **Templates** field. Start typing *New template* in the *Templates* field. The name of template we have created should appear in the dropdown list. Scroll down to select. See that it appears in the *Templates* field.  Click *Update* in the form to save the changes. The template is now added to the host, with all entities that it holds. As you may have guessed, this way it can be applied to any other host as well. Any changes to the items, triggers and other entities at the template level will propagate to the hosts the template is linked to. #### Lier le modèle à l'hôte Avec un modèle prêt, il ne reste plus qu'à l'ajouter à un hôte. Pour cela, allez dans *Configuration → Hôtes*, cliquez sur 'New host' pour ouvrir son formulaire de propriété et trouvez le champ **Modèles**. Commencez à saisir *New template* dans le champ *Modèles*. Le nom du modèle que nous avons créé devrait apparaître dans la liste déroulante. Faites défiler vers le bas pour sélectionner. Vérifiez qu'il apparaît dans le champ *Modèles*.  Cliquez sur *Mettre à jour* dans le formulaire pour enregistrer les modifications. Le modèle est maintenant ajouté à l'hôte, avec toutes les entités qu'il contient. Comme vous l'avez peut-être deviné, cela peut également être appliqué à n'importe quel autre hôte. Toute modification apportée aux éléments, déclencheurs et autres entités au niveau du modèle se propagera aux hôtes auxquels le modèle est lié. #### Links available For each entry the following links are available: - Hosts - Monitoring - Latest data - Problems - Graphs - Host dashboards - Web scenarios - Configuration - Items - Triggers - Graphs - Discovery rules - Web scenarios ```{=html} <!-- --> ``` - Host groups - Monitoring - Latest data - Problems - Web scenarios - Configuration - Hosts - Templates ```{=html} <!-- --> ``` - Templates - Configuration - Items - Triggers - Graphs - Template dashboards - Discovery rules - Web scenarios #### Liens disponibles Pour chaque entrée les liens suivants sont disponibles : - Hôtes - Surveillance - Dernières données - Problèmes - Graphiques - Tableaux de bord des hôtes - Scénarios Web - Configuration - Eléments - Déclencheurs - Graphiques - Règles de découverte - Scénarios Web ```{=html} <!-- --> ``` - Groupes d'hôtes - Surveillance - Dernières données - Problèmes - Scénarios Web - Configuration - Hôtes - Modèles ```{=html} <!-- --> ``` - Modèles - Configuration - Eléments - Déclencheurs - Graphiques - Modèles de tableaux de bord - Règles de découverte - Scénarios Web ##### Links Clicking on a map element opens a menu with some available links. ##### Liens Cliquer sur un élément de la carte ouvre un menu avec quelques liens disponibles. #### Linux kernel threads #### Threads du noyau Linux ##### Linux On Linux systems `ps` command can be used together with `watch` command for observing how Zabbix is doing. For example, to run `ps` command 5 times per second to see process activities: watch -n 0.2 ps -fu zabbix To show only Zabbix proxy and agent processes: watch -tn 0.2 'ps -f -C zabbix_proxy -C zabbix_agentd' To show only history syncer processes: watch -tn 0.2 'ps -fC zabbix_server | grep history' The `ps` command produces a wide output (approximately 190 columns) as some activity messages are long. If your terminal has less than 190 columns of text you can try watch -tn 0.2 'ps -o cmd -C zabbix_server -C zabbix_proxy -C zabbix_agentd' to display only commandlines without UID, PID, start time etc. `top` command also can be used for observing Zabbix performance. Pressing 'c' key in `top` shows processes with their commandlines. In our tests on Linux `top` and `atop` correctly displayed changing activities of Zabbix processes, but `htop` was not displaying changing activities. ##### Linux Sur les systèmes Linux, la commande `ps` peut être utilisée avec la commande `watch` pour observer comment fonctionne de Zabbix. Par exemple, pour exécuter la commande `ps` 5 fois par seconde pour afficher les activités des processus : watch -n 0.2 ps -fu zabbix Pour afficher uniquement les processus de proxy et d'agent Zabbix : watch -tn 0.2 'ps -f -C zabbix_proxy -C zabbix_agentd' Pour afficher uniquement les processus de syncer d'historique : watch -tn 0.2 'ps -fC zabbix_server | grep history' La commande `ps` produit une sortie large (environ 190 colonnes) car certains messages d'activité sont longs. Si votre terminal a moins de 190 colonnes de texte, vous pouvez essayer watch -tn 0.2 'ps -o cmd -C zabbix_server -C zabbix_proxy -C zabbix_agentd' pour afficher uniquement les lignes de commande sans UID, PID, start time, etc. La commande `top` peut également être utilisée pour observer les performances de Zabbix. En appuyant sur 'c', appuyez sur `top` pour afficher les processus avec leurs lignes de commande. Dans nos tests sur Linux, `top` et `atop` affichaient correctement les activités changeantes des processus Zabbix, mais `htop` n'affichait pas les activités en évolution. #### Linux See values supported for 'memtype' parameter on Linux in the table. |Supported value|Description|Source in /proc/<pid>/status file| |--|------|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|VmSize| |pmem|Percentage of real memory|(VmRSS/total\_memory) \* 100| |rss|Resident set size|VmRSS| |data|Size of data segment|VmData| |exe|Size of code segment|VmExe| |hwm|Peak resident set size|VmHWM| |lck|Size of locked memory|VmLck| |lib|Size of shared libraries|VmLib| |peak|Peak virtual memory size|VmPeak| |pin|Size of pinned pages|VmPin| |pte|Size of page table entries|VmPTE| |size|Size of process code + data + stack segments|VmExe + VmData + VmStk| |stk|Size of stack segment|VmStk| |swap|Size of swap space used|VmSwap| Notes for Linux: 1. Not all 'memtype' values are supported by older Linux kernels. For example, Linux 2.4 kernels do not support `hwm`, `pin`, `peak`, `pte` and `swap` values. 2. We have noticed that self-monitoring of the Zabbix agent active check process with `proc.mem[...,...,...,...,data]` shows a value that is 4 kB larger than reported by `VmData` line in the agent's /proc/<pid>/status file. At the time of self-measurement the agent's data segment increases by 4 kB and then returns to the previous size. ####Linux Vous trouverez les valeurs prises en charge pour le paramètre 'memtype' sous Linux dans le tableau suivant. |Valeur prise en charge|Description|Source dans le fichier /proc/<pid>/status| |--|------|--| |vsize ^[1](proc_mem_notes#footnotes)^|Taille de la mémoire virtuelle|VmSize| |pmem|Pourcentage de mémoire réelle|(VmRSS/total\_memory) \* 100| |rss|Taille de l'ensemble résident|VmRSS| |data|Taille du segment de données|VmData| |exe|Taille du segment de code|VmExe| |hwm|Taille maximale de l'ensemble résident|VmHWM| |lck|Taille de la mémoire verrouillée|VmLck| |lib|Taille des bibliothèques partagées|VmLib| |peak|Taille maximale de la mémoire virtuelle|VmPeak| |pin|Taille des pages épinglées|VmPin| |pte|Taille des entrées de la table des pages|VmPTE| |taille|Taille du code de processus + données + segments de pile|VmExe + VmData + VmStk| |stk|Taille du segment de pile|VmStk| |swap|Taille de l'espace de swap utilisé|VmSwap| Remarques pour Linux : 1. Toutes les valeurs 'memtype' ne sont pas prises en charge par les anciens noyaux Linux. Par exemple, les noyaux Linux 2.4 ne prennent pas en charge les valeurs `hwm`, `pin`, `peak`, `pte` et `swap`. 2. Nous avons remarqué que l'autosurveillance de l'agent Zabbix actif vérifiant le processus avec `proc.mem[...,...,...,...,data]` affiche une valeur de 4 ko de plus de ce qui est indiqué par la ligne "VmData" dans le fichier de l'agent /proc/<pid>/status. Au moment de l'auto-mesure, le segment de données de l'agent augmente de 4 ko, puis revient à la taille précédente. ##### List of sorting fields available for each type of diagnostic information request Following statistic fields can be used to sort and limit requested information. |Diagnostic type|Available fields|[Type](/manual/api/reference_commentary#data_types)| |---------------|----------------|---------------------------------------------------| |historycache|values|integer| |valuecache|values|integer| |^|request.values|integer| |preprocessing|values|integer| |alerting|media.alerts|integer| |^|source.alerts|integer| |lld|values|integer| ##### Liste des champs de tri disponibles pour chaque type de demande d'informations de diagnostic Les champs statistiques suivants peuvent être utilisés pour trier et limiter les informations demandées. |Type de diagnostic|Champs disponibles|[Type](/manual/api/reference_commentary#data_types)| |---------------|----------------|---------------------------------------------------| |historycache|values|integer| |valuecache|values|integer| |^|request.values|integer| |preprocessing|values|integer| |alerting|media.alerts|integer| |^|source.alerts|integer| |lld|values|integer| ##### List of statistic fields available for each type of diagnostic information request Following statistic fields can be requested for each type of diagnostic information request property. |Diagnostic type|Available fields|Description| |---------------|----------------|-----------| |historycache|items|Number of cached items.| |^|values|Number of cached values.| |^|memory|Shared memory statistics (free space, number of used chunks, number of free chunks, max size of free chunk).| |^|memory.data|History data cache shared memory statistics.| |^|memory.index|History index cache shared memory statistics.| |valuecache|items|Number of cached items.| |^|values|Number of cached values.| |^|memory|Shared memory statistics (free space, number of used chunks, number of free chunks, max size of free chunk).| |^|mode|Value cache mode.| |preprocessing|values|Number of queued values.| |^|preproc.values|Number of queued values with preprocessing steps.| |alerting|alerts|Number of queued alerts.| |lld|rules|Number of queued rules.| |^|values|Number of queued values.| ##### Liste des champs statistiques disponibles pour chaque type de demande d'informations de diagnostic Les champs statistiques suivants peuvent être demandés pour chaque type de propriété de demande d'informations de diagnostic. |Type de diagnostic|Champs disponibles|Description| |---------------|----------------|-----------| |historycache|items|Nombre d'éléments mis en cache.| |^|values|Nombre de valeurs mises en cache.| |^|memory|Statistiques de la mémoire partagée (espace libre, nombre de morceaux utilisés, nombre de morceaux libres, taille maximale du morceau libre).| |^|memory.data|Statistiques de la mémoire partagée du cache de données d'historique.| |^|memory.index|Statistiques de la mémoire partagée du cache d'index de l'historique.| |valuecache|items|Nombre d'éléments mis en cache.| |^|values|Nombre de valeurs mises en cache.| |^|memory|Statistiques de la mémoire partagée (espace libre, nombre de morceaux utilisés, nombre de morceaux libres, taille maximale du morceau libre).| |^|mode|Mode cache de valeurs.| |preprocessing|values|Nombre de valeurs en file d'attente.| |^|preproc.values|Nombre de valeurs en file d'attente avec étapes de prétraitement.| |alerting|alerts|Nombre d'alertes en file d'attente.| |lld|rules|Nombre de règles en file d'attente.| |^|values|Nombre de valeurs en file d'attente.| ##### List of waiting items In this screen, each waiting item is listed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Scheduled check*|The time when the check was due is displayed.| |*Delayed by*|The length of the delay is displayed.| |*Host*|Host of the item is displayed.| |*Name*|Name of the waiting item is displayed.| |*Proxy*|The proxy name is displayed, if the host is monitored by proxy.| ##### Liste des éléments en attente Dans cet écran, chaque élément en attente est répertorié. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Vérification planifié*|L'heure à laquelle la vérification due est affichée.| |*Retardé de*|La durée du retard est affichée.| |*Hôte*|L'hôte de l'élément est affiché.| |*Nom*|Le nom de l'élément en attente est affiché.| |*Proxy*|Le nom du proxy est affiché, si l'hôte est surveillé par proxy.| ### LLD macro path The LLD macro path has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**lld\_macro**<br>(required)|string|LLD macro.| |**path**<br>(required)|string|Selector for value which will be assigned to corresponding macro.| ### Chemin de macro LLD Le chemin de la macro LLD a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**lld\_macro**<br>(obligatoire)|string|Macro LLD.| |**path**<br>(obligatoire)|string|Sélecteur de valeur qui sera affectée à la macro correspondante.| #### LLD rule filter condition The LLD rule filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.| ::: notetip To better understand how to use filters with various types of expressions, see examples on the [discoveryrule.get](get#retrieving_filter_conditions) and [discoveryrule.create](create#using_a_custom_expression_filter) method pages. ::: #### Condition de filtre de règle LLD L'objet de condition de filtre de règle LLD définit une vérification distincte à effectuer sur la valeur d'une macro LLD. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(obligatoire)|string|Macro LLD sur laquelle effectuer la vérification.| |**value**<br>(obligatoire)|string|Valeur à comparer.| |formulaid|string|ID unique arbitraire utilisé pour référencer la condition à partir d'une expression personnalisée. Ne peut contenir que des lettres majuscules. L'ID doit être défini par l'utilisateur lors de la modification des conditions de filtrage, mais sera généré à nouveau lors de sa demande ultérieure.| |operator|integer|Opérateur de condition.<br><br>Valeurs possibles :<br>8 - *(par défaut)* correspond à l'expression régulière ;<br>9 - ne correspond pas à l'expression régulière ;<br>12 - existe ;<br>13 -n'existe pas.| ::: notetip Pour mieux comprendre comment utiliser les filtres avec différents types d'expressions, consultez les exemples sur les pages de méthode [discoveryrule.get](get#retrieving_filter_conditions) et [discoveryrule.create](create#using_a_custom_expression_filter). ::: ### LLD rule filter The LLD rule filter object defines a set of conditions that can be used to filter discovered objects. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.| ### Filtre de règle LLD L'objet de filtre de règle LLD définit un ensemble de conditions qui peuvent être utilisées pour filtrer les objets découverts. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**conditions**<br>(obligatoire)|array|Ensemble de conditions de filtre à utiliser pour filtrer les résultats.| |**evaltype**<br>(obligatoire)|integer|Méthode d'évaluation de la condition de filtre.<br><br>Valeurs possibles :<br>0 - et/ou ;<br>1 - et ;<br>2 - ou ;<br>3 - expression personnalisée.| |eval\_formula|string|*(lecture seule)* Expression générée qui sera utilisée pour évaluer les conditions de filtre. L'expression contient des identifiants qui font référence à des conditions de filtre spécifiques par son `formulaid`. La valeur de `eval_formula` est égale à la valeur de `formula` pour les filtres avec une expression personnalisée.| |formula|string|Expression définie par l'utilisateur à utiliser pour évaluer les conditions des filtres avec une expression personnalisée. L'expression doit contenir des ID faisant référence à des conditions de filtre spécifiques par son `formulaid`. Les ID utilisés dans l'expression doivent correspondre exactement à ceux définis dans les conditions de filtre : aucune condition ne peut rester inutilisée ou omise.<br><br>Requis pour les filtres d'expression personnalisés.| #### LLD rule override filter condition The LLD rule override filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.| #### Condition de filtre de surcharge de règle LLD L'objet de condition de filtre de surcharge de règle LLD définit une vérification distincte à effectuer sur la valeur d'une macro LLD. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(obligatoire)|string|Macro LLD pour effectuer la vérification.| |**value**<br>(obligatoire)|string|Valeur à comparer.| |formulaid|string|ID unique arbitraire utilisé pour référencer la condition à partir d'une expression personnalisée. Ne peut contenir que des lettres majuscules. L'ID doit être défini par l'utilisateur lors de la modification des conditions de filtrage, mais sera généré à nouveau lors de sa demande ultérieure.| |operator|integer|Opérateur de condition.<br><br>Valeurs possibles :<br>8 - *(par défaut)* correspond à l'expression régulière ;<br>9 - ne correspond pas à l'expression régulière ;<br>12 - existe ;<br>13 - n'existe pas.| #### LLD rule override filter The LLD rule override filter object defines a set of conditions that if they match the discovered object the override is applied. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**evaltype**<br>(required)|integer|Override filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of override filter conditions to use for matching the discovered objects.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating override filter conditions. The expression contains IDs that reference specific override filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of override filters with a custom expression. The expression must contain IDs that reference specific override filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the override filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression override filters.| #### Filtre de surcharge de règle LLD L'objet de filtre de surcharge de règle LLD définit un ensemble de conditions qui, si elles correspondent à l'objet découvert, la surcharge est appliquée. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**evaltype**<br>(obligatoire)|integer|Remplacer la méthode d'évaluation de la condition de filtre.<br><br>Valeurs possibles :<br>0 - et/ou ;<br>1 - et ;<br>2 - ou ;<br>3 - expression personnalisée.| |**conditions**<br>(obligatoire)|array|Ensemble de conditions de filtre de surcharge à utiliser pour faire correspondre les objets découverts.| |eval\_formula|string|*(lecture seule)* Expression générée qui sera utilisée pour évaluer les conditions de filtre de surcharge. L'expression contient des ID qui font référence à des conditions de filtre de surcharge spécifiques par son `formulaid`. La valeur de `eval_formula` est égale à la valeur de `formula` pour les filtres avec une expression personnalisée.| |formula|string|Expression définie par l'utilisateur à utiliser pour évaluer les conditions des filtres de surcharge avec une expression personnalisée. L'expression doit contenir des ID faisant référence à des conditions de filtre de surcharge spécifiques par son `formulaid`. Les ID utilisés dans l'expression doivent correspondre exactement à ceux définis dans les conditions de filtre de surcharge : aucune condition ne peut rester inutilisée ou omise.<br><br>Requis pour les filtres de surcharge expression personnalisée.| ##### LLD rule override operation discover LLD rule override operation discover status that is set to discovered object. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**discover**<br>(required)|integer|Override the discover status for selected object.<br><br>Possible values:<br>0 - Yes, continue discovering the objects;<br>1 - No, new objects will not be discovered and existing ones will be marked as lost.| ##### Opération de surcharge de découverte de la règle LLD Statut l'opération de surcharge de découverte de la règle LLD qui est défini sur l'objet découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**discover**<br>(obligatoire)|integer|Surcharge l'état de découverte de l'objet sélectionné.<br><br>Valeurs possibles :<br>0 - Oui, continuer à découvrir les objets ;<br>1 - Non, les nouveaux objets ne seront pas découverts et les objets existants seront marqués comme perdus .| ##### LLD rule override operation history LLD rule override operation history value that is set to discovered item. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**history**<br>(required)|string|Override the history of item prototype which is a time unit of how long the history data should be stored. Also accepts user macro and LLD macro.| ##### Opération de surcharge de l'historique de la règle LLD L'opération de surcharge de l'historique de la règle LLD définie sur l'élément découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**history**<br>(obligatoire)|string|Surcharge l'historique du prototype d'élément qui est une unité de temps de la durée pendant laquelle les données d'historique doivent être stockées. Accepte également la macro utilisateur et la macro LLD.| ##### LLD rule override operation inventory LLD rule override operation inventory mode value that is set to discovered host. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**inventory\_mode**<br>(required)|integer|Override the host prototype inventory mode.<br><br>Possible values are:<br>-1 - disabled;<br>0 - *(default)* manual;<br>1 - automatic.| ##### Opération de surcharge d'inventaire de la règle LLD Opération de surcharge de la valeur de mode d'inventaire de la règle LLD qui est définie sur l'hôte découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**inventory\_mode**<br>(obligatoire)|integer|Ignorer le mode d'inventaire du prototype de l'hôte.<br><br>Les valeurs possibles sont :<br>-1 - désactivé ;<br>0 - *(par défaut)* manuel ;<br>1 - automatique.| ##### LLD rule override operation period LLD rule override operation period is an update interval value (supports custom intervals) that is set to discovered item. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**delay**<br>(required)|string|Override the update interval of the item prototype. Accepts seconds or a time unit with suffix (30s,1m,2h,1d) as well as flexible and scheduling intervals and user macros or LLD macros. Multiple intervals are separated by a semicolon.| ##### Période d'opération de surcharge de la règle LLD La période d'opération de surcharge de règle LLD est une valeur d'intervalle de mise à jour (prend en charge les intervalles personnalisés) qui est définie sur l'élément découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**delay**<br>(obligatoire)|string|Surcharge l'intervalle de mise à jour du prototype d'élément. Accepte les secondes ou une unité de temps avec suffixe (30s,1m,2h,1d) ainsi que des intervalles flexibles et de planification et des macros utilisateur ou LLD. Les intervalles multiples sont séparés par un point-virgule.| ##### LLD rule override operation severity LLD rule override operation severity value that is set to discovered trigger. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**severity**<br>(required)|integer|Override the severity of trigger prototype.<br><br>Possible values are: 0 - *(default)* not classified;<br>1 - information;<br>2 - warning;<br>3 - average;<br>4 - high;<br>5 - disaster.| ##### Opération de surcharge de la sévérité de la règle LLD L'opération de surcharge de la sévérité de la règle LLD définie sur le déclencheur découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**severity**<br>(obligatoire)|integer|Surcharge la sévérité du prototype de déclencheur.<br><br>Les valeurs possibles sont : 0 - *(par défaut)* non classifié ;<br>1 - information ;<br>2 - avertissement ;<br>3 - moyenne ;<br >4 - élevé ;<br>5 - désastre.| ##### LLD rule override operation status LLD rule override operation status that is set to discovered object. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**status**<br>(required)|integer|Override the status for selected object.<br><br>Possible values:<br>0 - Create enabled;<br>1 - Create disabled.| ##### Statut de l'opération de surcharge de la règle LLD Statut d'opération de surcharge de règle LLD qui est défini sur objet découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**status**<br>(obligatoire)|integer|Remplace le statut de l'objet sélectionné.<br><br>Valeurs possibles :<br>0 - Création activée ;<br>1 - Création désactivée.| ##### LLD rule override operation tag LLD rule override operation tag object contains tag name and value that are set to discovered object. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|New tag name.| |value|string|New tag value.| ##### Opération de surcharge de tag de la règle LLD L'opération de surcharge de tag de la règle LLD contient le nom et la valeur du tag définis sur l'objet découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nouveau nom de tag.| |value|string|Nouvelle valeur de tag.| ##### LLD rule override operation template LLD rule override operation template object that is linked to discovered host. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templateid**<br>(required)|string|Override the template of host prototype linked templates.| ##### Opération de surcharge de modèle de la règle LLD Objet d'opération de surcharge de modèle lié à l'hôte découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templateid**<br>(obligatoire)|string|Surcharge le modèle des modèles liés au prototype d'hôte.| #### LLD rule override operation The LLD rule override operation is combination of conditions and actions to perform on the prototype object. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operationobject**<br>(required)|integer|Type of discovered object to perform the action.<br><br>Possible values:<br>0 - Item prototype;<br>1 - Trigger prototype;<br>2 - Graph prototype;<br>3 - Host prototype.| |operator|integer|Override condition operator.<br><br>Possible values:<br>0 - *(default)* equals;<br>1 - does not equal;<br>2 - contains;<br>3 - does not contain;<br>8 - matches;<br>9 - does not match.| |value|string|Pattern to match item, trigger, graph or host prototype name depending on selected object.| |opstatus|object|Override operation status object for item, trigger and host prototype objects.| |opdiscover|object|Override operation discover status object (all object types).| |opperiod|object|Override operation period (update interval) object for item prototype object.| |ophistory|object|Override operation history object for item prototype object.| |optrends|object|Override operation trends object for item prototype object.| |opseverity|object|Override operation severity object for trigger prototype object.| |optag|array|Override operation tag object for trigger and host prototype objects.| |optemplate|array|Override operation template object for host prototype object.| |opinventory|object|Override operation inventory object for host prototype object.| #### Opération de surcharge de règle LLD L'opération de surcharge de règle LLD est une combinaison de conditions et d'actions à effectuer sur l'objet prototype. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operationobject**<br>(obligatoire)|integer|Type d'objet découvert pour effectuer l'action.<br><br>Valeurs possibles :<br>0 - Prototype d'élément ;<br>1 - Prototype de déclencheur ;<br>2 - Prototype de graphique ;<br>3 - Prototype d'hôte.| |operator|integer|Opérateur de condition de surcharge.<br><br>Valeurs possibles :<br>0 - *(par défaut)* est égal ;<br>1 - n'est pas égal ;<br>2 - contient ;<br>3 - ne contient pas ; <br>8 - correspond ;<br>9 - ne correspond pas.| |value|string|Motif pour faire correspondre l'élément, le déclencheur, le graphique ou le nom du prototype d'hôte en fonction de l'objet sélectionné.| |opstatus|object|Objet statut d'opération de surcharge pour les objets de prototype d'élément, de déclencheur et d'hôte.| |opdiscover|object|Objet statut d'opération de surcharge de découverte (tout type d'objet).| |opperiod|object|Objet période d'opération de surcharge (intervalle de mise à jour) pour l'objet prototype d'élément.| |ophistory|object|Objet historique d'opération de surcharge pour l'objet prototype d'élément.| |optrends|object|Objet tendances d'opération de surcharge pour l'objet prototype d'élément.| |opseverity|object|Objet sévérité d'opération de surcharge pour l'objet prototype de déclencheur.| |optag|array|Objet tag d'opération de surcharge pour l'objet prototype d'hôte.| |optemplate|array|Objet modèle d'opération de surcharge pour l'objet prototype d'hôte.| |opinventory|object|Objet inventaire d'opération de surcharge pour l'objet prototype d'hôte.| ##### LLD rule override operation trends LLD rule override operation trends value that is set to discovered item. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**trends**<br>(required)|string|Override the trends of item prototype which is a time unit of how long the trends data should be stored. Also accepts user macro and LLD macro.| ##### Opération de surcharge des tendances de la règle LLD L'opération de surcharge des tendances de la règle LLD définie sur l'élément découvert. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**trends**<br>(obligatoire)|string|Surcharge les tendances du prototype d'élément qui est une unité de temps de la durée pendant laquelle les données de tendances doivent être stockées. Accepte également la macro utilisateur et la macro LLD.| ### LLD rule overrides The LLD rule overrides object defines a set of rules (filters, conditions and operations) that are used to override properties of different prototype objects. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Unique override name.| |**step**<br>(required)|integer|Unique order number of the override.| |stop|integer|Stop processing next overrides if matches.<br><br>Possible values:<br>0 - *(default)* don't stop processing overrides;<br>1 - stop processing overrides if filter matches.| |filter|object|Override filter.| |operations|array|Override operations.| ### Surcharge de règle LLD L'objet de surcharge de règle LLD définit un ensemble de règles (filtres, conditions et opérations) qui sont utilisées pour remplacer les propriétés de différents objets prototypes. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(obligatoire)|string|Nom unique de surcharge.| |**step**<br>(obligatoire)|integer|Numéro d'ordre unique de la surcharge.| |stop|integer|Arrêt de traitement des prochaines surcharges si correspondances.<br><br>Valeurs possibles :<br>0 - *(par défaut)* n'arrête pas de traiter les surcharges ;<br>1 - arrête de traiter les surcharges si le filtre correspond.| |filter|object|Filtre de surcharge.| |operations|array|Opérations de surcharge.| ### LLD rule The low-level discovery rule object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the LLD rule.| |**delay**<br>(required)|string|Update interval of the LLD rule. Accepts seconds or time unit with suffix and with or without one or more [custom intervals](/manual/config/items/item/custom_intervals) that consist of either flexible intervals and scheduling intervals as serialized strings. Also accepts user macros. Flexible intervals could be written as two macros separated by a forward slash. Intervals are separated by a semicolon.<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host that the LLD rule belongs to.| |**interfaceid**<br>(required)|string|ID of the LLD rule's host interface. Used only for host LLD rules.<br><br>Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, dependent, database monitor and script LLD rules. Optional for HTTP agent LLD rules.| |**key\_**<br>(required)|string|LLD rule key.| |**name**<br>(required)|string|Name of the LLD rule.| |**type**<br>(required)|integer|Type of the LLD rule.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>10 - external check;<br>11 - database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - TELNET agent;<br>16 - JMX agent;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script.| |**url**<br>(required)|string|URL string, required for HTTP agent LLD rule. Supports user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |allow\_traps|integer|HTTP agent LLD rule field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent or HTTP agent LLD rules.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM| |description|string|Description of the LLD rule.| |error|string|*(readonly)* Error text if there are problems updating the LLD rule.| |follow\_redirects|integer|HTTP agent LLD rule field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent LLD rule field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |http\_proxy|string|HTTP agent LLD rule field. HTTP(S) proxy connection string.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI LLD rules.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lifetime|string|Time period after which items that are no longer discovered will be deleted. Accepts seconds, time unit with suffix and user macro.<br><br>Default: `30d`.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and maximum count of dependent items equal to 999 are allowed.<br>Discovery rule cannot be master item for another discovery rule.<br><br>Required for Dependent item.| |output\_format|integer|HTTP agent LLD rule field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the LLD rule:<br>- executed script for SSH and Telnet LLD rules;<br>- SQL query for database monitor LLD rules;<br>- formula for calculated LLD rules.| |parameters|array|Additional parameters for script type LLD rule. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent LLD rules.| |post\_type|integer|HTTP agent LLD rule field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent LLD rule field. HTTP(S) request body data. Used with post\_type.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent LLD rule field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent LLD rule field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent LLD rule field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent LLD rule field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent LLD rule field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent LLD rule field. Password for SSL Key file.| |state|integer|*(readonly)* State of the LLD rule.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - not supported.| |status|integer|Status of the LLD rule.<br><br>Possible values:<br>0 - *(default)* enabled LLD rule;<br>1 - disabled LLD rule.| |status\_codes|string|HTTP agent LLD rule field. Ranges of required HTTP status codes separated by commas. Also supports user macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template LLD rule.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script LLD rules. Supports user macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper LLD rules or HTTP agent LLD rules.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent LLD rules.<br><br>Required by SSH and Telnet LLD rules.| |uuid|string|Universal unique identifier, used for linking imported LLD rules to already existing ones. Used only for LLD rules on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |verify\_host|integer|HTTP agent LLD rule field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |verify\_peer|integer|HTTP agent LLD rule field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Règle LLD L'objet de règle de découverte de bas niveau a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(lecture seule)* ID de la règle LLD.| |**delay**<br>(obligatoire)|string|Intervalle de mise à jour de la règle LLD. Accepte les secondes ou l'unité de temps avec suffixe et avec ou sans un ou plusieurs [intervalles personnalisés](/manual/config/items/item/custom_intervals) qui se composent d'intervalles flexibles et d'intervalles de planification sous forme de chaînes sérialisées. Accepte également les macros utilisateur. Les intervalles flexibles peuvent être écrits sous la forme de deux macros séparées par une barre oblique. Les intervalles sont séparés par un point-virgule.<br><br>Facultatif pour le trappeur Zabbix, les éléments dépendants et pour l'agent Zabbix (actif) avec la clé `mqtt.get`.| |**hostid**<br>(obligatoire)|string|ID de l'hôte auquel appartient la règle LLD.| |**interfaceid**<br>(obligatoire)|string|ID de l'interface hôte de la règle LLD. Utilisé uniquement pour les règles LLD d'hôte.<br><br>Non requis pour l'agent Zabbix (actif), Zabbix interne, le trappeur Zabbix, dépendant, le moniteur de base de données et les règles LLD script. Facultatif pour les règles LLD de l'agent HTTP.| |**key\_**<br>(obligatoire)|string|Clé de la règle LLD.| |**name**<br>(obligatoire)|string|Nom de la règle LLD.| |**type**<br>(obligatoire)|integer|Type de la règle LLD..<br><br>Valeurs possibles :<br>0 - agent Zabbix ;<br>2 - trappeur Zabbix ;<br>3 - vérification simple ;<br>5 - Zabbix interne ;<br>7 - agent Zabbix (actif) ;<br>10 - vérification externe ;<br>11 - moniteur de base de données ;<br>12 - agent IPMI ;<br>13 - agent SSH ;<br>14 - agent TELNET ;<br>16 - agent JMX ;<br>18 - élément dépendant ;< br>19 - Agent HTTP ;<br>20 - Agent SNMP ;<br>21 - Script.| |**url**<br>(obligatoire)|string|Chaîne URL, requise pour la règle LLD de l'agent HTTP. Prend en charge les macros utilisateur, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |allow\_traps|integer|Champ de la règle LLD de l'agent HTTP. Autoriser également le remplissage de la valeur comme dans le type d'élément trappeur.<br><br>0 - *(par défaut)* Ne pas autoriser l'acceptation des données entrantes.<br>1 - Autoriser l'acceptation des données entrantes.| |authtype|integer|Utilisé uniquement par les règles LLD de l'agent SSH ou de l'agent HTTP.<br><br>Valeurs possibles de la méthode d'authentification de l'agent SSH :<br>0 - mot de passe *(par défaut)* ;<br>1 - clé publique.<br><br> Valeurs possibles de la méthode d'authentification de l'agent HTTP :<br>0 - *(par défaut)* aucune<br>1 - de base<br>2 - NTLM| |description|string|Description de la règle LLD.| |error|string|*(lecture seule)* Texte d'erreur en cas de problèmes de mise à jour de la règle LLD.| |follow\_redirects|integer|Champ de règle LLD de l'agent HTTP. Suivre les redirections de réponse lors du regroupement des données.<br><br>0 : Ne pas suivre les redirections.<br>1 : *(par défaut)* Suivez les redirections.| |headers|object|Champ de règle LLD de l'agent HTTP. Objet avec en-têtes de requête HTTP(S), où le nom de l'en-tête est utilisé comme clé et la valeur de l'en-tête comme valeur.<br><br>Exemple :<br>{ "User-Agent": "Zabbix" }| |http\_proxy|string|Champ de règle LLD de l'agent HTTP. Chaîne de connexion proxy HTTP(S).| |ipmi\_sensor|string|Capteur IPMI. Utilisé uniquement par les règles IPMI LLD.| |jmx\_endpoint|string|Chaîne de connexion personnalisée de l'agent JMX.<br><br>Valeur par défaut :<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lifetime|string|Période après laquelle les éléments qui ne sont plus découverts seront supprimés. Accepte les secondes, l'unité de temps avec suffixe et la macro utilisateur.<br><br>Par défaut : `30d`.| |master\_itemid|integer|ID de l'élément principal.<br> La récursivité jusqu'à 3 éléments dépendants et le nombre maximal d'éléments dépendants égal à 999 sont autorisés.<br> La règle de découverte ne peut pas être l'élément principal pour une autre règle de découverte.<br><br> Obligatoire pour l'élément dépendant.| |output\_format|integer|Champ de règle LLD de l'agent HTTP. La réponse doit-elle être convertie en JSON.<br><br>0 - *(par défaut)* Stocker brut.<br>1 - Convertir en JSON.| |params|string|Paramètres supplémentaires en fonction du type de règle LLD :<br>- script exécuté pour les règles LLD SSH et Telnet ;<br>- requête SQL pour les règles LLD moniteur de base de données ;<br>- formule pour les règles LLD calculées.| |parameters|array|Paramètres supplémentaires pour la règle LLD de type script. Tableau d'objets avec les propriétés 'name' et 'value', où name doit être unique.| |password|string|Mot de passe pour l'authentification. Utilisé pour vérification simple, SSH, Telnet, moniteur de base de données, règles LLD JMX et agent HTTP.| |post\_type|integer|Champ de règle LLD de l'agent HTTP. Type de corps de données post stocké dans la propriété posts.<br><br>0 - *(par défaut)* Données brutes.<br>2 - Données JSON.<br>3 - Données XML.| |posts|string|Champ de règle LLD de l'agent HTTP. Données du corps de la requête HTTP(S). Utilisé avec post\_type.| |privatekey|string|Nom du fichier de clé privée.| |publickey|string|Nom du fichier de clé publique.| |query\_fields|array|Champ de règle LLD de l'agent HTTP. Paramètres de requête. Tableau d'objets avec des paires 'clé':'valeur', où la valeur peut être une chaîne vide.| |request\_method|integer|Champ de règle LLD de l'agent HTTP. Type de méthode de requête.<br><br>0 - *(par défaut)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|Champ de règle LLD de l'agent HTTP. Quelle partie de la réponse doit être stockée.<br><br>0 - *(par défaut)* Corps.<br>1 - En-têtes.<br>2 - Le corps et les en-têtes seront stockés.<br><br>Pour request\_method HEAD seul 1 est la valeur autorisée.| |snmp\_oid|string|OID SNMP.| |ssl\_cert\_file|string|Champ de règle LLD de l'agent HTTP. Chemin d'accès au fichier de clé SSL publique.| |ssl\_key\_file|string|Champ de règle LLD de l'agent HTTP. Chemin d'accès au fichier de clé SSL privée.| |ssl\_key\_password|string|Champ de règle LLD de l'agent HTTP. Mot de passe pour le fichier de clé SSL.| |state|integer|*(lecture seule)* État de la règle LLD.<br><br>Valeurs possibles :<br>0 - *(par défaut)* normal ;<br>1 - non pris en charge.| |status|integer|Statut de la règle LLD.<br><br>Valeurs possibles :<br>0 - *(par défaut)* règle LLD activée ;<br>1 - règle LLD désactivée.| |status\_codes|string|Champ de règle LLD de l'agent HTTP. Plages de codes d'état HTTP requis séparés par des virgules. Prend également en charge les macros utilisateur dans le cadre d'une liste séparée par des virgules.<br><br>Exemple : 200,200-{$M},{$M},200-400| |templateid|string|(lecture seule) ID de la règle LLD du modèle parent.| |timeout|string|Délai d'expiration de la demande d'interrogation des données d'élément. Utilisé pour l'agent HTTP et les règles LLD script. Prend en charge les macros utilisateur.<br><br>par défaut : 3s<br>valeur maximale : 60s| |trapper\_hosts|string|Hôtes autorisés. Utilisé par les règles LLD trapper ou les règles LLD agent HTTP.| |username|string|Nom d'utilisateur pour l'authentification. Utilisé par vérification simple, SSH, Telnet, moniteur de base de données, JMX et règles LLD agent HTTP.<br><br>Requis par les règles LLD SSH et Telnet.| |uuid|string|Identifiant unique universel, utilisé pour lier les règles LLD importées à celles déjà existantes. Utilisé uniquement pour les règles LLD sur les modèles. Généré automatiquement, s'il n'est pas fourni.<br><br>Pour les opérations de mise à jour, ce champ est en *lecture seule*.| |verify\_host|integer|Champ de règle LLD agent HTTP. Valide que le nom d'hôte dans l'URL se trouve dans le champ Nom commun ou dans un champ Autre nom du sujet du certificat d'hôte.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| |verify\_peer|integer|Champ de règle LLD agent HTTP. Valide si le certificat de l'hôte est authentique.<br><br>0 - *(par défaut)* Ne pas valider.<br>1 - Valider.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. ### Loadable MongoDB plugin MongoDB [plugin](https://git.zabbix.com/projects/AP/repos/mongodb/browse/README.md) is no longer part of Zabbix agent 2 and is now available as a loadable plugin instead. List of supported MongoDB versions has been extended to *2.6-5.3*. Plugin functionality and set of supported [items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#mongodb) haven't change. ### Plugin MongoDB chargeable Le [plugin MongoDB](https://git.zabbix.com/projects/AP/repos/mongodb/browse/README.md) ne fait plus partie de l'agent Zabbix 2 et est désormais disponible en tant que plugin chargeable à la place. La liste des versions de MongoDB prises en charge a été étendue à *2.6-5.3*. La fonctionnalité du plug-in et l'ensemble des [éléments](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#mongodb) pris en charge n'ont pas changé. ### Loadable MongoDB plugin MongoDB [plugin](https://git.zabbix.com/projects/AP/repos/mongodb/browse/README.md) is no longer part of Zabbix agent 2 and is now available as a loadable plugin instead. List of supported MongoDB versions has been extended to *2.6-5.3*. Plugin functionality and set of supported [items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#mongodb) haven't change. The MongoDB plugin, along with other loadable plugins which may potentially be added in the future, is stored in the new repository [zabbix-agent2-plugins](http://repo.zabbix.com/zabbix-agent2-plugins/). The package *zabbix-release* now adds this repository to the user's system. To continue monitoring MongoDB on the installations from official Zabbix packages, update *zabbix-release* package and install *zabbix-agent2-plugin-mongodb* package. Sources are available on [CDN](https://cdn.zabbix.com/zabbix-agent2-plugins/sources/mongodb/). ### Plugin MongoDB chargeable Le [plugin MongoDB](https://git.zabbix.com/projects/AP/repos/mongodb/browse/README.md) ne fait plus partie de l'agent Zabbix 2 et est désormais disponible en tant que plugin chargeable à la place. La liste des versions de MongoDB prises en charge a été étendue à *2.6-5.3*. La fonctionnalité du plug-in et l'ensemble des [éléments](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#mongodb) pris en charge n'ont pas changé. Le plugin MongoDB, ainsi que d'autres plugins chargeables qui pourraient potentiellement être ajoutés à l'avenir, sont stockés dans le nouveau référentiel [zabbix-agent2-plugins](http://repo.zabbix.com/zabbix-agent2-plugins/). Le package *zabbix-release* ajoute maintenant ce référentiel au système de l'utilisateur. Pour continuer à surveiller MongoDB sur les installations à partir des packages officiels de Zabbix, mettez à jour le package *zabbix-release* et installez le package *zabbix-agent2-plugin-mongodb*. Les sources sont disponibles sur [CDN](https://cdn.zabbix.com/zabbix-agent2-plugins/sources/mongodb/). ## Loadable plugins ### Encrypted MongoDB plugin connection MongoDB plugin now supports TLS encryption when connecting to MongoDB using named sessions. Updated plugin (MongoDB plugin 1.2.1) is included into Zabbix official packages starting from Zabbix 6.0.14. Note that MongoDB is a loadable plugin and can be installed separately either from packages or from sources. The plugin will work with any minor version of Zabbix 6.0. For more details see [MongoDB plugin](/manual/appendix/config/zabbix_agent2_plugins/mongodb_plugin). ## Plugin chargeable ### Connexion chiffrée du plugin MongoDB Le plugin MongoDB prend désormais en charge le chiffrement TLS lors de la connexion à MongoDB à l'aide de sessions nommées. Le plugin à jour (plugin MongoDB 1.2.1) est inclus dans les paquets officiels de Zabbix à partir de Zabbix 6.0.14. Notez que MongoDB est un plugin chargeable et peut être installé séparément des paquets ou des sources. Le plugin fonctionnera avec n'importe quelle version mineure de Zabbix 6.0. Pour plus de détails, voir [Plugin MongoDB](/manual/appendix/config/zabbix_agent2_plugins/mongodb_plugin). ##### Load on I/O Item's persistent file is updated after successful sending of every batch of data \(containing item's data\) to server. For example, default 'BufferSize' is 100. If a log item has found 70 matching records then the first 50 records will be sent in one batch, persistent file will be updated, then remaining 20 records will be sent \(maybe with some delay when more data is accumulated\) in the 2nd batch, and the persistent file will be updated again. ##### Charge sur les E/S Le fichier persistant de l'élément est mis à jour après l'envoi réussi de chaque lot de données \(contenant les données de l'élément\) au serveur. Par exemple, 'BufferSize' par défaut est 100. Si un élément de journal a trouvé 70 enregistrements correspondants, les 50 premiers enregistrements seront envoyés en un seul lot, le fichier persistant sera mis à jour, puis les 20 enregistrements restants seront envoyés \(peut-être avec un certain retard lorsque plus de données sont accumulées \) dans le 2e lot, et le fichier persistant sera à nouveau mis à jour. #### Locale Note that the agent requires a UTF-8 locale so that some textual agent items can return the expected content. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically. #### Environnement local Notez que l'agent requiert un environnement local UTF-8 afin que certains éléments textuels d'agent puissent renvoyer le contenu attendu. La plupart des systèmes modernes de type Unix ont un paramètre régional UTF-8 par défaut, cependant, certains systèmes peuvent avoir besoin d'être définis spécifiquement. #### Locale Note that the proxy requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically. #### Environnement Local Notez que le proxy requiert un environnement local UTF-8 afin que certains éléments textuels puissent être interprétés correctement. La plupart des systèmes modernes de type Unix ont un paramètre régional UTF-8 par défaut, cependant, certains systèmes peuvent avoir besoin d'être définis spécifiquement. #### Locale Note that the server requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically. #### Environnement local Notez que le serveur requiert un environnement local UTF-8 afin que les éléments textuels puissent être interprétés correctement. La plupart des systèmes modernes de type Unix ont un paramètre régional UTF-8 par défaut, cependant, certains systèmes peuvent avoir besoin d'être définis spécifiquement. ### Log entry The log entry object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |level|integer|Log level.| |ms|string|The time elapsed in milliseconds since the script was run before log entry was added.| |message|string|Log message.| ### Entrée de journal L'objet d'entrée de journal a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |level|integer|Niveau de journal.| |ms|string|Le temps écoulé en millisecondes depuis l'exécution du script avant l'ajout de l'entrée de journal.| |message|string|Message de journal.| #### Log file monitoring `log[]` and `logrt[]` items repeatedly reread log file from the beginning if file system is 100% full and the log file is being appended (see [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) for more information). #### Surveillance des fichiers de log Les éléments `log[]` et `logrt[]` relisent à plusieurs reprises le fichier journal depuis le début si le système de fichiers est plein à 100 % et que le fichier de log est en mode append (voir [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) pour plus d'informations). ##### Logging Add the "Log test" entry to the Zabbix server log and receive the item value "1" in return: - Create an item with type "Script". - In the *Script* field, enter: ```javascript Zabbix.log(3, 'Log test'); return 1; ``` ##### Journalisation Ajouter l'entrée "Log test" au fichier de log du serveur Zabbix et recevez la valeur de l'élément "1" en retour : - Créer un élément de type "Script". - Dans le champ *Script*, saisir : ```javascript Zabbix.log(3, 'Log test'); return 1; ``` #### Logging out Log out from the API. Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.logout", "params": [], "id": 1, "auth": "16a46baf181ef9602e1687f3110abf8a" } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` #### Déconnecter Déconnectez-vous de l'API. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.logout", "params": [], "id": 1, "auth": "16a46baf181ef9602e1687f3110abf8a" } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": true, "id": 1 } ``` ### Log history The log history object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.| ### Historique des log L'objet d'historique de log a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID de l'entrée d'historique.| |clock|timestamp|Heure à laquelle cette valeur a été reçue.| |itemid|string|ID de l'élément associé.| |logeventid|integer|ID d'entrée du journal des événements Windows.| |ns|integer|Nanosecondes lorsque la valeur a été reçue.| |severity|integer|Niveau d'entrée du journal des événements Windows.| |source|string|Source de l'entrée du journal des événements Windows.| |timestamp|timestamp|Heure d'entrée du journal des événements Windows.| |value|text|Valeur reçue.| #### Login and systemd We recommend [creating](/manual/installation/install#create_user_account) a *zabbix* user as system user, that is, without ability to log in. Some users ignore this recommendation and use the same account to log in (e. g. using SSH) to host running Zabbix. This might crash Zabbix daemon on log out. In this case you will get something like the following in Zabbix server log: zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument and in Zabbix agent log: zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument This happens because of default systemd setting `RemoveIPC=yes` configured in `/etc/systemd/logind.conf`. When you log out of the system the semaphores created by Zabbix previously are removed which causes the crash. A quote from systemd documentation: RemoveIPC= Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources after the last of the user's sessions terminated. This covers System V semaphores, shared memory and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the root user and other system users are excluded from the effect of this setting. Defaults to "yes". There are 2 solutions to this problem: 1. (recommended) Stop using *zabbix* account for anything else than Zabbix processes, create a dedicated account for other things. 2. (not recommended) Set `RemoveIPC=no` in `/etc/systemd/logind.conf` and reboot the system. Note that `RemoveIPC` is a system-wide parameter, changing it will affect the whole system. #### Connexion et systemd Nous recommandons de [créer](/manual/installation/install#create_user_account) un utilisateur *zabbix* en tant qu'utilisateur système, c'est-à-dire sans possibilité de se connecter. Certains utilisateurs ignorent cette recommandation et utilisent le même compte pour se connecter (par exemple en utilisant SSH) à l'hôte qui exécute de Zabbix. Cela pourrait faire tomber le démon Zabbix lors de la déconnexion. Dans ce cas, vous obtiendrez quelque chose comme ce qui suit dans le journal du serveur Zabbix : zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument et dans le journal de l'agent Zabbix : zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument Cela se produit à cause du paramètre par défaut de systemd `RemoveIPC=yes` configuré dans `/etc/systemd/logind.conf`. Lorsque vous vous déconnectez du système, les sémaphores créés précédemment par Zabbix sont supprimés, ce qui provoque le plantage. Une citation de la documentation de systemd : RemoveIPC= Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources after the last of the user's sessions terminated. This covers System V semaphores, shared memory and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the root user and other system users are excluded from the effect of this setting. Defaults to "yes". Il existe 2 solutions à ce problème : 1. (recommandée) Arrêtez d'utiliser le compte *zabbix* pour autre chose que les processus Zabbix, créez un compte dédié pour d'autres choses. 2. (non recommandée) Définissez `RemoveIPC=no` dans `/etc/systemd/logind.conf` et redémarrez le système. Notez que `RemoveIPC` est un paramètre à l'échelle du système, sa modification affectera l'ensemble du système. #### Log in Zabbix frontend is ready! The default user name is **Admin**, password **zabbix**. {width="350"} Proceed to [getting started with Zabbix](/manual/quickstart/login). #### Connexion L'interface Zabbix est prête ! Le nom d'utilisateur par défaut est **Admin**, mot de passe **zabbix**. {width="350"} Passez à [Démarrer avec Zabbix](/manual/quickstart/login). ### Log level control targets *process-type* All processes of specified type (active checks, collector, listener) *process-type,N* Process type and number (e.g., listener,3) *pid* Process identifier, up to 65535. For larger values specify target as "process-type,N" ```{=html} <!-- --> ``` **-p**, **--print** Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are: d Number with a decimal part. m Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state. s Text. Maximum length not limited. t Text. Same as **s**. u Unsigned integer. **-t**, **--test** *item-key* Test single item and exit. See **--print** for output description. **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAH} ### Cibles de contrôle au niveau du journal *process-type* Tous les processus du type spécifié (vérifications actives, collecteur, listener) *process-type,N* Type et nombre de processus (par exemple, listener,3) *pid* Identificateur de processus, jusqu'à 65535. Pour des valeurs supérieures, spécifiez la cible comme "process-type,N" ```{=html} <!-- --> ``` **-p**, **--print** Imprimer les éléments connus et quitter. Pour chaque élément, soit des valeurs par défaut génériques sont utilisées, soit des valeurs par défaut spécifiques pour les tests sont fournies. Ces valeurs par défaut sont répertoriées entre crochets en tant que paramètres clés de l'élément. Les valeurs renvoyées sont entre crochets et préfixées par le type de la valeur renvoyée, séparées par un caractère pipe. Pour les paramètres utilisateur, le type est toujours **t**, car l'agent ne peut pas déterminer toutes les valeurs de retour possibles. Les éléments, affichés comme fonctionnant, ne sont pas garantis de fonctionner à partir du serveur Zabbix ou de zabbix\_get lors de l'interrogation d'un démon d'agent en cours d'exécution, car les autorisations ou l'environnement peuvent être différents. Les types de valeurs renvoyées sont : d Nombre avec une partie décimale. m Non supporté. Cela peut être dû à l'interrogation d'un élément qui ne fonctionne qu'en mode actif, comme un élément de surveillance du journal ou un élément qui nécessite plusieurs valeurs collectées. Des problèmes d'autorisation ou des paramètres utilisateur incorrects peuvent également entraîner l'état non pris en charge. s Texte. Longueur maximale non limitée. t Texte. Comme **s**. u Entier non signé. **-t**, **--test** *item-key* Tester un seul élément et quitter. Voir **--print** pour la description de la sortie. **-h**, **--help** Afficher cette aide et quitter. **-V**, **--version** Afficher les informations de version et quitter. [ ]{#lbAH} ###### Log request A request sent by a plugin to write a log message into the agent log file. | | | |---|---| |direction|plugin → agent| |response|no| Parameters specific to log requests: |Name|Type|Comments| |---------|--------|----------| |severity|uint32|The message severity (log level).| |message|string|The message to log.| *Example:* {"id":0,"type":1,"severity":3,"message":"message"} ###### Requête de journal Requête envoyée par un plug-in pour écrire un message de journal dans le fichier journal de l'agent. | | | |---|---| |direction|plugin → agent| |réponse|non| Paramètres spécifiques aux requêtes de journal : |Nom|Type|Commentaires| |---------|--------|----------| |severity|uint32|La gravité du message (niveau de journalisation).| |message|chaîne|Le message à consigner.| *Exemple:* {"id":0,"type":1,"severity":3,"message":"message"} #### Low-level discovery Configure low-level discovery rules as well as item, trigger and graph prototypes to monitor dynamic entities. [LLD rule API](/manual/api/reference/discoveryrule) | [Item prototype API](/manual/api/reference/itemprototype) | [Trigger prototype API](/manual/api/reference/triggerprototype) | [Graph prototype API](/manual/api/reference/graphprototype) | [Host prototype API](/manual/api/reference/hostprototype) #### Découverte de bas niveau Configurez des règles de découverte de bas niveau ainsi que des prototypes d'éléments, de déclencheurs et de graphiques pour surveiller les entités dynamiques. [API Règle de découverte bas niveau](/manual/api/reference/discoveryrule) | [API Prototype d'élément](/manual/api/reference/itemprototype) | [API Prototype de déclencheur](/manual/api/reference/triggerprototype) | [API Prototype de graphique](/manual/api/reference/graphprototype) | [API Prototype d'hôte](/manual/api/reference/hostprototype) #### Low-level discovery In a [low-level discovery rule](/manual/discovery/low_level_discovery#configuring_low-level_discovery), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Key parameters|<|yes| |Update interval|<|no| |Custom interval|<|no| |Keep lost resources period|<|no| |Description|<|yes| |*SNMP agent*|<|<| | |SNMP OID|yes| |*SSH agent*|<|<| | |Username|yes| |^|Public key file|yes| |^|Private key file|yes| |^|Password|yes| |^|Script|yes| |*TELNET agent*|<|<| | |Username|yes| |^|Password|yes| |^|Script|yes| |*Zabbix trapper*|<|<| | |Allowed hosts|yes| |*Database monitor*|<|<| | |Username|yes| |^|Password|yes| |^|SQL query|yes| |*JMX agent*|<|<| | |JMX endpoint|yes| |*HTTP agent*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|yes| |^|Query fields|yes| |^|Timeout|no| |^|Request body|yes| |^|Headers (names and values)|yes| |^|Required status codes|yes| |^|HTTP authentication username|yes| |^|HTTP authentication password|yes| |*Filters*|<|<| | |Regular expression|yes| |*Overrides*|<|<| | |Filters: regular expression|yes| |^|Operations: update interval (for item prototypes)|no| |^|Operations: history storage period (for item prototypes)|no| |^|Operations: trend storage period (for item prototypes)|no| #### Découverte de bas niveau Dans une [règle de découverte de bas niveau](/manual/discovery/low_level_discovery#configuring_low-level_discovery), les macros utilisateur peuvent être utilisées dans les champs suivants : |Emplacement|<|Plusieurs macros/mix avec du texte^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Paramètres de clé|<|oui| |Intervalle de mise à jour|<|non| |Intervalle personnalisé|<|non| |Période de conservation des ressources perdues|<|non| |Description|<|oui| |*Agent SNMP*|<|<| | |OID SNMP|oui| |*Agent SSH*|<|<| | |Nom d'utilisateur|oui| |^|Fichier de clé publique|oui| |^|Fichier de clé privée|oui| |^|Mot de passe|oui| |^|Script|oui| |*Agent TELNET*|<|<| | |Nom d'utilisateur|oui| |^|Mot de passe|oui| |^|Script|oui| |*Trapper Zabbix*|<|<| | |Hötes autorisés|oui| |*Surveillance de base de données*|<|<| | |Nom d'utilisateur|oui| |^|Mot de passe|oui| |^|Requête SQL|oui| |*Agent JMX agent*|<|<| | |Point de terminaison JMX|oui| |*Agent HTTP*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|oui| |^|Champs de requête|oui| |^|Délai d'expiration|non| |^|Corps de la requête|oui| |^|En-têtes (noms et valeurs)|oui| |^|Codes de statuts requis|oui| |^|Nom d'utilisateur d'authentification HTTP|oui| |^|Mot de passe d'authentification HTTP|oui| |*Filtres*|<|<| | |Expression régulière|oui| |*Remplacements*|<|<| | |Filtres : Expression régulière|oui| |^|Opérations : intervalle de mise à jour (pour les prototypes d'éléments)|non| |^|Opérations : période de stockage de l'historique (pour les prototypes d'éléments)|non| |^|Opérations : période de stockage des tendances (pour les prototypes d'éléments)|non| #### Low-level discovery macros Even though no low-level discovery macros are created in the returned JSON, these macros can be defined by the user as an additional step, using the [custom LLD macro](/manual/discovery/low_level_discovery#custom_macros) functionality with JSONPath pointing to the discovered values in the returned JSON. The macros then can be used to create item, trigger, etc prototypes. #### Macros de découverte de bas niveau Même si aucune macro de découverte de bas niveau n'est créée dans le JSON renvoyé, ces macros peuvent être définies par l'utilisateur comme une étape supplémentaire, à l'aide de [macros LLD personnalisées](/manual/discovery/low_level_discovery#custom_macros) avec un JSONPath pointant vers les valeurs découvertes dans le JSON renvoyé. Les macros peuvent ensuite être utilisées pour créer des prototypes d'éléments, de déclencheurs, etc. #### Macros #### Macros Macros for internal actions contain the reason why an item, an LLD-rule, or a trigger became unsupported: - {ITEM.STATE.ERROR} - for item-based internal notifications; - {LLDRULE.STATE.ERROR} - for LLD-rule based internal notifications; - {TRIGGER.STATE.ERROR} - for trigger-based internal notifications. For more details, see [Supported macros](/manual/appendix/macros/supported_by_location). Les macros pour les actions internes contiennent la raison pour laquelle un élément, une règle LLD ou un déclencheur n'est plus pris en charge : - {ITEM.STATE.ERROR} - pour les notifications internes basées sur les éléments ; - {LLDRULE.STATE.ERROR} - pour les notifications internes basées sur les règles LLD ; - {TRIGGER.STATE.ERROR} - pour les notifications internes basées sur des déclencheurs. Pour plus de détails, voir [Macros prises en charge](/manual/appendix/macros/supported_by_location). #### Macro support The following macros may be used in trigger tags: - {ITEM.VALUE}, {ITEM.LASTVALUE}, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros can be used to populate the tag name or tag value - {INVENTORY.\*} [macros](/manual/appendix/macros/supported_by_location) can be used to reference host inventory values from one or several hosts in a trigger expression - [User macros](/manual/config/macros/user_macros) and user macro context is supported for the tag name/value. User macro context may include low-level discovery macros - Low-level discovery macros can be used for the tag name/value in trigger prototypes The following macros may be used in trigger-based notifications: - {EVENT.TAGS} and {EVENT.RECOVERY.TAGS} macros will resolve to a comma separated list of event tags or recovery event tags - {EVENT.TAGSJSON} and {EVENT.RECOVERY.TAGSJSON} macros will resolve to a JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag) or recovery event tag objects The following macros may be used in template, host, item and web scenario tags: - {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros - {INVENTORY.\*} [macros](/manual/appendix/macros/supported_by_location) - [User macros](/manual/config/macros/user_macros) - Low-level discovery macros can be used in item prototype tags The following macros may be used in host prototype tags: - {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros - {INVENTORY.\*} [macros](/manual/appendix/macros/supported_by_location) - [User macros](/manual/config/macros/user_macros) - [Low-level discovery macros](/manual/config/macros/lld_macros) will be resolved during discovery process and then added to the discovered host #### Prise en charge des macros Les macros suivantes peuvent être utilisées dans les tags de déclenchement : - Les macros {ITEM.VALUE}, {ITEM.LASTVALUE}, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} et {HOST.ID} peuvent être utilisées pour remplir le nom ou la valeur de la balise - Les [macros](/manual/appendix/macros/supported_by_location) {INVENTORY.\*} peuvent être utilisées pour référencer les valeurs d'inventaire d'un ou plusieurs hôtes dans une expression de déclencheur - Les [macros utilisateur](/manual/config/macros/user_macros) et le contexte de la macro utilisateur sont pris en charge pour le nom/la valeur du tag. Le contexte de la macro utilisateur peut inclure des macros de découverte de bas niveau - Des macros de découverte de bas niveau peuvent être utilisées pour le nom/la valeur du tag dans les prototypes de déclencheur Les macros suivantes peuvent être utilisées dans les notifications basées sur des déclencheurs : - Les macros {EVENT.TAGS} et {EVENT.RECOVERY.TAGS} seront résolu es en une liste de tags d'événement ou de tags d'événement de récupération séparées par des virgules - Les macros {EVENT.TAGSJSON} et {EVENT.RECOVERY.TAGSJSON} seront résolues en un tableau JSON contenant des [objects](/manual/api/reference/event/object#event_tag) tag d'événement ou des objets de tag d'événement de récupération Les macros suivantes peuvent être utilisées dans les tags de modèle, d'hôte, d'élément et de scénario Web : - Les macros {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} et {HOST.ID} - Les [macros](/manual/appendix/macros/supported_by_location) {INVENTORY.\*} - Les [Macros utilisateur](/manual/config/macros/user_macros) - Les macros de découverte de bas niveau peuvent être utilisées dans les tags de prototype d'élément Les macros suivantes peuvent être utilisées dans les tags de prototype d'hôte : - Les macros {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} et {HOST.ID} - Les [macros](/manual/appendix/macros/supported_by_location) {INVENTORY.\*} - Les [macros utilisateur](/manual/config/macros/user_macros) - Les [macros de découverte de bas niveau](/manual/config/macros/lld_macros) seront résolues pendant le processus de découverte, puis ajoutées à l'hôte découvert # maintenance.create # maintenance.create # maintenance.delete # maintenance.delete # maintenance.get # maintenance.get ### Maintenance The maintenance object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |maintenanceid|string|*(readonly)* ID of the maintenance.| |**name**<br>(required)|string|Name of the maintenance.| |**active\_since**<br>(required)|timestamp|Time when the maintenance becomes active.<br><br>The given value will be rounded down to minutes.| |**active\_till**<br>(required)|timestamp|Time when the maintenance stops being active.<br><br>The given value will be rounded down to minutes.| |description|string|Description of the maintenance.| |maintenance\_type|integer|Type of maintenance.<br><br>Possible values:<br>0 - *(default)* with data collection;<br>1 - without data collection.| |tags\_evaltype|integer|Problem tag evaluation method.<br><br>Possible values:<br>0 - *(default)* And/Or;<br>2 - Or.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Maintenance L'objet maintenance a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |maintenanceid|string|*(lecture seule)* ID de la maintenance.| |**name**<br>(obligatoire)|string|Nom de la maintenance.| |**active\_since**<br>(obligatoire)|timestamp|Heure à laquelle la maintenance devient active.<br><br>La valeur donnée sera arrondie aux minutes inférieures.| |**active\_till**<br>(obligatoire)|timestamp|Heure à laquelle la maintenance arrête d'être active.<br><br>La valeur donnée sera arrondie aux minutes inférieures.| |description|string|Description de la maintenance.| |maintenance\_type|integer|Type de la maintenance.<br><br>Valeurs possibles :<br>0 - *(par défaut)* avec collecte de données ;<br>1 - sans collecte de données.| |tags\_evaltype|integer|Méthode d'évaluation du tag de problème.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Et/Ou ;<br>2 - Ou.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # maintenance.update # maintenance.update ### Makefile targets Loadable plugins provided by Zabbix have simple makefiles with the following targets: |Target|Description| |--|--------| |make|Build plugin.| |make clean|Delete all files that are normally created by building the plugin.| |make check|Perform self-tests. A real PostgreSQL database is required.| |make style|Check Go code style with 'golangci-lint'.| |make format|Format Go code with 'go fmt'.| |make dist|Create an archive containing the plugin sources and sources of all packages needed to build the plugin and and its self-tests.| ### Cibles Makefile Les plugins chargeables fournis par Zabbix ont des makefiles simples avec les cibles suivantes : |Cible|Description| |--|--------| |make|Construire le plugin.| |make clean|Supprimer tous les fichiers qui sont normalement créés en construisant le plugin.| |make check|Effectuer des auto-tests. Une vraie base de données PostgreSQL est requise.| |make style|Vérifier le style de code Go avec 'golangci-lint'.| |make format|Formater le code Go avec 'go fmt'.| |make dist|Créer une archive contenant les sources du plug-in et les sources de tous les packages nécessaires pour créer le plug-in et ses auto-tests.| ##### Manifest preparation Each module is expected to have a manifest.json file with the following fields in JSON format: |Parameter|Required|Type|Default|Description| |---------|---|----|--|-------------------| |manifest\_version|Yes|Double|\-|Manifest version of the module. Currently supported version is **1**.| |id|Yes|String|\-|Module ID. Only one module with given ID can be enabled at the same time.| |name|Yes|String|\-|Module name as displayed in the Administration section.| |version|Yes|String|\-|Module version as displayed in the Administration section.| |namespace|Yes|String|\-|PHP namespace for Module.php and action classes.| |author|No|String|""|Module author as displayed in the Administration section.| |url|No|String|""|Module URL as displayed in the Administration section.| |description|No|String|""|Module description as displayed in the Administration section.| |actions|No|Object|{}|Actions to register with this module. See Actions.| |config|No|Object|{}|Module configuration.| For reference, please see an example of manifest.json in the [Reference](#reference) section. ##### Préparation du manifeste Chaque module doit avoir un fichier manifest.json avec les champs suivants au format JSON : |Paramètre|Requis|Type|Par défaut|Description| |---------|---|----|--|-------------------| |manifest\_version|Oui|Double|\-|Version manifeste du module. La version actuellement prise en charge est **1**.| |id|Oui|Chaîne|\-|ID du module. Un seul module avec un ID donné peut être activé en même temps.| |name|Yes|Chaîne|\-|Nom du module tel qu'affiché dans la section Administration.| |version|Oui|Chaîne|\-|Version du module telle qu'affichée dans la section Administration.| |namespace|Oui|Chaîne|\-|Espace de noms PHP pour Module.php et les classes d'action.| |author|No|Chaîne|""|Auteur du module tel qu'affiché dans la section Administration.| |url|No|Chaîne|""|URL du module tel qu'affiché dans la section Administration.| |description|No|Chaîne|""|Description du module telle qu'affichée dans la section Administration.| |actions|Non|Objet|{}|Actions à enregistrer avec ce module. Voir Actions.| |config|Non|Objet|{}|Configuration du module.| Pour référence, veuillez consulter un exemple de manifest.json dans la section [Réference](#reference). ##### Manual mode When [configuring a host](/manual/config/hosts/host), in the *Inventory* tab you can enter such details as the type of device, serial number, location, responsible person, etc., - the data that will populate inventory information. If a URL is included in the host inventory information and it starts with 'http' or 'https', it will result in a clickable link in the *Inventory* section. ##### Mode manuel Lors de la [configuration d'un hôte](/manual/config/hosts/host), dans l'onglet *Inventaire*, vous pouvez entrer des détails telles que le type du périphérique, le numéro de série, l'emplacement, la personne responsable, etc., - le donnée qui peuplera l'information d'inventaire. Si une URL est incluse dans les informations de l'inventaire de l'hôte et qu'elle commence par `http` ou `https`, un lien cliquable apparaît dans la section *Inventaire*. # map.create # map.create # map.delete # map.delete #### Map element Host group The map element Host group object defines one host group element. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groupid|string|Host group ID| #### Élément de carte Groupe d'hôtes L'objet élément de carte Groupe d'hôtes définit un élément groupe d'hôtes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groupid|string|ID du groupe d'hôtes.| #### Map element Host The map element Host object defines one host element. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostid|string|Host ID| #### Élément de carte Hôte L'objet élément de carte Hôte définit un élément hôte. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostid|string|ID de l'hôte.| #### Map element Map The map element Map object defines one map element. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapid|string|Map ID| #### Élément de carte Carte L'objet élément de carte Carte définit un élément de carte. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |-----------|----|-----------| |sysmapid|string|ID de la carte.| ### Map element The map element object defines an object displayed on a map. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |selementid|string|*(readonly)* ID of the map element.| |**elements**<br>(required)|array|Element data object. Required for host, host group, trigger and map type elements.| |**elementtype**<br>(required)|integer|Type of map element.<br><br>Possible values:<br>0 - host;<br>1 - map;<br>2 - trigger;<br>3 - host group;<br>4 - image.| |**iconid\_off**<br>(required)|string|ID of the image used to display the element in default state.| |areatype|integer|How separate host group hosts should be displayed.<br><br>Possible values:<br>0 - *(default)* the host group element will take up the whole map;<br>1 - the host group element will have a fixed size.| |elementsubtype|integer|How a host group element should be displayed on a map.<br><br>Possible values:<br>0 - *(default)* display the host group as a single element;<br>1 - display each host in the group separately.| |evaltype|integer|Map element tag filtering condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>2 - OR.| |height|integer|Height of the fixed size host group element in pixels.<br><br>Default: 200.| |iconid\_disabled|string|ID of the image used to display disabled map elements. Unused for image elements.| |iconid\_maintenance|string|ID of the image used to display map elements in maintenance. Unused for image elements.| |iconid\_on|string|ID of the image used to display map elements with problems. Unused for image elements.| |label|string|Label of the element.| |label\_location|integer|Location of the map element label.<br><br>Possible values:<br>-1 - *(default)* default location;<br>0 - bottom;<br>1 - left;<br>2 - right;<br>3 - top.| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|*(readonly)* ID of the map that the element belongs to.| |urls|array|Map element URLs.<br><br>The map element URL object is [described in detail below](object#map_element_url).| |use\_iconmap|integer|Whether icon mapping must be used for host elements.<br><br>Possible values:<br>0 - do not use icon mapping;<br>1 - *(default)* use icon mapping.| |viewtype|integer|Host group element placing algorithm.<br><br>Possible values:<br>0 - *(default)* grid.| |width|integer|Width of the fixed size host group element in pixels.<br><br>Default: 200.| |x|integer|X-coordinates of the element in pixels.<br><br>Default: 0.| |y|integer|Y-coordinates of the element in pixels.<br><br>Default: 0.| ### Elément de carte L'objet élément de carte définit un objet affiché sur une carte. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |selementid|string|*(lecture seule)* ID de l'élément de carte.| |**elements**<br>(obligatoire)|array|Objet de données d'élément. Requis pour les éléments de type hôte, groupe d'hôtes, déclencheur et carte.| |**elementtype**<br>(obligatoire)|integer|Type d'élément de carte.<br><br>Valeurs possibles :<br>0 - hôte ;<br>1 - carte ;<br>2 - déclencheur ;<br>3 - groupe d'hôtes ;<br>4 - image.| |**iconid\_off**<br>(obligatoire)|string|ID de l'image utilisée pour afficher l'élément à l'état par défaut.| |areatype|integer|Manière dont les différents hôtes du groupe d'hôtes doivent être affichés.<br><br>Valeurs possibles :<br>0 - *(par défaut)* l'élément du groupe d'hôtes occupera toute la carte ;<br>1 - l'élément du groupe d'hôtes aura une taille fixe.| |elementsubtype|integer|Manière dont un élément de groupe d'hôtes doit être affiché sur une carte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* afficher le groupe d'hôtes en tant qu'élément unique ;<br>1 - affiche chaque hôte du groupe séparément.| |evaltype|integer|Méthode d'évaluation des conditions de filtrage des balises d'élément cartographique.<br><br>Valeurs possibles :<br>0 - *(par défaut)* AND / OR;<br>2 - OR.| |height|integer|Hauteur de l'élément de groupe d'hôtes de taille fixe en pixels.<br><br>Par défaut : 200.| |iconid\_disabled|string|ID de l'icône utilisée pour afficher les éléments de carte désactivés. Non utilisé pour les éléments de type image.| |iconid\_maintenance|string|ID de l'icône utilisée pour afficher les éléments de la carte en maintenance. Non utilisé pour les éléments de type image.| |iconid\_on|string|ID de l'icône utilisée pour afficher les éléments de carte avec des problèmes. Non utilisé pour les éléments de type image.| |label|string|Etiquette de l'élément.| |label\_location|integer|Position de l'étiquette de l'élément de carte.<br><br>Valeurs possibles :<br>-1 - *(par défaut)* position par défaut ;<br>0 - bas ;<br>1 - gauche ;<br>2 - droite ;<br>3 - haut.| |permission|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>-1 - aucun ;<br>2 - lecture seule ;<br>3 - lecture-écriture.| |sysmapid|string|*(lecture seule)* ID de la carte à laquelle l'élément appartient.| |urls|array|Éléments de carte URL.<br><br>L'objet élément de carte URL est [décrit en détail ci-dessous](object#map_element_url).| |use\_iconmap|integer|Indique si la correspondance d'icône doit être utilisée pour les éléments hôtes.<br><br>Valeurs possibles :<br>0 - ne pas utiliser la correspondance d'icône ;<br>1 - *(par défaut)* utiliser la correspondance d'icône.| |viewtype|integer|Algorithme de placement d'élément groupe d'hôtes.<br><br>Valeurs possibles :<br>0 - *(par défaut)* grille.| |width|integer|Largeur de l'élément groupe d'hôtes de taille fixe en pixels.<br><br>Par défaut : 200.| |x|integer|Coordonnée X de l'élément en pixels.<br><br>Par défaut : 0.| |y|integer|Coordonnée Y de l'élément en pixels.<br><br>Par défaut : 0.| #### Map element Trigger The map element Trigger object defines one or more trigger elements. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |triggerid|string|Trigger ID| #### Élément de carte Déclencheur L'objet élément de carte Déclencheur définit un ou plusieurs éléments déclencheurs. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |triggerid|string|ID du déclencheur.| #### Map element URL The map element URL object defines a clickable link that will be available for a specific map element. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapelementurlid|string|*(readonly)* ID of the map element URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |selementid|string|ID of the map element that the URL belongs to.| #### Élément de carte URL L'objet élément de carte URL définit un lien cliquable qui sera disponible pour un élément de carte spécifique. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapelementurlid|string|*(lecture seule)* ID de l'élément de carte URL.| |**name**<br>(obligatoire)|string|Légende de lien.| |**url**<br>(obligatoire)|string|URL du lien.| |selementid|string|ID de l'élément de carte auquel l'URL appartient.| # map.get # map.get #### Map lines Create a map line. Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map API lines", "width": 500, "height": 500, "lines": [ { "x1": 30, "y1": 10, "x2": 100, "y2": 50, "line_type": 1, "line_width": 10, "line_color": "009900" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "11" ] }, "id": 1 } ``` #### Ligne de carte Créer une ligne de carte. Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map API lines", "width": 500, "height": 500, "lines": [ { "x1": 30, "y1": 10, "x2": 100, "y2": 50, "line_type": 1, "line_width": 10, "line_color": "009900" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "11" ] }, "id": 1 } ``` ### Map lines The map line object defines an line displayed on a map. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmap\_shapeid|string|*(readonly)* ID of the map shape element.| |x1|integer|X-coordinates of the line point 1 in pixels.<br><br>Default: 0.| |y1|integer|Y-coordinates of the line point 1 in pixels.<br><br>Default: 0.| |x2|integer|X-coordinates of the line point 2 in pixels.<br><br>Default: 200.| |y2|integer|Y-coordinates of the line point 2 in pixels.<br><br>Default: 200.| |line\_type|integer|Type of the lines.<br><br>Possible values:<br>0 - none;<br>1 - `—————`;<br>2 - `·····`;<br>3 - `- - -`.<br><br>Default: 0.| |line\_width|integer|Width of the lines in pixels.<br><br>Default: 0.| |line\_color|string|Line color.<br><br>Default: '000000'.| |zindex|integer|Value used to order all shapes and lines (z-index).<br><br>Default: 0.| ### Ligne de carte L'objet Ligne de carte définit une ligne affichée sur une carte. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmap\_shapeid|string|*(lecture seule)* ID de la forme de carte.| |x1|integer|Coordonnée X du point 1 de la ligne en pixels.<br><br>Par défaut : 0.| |y1|integer|Coordonnée Y du point 1 de la ligne en pixels.<br><br>Par défaut : 0.| |x2|integer|Coordonnée X du point 2 de la ligne en pixels.<br><br>Par défaut : 200.| |y2|integer|Coordonnée Y du point 2 de la ligne en pixels.<br><br>Par défaut : 200.| |line\_type|integer|Type de ligne.<br><br>Valeurs possibles :<br>0 - aucune ;<br>1 - `—————` ;<br>2 - `·····` ;<br>3 - `- - -`.<br><br>Par défaut : 0.| |line\_width|integer|Largeur de la ligne en pixels.<br><br>Par défaut : 0.| |line\_color|string|Couleur de la ligne.<br><br>Par défaut : '000000'.| |zindex|integer|Valeur utilisée pour ordonner toutes les formes et lignes (z-index).<br><br>Par défaut : 0.| ### Map link The map link object defines a link between two map elements. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |linkid|string|*(readonly)* ID of the map link.| |**selementid1**<br>(required)|string|ID of the first map element linked on one end.| |**selementid2**<br>(required)|string|ID of the first map element linked on the other end.| |color|string|Line color as a hexadecimal color code.<br><br>Default: `000000`.| |drawtype|integer|Link line draw style.<br><br>Possible values:<br>0 - *(default)* line;<br>2 - bold line;<br>3 - dotted line;<br>4 - dashed line.| |label|string|Link label.| |linktriggers|array|Map link triggers to use as link status indicators.<br><br>The map link trigger object is [described in detail below](object#map_link_trigger).| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|ID of the map the link belongs to.| ### Lien de carte L'objet lien de carte définit un lien entre deux éléments de carte. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |linkid|string|*(lecture seule)* ID du lien de carte.| |**selementid1**<br>(obligatoire)|string|ID du premier élément de carte lié à une extrémité.| |**selementid2**<br>(obligatoire)|string|ID du premier élément de carte lié à l'autre extrémité.| |color|string|Couleur de ligne sous forme de code couleur hexadécimal.<br><br>Par défaut : `000000`.| |drawtype|integer|Style de ligne de lien.<br><br>Valeurs possibles :<br>0 - *(par défaut)* ligne ;<br>2 - ligne en gras ;<br>3 - ligne pointillée ;<br>4 - ligne avec des tirets.| |label|string|Étiquette de lien.| |linktriggers|array|Les déclencheurs de lien de carte à utiliser comme indicateurs d'état de lien.<br><br>L'objet déclencheur de lien de carte est [décrit en détail ci-dessous](object#map_link_trigger).| |permission|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>-1 - aucun ;<br>2 - lecture seule ;<br>3 - lecture-écriture.| |sysmapid|string|ID de la carte à laquelle le lien appartient.| #### Map listing {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the map. Click on the name to [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) the map.| |*Width*|Map width is displayed.| |*Height*|Map height is displayed.| |*Actions*|Two actions are available:<br>**Properties** - edit general map [properties](/manual/config/visualization/maps/map#creating_a_map)<br>**Constructor** - access the grid for adding [map elements](/manual/config/visualization/maps/map#adding_elements)| To [configure](/manual/config/visualization/maps/map#creating_a_map) a new map, click on the *Create map* button in the top right-hand corner. To import a map from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner. The user who imports the map will be set as its owner. Two buttons below the list offer some mass-editing options: - *Export* - export the maps to a YAML, XML, or JSON file - *Delete* - delete the maps To use these options, mark the checkboxes before the respective maps, then click on the required button. #### Liste des cartes {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom de la carte. Cliquez sur le nom pour [afficher](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) la carte.| |*Largeur*|La largeur de la carte est affichée.| |*Hauteur*|La hauteur de la carte est affichée.| |*Actions*|Deux actions sont disponibles :<br>**Propriétés** - modifier [propriétés](/manual/config/visualization/maps/map#creating_a_map) générales de la carte<br>**Constructeur** - accéder à la grille pour ajouter des [éléments de carte](/manual/config/visualization/maps/map#adding_elements)| Pour [configurer](/manual/config/visualization/maps/map#creating_a_map) une nouvelle carte, cliquez sur le bouton *Créer une carte* dans le coin supérieur droit. Pour importer une carte à partir d'un fichier YAML, XML ou JSON, cliquez sur le bouton *Importer* dans le coin supérieur droit. L'utilisateur qui importe la carte sera défini comme son propriétaire. Deux boutons sous la liste offrent des options d'édition en masse : - *Exporter* - exporter les cartes vers un fichier YAML, XML ou JSON - *Supprimer* - supprimer les cartes Pour utiliser ces options, cochez les cases devant les cartes respectives, puis cliquez sur le bouton requis. ##### Mapping LLD macros Next you have to go to the LLD macros tab and make the following mappings: {#VOLUME}=$.labels['volume'] {#METRIC}=$['name'] {#HELP}=$['help'] ##### Correspondance des macros LLD Ensuite, vous devez vous rendre dans l'onglet Macros LLD et effectuer les correspondances suivantes : {#VOLUME}=$.labels['volume'] {#METRIC}=$['name'] {#HELP}=$['help'] #### Maps Configure maps to create detailed dynamic representations of your IT infrastructure. [Map API](/manual/api/reference/map) #### Cartes Configurez des cartes pour créer des représentations dynamiques de votre infrastructure informatique. [API Cartes](/manual/api/reference/map) #### Map shapes Create a map with map name title. Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Host map", "width": 600, "height": 600, "shapes": [ { "type": 0, "x": 0, "y": 0, "width": 600, "height": 11, "text": "{MAP.NAME}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "10" ] }, "id": 1 } ``` #### Formes de carte Créer une carte avec un titre. Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Host map", "width": 600, "height": 600, "shapes": [ { "type": 0, "x": 0, "y": 0, "width": 600, "height": 11, "text": "{MAP.NAME}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "10" ] }, "id": 1 } ``` #### Map sharing Create a map with two types of sharing (user and user group). Request: ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map sharing", "width": 600, "height": 600, "users": [ { "userid": "4", "permission": "3" } ], "userGroups": [ { "usrgrpid": "7", "permission": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 1 } ``` #### Partager une carte Créer une carte avec deux types de partage (utilisateur et groupe d'utilisateurs). Requête : ```json { "jsonrpc": "2.0", "method": "map.create", "params": { "name": "Map sharing", "width": 600, "height": 600, "users": [ { "userid": "4", "permission": "3" } ], "userGroups": [ { "usrgrpid": "7", "permission": "2" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "9" ] }, "id": 1 } ``` ### Map The map object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapid|string|*(readonly)* ID of the map.| |**height**<br>(required)|integer|Height of the map in pixels.| |**name**<br>(required)|string|Name of the map.| |**width**<br>(required)|integer|Width of the map in pixels.| |backgroundid|string|ID of the image used as the background for the map.| |expand\_macros|integer|Whether to expand macros in labels when configuring the map.<br><br>Possible values:<br>0 - *(default)* do not expand macros;<br>1 - expand macros.| |expandproblem|integer|Whether the problem trigger will be displayed for elements with a single problem.<br><br>Possible values:<br>0 - always display the number of problems;<br>1 - *(default)* display the problem trigger if there's only one problem.| |grid\_align|integer|Whether to enable grid aligning.<br><br>Possible values:<br>0 - disable grid aligning;<br>1 - *(default)* enable grid aligning.| |grid\_show|integer|Whether to show the grid on the map.<br><br>Possible values:<br>0 - do not show the grid;<br>1 - *(default)* show the grid.| |grid\_size|integer|Size of the map grid in pixels.<br><br>Supported values: 20, 40, 50, 75 and 100.<br><br>Default: 50.| |highlight|integer|Whether icon highlighting is enabled.<br><br>Possible values:<br>0 - highlighting disabled;<br>1 - *(default)* highlighting enabled.| |iconmapid|string|ID of the icon map used on the map.| |label\_format|integer|Whether to enable advanced labels.<br><br>Possible values:<br>0 - *(default)* disable advanced labels;<br>1 - enable advanced labels.| |label\_location|integer|Location of the map element label.<br><br>Possible values:<br>0 - *(default)* bottom;<br>1 - left;<br>2 - right;<br>3 - top.| |label\_string\_host|string|Custom label for host elements.<br><br>Required for maps with custom host label type.| |label\_string\_hostgroup|string|Custom label for host group elements.<br><br>Required for maps with custom host group label type.| |label\_string\_image|string|Custom label for image elements.<br><br>Required for maps with custom image label type.| |label\_string\_map|string|Custom label for map elements.<br><br>Required for maps with custom map label type.| |label\_string\_trigger|string|Custom label for trigger elements.<br><br>Required for maps with custom trigger label type.| |label\_type|integer|Map element label type.<br><br>Possible values:<br>0 - label;<br>1 - IP address;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing.| |label\_type\_host|integer|Label type for host elements.<br><br>Possible values:<br>0 - label;<br>1 - IP address;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_hostgroup|integer|Label type for host group elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_image|integer|Label type for host group elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>4 - nothing;<br>5 - custom.| |label\_type\_map|integer|Label type for map elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_trigger|integer|Label type for trigger elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |markelements|integer|Whether to highlight map elements that have recently changed their status.<br><br>Possible values:<br>0 - *(default)* do not highlight elements;<br>1 - highlight elements.| |severity\_min|integer|Minimum severity of the triggers that will be displayed on the map.<br><br>Refer to the [trigger "severity" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.| |show\_unack|integer|How problems should be displayed.<br><br>Possible values:<br>0 - *(default)* display the count of all problems;<br>1 - display only the count of unacknowledged problems;<br>2 - display the count of acknowledged and unacknowledged problems separately.| |userid|string|Map owner user ID.| |private|integer|Type of map sharing.<br><br>Possible values:<br>0 - public map;<br>1 - *(default)* private map.| |show\_suppressed|integer|Whether suppressed problems are shown.<br><br>Possible values:<br>0 - *(default)* hide suppressed problems;<br>1 - show suppressed problems.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Carte L'objet carte a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapid|string|*(lecture seule)* ID de la carte.| |**height**<br>(obligatoire)|integer|Hauteur de la carte en pixels.| |**name**<br>(obligatoire)|string|Nom de la carte.| |**width**<br>(obligatoire)|integer|Largeur de la carte en pixels.| |backgroundid|string|ID de l'image utilisée comme arrière-plan de la carte.| |expand\_macros|integer|Indique s'il faut développer les macros dans les étiquettes lors de la configuration de la carte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* ne pas développer ;<br>1 - développer.| |expandproblem|integer|Indique si le déclencheur du problème sera affiché pour les éléments avec un seul problème.<br><br>Valeurs possibles :<br>0 - affiche toujours le nombre de problèmes ;<br>1 - *(par défaut)* affiche le déclencheur du problème s'il n'y a qu'un seul problème.| |grid\_align|integer|Indique s'il faut activer l'alignement sur la grille.<br><br>Valeurs possibles :<br>0 - désactiver l'alignement sur la grille ;<br>1 - *(par défaut)* activer l'alignement sur la grille.| |grid\_show|integer|Indique s'il faut afficher la grille sur la carte.<br><br>Valeurs possibles :<br>0 - ne pas montrer la grille ;<br>1 - *(par défaut)* montrer la grille.| |grid\_size|integer|Taille de la grille de la carte en pixels.<br><br>Valeurs supportées : 20, 40, 50, 75 et 100.<br><br>Par défaut : 50.| |highlight|integer|Indique si la mise en surbrillance des icônes est activée.<br><br>Valeurs possibles :<br>0 - surbrillance désactivée ;<br>1 - *(par défaut)* surbrillance activée.| |iconmapid|string|ID de la correspondance d'icône utilisée sur la carte.| |label\_format|integer|Indique s'il faut activer les étiquettes avancées.<br><br>Valeurs possibles :<br>0 - *(par défaut)* désactiver les étiquettes avancées ;<br>1 - activer les étiquettes avancées.| |label\_location|integer|Emplacement de l'étiquette de l'élément de carte.<br><br>Valeurs possibles :<br>0 - *(par défaut)* bas ;<br>1 - gauche ;<br>2 - droite ;<br>3 - haut.| |label\_string\_host|string|Étiquette personnalisée pour les éléments hôtes.<br><br>Requis pour les cartes avec un type d'étiquette d'hôte personnalisé.| |label\_string\_hostgroup|string|Étiquette personnalisée pour les éléments groupe d'hôtes.<br><br>Requis pour les cartes avec un type d'étiquette groupe d'hôtes personnalisé.| |label\_string\_image|string|Étiquette personnalisée pour les éléments images.<br><br>Requis pour les cartes avec un type d'étiquette image personnalisé.| |label\_string\_map|string|Étiquette personnalisée pour les éléments cartes.<br><br>Requis pour les cartes avec un type d'étiquette carte personnalisé.| |label\_string\_trigger|string|Étiquette personnalisée pour les éléments déclencheurs.<br><br>Requis pour les cartes avec un type d'étiquette déclencheur personnalisé.| |label\_type|integer|Type d'étiquette d'élément de carte.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>1 - adresse IP ;<br>2 - *(par défaut)* nom de l'élément ;<br>3 - statut uniquement ;<br>4 - rien.| |label\_type\_host|integer|Type d'étiquette pour les éléments hôtes.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>1 - adresse IP ;<br>2 - *(par défaut)* nom de l'élément ;<br>3 - statut uniquement ;<br>4 - rien ;<br>5 - personnalisé.| |label\_type\_hostgroup|integer|Type d'étiquette pour les éléments groupes d'hôtes.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>2 - *(par défaut)* nom de l'élément ;<br>3 - statut uniquement ;<br>4 - rien ;<br>5 - personnalisé.| |label\_type\_image|integer|Type d'étiquette pour les éléments images.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>2 - *(par défaut)* nom de l'élément ;<br>4 - rien ;<br>5 - personnalisé.| |label\_type\_map|integer|Type d'étiquette pour les éléments cartes.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>2 - *(par défaut)* nom de l'élément ;<br>3 - statut uniquement ;<br>4 - rien ;<br>5 - personnalisé.| |label\_type\_trigger|integer|Type d'étiquette pour les éléments déclencheurs.<br><br>Valeurs possibles :<br>0 - étiquette ;<br>2 - *(par défaut)* nom de l'élément ;<br>3 - statut uniquement ;<br>4 - rien ;<br>5 - personnalisé.| |markelements|integer|Indique s'il faut mettre en évidence les éléments de la carte qui ont récemment changé de statut.<br><br>Valeurs possibles :<br>0 - *(par défaut)* ne pas surligner les éléments ;<br>1 - surligner les éléments.| |severity\_min|integer|Sévérité minimale des déclencheurs qui seront affichés sur la carte.<br><br>Se référer à la [propriété "sévérité" d'un déclencheur](/manual/api/reference/trigger/object#trigger) pour une liste de sévérités supportées.| |show\_unack|integer|Manière dont les problèmes doivent être affichés.<br><br>Valeurs possibles :<br>0 - *(par défaut)* afficher le nombre de tous les problèmes ;<br>1 - afficher uniquement le nombre de problèmes non acquittés ;<br>2 - afficher le nombre de problèmes acquittés et non acquittés séparément.| |userid|string|ID utilisateur du propriétaire de la carte.| |private|integer|Type de partage de carte.<br><br>Valeurs possibles :<br>0 - carte publique ;<br>1 - *(par défaut)* carte privée.| |show\_suppressed|integer|Indique si les problèmes supprimés sont affichés.<br><br>Valeurs possibles :<br>0 - *(par défaut)* masquer les problèmes supprimés ;<br>1 - afficher les problèmes supprimés.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # map.update # map.update ### Map URL The map URL object defines a clickable link that will be available for all elements of a specific type on the map. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapurlid|string|*(readonly)* ID of the map URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |elementtype|integer|Type of map element for which the URL will be available.<br><br>Refer to the [map element "type" property](object#map_element) for a list of supported types.<br><br>Default: 0.| |sysmapid|string|ID of the map that the URL belongs to.| ### URL de carte L'objet URL de carte définit un lien cliquable qui sera disponible pour tous les éléments d'un type spécifique sur la carte. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapurlid|string|*(lecture seule)* ID de l'URL de carte.| |**name**<br>(obligatoire)|string|Légende du lien.| |**url**<br>(obligatoire)|string|URL du lien.| |elementtype|integer|Type d'élément de carte pour lequel l'URL sera disponible.<br><br>Se référer à [la propriété "elementtype" de l'élément de carte(object#map_element) pour une liste de types supportés.<br><br>Par défaut : 0.| |sysmapid|string|ID de la carte à laquelle l'URL appartient.| ### Map user group List of map permissions based on user groups. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapusrgrpid|string|*(readonly)* ID of the map user group.| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;| ### Groupe d'utilisateurs de carte L'objet Groupe d'utilisateurs de carte liste des autorisations de carte basées sur les groupes d'utilisateurs. Il a les propriétés suivantes : |Propriété[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapusrgrpid|string|*(lecture seule)* ID du groupe d'utilisateurs de carte.| |**usrgrpid**<br>(obligatoire)|string|ID du groupe d'utilisateurs.| |**permission**<br>(obligatoire)|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>2 - lecture seule ;<br>3 - lecture-écriture ;| ### Map user List of map permissions based on users. It has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapuserid|string|*(readonly)* ID of the map user.| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;| ### Utilisateur de carte L'objet Utilisateur de carte liste des autorisations de carte basées sur les utilisateurs. Il a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapuserid|string|*(lecture seule)* ID de l'utilisateur de carte.| |**userid**<br>(obligatoire)|string|ID de l'utilisateur.| |**permission**<br>(obligatoire)|integer|Type de niveau d'autorisation.<br><br>Valeurs possibles :<br>2 - lecture seule ;<br>3 - lecture-écriture ;| ### MariaDB 10.10 support The maximum supported version for MariaDB is now 10.10.X. ### Prise en charge de MariaDB 10.10 La version maximale prise en charge pour MariaDB est désormais 10.10.X. ### MariaDB 10.11 support The maximum [supported version](/manual/installation/requirements#third-party-external-surrounding-software) for MariaDB is now 10.11.X. ### Prise en charge de MariaDB 10.11 La [version maximale prise en charge](/manual/installation/requirements#logiciel-denvironnement-externe-tiers) pour MariaDB est désormais 10.11.X. ### MariaDB 10.7 support The maximum supported version for MariaDB is now 10.7.X. ### Prise en charge de MariaDB 10.7 La version maximale prise en charge pour MariaDB est désormais 10.7.X. ### MariaDB 10.8 support The maximum supported version for MariaDB is now 10.8.X. ### Prise en charge de MariaDB 10.8 La version maximale prise en charge pour MariaDB est désormais 10.8.X. ##### Mass editing options A button below the list offers one mass-editing option: - *Delete* - delete the maintenance periods To use this option, mark the checkboxes before the respective maintenance periods and click on *Delete*. ##### Options d'édition en masse Un bouton sous la liste offre une option d'édition en masse : - *Supprimer* - supprimer les périodes de maintenance Pour utiliser cette option, cochez les cases devant les périodes de maintenance respectives et cliquez sur *Supprimer*. ##### Mass editing options A button below the list offers one mass-editing option: - *Delete* - delete the scripts To use this option, mark the checkboxes before the respective scripts and click on *Delete*. ##### Options d'édition en masse Un bouton sous la liste offre une option d'édition en masse : - *Supprimer* - supprimer les scripts Pour utiliser cette option, cochez les cases devant les scripts respectifs et cliquez sur *Supprimer*. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Copy* - copy the graphs to other hosts or templates - *Delete* - delete the graphs To use these options, mark the checkboxes before the respective graphs, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Copier* - copier les graphiques vers d'autres hôtes ou modèles - *Supprimer* - supprimer les graphiques Pour utiliser ces options, cochez les cases devant les graphiques respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Copy* - copy the graphs to other hosts or templates - *Delete* - delete the graphs To use these options, mark the checkboxes before the respective graphs, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Copier* - copier les graphiques vers d'autres hôtes ou modèles - *Supprimer* - supprimer les graphiques Pour utiliser ces options, cochez les cases devant les graphiques respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these hosts as *Enabled* - *Create disabled* - create these hosts as *Disabled* - *Delete* - delete these host prototypes To use these options, mark the checkboxes before the respective host prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créer ces hôtes comme *Activé* - *Créer désactivé* - créer ces hôtes comme *Désactivé* - *Supprimer* - supprimer ces prototypes d'hôtes Pour utiliser ces options, cochez les cases devant les prototypes hôtes respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these hosts as *Enabled* - *Create disabled* - create these hosts as *Disabled* - *Delete* - delete these host prototypes To use these options, mark the checkboxes before the respective host prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créer ces hôtes comme *Activé* - *Créer désactivé* - créer ces hôtes comme *Désactivé* - *Supprimer* - supprimer ces prototypes d'hôtes Pour utiliser ces options, cochez les cases devant les prototypes hôtes respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these items as *Enabled* - *Create disabled* - create these items as *Disabled* - *Mass update* - mass update these item prototypes - *Delete* - delete these item prototypes To use these options, mark the checkboxes before the respective item prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créer ces éléments comme *Activé* - *Créer désactivé* - créer ces éléments comme *Désactivé* - *Mise à jour en masse* - mise à jour en masse de ces prototypes d'élément - *Supprimer* - supprimer ces prototypes d'élément Pour utiliser ces options, cochez les cases devant les prototypes d'éléments respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these items as *Enabled* - *Create disabled* - create these items as *Disabled* - *Mass update* - mass update these item prototypes - *Delete* - delete these item prototypes To use these options, mark the checkboxes before the respective item prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créez ces éléments comme *Activé* - *Créer désactivé* - créez ces éléments comme *Désactivé* - *Mise à jour en masse* - mise à jour en masse de ces prototypes d'élément - *Supprimer* - supprimer ces prototypes d'élément Pour utiliser ces options, cochez les cases devant les prototypes d'élément respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these triggers as *Enabled* - *Create disabled* - create these triggers as *Disabled* - *Mass update* - mass update these trigger prototypes - *Delete* - delete these trigger prototypes To use these options, mark the checkboxes before the respective trigger prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créer ces déclencheurs comme *Activé* - *Créer désactivé* - créer ces déclencheurs comme *Désactivé* - *Mise à jour en masse* - mise à jour en masse de ces prototypes de déclencheurs - *Supprimer* - supprimer ces prototypes de déclencheur Pour utiliser ces options, cochez les cases devant les prototypes de déclencheur respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Create enabled* - create these triggers as *Enabled* - *Create disabled* - create these triggers as *Disabled* - *Mass update* - mass update these trigger prototypes - *Delete* - delete these trigger prototypes To use these options, mark the checkboxes before the respective trigger prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Créer activé* - créer ces déclencheurs comme *Activé* - *Créer désactivé* - créer ces déclencheurs comme *Désactivé* - *Mise à jour en masse* - mise à jour en masse de ces prototypes de déclencheurs - *Supprimer* - supprimer ces prototypes de déclencheur Pour utiliser ces options, cochez les cases devant les prototypes de déclencheur respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Delete* - delete these graph prototypes To use these options, mark the checkboxes before the respective graph prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Supprimer* - supprimer ces prototypes de graphique Pour utiliser ces options, cochez les cases devant les prototypes de graphique respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Delete* - delete these graph prototypes To use these options, mark the checkboxes before the respective graph prototypes, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Supprimer* - supprimer ces prototypes de graphique Pour utiliser ces options, cochez les cases devant les prototypes de graphique respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change host status to *Monitored* - *Disable* - change host status to *Not monitored* - *Export* - export the hosts to a YAML, XML or JSON file - *Mass update* - [update several properties](/manual/config/hosts/hostupdate) for a number of hosts at once - *Delete* - delete the hosts To use these options, mark the checkboxes before the respective hosts, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut de l'hôte en *Surveillé* - *Désactiver* - changer le statut de l'hôte en *Non surveillé* - *Exporter* - exporter les hôtes vers un fichier YAML, XML ou JSON - *Mise à jour de masse* - [mettre à jour plusieurs propriétés](/manual/config/hosts/hostupdate) pour plusieurs hôtes à la fois - *Supprimer* - supprimer les hôtes Pour utiliser ces options, cochez les cases devant les hôtes respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change item status to *Enabled*. - *Disable* - change item status to *Disabled*. - *Copy* - copy the items to other hosts or templates. - *Mass update* - [update several properties](/manual/config/items/itemupdate) for a number of items at once. - *Delete* - delete the items. To use these options, mark the checkboxes before the respective items, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut de l'élément en *Activé*. - *Désactiver* - changer le statut de l'élément en *Désactivé*. - *Copier* - copier les éléments vers d'autres hôtes ou modèles. - *Mise à jour en masse* - [mettre à jour plusieurs propriétés](/manual/config/items/itemupdate) pour un certain nombre d'éléments à la fois. - *Supprimer* - supprimer les éléments. Pour utiliser ces options, cochez les cases devant les éléments respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the action status to *Enabled* - *Disable* - change the action status to *Disabled* - *Delete* - delete the actions To use these options, mark the checkboxes before the respective actions, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut de l'action en *Activé* - *Désactiver* - changer le statut de l'action en *Désactivé* - *Supprimer* - supprimer les actions Pour utiliser ces options, cochez les cases devant les actions respectives, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the correlation rule status to *Enabled* - *Disable* - change the correlation rule status to *Disabled* - *Delete* - delete the correlation rules To use these options, mark the checkboxes before the respective correlation rules, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut de la règle de corrélation en *Activé* - *Désactiver* - changer le statut de la règle de corrélation en *Désactivé* - *Supprimer* - supprimer les règles de corrélation Pour utiliser ces options, cochez les cases devant les règles de corrélation respectives, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the discovery rule status to *Enabled* - *Disable* - change the discovery rule status to *Disabled* - *Delete* - delete the discovery rules To use these options, mark the checkboxes before the respective discovery rules, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut de la règle de découverte en *Activé* - *Désactiver* - changer l'état de la règle de découverte en *Désactivé* - *Supprimer* - supprimer les règles de découverte Pour utiliser ces options, cochez les cases devant les règles de découverte respectives, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the low-level discovery rule status to *Enabled* - *Disable* - change the low-level discovery rule status to *Disabled* - *Delete* - delete the low-level discovery rules To use these options, mark the checkboxes before the respective discovery rules, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer l'état de la règle de découverte de bas niveau en *Activé* - *Désactiver* - changer l'état de la règle de découverte de bas niveau en *Désactivé* - *Supprimer* - supprimer les règles de découverte de bas niveau Pour utiliser ces options, cochez les cases devant les règles de découverte respectives, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the media type status to *Enabled* - *Disable* - change the media type status to *Disabled* - *Export* - export the media types to a YAML, XML or JSON file - *Delete* - delete the media types To use these options, mark the checkboxes before the respective media types, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer l'état du type de média en *Activé* - *Désactiver* - changer l'état du type de média en *Désactivé* - *Exporter* - exporter les types de médias vers un fichier YAML, XML ou JSON - *Supprimer* - supprimer les types de médias Pour utiliser ces options, cochez les cases devant les types de média respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the scenario status to *Enabled* - *Disable* - change the scenario status to *Disabled* - *Delete* - delete the web scenarios To use these options, mark the checkboxes before the respective web scenarios, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut du scénario en *Activé* - *Désactiver* - changer le statut du scénario en *Désactivé* - *Supprimer* - supprimer les scénarios Web Pour utiliser ces options, cochez les cases devant les scénarios Web respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change the user group status to *Enabled* - *Disable* - change the user group status to *Disabled* - *Enable debug mode* - enable debug mode for the user groups - *Disable debug mode* - disable debug mode for the user groups - *Delete* - delete the user groups To use these options, mark the checkboxes before the respective user groups, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer le statut du groupe d'utilisateurs en *Activé* - *Désactiver* - changer le statut du groupe d'utilisateurs en *Désactivé* - *Activer le mode débogage* - activer le mode débogage pour les groupes d'utilisateurs - *Désactiver le mode débogage* - désactiver le mode débogage pour les groupes d'utilisateurs - *Supprimer* - supprimer les groupes d'utilisateurs Pour utiliser ces options, cochez les cases devant les groupes utilisateur respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change trigger status to *Enabled* - *Disable* - change trigger status to *Disabled* - *Copy* - copy the triggers to other hosts or templates - *Mass update* - update several properties for a number of triggers at once - *Delete* - delete the triggers To use these options, mark the checkboxes before the respective triggers, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer l'état du déclencheur en *Activé* - *Désactiver* - changer l'état du déclencheur en *Désactivé* - *Copier* - copier les déclencheurs vers d'autres hôtes ou modèles - *Mise à jour de masse* - mettre à jour plusieurs propriétés pour un certain nombre de déclencheurs à la fois - *Supprimer* - supprimer les déclencheurs Pour utiliser ces options, cochez les cases devant les déclencheurs respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable* - change trigger status to *Enabled*. - *Disable* - change trigger status to *Disabled*. - *Copy* - copy the triggers to other hosts or templates. - *Mass update* - update several properties for a number of triggers at once. - *Delete* - delete the triggers. To use these options, mark the checkboxes before the respective triggers, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer* - changer l'état du déclencheur en *Activé*. - *Désactiver* - changer l'état du déclencheur en *Désactivé*. - *Copier* - copier les déclencheurs vers d'autres hôtes ou modèles. - *Mise à jour de masse* - mettre à jour plusieurs propriétés pour un certain nombre de déclencheurs à la fois. - *Supprimer* - supprimer les déclencheurs. Pour utiliser ces options, cochez les cases devant les déclencheurs respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable hosts* - change the status of all hosts in the group to "Monitored" - *Disable hosts* - change the status of all hosts in the group to "Not monitored" - *Delete* - delete the host groups To use these options, mark the checkboxes before the respective host groups, then click on the required button. ##### Options d'édition de masse Les boutons situés sous la liste offrent des options d’édition collective : - *Activer les hôtes* - change le statut de tous les hôtes du groupe en "Supervisé" - *Désactiver les hôtes* - modifie le statut de tous les hôtes du groupe en "Non supervisé". - *Supprimer* - supprime les groupes d'hôtes Pour utiliser ces options, cochez les cases devant les groupes d'hôtes respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Enable hosts* - change the status of hosts monitored by the proxy to *Monitored* - *Disable hosts* - change the status of hosts monitored by the proxy to *Not monitored* - *Delete* - delete the proxies To use these options, mark the checkboxes before the respective proxies, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Activer les hôtes* - changer le statut des hôtes surveillés par le proxy en *Surveillé* - *Désactiver les hôtes* - changer le statut des hôtes surveillés par le proxy en *Non surveillé* - *Supprimer* - supprimer les proxys Pour utiliser ces options, cochez les cases devant les proxys respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Export* - export the template to a YAML, XML or JSON file - *Mass update* - [update several properties](/manual/config/templates/mass) for a number of templates at once - *Delete* - delete the template while leaving its linked entities (items, triggers etc.) with the hosts - *Delete and clear* - delete the template and its linked entities from the hosts To use these options, mark the checkboxes before the respective templates, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Exporter* - exporter le modèle vers un fichier YAML, XML ou JSON - *Mise à jour en masse* - [mettre à jour plusieurs propriétés](/manual/config/templates/mass) pour plusieurs modèles à la fois - *Supprimer* - supprimer le modèle tout en laissant ses entités liées (éléments, déclencheurs, etc.) aux hôtes - *Supprimer et effacer* - supprimer le modèle et ses entités liées des hôtes Pour utiliser ces options, cochez les cases devant les modèles respectifs, puis cliquez sur le bouton requis. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Mass update* - update the selected problems by navigating to the [problem update](/manual/acknowledges#updating_problems) screen To use this option, mark the checkboxes before the respective problems, then click on the *Mass update* button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Mise à jour en masse* - mettez à jour les problèmes sélectionnés en accédant à l'écran [mise à jour des problèmes](/manual/acknowledges#updating_problems) Pour utiliser cette option, cochez les cases devant les problèmes respectifs, puis cliquez sur le bouton *Mise à jour en masse*. ##### Mass editing options Buttons below the list offer some mass-editing options: - *Unblock* - re-enable system access to blocked users - *Delete* - delete the users To use these options, mark the check-boxes before the respective users, then click on the required button. ##### Options d'édition en masse Les boutons situés sous la liste offrent des options d'édition en masse : - *Débloquer* - réactiver l'accès au système pour les utilisateurs bloqués - *Supprimer* - supprimer les utilisateurs Pour utiliser ces options, cochez les cases devant les utilisateurs respectifs, puis cliquez sur le bouton requis. ##### Master item Create an IPMI item using the following key: ipmi.get  Set the type of information to "Text" for possibly big JSON data. ##### Élément principal Créez un élément IPMI à l'aide de la clé suivante : ipmi.get  Définissez le type d'informations sur "Texte" pour les données JSON éventuellement volumineuses. ##### Master item Create a Zabbix agent item using the following key: vfs.fs.get  Set the type of information to "Text" for possibly big JSON data. The data returned by this item will contain something like the following for a mounted filesystem: ``` {.java} { "fsname": "/", "fstype": "rootfs", "bytes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 }, "inodes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 } } ``` ##### Elément maître Créez un élément d'agent Zabbix à l'aide de la clé suivante : vfs.fs.get  Définissez le type d'informations sur "Texte" pour les données JSON éventuellement volumineuses. Les données renvoyées par cet élément contiendront quelque chose comme ce qui suit pour un système de fichiers monté : ``` {.java} { "fsname": "/", "fstype": "rootfs", "bytes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 }, "inodes": { "total": 1000, "free": 500, "used": 500, "pfree": 50.00, "pused": 50.00 } } ``` # mediatype.create # mediatype.create # mediatype.delete # mediatype.delete # mediatype.get # mediatype.get # mediatype.update # mediatype.update #### Memory suffixes Memory size suffixes are supported in: - trigger [expression](/manual/config/triggers/expression) constants and function parameters - constants of [calculated item](/manual/config/items/itemtypes/calculated) formulas For memory size you can use: - **K** - kilobyte - **M** - megabyte - **G** - gigabyte - **T** - terabyte #### Suffixes Memoires Les suffixes de taille mémoire sont pris en charge dans : - les [expressions](/manual/config/triggers/expression) des constantes et les paramètres de fonction du déclencheur. - les formules des constantes des [éléments calculés](/manual/config/items/itemtypes/calculated) Pour la taille de la mémoire, vous pouvez utiliser : - **K** - kilooctet - **M** - megaoctet - **G** - gigaoctet - **T** - teraoctet **Memory** Zabbix requires both physical and disk memory. The amount of required disk memory obviously depends on the number of hosts and parameters that are being monitored. If you're planning to keep a long history of monitored parameters, you should be thinking of at least a couple of gigabytes to have enough space to store the history in the database. Each Zabbix daemon process requires several connections to a database server. The amount of memory allocated for the connection depends on the configuration of the database engine. ::: noteclassic The more physical memory you have, the faster the database (and therefore Zabbix) works. ::: **Mémoire** Zabbix nécessite à la fois de la mémoire physique et de la mémoire disque. 128 Mo de mémoire physique et 256 Mo d'espace disque libre pourraient être un bon point de départ. Cependant, la quantité de mémoire disque requise dépend évidemment du nombre d'hôtes et de paramètres surveillés. Si vous prévoyez de conserver un historique conséquent des paramètres surveillés, vous devriez penser à au moins quelques gigaoctets pour avoir assez d'espace pour stocker l'historique dans la base de données. Chaque processus démon Zabbix nécessite plusieurs connexions à un serveur de base de données. La quantité de mémoire allouée à la connexion dépend de la configuration du moteur de base de données. ::: noteclassic Plus vous aurez de mémoire physique, plus la base de données (et donc Zabbix) fonctionnera rapidement. ::: ### Message template The message template object defines a template that will be used as a default message for action operations to send a notification. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**eventsource**<br>(required)|integer|Event source.<br><br>Possible values:<br>0 - triggers;<br>1 - discovery;<br>2 - autoregistration;<br>3 - internal;<br>4 - services.| |**recovery**<br>(required)|integer|Operation mode.<br><br>Possible values:<br>0 - operations;<br>1 - recovery operations;<br>2 - update operations.| |subject|string|Message subject.| |message|string|Message text.| ### Modèle de message L'objet modèle de message définit un modèle qui sera utilisé comme message par défaut pour les opérations d'action afin d'envoyer une notification. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**eventsource**<br>(obligatoire)|integer|Source de l'évènement.<br><br>Valeurs possibles :<br>0 - déclencheurs ;<br>1 - découverte ;<br>2 - enregistrement automatique ;<br>3 - interne ;<br>4 - services.| |**recovery**<br>(obligatoire)|integer|Mode d'opération.<br><br>Valeurs possibles :<br>0 - opérations;<br>1 - opérations de récupération ;<br>2 - opérations de mise à jour.| |subject|string|Sujet du message.| |message|string|Texte du message.| # Method reference This section provides an overview of the functions provided by the Zabbix API and will help you find your way around the available classes and methods. # Référentiel des méthodes Cette section fournit une vue d'ensemble des fonctions fournies par l'API Zabbix et vous aidera à vous repérer dans les classes et méthodes disponibles. #### Migration with running server * Export current history, import it to the temp table, then insert the data into new tables while ignoring duplicates: ``` {.sql} \copy history_old TO '/tmp/history.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value DOUBLE PRECISION DEFAULT '0.0000' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history FROM '/tmp/history.csv' DELIMITER ',' CSV INSERT INTO history SELECT * FROM temp_history ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_uint_old TO '/tmp/history_uint.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_uint ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value numeric(20) DEFAULT '0' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_str_old TO '/tmp/history_str.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_str ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value varchar(255) DEFAULT '' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_str FROM '/tmp/history_str.csv' DELIMITER ',' CSV INSERT INTO history_str (itemid,clock,value,ns) SELECT * FROM temp_history_str ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_log_old TO '/tmp/history_log.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_log ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, timestamp integer DEFAULT '0' NOT NULL, source varchar(64) DEFAULT '' NOT NULL, severity integer DEFAULT '0' NOT NULL, value text DEFAULT '' NOT NULL, logeventid integer DEFAULT '0' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_log FROM '/tmp/history_log.csv' DELIMITER ',' CSV INSERT INTO history_log SELECT * FROM temp_history_log ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_text_old TO '/tmp/history_text.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_text ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value text DEFAULT '' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_text FROM '/tmp/history_text.csv' DELIMITER ',' CSV INSERT INTO history_text SELECT * FROM temp_history_text ON CONFLICT (itemid,clock,ns) DO NOTHING; ``` * Follow [post-migration instructions](#post-migration) to drop the old tables. #### Migration avec serveur en cours d'exécution * Exporter l'historique actuel, importez le dans la table temporaire, puis insérez les données dans de nouvelles tables en ignorant les doublons : ``` {.sql} \copy history_old TO '/tmp/history.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value DOUBLE PRECISION DEFAULT '0.0000' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history FROM '/tmp/history.csv' DELIMITER ',' CSV INSERT INTO history SELECT * FROM temp_history ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_uint_old TO '/tmp/history_uint.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_uint ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value numeric(20) DEFAULT '0' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_str_old TO '/tmp/history_str.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_str ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value varchar(255) DEFAULT '' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_str FROM '/tmp/history_str.csv' DELIMITER ',' CSV INSERT INTO history_str (itemid,clock,value,ns) SELECT * FROM temp_history_str ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_log_old TO '/tmp/history_log.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_log ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, timestamp integer DEFAULT '0' NOT NULL, source varchar(64) DEFAULT '' NOT NULL, severity integer DEFAULT '0' NOT NULL, value text DEFAULT '' NOT NULL, logeventid integer DEFAULT '0' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_log FROM '/tmp/history_log.csv' DELIMITER ',' CSV INSERT INTO history_log SELECT * FROM temp_history_log ON CONFLICT (itemid,clock,ns) DO NOTHING; \copy history_text_old TO '/tmp/history_text.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_text ( itemid bigint NOT NULL, clock integer DEFAULT '0' NOT NULL, value text DEFAULT '' NOT NULL, ns integer DEFAULT '0' NOT NULL ); \copy temp_history_text FROM '/tmp/history_text.csv' DELIMITER ',' CSV INSERT INTO history_text SELECT * FROM temp_history_text ON CONFLICT (itemid,clock,ns) DO NOTHING; ``` * Suivez les [instructions post-migration](#post-migration) pour supprimer les anciennes tables. ##### Mikrotik routers Use SNMP agent provided by Mikrotik. See <http://www.mikrotik.com> for more information. ##### Routeurs Mikrotik Utilisez un agent SNMP fourni par Mikrotik. Voir <http://www.mikrotik.com> pour plus d'informations. ##### Minimum weekly disk space among clusters View the lowest disk space among clusters over a week. - add to the data set: hosts `cluster*`, key "Free disk space on /data" - select the aggregate function `min` and specify interval `1w` - a bar graph is displayed, where each bar represents the minimum disk space per week for each /data volume of the cluster ##### Espace disque hebdomadaire minimal entre les clusters Affichez l'espace disque le plus faible parmi les clusters sur une semaine. - ajoutez à l'ensemble de données : hôtes `cluster*`, clé "Espace disque libre sur /data" - sélectionnez la fonction d'agrégation `min` et spécifiez l'intervalle `1w` - un graphique à barres s'affiche, où chaque barre représente l'espace disque minimum par semaine pour chaque volume /data du cluster ##### Miscellaneous aspects of escalation behavior Let's consider what happens in different circumstances if an action contains several escalation steps. |Situation|Behavior| |---------|--------| |*The host in question goes into maintenance after the initial problem notification is sent*|Depending on the *Pause operations for suppressed problems* setting in action [configuration](/manual/config/notifications/action/operation#configuring_an_operation), all remaining escalation steps are executed either with a delay caused by the maintenance period or without delay. A maintenance period does not cancel operations.| |*The time period defined in the **Time period** action condition ends after the initial notification is sent*|All remaining escalation steps are executed. The *Time period* condition cannot stop operations; it has effect with regard to when actions are started/not started, not operations.| |*A problem starts during maintenance and continues (is not resolved) after maintenance ends*|Depending on the *Pause operations for suppressed problems* setting in action [configuration](/manual/config/notifications/action/operation#configuring_an_operation), all escalation steps are executed either from the moment maintenance ends or immediately.| |*A problem starts during a no-data maintenance and continues (is not resolved) after maintenance ends*|It must wait for the trigger to fire, before all escalation steps are executed.| |*Different escalations follow in close succession and overlap*|The execution of each new escalation supersedes the previous escalation, but for at least one escalation step that is always executed on the previous escalation. This behavior is relevant in actions upon events that are created with EVERY problem evaluation of the trigger.| |*During an escalation in progress (like a message being sent), based on any type of event:<br>- the action is disabled<br>Based on trigger event:<br>- the trigger is disabled<br>- the host or item is disabled<br>Based on internal event about triggers:<br>- the trigger is disabled<br>Based on internal event about items/low-level discovery rules:<br>- the item is disabled<br>- the host is disabled*|The message in progress is sent and then one more message on the escalation is sent. The follow-up message will have the cancellation text at the beginning of the message body (*NOTE: Escalation canceled*) naming the reason (for example, *NOTE: Escalation canceled: action '<Action name>' disabled*). This way the recipient is informed that the escalation is canceled and no more steps will be executed. This message is sent to all who received the notifications before. The reason of cancellation is also logged to the server log file (starting from [Debug Level](/manual/appendix/config/zabbix_server) 3=Warning).<br><br>Note that the *Escalation canceled* message is also sent if operations are finished, but recovery operations are configured and are not executed yet.| |*During an escalation in progress (like a message being sent) the action is deleted*|No more messages are sent. The information is logged to the server log file (starting from [Debug Level](/manual/appendix/config/zabbix_server) 3=Warning), for example: `escalation canceled: action id:334 deleted`| ##### Aspects divers du comportement d'escalade Considérons ce qui se passe dans différentes circonstances si une action contient plusieurs étapes d'escalade. |Situation|Comportement| |---------|--------| |*L'hôte en question passe en maintenance après l'envoi de la notification de problème initiale*|Selon le paramètre *Suspendre les opérations pour les problèmes supprimés* dans la [configuration](/manual/config/notifications/action/operation#configuring_an_operation) de l'action, tout les étapes d'escalade restantes sont exécutées soit avec un retard causé par la période de maintenance, soit sans retard. Une période de maintenance n'annule pas les opérations.| |*La période de temps définie dans la condition d'action **Période de temps** se termine après l'envoi de la notification initiale*|Toutes les étapes d'escalade restantes sont exécutées. La condition *Période* ne peut pas arrêter les opérations ; il a un effet sur le moment où les actions sont démarrées/non démarrées, pas sur les opérations.| |*Un problème commence pendant la maintenance et continue (n'est pas résolu) après la fin de la maintenance*|Selon le paramètre *Suspendre les opérations pour les problèmes supprimés* dans la [configuration](/manual/config/notifications/action/operation#configuring_an_operation) de l'action, toutes les étapes d'escalade sont exécutées dès la fin de la maintenance ou immédiatement.| |*Un problème commence pendant une maintenance sans donnée et continue (n'est pas résolu) après la fin de la maintenance*|Il doit attendre que le déclencheur se déclenche, avant que toutes les étapes d'escalade ne soient exécutées.| |*Différentes escalades se succèdent et se chevauchent*|L'exécution de chaque nouvelle escalade remplace l'escalade précédente, mais pour au moins une étape d'escalade qui est toujours exécutée sur l'escalade précédente. Ce comportement est pertinent dans les actions sur les événements qui sont créés avec CHAQUE évaluation de problème du déclencheur.| |*Lors d'une escalade en cours (comme l'envoi d'un message), en fonction de tout type d'événement :<br>- l'action est désactivée<br>En fonction de l'événement déclencheur :<br>- le déclencheur est désactivé<br>- l'hôte ou l'élément est désactivé<br>Selon un événement interne concernant les déclencheurs :<br>- le déclencheur est désactivé<br>Selon un événement interne concernant les éléments/règles de découverte de bas niveau :<br>- l'élément est désactivé<br >- l'hébergeur est désactivé*|Le message en cours est envoyé puis un autre message sur l'escalade est envoyé. Le message de suivi contiendra le texte d'annulation au début du corps du message (*NOTE: Escalation canceled*) indiquant la raison (par exemple, **NOTE: Escalation canceled: action '\<Action name\>' disabled*). De cette façon, le destinataire est informé que l'escalade est annulée et qu'aucune autre étape ne sera exécutée. Ce message est envoyé à tous ceux qui ont reçu les notifications auparavant. La raison de l'annulation est également consignée dans le fichier journal du serveur (à partir du [Niveau de débogage](/manual/appendix/config/zabbix_server) 3=Avertissement).<br><br>Notez que le message *Escalation canceled* est également envoyé si les opérations sont terminées, mais les opérations de récupération sont configurées et ne sont pas encore exécutées.| |*Lors d'une escalade en cours (comme l'envoi d'un message) l'action est supprimée*|Plus aucun message n'est envoyé. Les informations sont consignées dans le fichier journal du serveur (à partir du [Niveau de débogage](/manual/appendix/config/zabbix_server) 3=Avertissement), par exemple : `escalation canceled: action id:334 deleted`| ### Modifying existing services :::noteclassic The buttons described below are visible only when *Services* section is in the Edit mode. ::: To edit an existing service, press the pencil icon next to the service. To clone an existing service, press the pencil icon to open its configuration and then press Clone button. When a service is cloned, its parent links are preserved, while the child links are not. To delete a service, press on the `x` icon next to it. When you delete a parent service, its child services will not be deleted and will move one level higher in the service tree (1st level children will get the same level as the deleted parent service). Two buttons below the list of services offer some mass-editing options: - *Mass update* - mass update service properties - *Delete* - delete the services To use these options, mark the checkboxes before the respective services, then click on the required button. ### Modification des services existants :::noteclassique Les boutons décrits ci-dessous ne sont visibles que lorsque la section *Services* est en mode Édition. ::: Pour modifier un service existant, appuyez sur l'icône en forme de crayon à côté du service. Pour cloner un service existant, appuyez sur l'icône en forme de crayon pour ouvrir sa configuration, puis appuyez sur le bouton Cloner. Lorsqu'un service est cloné, ses liens parents sont conservés, tandis que les liens enfants ne le sont pas. Pour supprimer un service, appuyez sur l'icône `x` à côté de celui-ci. Lorsque vous supprimez un service parent, ses services enfants ne seront pas supprimés et passeront d'un niveau supérieur dans l'arborescence des services (les enfants de 1er niveau obtiendront le même niveau que le service parent supprimé). Deux boutons sous la liste des services offrent des options d'édition en masse : - *Mise à jour en masse* - mise à jour en masse des propriétés du service - *Supprimer* - supprimer les services Pour utiliser ces options, cochez les cases devant les services, puis cliquez sur le bouton requis. ##### Module structure Each module is a directory (placed within the `modules` directory) with sub-directories containing controllers, views and any other code: example_module_directory/ (required) manifest.json (required) Metadata and action definition. Module.php Module initialization and event handling. actions/ Action controller files. SomethingView.php SomethingCreate.php SomethingDelete.php data_export/ ExportAsXml.php ExportAsExcel.php views/ View files. example.something.view.php example.something.delete.php js/ JavaScript files used in views. example.something.view.js.php partials/ View partial files. example.something.reusable.php js/ JavaScript files used in partials. example.something.reusable.js.php As you can see, the only mandatory file within the custom module directory is `manifest.json`. The module will not register without this file. `Module.php` is responsible for registering menu items and processing events such as 'onBeforeAction' and 'onTerminate'. The *actions*, *views* and *partials* directories contain PHP and JavaScript code needed for module actions. ##### Structure des modules Chaque module est un répertoire (placé dans le répertoire `modules`) avec des sous-répertoires contenant des contrôleurs, des vues et tout autre code : exemple_repertoire_module/ (obligatoire) manifest.json (obligatoire) Définition des métadonnées et des actions. Module.php Initialisation du module et gestion des événements. actions/ Fichiers de contrôleur d'action. SomethingView.php SomethingCreate.php SomethingDelete.php data_export/ ExportAsXml.php ExportAsExcel.php views/ Fichiers des vues. example.something.view.php example.something.delete.php js/ Fichiers JavaScript utilisés dans views.example.something.view.js.php partials/ Fichiers partiels des vues. example.something.reusable.php js/ Fichiers JavaScript utilisés dans les partiels. example.something.reusable.js.php Comme vous pouvez le voir, le seul fichier obligatoire dans le répertoire du module personnalisé est `manifest.json`. Le module ne s'enregistrera pas sans ce fichier. `Module.php` est responsable de l'enregistrement des éléments de menu et du traitement des événements tels que 'onBeforeAction' et 'onTerminate'. Les répertoires *actions*, *views* et *partials* contiennent le code PHP et JavaScript nécessaire aux actions du module. ### Module The module object has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**moduleid**<br>(required)|string|ID of the module.| |status|integer|Whether access to the module is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| ### Module L'objet module a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**moduleid**<br>(obligatoire)|string|ID du module.| |status|integer|Indique si l'accès au module est activé.<br><br>Valeurs possibles :<br>0 - Désactivé;<br>1 - *(par défaut)* Activé.| ### MongoDB |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mongodb.collection.stats\[connString,<user>,<password>,<database>,collection\]|<|<|<| |Returns a variety of storage statistics for a given collection.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).<br>**collection** — collection name.| | |mongodb.collections.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered collections. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.collections.usage\[connString,<user>,<password>\]|<|<|<| |Returns usage statistics for collections.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.connpool.stats\[connString,<user>,<password>\]|<|<|<| |Returns information regarding the open outgoing connections from the current database instance to other members of the sharded cluster or replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.db.stats\[connString,<user>,<password>,<database>\]|<|<|<| |Returns statistics reflecting a given database system state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).| | |mongodb.db.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.jumbo\_chunks.count\[connString,<user>,<password>\]|<|<|<| |Returns count of jumbo chunks.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.oplog.stats\[connString,<user>,<password>\]|<|<|<| |Returns a status of the replica set, using data polled from the oplog.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.ping\[connString,<user>,<password>\]|<|<|<| |Tests if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.rs.config\[connString,<user>,<password>\]|<|<|<| |Returns a current configuration of the replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.rs.status\[connString,<user>,<password>\]|<|<|<| |Returns a replica set status from the point of view of the member where the method is run.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.server.status\[connString,<user>,<password>\]|<|<|<| |Returns database state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.sh.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered shards present in the cluster.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | ### MongoDB |Clé<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |mongodb.collection.stats\[connString,\<user\>,\<password\>,\<database\>,collection\]|<|<|<| |Renvoie diverses statistiques de stockage pour une collection donnée.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.<br>**database** - nom de la base de données (par défaut : admin).<br>**collection** — nom de la collection.| | |mongodb.collections.discovery\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie une liste des collections découvertes. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.collections.usage\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie les statistiques d'utilisation des collections.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.connpool.stats\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie des informations concernant les connexions sortantes ouvertes de l'instance de base de données actuelle vers d'autres membres du cluster partitionné ou du jeu de réplicas.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.db.stats\[connString,\<user\>,\<password\>,\<database\>\]|<|<|<| |Renvoie des statistiques reflétant un état système de base de données donné.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.<br>**database** - nom de la base de données (par défaut : admin).| | |mongodb.db.discovery\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie une liste des bases de données découvertes. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.jumbo\_chunks.count\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie le nombre de jumbo chunks.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.oplog.stats\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie un état du jeu de répliques, en utilisant les données interrogées à partir de l'oplog.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.ping\[connString,\<user\>,\<password\>\]|<|<|<| |Teste si une connexion est active ou non.|1 - la connexion est active<br><br>0 - la connexion est interrompue (en cas d'erreur, y compris AUTH et problèmes de configuration).|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.rs.config\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie une configuration actuelle du jeu de réplicas.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.rs.status\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie un état de jeu de réplicas du point de vue du membre où la méthode est exécutée.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.server.status\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie l'état de la base de données.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | |mongodb.sh.discovery\[connString,\<user\>,\<password\>\]|<|<|<| |Renvoie une liste des fragments découverts présents dans le cluster.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion MongoDB.| | ##### Monitoring → Overview removed The Overview section in the Monitoring menu has been removed completely. The same functionality can be still accessed by using the *Data overview* and *Trigger overview* dashboard [widgets](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets). ##### Surveillance → Aperçu supprimé La section Aperçu du menu Surveillance a été complètement supprimée. La même fonctionnalité est toujours accessible à l'aide des [widgets](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets) de tableaux de bord *Aperçu des données* et *Aperçu des déclencheurs* . #### Monitoring → Problems The following parameters are supported: - `show` - filter option "Show": 1 - recent problems, 2 - all, 3 - in problem state - `name` - filter option "Problem": freeform string - `severities` - filter option "Severity": array of selected severities in a format 'severities\[\*\]=\*' (replace \* with severity level): 0 - not classified, 1 - information, 2 - warning, 3 - average, 4 - high, 5 - disaster - `inventory` - filter option "Host inventory": array of inventory fields: \[field\], \[value\] - `evaltype` - filter option "Tags", tag filtering strategy: 0 - And/Or, 2 - Or - `tags` - filter option "Tags": array of defined tags: \[tag\], \[operator\], \[value\] - `show_tags` - filter option "Show tags": 0 - none, 1 - one, 2 - two, 3 - three - `tag_name_format` - filter option "Tag name": 0 - full name, 1 - shortened, 2 - none - `tag_priority` - filter option "Tag display priority": comma-separated string of tag display priority - `show_suppressed` - filter option "Show suppressed problems": should be 'show\_suppressed=1' to show - `unacknowledged` - filter option "Show unacknowledged only": should be 'unacknowledged=1' to show - `compact_view` - filter option "Compact view": should be 'compact\_view=1' to show - `highlight_row` - filter option "Highlight whole row" (use problem color as background color for every problem row): should be '1' to highlight; can be set only when 'compact\_view' is set - `filter_name` - filter properties option "Name": freeform string - `filter_show_counter` - filter properties option "Show number of records": 1 - show, 0 - do not show - `filter_custom_time` - filter properties option "Set custom time period": 1 - set, 0 - do not set - `sort` - sort column: clock, host, severity, name - `sortorder` - sort order or results: DESC - descending, ASC - ascending - `age_state` - filter option "Age less than": should be 'age\_state=1' to enable 'age'. Is used only when 'show' equals 3. - `age` - filter option "Age less than": days - `groupids` - filter option "Host groups": array of host groups IDs - `hostids` - filter option "Hosts": array of host IDs - `triggerids` - filter option "Triggers": array of trigger IDs - `show_timeline` - filter option "Show timeline": should be 'show\_timeline=1' to show - `details` - filter option "Show details": should be 'details=1' to show - `from` - date range start, can be 'relative' (e.g.: now-1m). Is used only when 'filter\_custom\_time' equals 1. - `to` - date range end, can be 'relative' (e.g.: now-1m). Is used only when 'filter\_custom\_time' equals 1. #### Surveillance → Problèmes Les paramètres suivants sont pris en charge : - `show` - option de filtre "Afficher" : 1 - problèmes récents, 2 - tous, 3 - en état de problème - `name` - option de filtre "Problème" : chaîne de forme libre - `severities` - option de filtre "Sévérité" : tableau des sévérités sélectionnées au format 'severities\[\*\]=\*' (remplacez \* par le niveau de sévérité) : 0 - non classifié, 1 - information, 2 - avertissement, 3 - moyenne , 4 - élevé, 5 - désastre - `inventory` - option de filtre "Inventaire de l'hôte" : tableau des champs d'inventaire : \[champ\], \[valeur\] - `evaltype` - option de filtre "Tags", stratégie de filtrage des tags : 0 - Et/Ou, 2 - Ou - `tags` - option de filtre "Tags" : tableau de tags définis : \[tag\], \[operateur\], \[valeur\] - `show_tags` - option de filtre "Afficher les tags" : 0 - aucun, 1 - un, 2 - deux, 3 - trois - `tag_name_format` - option de filtre "Nom du tag" : 0 - nom complet, 1 - raccourci, 2 - aucun - `tag_priority` - option de filtre "Priorité d'affichage des tags" : chaîne séparée par des virgules de la priorité d'affichage des tags - `show_suppressed` - option de filtre "Afficher les problèmes supprimés" : doit être 'show\_suppressed=1' pour afficher - `unacknowledged` - option de filtre "Afficher uniquement les éléments non acquittés" : doit être 'unacknowledged=1' pour afficher - `compact_view` - option de filtre "Vue compacte": doit être 'compact\_view=1' pour afficher - `highlight_row` - option de filtre "Mettre en surbrillance la ligne entière" (utiliser la couleur du problème comme couleur d'arrière-plan pour chaque ligne du problème) : doit être '1' pour mettre en surbrillance ; ne peut être défini que lorsque 'compact\_view' est défini - `filter_name` - option de propriétés de filtre "Nom" : chaîne de forme libre - `filter_show_counter` - option de propriétés de filtre "Afficher le nombre d'enregistrements": 1 - afficher, 0 - ne pas afficher - `filter_custom_time` - option de propriétés de filtre "Définir une période de temps personnalisée" : 1 - définir, 0 - ne pas définir - `sort` - colonne de tri : horloge, hôte, sévérité, nom - `sortorder` - ordre de tri ou résultats : DESC - décroissant, ASC - croissant - `age_state` - fl'option de filtrage "Âge inférieur à" : doit être 'age\_state=1' pour activer 'age'. Est utilisé uniquement lorsque 'show' est égal à 3. - `age` - option de filtre " Âge inférieur à " : jours - `groupids` - option de filtre "Groupes d'hôtes" : tableau d'ID de groupes d'hôtes - `hostids` - option de filtre "Hôtes" : tableau d'ID d'hôtes - `triggerids` - option de filtre "Déclencheurs" : tableau d'ID de déclencheurs - `show_timeline` - option de filtre "Afficher la chronologie": doit être 'show\_timeline=1' pour afficher - `details` - option de filtre "Afficher les détails": doit être 'details=1' pour afficher - `from` - début de la plage de dates, peut être 'relatifve' (par exemple : now-1m). Est utilisé uniquement lorsque 'filter\_custom\_time' est égal à 1. - `to` - fin de la plage de dates, peut être 'relative' (par exemple : now-1m). Est utilisé uniquement lorsque 'filter\_custom\_time' est égal à 1. ##### Monitoring server availability At least three methods (or combination of all methods) may be used in order to monitor availability of a server. - ICMP ping ("icmpping" key) - "zabbix\[host,agent,available\]" item - trigger function nodata() for monitoring the availability of hosts that use active checks only ##### Supervision de la disponibilité du serveur Au moins trois méthodes (ou une combinaison de toutes les méthodes) peuvent être utilisées afin de superviser la disponibilité d'un serveur. * Ping ICMP (clé "icmpping") * Élément "zabbix[host,agent,available]" * La fonction de déclenchement nodata() permet de surveiller la disponibilité des hôtes utilisant uniquement des contrôles actifs. #### Monitoring specific applications #### Supervision des applications spécifiques ### Monitoring The Zabbix API allows you to access history and other data gathered during monitoring. ### Surveillance L'API Zabbix vous permet d'accéder à l'historique et aux autres données collectées lors de la surveillance. ### Month abbreviated with capital letter A "month" is now abbreviated with the capital "M" in the frontend. Previously it was abbreviated with the small "m", overlapping with the abbreviation of a minute. ### Mois abrégé avec une majuscule Un "mois" est maintenant abrégé avec le "M" majuscule dans l'interface. Auparavant, il était abrégé avec le petit "m", chevauchant avec l'abréviation d'une minute. #### More info See [Virtual machine monitoring](/manual/vm_monitoring) for detailed information how to configure Zabbix to monitor VMware environments. #### Plus d'informations Voir [Surveillance des machines virtuelles](/manual/vm_monitoring) pour des informations détaillées sur la configuration de Zabbix pour surveiller les environnements VMware. Most trigger functions are evaluated based on item value [history](/manual/config/items/history_and_trends) data, while some trigger functions for long-term analytics, e.g. **trendavg()**, **trendcount()**, etc, use trend data. La plupart des fonctions de déclenchement sont évaluées en fonction des données de la valeur d'[historique](/manual/config/items/history_and_trends) de l'élément, tandis que certaines fonctions de déclenchement pour l'analyse à long terme, par exemple **trendavg()**, **trendcount()**, etc., utilisent les données de tendance. #### Moving and copy-pasting elements Several selected elements can be **moved** to another place in the map by clicking on one of the selected elements, holding down the mouse button, and moving the cursor to the desired location. One or more elements can be **copied** by selecting the elements, then clicking on a selected element with the right mouse button and selecting *Copy* from the menu. {width="600"} To paste the elements, click on a map area with the right mouse button and select *Paste* from the menu. The *Paste without external links* option will paste the elements retaining only the links that are between the selected elements. Copy-pasting works within the same browser window. Keyboard shortcuts are not supported. #### Déplacer et copier-coller des éléments Plusieurs éléments sélectionnés peuvent être **déplacés** vers un autre endroit de la carte en cliquant sur l'un des éléments sélectionnés, en maintenant le bouton de la souris enfoncé et en déplaçant le curseur à l'emplacement souhaité. Un ou plusieurs éléments peuvent être **copiés** en sélectionnant les éléments, puis en cliquant sur un élément sélectionné avec le bouton droit de la souris et en sélectionnant *Copier* dans le menu. {width="600"} Pour coller les éléments, cliquez sur une zone de la carte avec le bouton droit de la souris et sélectionnez *Coller* dans le menu. L'option *Coller sans liens externes* collera les éléments en ne conservant que les liens qui se trouvent entre les éléments sélectionnés. Le copier-coller fonctionne dans la même fenêtre de navigateur. Les raccourcis clavier ne sont pas pris en charge. ### MQTT |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<| |Subscribes to a specific topic or topics (with wildcards) of the provided broker and waits for publications.|Depending on topic content.<br><br>If wildcards are used, returns topic content as JSON.|**broker\_url** - MQTT broker URL (if empty, *localhost* with port 1883 is used).<br>**topic** - MQTT topic (mandatory). Wildcards (+,\#) are supported.<br>**username,password** - authentication credentials (if required)|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (active)' item type).<br><br>TLS encryption certificates can be used by saving them into a default location (e.g. `/etc/ssl/certs/` directory for Ubuntu). For TLS, use the `tls://` scheme.| ### MQTT |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur retournée**|**Paramètres**|**Commentaires**| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<| |S'abonne à un ou plusieurs sujets spécifiques (avec des caractères génériques) du broker fourni et attend les publications.|En fonction du contenu du sujet.<br><br>Si des caractères génériques sont utilisés, renvoie le contenu du sujet au format JSON.|**broker\_url** - URL du broker MQTT (si vide, *localhost* avec le port 1883 est utilisé).<br>**topic** - Topic MQTT (obligatoire). Les caractères génériques (+,\#) sont pris en charge.<br>**username,password** - identifiants d'authentification (si nécessaire)|L'élément doit être configuré en tant que [vérification active](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (active)' type d'élément).<br><br>Les certificats de chiffrement TLS peuvent être utilisés en les enregistrant dans un emplacement par défaut (par exemple, le répertoire `/etc/ssl/certs/` pour Ubuntu). Pour TLS, utilisez le schéma `tls://`.| ##### Multiple HTTP requests Collect the content of both *https://www.example.com* and *https://www.example.com/release\_notes*: - Create an item with type "Script". - In the *Script* field, enter: ```javascript var request = new HttpRequest(); return request.get("https://www.example.com") + request.get("https://www.example.com/release_notes"); ``` ##### Requêtes HTTP multiples Collecter le contenu de *https://www.example.com* et *https://www.example.com/release\_notes* : - Créer un élément de type "Script". - Dans le champ *Script*, saisir : ```javascript var request = new HttpRequest(); return request.get("https://www.example.com") + request.get("https://www.example.com/release_notes"); ``` #### Multiple LLD rules for the same item Since Zabbix agent version 3.2 it is possible to define several low-level discovery rules with the same discovery item. To do that you need to define the Alias agent [parameter](/manual/appendix/config/zabbix_agentd), allowing to use altered discovery item keys in different discovery rules, for example `vfs.fs.discovery[foo]`, `vfs.fs.discovery[bar]`, etc. #### Plusieurs règles LLD pour le même élément Depuis la version 3.2 de l'agent Zabbix, il est possible de définir plusieurs règles de découverte de bas niveau avec le même élément de découverte. Pour ce faire, vous devez définir le [paramètre](/manual/appendix/config/zabbix_agentd) d'alias de l'agent, permettant d'utiliser des clés d'éléments de découverte modifiées dans différentes règles de découverte, par exemple `vfs.fs.discovery[foo]`, ` vfs.fs.discovery[bar]`, etc. #### MySQL - CR\_CONN\_HOST\_ERROR - CR\_SERVER\_GONE\_ERROR - CR\_CONNECTION\_ERROR - CR\_SERVER\_LOST - CR\_UNKNOWN\_HOST - ER\_SERVER\_SHUTDOWN - ER\_ACCESS\_DENIED\_ERROR - ER\_ILLEGAL\_GRANT\_FOR\_TABLE - ER\_TABLEACCESS\_DENIED\_ERROR - ER\_UNKNOWN\_ERROR #### MySQL - CR\_CONN\_HOST\_ERROR - CR\_SERVER\_GONE\_ERROR - CR\_CONNECTION\_ERROR - CR\_SERVER\_LOST - CR\_UNKNOWN\_HOST - ER\_SERVER\_SHUTDOWN - ER\_ACCESS\_DENIED\_ERROR - ER\_ILLEGAL\_GRANT\_FOR\_TABLE - ER\_TABLEACCESS\_DENIED\_ERROR - ER\_UNKNOWN\_ERROR #### MySQL custom error codes If Zabbix is used with MySQL installation on Azure, an unclear error message *\[9002\] Some errors occurred* may appear in Zabbix logs. This generic error text is sent to Zabbix server or proxy by the database. To get more information about the cause of the error, check Azure logs. #### Codes d'erreur personnalisés MySQL Si Zabbix est utilisé avec l'installation de MySQL sur Azure, un message d'erreur peu clair *\[9002\] Some errors occurred* peut apparaître dans les journaux Zabbix. Ce texte d'erreur générique est envoyé au serveur ou proxy Zabbix par la base de données. Pour obtenir plus d'informations sur la cause de l'erreur, consultez les journaux Azure. ### MySQL Export and import must be performed in tmux/screen to ensure that the session isn't dropped. See also: [Important notes](#important-notes) ### MySQL L'exportation et l'importation doivent être effectuées dans tmux/screen pour s'assurer que la session n'est pas abandonnée. Voir également : [Notes importantes](#important-notes) ### MySQL |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mysql.db.discovery\[connString,<username>,<password>\]|<|<|<| |List of MySQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show databases" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.db.size\[connString,<username>,<password>,dbName\]|<|<|<| |Database size in bytes.|Result of the "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" SQL query for specific database in bytes.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**dbName** - Database name.| | |mysql.get\_status\_variables\[connString,<username>,<password>\]|<|<|<| |Values of global status variables.|Result of the "show global status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.ping\[connString,<username>,<password>\]|<|<|<| |Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.replication.discovery\[connString,<username>,<password>\]|<|<|<| |List of MySQL replications. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show slave status" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.replication.get\_slave\_status\[connString,<username>,<password>,<masterHost>\]|<|<|<| |Replication status.|Result of the "show slave status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**masterHost** - Replication master host name.| | |mysql.version\[connString,<username>,<password>\]|<|<|<| |MySQL version.|String with MySQL instance version.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | ### MySQL |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |mysql.db.discovery\[connString, \<username\>, \<password\>\]|<|<|<| |Liste des bases de données MySQL. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Résultat de la requête SQL "show databases" au format LLD JSON.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.| | |mysql.db.size\[connString, \<username\>, \<password\>,dbName\]|<|<|<| |Taille de la base de données en octets.|Résultat de la requête SQL "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" pour une base de données spécifique en octets.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.<br>**dbName** - Nom de la base de données.| | |mysql.get\_status\_variables\[connString, \<username\>, \<password\>\]|<|<|<| |Valeurs des variables de statut global.|Résultat de la requête SQL "show global status" au format JSON.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.| | |mysql.ping\[connString, \<username\>, \<password\>\]|<|<|<| |Teste si une connexion est active ou non.|1 - la connexion est active<br><br>0 - la connexion est interrompue (si une erreur se présente, y compris AUTH et problèmes de configuration).|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.| | |mysql.replication.discovery\[connString, \<username\>, \<password\>\]|<|<|<| |Liste des réplications MySQL. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Résultat de la requête SQL "show slave status" au format LLD JSON.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.| | |mysql.replication.get\_slave\_status\[connString, \<username\>, \<password\>, \<masterHost\>\]|<|<|<| |État de la réplication.|Résultat de la requête SQL "show slave status" au format JSON.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.<br>**masterHost** - Nom d'hôte du maître de réplication.| | |mysql.version\[connString, \<username\>, \<password\>\]|<|<|<| |Version MySQL.|Chaîne avec la version de l'instance MySQL.|**connString** - URI ou nom de session.<br>**username, password** - Identifiants de connexion MySQL.| | #### MySQL/MariaDB Historically, MySQL and derivatives used 'utf8' as an alias for utf8mb3 - MySQL's own 3-byte implementation of the standard UTF8, which is 4-byte. Starting from MySQL 8.0.28 and MariaDB 10.6.1, 'utf8mb3' character set is deprecated and at some point its support will be dropped while 'utf8' will become a reference to 'utf8mb4'. Since Zabbix 6.0, 'utf8mb4' is supported. To avoid future problems, it is highly recommended to use 'utf8mb4'. Another advantage of switching to 'utf8mb4' is support of supplementary Unicode characters. ::: notewarning As versions before Zabbix 6.0 are not aware of utf8mb4, make sure to first upgrade Zabbix server and DB schema to 6.0.x before executing utf8mb4 conversion. ::: **1.** Check the database character set and collation. For example: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | latin2 | latin2 _general_ci | +--------------------------+----------------------+ Or: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8 | utf8_bin | +--------------------------+----------------------+ As we see, the character set here is not 'utf8mb4' and collation is not 'utf8mb4\_bin', so we need to fix them. **2.** Stop Zabbix. **3.** Create a backup copy of the database! **4.** Fix the character set and collation on database level: alter database <your DB name> character set utf8mb4 collate utf8mb4_bin; Fixed values: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_bin | +--------------------------+----------------------+ **5.** Load the [script](../../../../assets/en/manual/appendix/install/utf8mb4_convert.sql) to fix character set and collation on table and column level: mysql <your DB name> < utf8mb4_convert.sql **6.** Execute the script: SET @ZABBIX_DATABASE = '<your DB name>'; If MariaDB → set innodb_strict_mode = OFF; CALL zbx_convert_utf8(); If MariaDB → set innodb_strict_mode = ON; drop procedure zbx_convert_utf8; Please note that 'utf8mb4' is expected to consume slightly more disk space. **7.** If no errors - you may want to create a database backup copy with the fixed database. **8.** Start Zabbix. #### MySQL/MariaDB Historiquement, MySQL et ses dérivés utilisaient 'utf8' comme alias pour utf8mb3 - la propre implémentation de 3 octets de MySQL de l'UTF8 standard, qui est de 4 octets. À partir de MySQL 8.0.28 et MariaDB 10.6.1, le jeu de caractères 'utf8mb3' est obsolète et à un moment donné, son support sera abandonné tandis que 'utf8' deviendra une référence à 'utf8mb4'. Depuis Zabbix 6.0, 'utf8mb4' est pris en charge. Pour éviter de futurs problèmes, il est fortement recommandé d'utiliser 'utf8mb4'. Un autre avantage du passage à 'utf8mb4' est la prise en charge de caractères Unicode supplémentaires. ::: notewarning Comme les versions antérieures à Zabbix 6.0 ne connaissent pas utf8mb4, assurez-vous d'abord de mettre à niveau le serveur Zabbix et le schéma de base de données vers 6.0.x avant d'exécuter la conversion utf8mb4. ::: **1.** Vérifiez le jeu de caractères et le classement de la base de données. Par exemple: mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | latin2 | latin2 _general_ci | +--------------------------+----------------------+ Ou : mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8 | utf8_bin | +--------------------------+----------------------+ Comme nous le voyons, le jeu de caractères ici n'est pas 'utf8mb4' et la collation n'est pas 'utf8mb4\_bin', nous devons donc les corriger. **2.** Arrêtez Zabbix. **3.** Créez une copie de sauvegarde de la base de données ! **4.** Corrigez le jeu de caractères et le classement au niveau de la base de données : alter database <your DB name> character set utf8mb4 collate utf8mb4_bin; Valeurs corrigées : mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_bin | +--------------------------+----------------------+ **5.** Chargez le [script](../../../../assets/en/manual/appendix/install/utf8mb4_convert.sql) pour corriger le jeu de caractères et le classement au niveau de la table et de la colonne : mysql <your DB name> < utf8mb4_convert.sql **6.** Exécutez le script : SET @ZABBIX_DATABASE = '<nom de votre base de données>'; Si MariaDB → set innodb_strict_mode = OFF; CALL zbx_convert_utf8(); Si MariaDB → set innodb_strict_mode = ON; drop procedure zbx_convert_utf8; Veuillez noter que 'utf8mb4' devrait consommer un peu plus d'espace disque. **7.** S'il n'y a pas d'erreurs, vous pouvez créer une copie de sauvegarde de la base de données avec la base de données corrigée. **8.** Démarrez Zabbix. ##### MySQL Several user parameters can be used for the monitoring of MySQL in the agent configuration file: /usr/local/etc/zabbix\_agentd.conf ### Set of parameters for monitoring MySQL server (v3.23.42 and later) ### Change -u and add -p if required #UserParameter=mysql.ping,mysqladmin -uroot ping|grep alive|wc -l #UserParameter=mysql.uptime,mysqladmin -uroot status|cut -f2 -d":"|cut -f2 -d" " #UserParameter=mysql.threads,mysqladmin -uroot status|cut -f3 -d":"|cut -f2 -d" " #UserParameter=mysql.questions,mysqladmin -uroot status|cut -f4 -d":"|cut -f2 -d" " #UserParameter=mysql.slowqueries,mysqladmin -uroot status|cut -f5 -d":"|cut -f2 -d" " #UserParameter=mysql.qps,mysqladmin -uroot status|cut -f9 -d":"|cut -f2 -d" " #UserParameter=mysql.version,mysql -V - *mysql.ping* Check whether MySQL is alive. Result: 0 - not started 1 - alive - *mysql.uptime* Number of seconds MySQL is running. - *mysql.threads* Number of MySQL threads. - *mysql.questions* Number of processed queries. - *mysql.slowqueries* Number of slow queries. - *mysql.qps* Queries per second. - *mysql.version* Version of MySQL. For example: mysql Ver 14.14 Distrib 5.1.53, for pc-linux-gnu (i686) For additional information see also the userparameter\_mysql.conf file in conf/zabbix\_agentd directory. ##### MySQL Plusieurs paramètres utilisateur peuvent être utilisés pour surveiller MySQL dans le fichier de configuration de l'agent : /usr/local/etc/zabbix\_agentd.conf ### Ensemble de paramètres pour superviser le serveur MySQL (v3.23.42 et ultérieur) ### Changer -u et ajouter -p si nécessaire #UserParameter=mysql.ping,mysqladmin -uroot ping|grep alive|wc -l #UserParameter=mysql.uptime,mysqladmin -uroot status|cut -f2 -d":"|cut -f2 -d" " #UserParameter=mysql.threads,mysqladmin -uroot status|cut -f3 -d":"|cut -f2 -d" " #UserParameter=mysql.questions,mysqladmin -uroot status|cut -f4 -d":"|cut -f2 -d" " #UserParameter=mysql.slowqueries,mysqladmin -uroot status|cut -f5 -d":"|cut -f2 -d" " #UserParameter=mysql.qps,mysqladmin -uroot status|cut -f9 -d":"|cut -f2 -d" " #UserParameter=mysql.version,mysql -V - *mysql.ping* Vérifier si MySQL est démarré. Résultat : 0 - non démarré 1 - démarré - *mysql.uptime* Nombre de secondes d'exécution de MySQL. - *mysql.threads* Numbre de threads MySQL. - *mysql.questions* Nombre de requêtes traitées. - *mysql.slowqueries* Nombre de requêtes lentes. - *mysql.qps* Requêtes par seconde. - *mysql.version* Version de MySQL. Par exemple : mysql Ver 14.14 Distrib 5.1.53, pour pc-linux-gnu (i686) Pour plus d'informations, consultez également le fichier userparameter\_mysql.conf dans le répertoire conf/zabbix\_agentd. ## NAME zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC} ## NOM zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC} ## NAME zabbix\_agentd - Zabbix agent daemon [ ]{#lbAC} ## NOM zabbix\_agentd - Démon de l'agent Zabbix [ ]{#lbAC} ## NAME zabbix\_get - Zabbix get utility [ ]{#lbAC} ## NOM zabbix\_get - Utilitaire Zabbix get [ ]{#lbAC} ## NAME zabbix\_js - Zabbix JS utility [ ]{#lbAC} ## NOM zabbix\_js - Utilitaire Zabbix JS [ ]{#lbAC} ## NAME zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC} ## NOM zabbix\_proxy - Démon proxy Zabbix proxy [ ]{#lbAC} ## NAME zabbix\_sender - Zabbix sender utility [ ]{#lbAC} ## NOM zabbix\_sender - Utilitaire Zabbix sender [ ]{#lbAC} ## NAME zabbix\_server - Zabbix server daemon [ ]{#lbAC} ## NOM zabbix\_server - Démon serveur Zabbix [ ]{#lbAC} ## NAME zabbix\_web\_service - Zabbix web service [ ]{#lbAC} ## NOM zabbix\_web\_service - Service web Zabbix[ ]{#lbAC} ##### Naming and location of persistent files Zabbix agent distinguishes active checks by their keys. For example, logrt\[/home/zabbix/test.log\] and logrt\[/home/zabbix/test.log,\] are different items. Modifying the item logrt\[/home/zabbix/test.log,,,10\] in frontend to logrt\[/home/zabbix/test.log,,,20\] will result in deleting the item logrt[/home/zabbix/test.log,,,10] from the agent's list of active checks and creating logrt\[/home/zabbix/test.log,,,20\] item \(some attributes are carried across modification in frontend/server, not in agent\). The file name is composed of MD5 sum of item key with item key length appended to reduce possibility of collisions. For example, the state of logrt\[/home/zabbix50/test.log,,,,,,,,/home/zabbix50/agent_private\] item will be kept in persistent file c963ade4008054813bbc0a650bb8e09266. Multiple log items can use the same value of **persistent\_dir**. **persistent\_dir** is specified by taking into account specific file system layouts, mount points and mount options and storage mirroring configuration - the persistent file should be on the same mirrored filesystem as the monitored log file. If **persistent\_dir** directory cannot be created or does not exist, or access rights for Zabbix agent does not allow to create/write/read/delete files the log item becomes NOTSUPPORTED. ##### Nommage et emplacement des fichiers persistants L'agent Zabbix distingue les vérifications actives par leurs clés. Par exemple, logrt\[/home/zabbix/test.log\] et logrt\[/home/zabbix/test.log,\] sont des éléments différents. La modification de l'élément logrt\[/home/zabbix/test.log,,,10\] en frontend vers logrt\[/home/zabbix/test.log,,,20\] entraînera la suppression de l'élément logrt[/home /zabbix/test.log,,,10] de la liste des vérifications actives de l'agent et la création de l'élément logrt\[/home/zabbix/test.log,,,20\] \(certains attributs sont transmis lors de la modification dans le frontend/serveur , pas dans agent\). Le nom du fichier est composé de la somme MD5 de la clé d'élément avec la longueur de la clé d'élément ajoutée pour réduire les risques de collisions. Par exemple, l'état de l'élément logrt\[/home/zabbix50/test.log\,\,\,\,\,\,\,\,/home/zabbix50/agent_private\] sera conservé dans le fichier persistant c963ade4008054813bbc0a650bb8e09266. Plusieurs éléments de journal peuvent utiliser la même valeur **persistent\_dir**. **persistent\_dir** est spécifié en tenant compte des dispositions spécifiques du système de fichiers, des points de montage et des options de montage et de la configuration de la mise en miroir du stockage - le fichier persistant doit se trouver sur le même système de fichiers en miroir que le fichier journal surveillé. Si le répertoire **persistent\_dir** ne peut pas être créé ou n'existe pas, ou si les droits d'accès pour l'agent Zabbix ne permettent pas de créer/écrire/lire/supprimer des fichiers, l'élément de journal devient NOTSUPPORTED. ##### Naming convention Before you create a module, it is important to agree on the naming convention for different module items such as directories and files so that we could keep things well organized. You can also find examples above, in the [Module structure](#module_structure) section. |Item|Naming rules|Example| |----|------------|-------| |*Module directory*|Lowercase \[a-z\], underscore and decimal digits|example\_v2| |*Action subdirectories*|Lowercase \[a-z\] and underscore character|data\_export| |*Action files*|CamelCase, ending with action type|SomethingView.php| |*View and partial files*|Lowercase \[a-z\]<br>Words separated with dot<br>Prefixed by `module.` followed by module name<br>Ending with action type and .php file extension|module.example.something.view.php| |*Javascript files*|The same rules apply as for view and partial files, except the .js.php file extension.|module.example.something.view.js.php| Note that the 'module' prefix and name inclusion is mandatory for view and partial file names, unless you need to override Zabbix core views or partials. This rule, however, does not apply to action file names. ##### Convention de nommage Avant de créer un module, il est important de s'entendre sur la convention de nommage des différents éléments du module, tels que les répertoires et les fichiers, afin que nous puissions garder les choses bien organisées. Vous pouvez également trouver des exemples ci-dessus, dans la section [Structure du module](#module_structure). |Élément|Règles de nommage|Exemple| |----|------------|-------| |*Répertoire du module*|Minuscules \[a-z\], underscores et chiffres décimaux|exemple\_v2| |*Sous-répertoires d'action*|Minuscules \[a-z\] et underscores|data\_export| |*Fichiers d'action*|Cas d'usage, se terminant par le type d'action|SomethingView.php| |*fichiers vues et partiels*|Minuscules \[a-z\]<br>Mots séparés par un point<br>Préfixé par `module.` suivi du nom du module<br>Se terminant par le type d'action et l'extension de fichier .php|module.example.something.view.php| |*Fichiers Javascript*|Les mêmes règles s'appliquent que celles pour les fichiers vues et partiels, à l'exception de l'extension de fichier .js.php.|module.example.something.view.js.php| Notez que le préfixe 'module' et l'inclusion de nom sont obligatoires pour les noms de vue et de fichiers partiels, sauf si vous devez remplacer les vues principales ou partielles de Zabbix. Cette règle, cependant, ne s'applique pas aux noms de fichiers d'action. #### Negative problem duration It is actually possible in some common situations to have negative problem duration i.e. when the problem resolution time is earlier than problem creation time, e. g.: - If some host is monitored by proxy and a network error happens, leading to no data received from the proxy for a while, the nodata(/host/key) trigger will be fired by the server. When the connection is restored, the server will receive item data from the proxy having a time from the past. Then, the nodata(/host/key) problem will be resolved and it will have a negative problem duration; - When item data that resolve the problem event are sent by Zabbix sender and contain a timestamp earlier than the problem creation time, a negative problem duration will also be displayed. ::: noteclassic Negative problem duration is not affecting [SLA calculation](/manual/it_services) or [Availability report](/manual/web_interface/frontend_sections/reports/availability) of a particular trigger in any way; it neither reduces nor expands problem time. ::: #### Durée du problème négative Il est en fait possible dans certaines situations courantes d'avoir une durée de problème négative, c'est-à-dire lorsque l'heure de résolution du problème est antérieure à l'heure de création du problème, par exemple : - Si un hôte est surveillé par un proxy et qu'une erreur réseau se produit, entraînant l'absence de données reçues du proxy pendant un certain temps, le déclencheur nodata(/host/key) sera déclenché par le serveur. Lorsque la connexion est rétablie, le serveur recevra des données d'éléments du proxy ayant une heure passée. Ensuite, le problème nodata(/host/key) sera résolu et il aura une durée de problème négative ; - Lorsque les données d'élément qui résolvent l'événement de problème sont envoyées par Zabbix sender et contiennent un horodatage antérieur à l'heure de création du problème, une durée de problème négative sera également affichée. ::: noteclassic La durée négative du problème n'affecte en aucune façon le [calcul SLA](/manual/it_services) ou le [rapport de disponibilité](/manual/web_interface/frontend_sections/reports/availability) d'un déclencheur particulier ; il ne réduit ni ne prolonge le temps de problème. ::: #### NetBSD 8.0 and newer Various Zabbix processes may randomly crash on startup on the NetBSD versions 8.X and 9.X. That is due to the too small default stack size (4MB), which must be increased by running: ulimit -s 10240 For more information, please see the related problem report: [ZBX-18275](https://support.zabbix.com/browse/ZBX-18275). #### NetBSD 8.0 et plus récent Divers processus Zabbix peuvent planter de manière aléatoire au démarrage sur les versions 8.X et 9.X de NetBSD. Cela est dû à la taille trop petite de la pile par défaut (4 Mo), qui doit être augmentée en exécutant : ulimit -s 10240 Pour plus d'informations, veuillez consulter le rapport de problème connexe : [ZBX-18275](https://support.zabbix.com/browse/ZBX-18275). ##### Network data |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**net.dns**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |Checks if DNS service is up.|0 - DNS is down (server did not respond or DNS resolution failed)<br><br>1 - DNS is up|**ip** - IP address of DNS server (leave empty for the default DNS server, on Windows supported for Zabbix agent 2, ignored for Zabbix agent)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - number of tries for the request (default is 2)<br>**protocol** (since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (not supported for Zabbix agent on Windows, Zabbix agent 2 on all OS), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns*| |**net.dns.record**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |Performs a DNS query.|Character string with the required type of information|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - number of tries for the request (default is 2)<br>**protocol**(since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (not supported for Zabbix agent on Windows, Zabbix agent 2 on all OS), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns.query*| |**net.if.collisions**\[if\]|<|<|<| |Number of out-of-window collisions.|Integer|**if** - network interface name| | |**net.if.discovery**|<|<|<| |List of network interfaces. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>On FreeBSD, OpenBSD and NetBSD supported since Zabbix 2.2.<br><br>Some Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names.| |**net.if.in**\[if,<mode>\]|<|<|<| |Incoming traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*frame* - the number of packet framing errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver<br>*multicast* - the number of multicast frames received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix 1.8.6.<br><br>Examples:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |**net.if.out**\[if,<mode>\]|<|<|<| |Outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*collisions (colls)* - the number of collisions detected on the interface<br>*carrier* - the number of carrier losses detected by the device driver<br>*compressed* - the number of compressed packets transmitted by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix agent 1.8.6 version.<br><br>Examples:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |**net.if.total**\[if,<mode>\]|<|<|<| |Sum of incoming and outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Examples:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.<br><br>Note that dropped packets are supported only if both net.if.in and net.if.out work for dropped packets on your platform.| |**net.tcp.listen**\[port\]|<|<|<| |Checks if this TCP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - TCP port number|Example:<br>=> net.tcp.listen\[80\]<br><br>On Linux supported since Zabbix 1.8.4<br><br>Since Zabbix 3.0.0, on Linux kernels 2.6.14 and above, information about listening TCP sockets is obtained from the kernel's NETLINK interface, if possible. Otherwise, the information is retrieved from /proc/net/tcp and /proc/net/tcp6 files.| |**net.tcp.port**\[<ip>,port\]|<|<|<| |Checks if it is possible to make TCP connection to specified port.|0 - cannot connect<br><br>1 - can connect|**ip** - IP or DNS name (default is 127.0.0.1)<br>**port** - port number|Example:<br>=> net.tcp.port\[,80\] → can be used to test availability of web server running on port 80.<br><br>For simple TCP performance testing use net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).| |**net.tcp.service**\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.port for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |**net.tcp.service.perf**\[service,<ip>,<port>\]|<|<|<| |Checks performance of TCP service.|0 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,<port>\] for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |**net.tcp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.tcp.socket.count\[,80,,,established\] → check if local TCP port 80 is in "established" state<br><br>This item is supported since Zabbix 6.0.| |**net.udp.listen**\[port\]|<|<|<| |Checks if this UDP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - UDP port number|Example:<br>=> net.udp.listen\[68\]<br><br>On Linux supported since Zabbix 1.8.4| |**net.udp.service**\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |**net.udp.service.perf**\[service,<ip>,<port>\]|<|<|<| |Checks performance of UDP service.|0 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |**net.udp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *unconn*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → check if any UDP socket is in "listening" state<br><br>This item is supported since Zabbix 6.0.| ##### Données réseau |Clé d'élément|<|<|<| |--|--|------|------| |Description|Valeur de retour|Paramètres|Commentaires| |**net.dns**\[\<ip\>,name,\<type\>,\<timeout\>,\<count\>,\<protocol\>\]|<|<|<| |Vérifie si le service DNS est opérationnel.|0 - Le DNS est en panne (le serveur n'a pas répondu ou la résolution DNS a échoué)<br><br>1 - Le DNS est opérationnel|**ip** - Adresse IP du serveur DNS (laissez vide pour le serveur DNS par défaut, sous Windows pris en charge pour l'agent Zabbix 2, ignoré pour l'agent Zabbix)<br>**name** - Nom DNS à interroger<br>**type** - type d'enregistrement à interroger (la valeur par défaut est *SOA*)<br>**timeout** (ignoré sous Windows, sauf si vous utilisez l'agent Zabbix 2 version 6.0.1 ou plus récente) - délai d'expiration de la requête en secondes (la valeur par défaut est 1 seconde)<br>**count** (ignoré sous Windows, sauf si vous utilisez l'agent Zabbix 2 version 6.0.1 ou plus récente) - nombre d'essais pour la requête (la valeur par défaut est 2)<br>**protocol** (depuis la version 3.0) - le protocole utilisé pour effectuer les requêtes DNS : *udp* (par défaut) ou *tcp*|Exemple :<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>Les valeurs possibles pour `type` sont :<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (non pris en charge pour l'agent Zabbix sous Windows, l'agent Zabbix 2 sur tous les systèmes d'exploitation), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Les noms de domaine internationalisés ne sont pas pris en charge, veuillez utiliser des noms encodés IDNA à la place.<br><br>Le type d'enregistrement SRV est pris en charge depuis Zabbix 1.8.6 (Unix) et 2.0.0 (Windows).<br><br>Nommage avant Zabbix 2.0 (toujours pris en charge) : *net.tcp.dns*| |**net.dns.record**\[\<ip\>,name,\<type\>,\<timeout\>,\<count\>,\<protocol\>\]|<|<|<| |Effectue une requête DNS.|Chaîne de caractères avec le type d'informations requis|**ip** - Adresse IP du serveur DNS (laissez vide pour le serveur DNS par défaut, ignoré sous Windows, sauf si vous utilisez l'agent Zabbix 2 version 6.0.1 ou plus récente)<br>**name** - Nom DNS à interroger<br>**type** - type d'enregistrement à interroger (la valeur par défaut est *SOA*)<br>**timeout** (ignoré sous Windows, sauf si vous utilisez l'agent Zabbix 2 version 6.0.1 ou plus récente) - délai d'expiration de la requête en secondes (la valeur par défaut est 1 seconde)<br>**count** (ignoré sous Windows, sauf si vous utilisez l'agent Zabbix 2 version 6.0.1 ou plus récente) - nombre d'essais pour la requête (la valeur par défaut est 2)<br>**protocol**(depuis la version 3.0) - le protocole utilisé pour effectuer les requêtes DNS : *udp* (par défaut) ou *tcp*|Exemple :<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>Les valeurs possibles pour `type` sont :<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (non pris en charge pour l'agent Zabbix sous Windows, l'agent Zabbix 2 sur tous les systèmes d'exploitation), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Les noms de domaine internationalisés ne sont pas pris en charge, veuillez utiliser des noms encodés IDNA à la place.<br><br>Le type d'enregistrement SRV est pris en charge depuis Zabbix 1.8.6 (Unix) et 2.0.0 (Windows).<br><br>Nommage avant Zabbix 2.0 (toujours pris en charge) : *net.tcp.dns.query*| |**net.if.collisions**\[if\]|<|<|<| |Nombre de collisions hors fenêtre.|Entier|**if** - nom de l'interface réseau| | |**net.if.discovery**|<|<|<| |Liste des interfaces réseau. Utilisé pour la découverte de bas niveau.|Objet JSON| |Pris en charge depuis Zabbix 2.0.<br><br>Sur FreeBSD, OpenBSD et NetBSD pris en charge depuis Zabbix 2.2.<br><br>Certaines versions de Windows (par exemple, Server 2008) peuvent nécessiter l'installation des dernières mises à jour pour prendre en charge non-ASCII caractères dans les noms d'interface.| |**net.if.in**\[if,\<mode\>\]|<|<|<| |Statistiques du trafic entrant sur l'interface réseau.|Entier|**if** - nom de l'interface réseau (Unix) ; description complète de l'interface réseau ou adresse IPv4 ; ou, si entre accolades, le GUID de l'interface réseau (Windows)<br>**mode** - valeurs possibles :<br>*bytes* - nombre d'octets (par défaut)<br>*packets* - nombre de paquets<br>*errors* - nombre d'erreurs<br>*dropped* - nombre de paquets rejetés<br>*overruns (fifo)* - le nombre d'erreurs de tampon FIFO<br>*frame* - le nombre d'erreurs de cadrage de paquets<br>*compressed* - le nombre de paquets compressés transmis ou reçus par le pilote de périphérique<br>*multicast* - le nombre de trames multicast reçues par le pilote de périphérique|Sous Windows, l'élément obtient les valeurs des compteurs 64 bits s'ils sont disponibles. Les compteurs de statistiques d'interface 64 bits ont été introduits dans Windows Vista et Windows Server 2008. Si les compteurs 64 bits ne sont pas disponibles, l'agent utilise des compteurs 32 bits.<br><br>Les noms d'interface multi-octets sous Windows sont pris en charge depuis Zabbix 1.8.6.<br><br>Exemples :<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>Vous pouvez obtenir des descriptions d'interface réseau sous Windows avec les éléments net.if.discovery ou net.if.list.<br><br>Vous pouvez utiliser cette clé avec l'étape de prétraitement *Changement par seconde* afin d'obtenir des statistiques d'octets par seconde.| |**net.if.out**\[if,\<mode\>\]|<|<|<| |Statistiques du trafic sortant sur l'interface réseau.|Entier|**if** - nom de l'interface réseau (Unix) ; description complète de l'interface réseau ou adresse IPv4 ; ou, si entre accolades, le GUID de l'interface réseau (Windows)<br>**mode** - valeurs possibles :<br>*bytes* - nombre d'octets (par défaut)<br>*packets* - nombre de paquets<br>*errors* - nombre d'erreurs<br>*dropped* - nombre de paquets rejetés<br>*overruns (fifo)* - le nombre d'erreurs de tampon FIFO<br>*collisions (colls)* - le nombre de collisions détectées sur l'interface<br>*carrier* - le nombre de pertes de porteuse détectées par le pilote de périphérique<br>*compressed* - le nombre de paquets compressés transmis par le pilote de périphérique|Sous Windows, l'élément obtient les valeurs des compteurs 64 bits si disponibles. Les compteurs de statistiques d'interface 64 bits ont été introduits dans Windows Vista et Windows Server 2008. Si les compteurs 64 bits ne sont pas disponibles, l'agent utilise des compteurs 32 bits.<br><br>Les noms d'interface multi-octets sous Windows sont pris en charge depuis Zabbix version 1.8.6 de l'agent.<br><br>Exemples :<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>Vous pouvez obtenir des descriptions d'interface réseau sous Windows avec les éléments net.if.discovery ou net.if.list.<br><br>Vous pouvez utiliser cette clé avec l'étape de prétraitement *Changement par seconde* afin d'obtenir des statistiques d'octets par seconde .| |**net.if.total**\[if,\<mode\>\]|<|<|<| |Somme des statistiques de trafic entrant et sortant sur l'interface réseau.|Entier|**if** - nom de l'interface réseau (Unix) ; description complète de l'interface réseau ou adresse IPv4 ; ou, si entre accolades, le GUID de l'interface réseau (Windows)<br>**mode** - valeurs possibles:<br>*bytes* - nombre d'octets (par défaut)<br>*packets* - nombre de paquets<br>*errors* - nombre d'erreurs<br>*dropped* - nombre de paquets rejetés<br>*overruns (fifo)* - le nombre d'erreurs de tampon FIFO<br>*compressed* - le nombre de paquets compressés transmis ou reçus par le pilote de périphérique|Sous Windows, l'élément obtient les valeurs des compteurs 64 bits si disponibles. Les compteurs statistiques d'interface 64 bits ont été introduits dans Windows Vista et Windows Server 2008. Si les compteurs 64 bits ne sont pas disponibles, l'agent utilise des compteurs 32 bits.<br><br>Exemples :<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>Vous pouvez obtenir des descriptions d'interface réseau sous Windows avec les éléments net.if.discovery ou net.if.list.<br><br>Vous pouvez utiliser cette clé avec l'étape de prétraitement *Changement par seconde* afin d'obtenir des statistiques d'octets par seconde .<br><br>Notez que les paquets abandonnés ne sont pris en charge que si net.if.in et net.if.out fonctionnent pour les paquets abandonnés sur votre plate-forme.| |**net.tcp.listen**\[port\]|<|<|<| |Vérifie si ce port TCP est à l'état LISTEN.|0 - il n'est pas à l'état LISTEN<br><br>1 - il est à l'état LISTEN|**port** - Numéro de port TCP|Exemple :<br>=> net.tcp.listen\[80\]<br><br>Sur Linux pris en charge depuis Zabbix 1.8.4<br><br>Depuis Zabbix 3.0.0, sur les noyaux Linux 2.6.14 et supérieurs, les informations sur l'écoute des sockets TCP sont obtenues à partir de l'interface NETLINK du noyau, si possible. Sinon, les informations sont extraites des fichiers /proc/net/tcp et /proc/net/tcp6.| |**net.tcp.port**\[\<ip\>,port\]|<|<|<| |Vérifie s'il est possible d'établir une connexion TCP au port spécifié.|0 - impossible de se connecter<br><br>1 - peut se connecter|**ip** - Nom IP ou DNS (la valeur par défaut est 127.0.0.1)<br>**port** - numéro de port|Exemple :<br>=> net.tcp.port\[,80\] → peut être utilisé pour tester la disponibilité du serveur Web s'exécutant sur le port 80.<br><br>Pour un simple test de performances TCP, utilisez net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Notez que ces vérifications peuvent entraîner des messages supplémentaires dans les fichiers journaux du démon système (les sessions SMTP et SSH étant généralement enregistrées).| |**net.tcp.service**\[service,\<ip\>,\<port\>\]|<|<|<| |Vérifie si le service est en cours d'exécution et accepte les connexions TCP.|0 - le service est arrêté<br><br>1 - le service est en cours d'exécution|**service** - soit :<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (voir les [détails](/manual/appendix/items/service_check_details))<br>**ip** - Adresse IP (la valeur par défaut est 127.0.0.1)<br>**port** - numéro de port (par défaut, le numéro de port de service standard est utilisé)|Exemple :<br>=> net.tcp.service\[ftp,,45\] → peut être utilisé pour tester la disponibilité du serveur FTP sur le port TCP 45.<br><br>Notez que ces vérifications peuvent entraîner des messages supplémentaires dans les fichiers journaux du démon système (les sessions SMTP et SSH étant généralement enregistrées).<br><br> La vérification des protocoles chiffrés (comme IMAP sur le port 993 ou POP sur le port 995) n'est actuellement pas prise en charge. Pour contourner le problème, veuillez utiliser net.tcp.port pour des vérifications comme celles-ci.<br><br>La vérification de LDAP et HTTPS sous Windows n'est prise en charge que par l'agent Zabbix 2.<br><br>Notez que la vérification telnet recherche une invite de connexion (':' à la fin).<br><br>Voir aussi les [problèmes connus](/manual/installation/known_issues#https_checks) de la vérification du service HTTPS.<br><br>Les services *https* et *telnet* sont pris en charge depuis Zabbix 2.0.| |**net.tcp.service.perf**\[service,\<ip\>,\<port\>\]|<|<|<| |Vérifie les performances du service TCP.|0 - le service est en panne<br><br>secondes - le nombre de secondes passées lors de la connexion au service|**service** - soit :<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (voir les [détails](/manual/appendix/items/service_check_details))<br>**ip** - Adresse IP (la valeur par défaut est 127.0.0.1)<br>**port** - numéro de port (par défaut, le numéro de port de service standard est utilisé)|Exemple :<br>=> net.tcp.service.perf\[ssh\] → peut être utilisé pour tester la vitesse de réponse initiale du serveur SSH.<br><br>La vérification des protocoles cryptés (comme IMAP sur le port 993 ou POP sur le port 995) n'est actuellement pas prise en charge. Pour contourner ce problème, veuillez utiliser net.tcp.service.perf\[tcp,\<ip\>,\<port\>\] pour des vérifications comme celles-ci.<br><br>La vérification de LDAP et HTTPS sous Windows n'est prise en charge que par l'agent Zabbix 2.<br><br>Notez que la vérification telnet recherche une invite de connexion (':' à la fin).<br><br>Voir aussi les [problèmes connus](/manual/installation/known_issues#https_checks) de la vérification du service HTTPS.<br><br>Les services *https* et *telnet* sont pris en charge depuis Zabbix 2.0.| |**net.tcp.socket.count**\[\<laddr\>,\<lport\>,\<raddr\>,\<rport\>,\<state\>\]|<|<|<| |Renvoie le nombre de sockets TCP qui correspondent aux paramètres.|Entier|**laddr** - adresse IPv4/6 locale ou sous-réseau CIDR<br>**lport** - numéro de port local ou nom de service<br>**raddr** - adresse IPv4/6 distante ou sous-réseau CIDR<br>**rport** - numéro de port distant ou nom de service<br>**state** - état de connexion (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|Cet élément est pris en charge sous Linux uniquement sur l'agent Zabbix/agent 2. Sur l'agent Zabbix 2, il est également pris en charge sur Windows 64 bits.<br><br>Exemple :<br>=> net.tcp.socket.count\[,80,,,established\] → vérifier si le port TCP local 80 est à l'état "established"<br><br>Cet élément est pris en charge depuis Zabbix 6.0.| |**net.udp.listen**\[port\]|<|<|<| |Vérifie si ce port UDP est à l'état LISTEN.|0 - il n'est pas à l'état LISTEN<br><br>1 - il est à l'état LISTEN|**port** - Numéro de port UDP|Exemple :<br>=> net.udp.listen\[68\]<br><br>Sur Linux pris en charge depuis Zabbix 1.8.4 | |**net.udp.service**\[service,\<ip\>,\<port\>\]|<|<|<| |Vérifie si le service est en cours d'exécution et répond aux requêtes UDP.|0 - le service est en panne<br><br>1 - le service est en cours d'exécution|**service** - *ntp* (voir les [détails](/manual/appendix/items/service_check_details))<br>**ip** - Adresse IP (la valeur par défaut est 127.0.0.1)<br>**port** - numéro de port (par défaut, le numéro de port de service standard est utilisé)|Exemple :<br>=> net.udp.service\[ntp,,45\] → peut être utilisé pour tester la disponibilité du service NTP sur le port UDP 45.<br><br>Cet élément est pris en charge depuis Zabbix 3.0.0, mais le service *ntp* était disponible pour l'élément net.tcp.service\[\] dans versions antérieures.| |**net.udp.service.perf**\[service,\<ip\>,\<port\>\]|<|<|<| |Vérifie les performances du service UDP.|0 - le service est en panne<br><br>secondes - le nombre de secondes passées à attendre une réponse du service|**service** - *ntp* (voir les [détails](/manual/appendix/items/service_check_details))<br>**ip** - Adresse IP (la valeur par défaut est 127.0.0.1)<br>**port** - numéro de port (par défaut, le numéro de port de service standard est utilisé)|Exemple :<br>=> net.udp.service.perf\[ntp\] → peut être utilisé pour tester le temps de réponse du service NTP.<br><br>Cet élément est pris en charge depuis Zabbix 3.0.0, mais le service *ntp* était disponible pour l'élément net.tcp.service\[\] dans les versions précédentes.| |**net.udp.socket.count**\[\<laddr\>,\<lport\>,\<raddr\>,\<rport\>,\<state\>\]|<|<|<| |Renvoie le nombre de sockets TCP qui correspondent aux paramètres.|Entier|**laddr** - adresse IPv4/6 locale ou sous-réseau CIDR<br>**lport** - numéro de port local ou nom de service<br>**raddr** - adresse IPv4/6 distante ou sous-réseau CIDR<br>**rport** - numéro de port distant ou nom de service<br>**state** - état de connexion (*established*, *unconn*)|Cet élément est pris en charge sous Linux uniquement sur l'agent Zabbix/agent 2. Sur l'agent Zabbix 2, il est également pris en charge sur Windows 64 bits.<br><br>Exemple :<br>=> net.udp.socket.count\[,,,,listening\] → vérifie si un socket UDP est à l'état "listening"<br><br>Cet élément est pris en charge depuis Zabbix 6.0.| #### Network discovery In a [network discovery rule](/manual/discovery/network_discovery/rule), user macros can be used in the following fields: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Update interval|<|no| |*SNMP v1, v2*|<|<| | |SNMP community|yes| |^|SNMP OID|yes| |*SNMP v3*|<|<| | |Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |^|SNMP OID|yes| #### Découverte réseau Dans une [règle de découverte de réseau](/manual/discovery/network_discovery/rule), les macros utilisateur peuvent être utilisées dans les champs suivants : |Emplacement|<|Plusieurs macros/mix avec du texte^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Intervalle de mise à jour|<|non| |*SNMP v1, v2*|<|<| | |Communauté SNMP|oui| |^|OID SNMP|oui| |*SNMP v3*|<|<| | |Nom du contexte|oui| |^|Nom de sécurité|oui| |^|Phrase secrète d'authentification|oui| |^|Phrase secrète de confidentialité|oui| |^|OID SNMP|oui| #### Network discovery Manage network-level discovery rules to automatically find and monitor new hosts. Gain full access to information about discovered services and hosts. [Discovery rule API](/manual/api/reference/drule) | [Discovery check API](/manual/api/reference/dcheck) | [Discovered host API](/manual/api/reference/dhost) | [Discovered service API](/manual/api/reference/dservice) #### Découverte du Réseau Gérez les règles de découverte au niveau du réseau pour rechercher automatiquement les nouveaux hôtes. Obtenez un accès complet aux informations sur les services et les hôtes découverts. [API Règle de découverte](/manual/api/reference/drule) | [API Vérification découverte](/manual/api/reference/dcheck) | [API Découverte des hôtes](/manual/api/reference/dhost) | [API Découverte des services](/manual/api/reference/dservice) ##### New templates See the list of [new templates](/manual/introduction/whatsnew600#new_templates) in Zabbix 6.0.0 ##### Nouveaux modèles Voir la liste des [nouveaux modèles](/manual/introduction/whatsnew600#new_templates) dans Zabbix 6.0.0 ##### Non-primitive data types Since Zabbix 4.0.0 it is possible to work with custom MBeans returning non-primitive data types, which override the **toString()** method. ##### Types de données non-primitif Depuis Zabbix 4.0.0, il est possible de travailler avec des MBeans personnalisables retournant des types de données non-primitif, qui remplace la méthode **toString()**. ### Notation ### Notation ::: noteclassic Please be aware that after upgrading some third-party software integrations in Zabbix might be affected, if the external software is not compatible with the upgraded Zabbix version. ::: ::: noteclassic Veuillez noter qu'après la mise à niveau, certaines intégrations de logiciels tiers dans Zabbix peuvent être affectées, si le logiciel externe n'est pas compatible avec la version mise à niveau de Zabbix. ::: ::: noteimportant For SourceIP support in LDAP simple checks (e.g. `net.tcp.service[ldap]`), OpenLDAP version 2.6.1 or above is required. SourceIP is supported in LDAP simple checks since Zabbix 6.0.1. ::: ::: noteimportant Pour la prise en charge de SourceIP dans les vérifications simples LDAP (par exemple, `net.tcp.service[ldap]`), OpenLDAP version 2.6.1 ou supérieur est requis. SourceIP est pris en charge dans les vérifications simples LDAP depuis Zabbix 6.0.1. ::: ::: noteimportant When creating a maintenance period, the [time zone](/manual/web_interface/time_zone) of the user who creates it is used. However, when recurring maintenance periods (*Daily*, *Weekly*, *Monthly*) are scheduled, the time zone of the Zabbix server is used. To ensure predictable behavior of recurring maintenance periods, it is required to use a common time zone for all parts of Zabbix. ::: ::: noteimportant Lors de la création d'une période de maintenance, le [fuseau horaire](/manual/web_interface/time_zone) de l'utilisateur qui la crée est utilisé. Cependant, lorsque des périodes de maintenance récurrentes (*quotidiennes*, *hebdomadaires*, *mensuelles*) sont planifiées, le fuseau horaire du serveur Zabbix est utilisé. Pour garantir un comportement prévisible des périodes de maintenance récurrentes, il est nécessaire d'utiliser un fuseau horaire commun pour toutes les parties de Zabbix. ::: ##### Notes on connection termination If IPMI checks are not performed (by any reason: all host IPMI items disabled/notsupported, host disabled/deleted, host in maintenance etc.) the IPMI connection will be terminated from Zabbix server or proxy in 3 to 4 hours depending on the time when Zabbix server/proxy was started. ##### Remarques sur la fin de la connexion Si les vérifications IPMI ne sont pas effectuées (pour une raison quelconque : tous les éléments IPMI hôte désactivés/non pris en charge, hôte désactivé/supprimé, hôte en maintenance, etc.) la connexion IPMI sera terminée du serveur ou du proxy Zabbix en 3 à 4 heures selon l'heure lorsque le serveur/proxy Zabbix a été démarré. ##### Notes on discrete sensor names in OpenIPMI-2.0.16, 2.0.17, 2.0.18 and 2.0.19 Names of discrete sensors in OpenIPMI-2.0.16, 2.0.17 and 2.0.18 often have an additional "`0`" (or some other digit or letter) appended at the end. For example, while `ipmitool` and OpenIPMI-2.0.19 display sensor names as "`PhysicalSecurity`" or "`CATERR`", in OpenIPMI-2.0.16, 2.0.17 and 2.0.18 the names are "`PhysicalSecurity0`" or "`CATERR0`", respectively. When configuring an IPMI item with Zabbix server using OpenIPMI-2.0.16, 2.0.17 and 2.0.18, use these names ending with "0" in the *IPMI sensor* field of IPMI agent items. When your Zabbix server is upgraded to a new Linux distribution, which uses OpenIPMI-2.0.19 (or later), items with these IPMI discrete sensors will become "NOT SUPPORTED". You have to change their *IPMI sensor* names (remove the '0' in the end) and wait for some time before they turn "Enabled" again. ##### Notes sur les noms de capteurs discrets dans OpenIPMI-2.0.16, 2.0.17, 2.0.18 et 2.0.19 Les noms de capteurs discrets dans OpenIPMI-2.0.16, 2.0.17 et 2.0.18 ont souvent un "`0`" supplémentaire (ou un autre chiffre ou lettre) ajouté à la fin. Par exemple, si `ipmitool` et OpenIPMI-2.0.19 affichent les noms des capteurs comme "`PhysicalSecurity`" ou "`CATERR`", dans OpenIPMI-2.0.16, 2.0.17 et 2.0.18, les noms sont "`PhysicalSecurity0`" ou "`CATERR0`", respectivement. Lors de la configuration d'un élément IPMI avec le serveur Zabbix à l'aide d'OpenIPMI-2.0.16, 2.0.17 et 2.0.18, utilisez ces noms se terminant par "0" dans le champ *Capteur IPMI* des éléments de l'agent IPMI. Lorsque votre serveur Zabbix est mis à jour vers une nouvelle distribution Linux, qui utilise OpenIPMI-2.0.19 (ou une version ultérieure), les éléments avec ces capteurs IPMI discrets deviendront "NON SUPPORTE". Vous devrez changer leur nom de *capteur IPMI* (enlevez le '0' à la fin) et attendre un moment avant de les réactiver. #### Notes on handling 'copytruncate' log file rotation `logrt` with the `copytruncate` option assumes that different log files have different records (at least their timestamps are different), therefore MD5 sums of initial blocks (up to the first 512 bytes) will be different. Two files with the same MD5 sums of initial blocks means that one of them is the original, another - a copy. `logrt` with the `copytruncate` option makes effort to correctly process log file copies without reporting duplicates. However, things like producing multiple log file copies with the same timestamp, log file rotation more often than logrt\[\] item update interval, frequent restarting of agent are not recommended. The agent tries to handle all these situations reasonably well, but good results cannot be guaranteed in all circumstances. #### Remarques sur la gestion de 'copytruncate' dans la rotation des fichiers journaux `logrt` avec l'option `copytruncate` suppose que différents fichiers journaux ont des enregistrements différents (au moins leurs horodatages sont différents), donc les sommes MD5 des blocs initiaux (jusqu'à 512 premiers octets) seront différentes. Deux fichiers avec les mêmes sommes MD5 de blocs initiaux signifient que l'un d'eux est l'original, l'autre - une copie. `logrt` avec l'option `copytruncate` s'efforce de traiter correctement les copies de fichiers journaux sans signaler les doublons. Cependant, des choses telles que la production de plusieurs copies de fichiers journaux avec le même horodatage, la rotation du fichier journal plus souvent que l'intervalle de mise à jour de l'élément logrt\[\], le redémarrage fréquent de l'agent ne sont pas recommandés. L'agent essaie de gérer raisonnablement toutes ces situations, mais de bons résultats ne peuvent pas être garantis en toutes circonstances. ### Notes on installation See [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for: - installing the repository - installing server/agent/frontend - creating initial database, importing initial data - configuring database for Zabbix server - configuring PHP for Zabbix frontend - starting server/agent processes - configuring Zabbix frontend If you want to run Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root). Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually. ### Remarques sur l'installation Voir les [instructions d'installation](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) par plate-forme dans la page de téléchargement pour : - installer le référentiel - installer le serveur/l'agent/l'interface - créer la base de données initiale, importer les données initiales - configurer la base de données pour le serveur Zabbix - configurer PHP pour l'interface Zabbix - démarrer les processus serveur/agent - configurer l'interface Zabbix Si vous souhaitez exécuter l'agent Zabbix en tant que root, consultez [Exécuter l'agent en tant que root](/manual/appendix/install/run_agent_as_root). Le processus de service Web Zabbix, qui est utilisé pour [la génération de rapport planifié](/manual/web_interface/frontend_sections/reports/scheduled), nécessite le navigateur Google Chrome. Le navigateur n'est pas inclus dans les packages et doit être installé manuellement. ### Notes on installation See [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for: - installing the repository - installing server/agent/frontend - creating initial database, importing initial data - configuring database for Zabbix server - configuring PHP for Zabbix frontend - starting server/agent processes - configuring Zabbix frontend If you want to run Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root). Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually. ### Notes on installation Voir les [instructions d'installation](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) par plate-forme dans la page de téléchargement pour : - installation du dépôt - installation du serveur/de l'agent/de l'interface - création de la base de données initiale, importation des données initiales - configuration de la base de données pour le serveur Zabbix - configuration de PHP pour l'interface Zabbix - démarrage des processus serveur/agent - configuration de l'interface Zabbix Si vous souhaitez exécuter l'agent Zabbix en tant que root, consultez la page [exécuter l'agent en tant que root](/manual/appendix/install/run_agent_as_root). Le processus de service Web Zabbix, qui est utilisé pour [la génération de rapports planifiés](/manual/web_interface/frontend_sections/reports/scheduled), nécessite le navigateur Google Chrome. Le navigateur n'est pas inclus dans les packages et doit être installé manuellement. ### Notes on installation See the [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=22.04) per platform in the download page for: - installing the repository - installing server/agent/frontend - creating initial database, importing initial data - configuring database for Zabbix server - configuring PHP for Zabbix frontend - starting server/agent processes - configuring Zabbix frontend If you want to run Zabbix agent as root, see [running agent as root](/manual/appendix/install/run_agent_as_root). Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually. ### Notes on installation Voir les [instructions d'installation](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=22.04) par plate-forme dans la page de téléchargement pour : - installation du dépôt - installation du serveur/de l'agent/de l'interface - création de la base de données initiale, importation des données initiales - configuration de la base de données pour le serveur Zabbix - configuration de PHP pour l'interface Zabbix - démarrage des processus serveur/agent - configuration de l'interface Zabbix Si vous souhaitez exécuter l'agent Zabbix en tant que root, consultez la page [exécuter l'agent en tant que root](/manual/appendix/install/run_agent_as_root). Le processus de service Web Zabbix, qui est utilisé pour [la génération de rapports planifiés](/manual/web_interface/frontend_sections/reports/scheduled), nécessite le navigateur Google Chrome. Le navigateur n'est pas inclus dans les packages et doit être installé manuellement. #### Notes on IPMI discrete sensors To find sensors on a host start Zabbix server with **DebugLevel=4** enabled. Wait a few minutes and find sensor discovery records in Zabbix server logfile: $ grep 'Added sensor' zabbix_server.log 8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR' 8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp' 8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH' To decode IPMI sensor types and states, get a copy of IPMI 2.0 specifications at <http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html> (At the time of writing the newest document was <http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf>) The first parameter to start with is "reading\_type". Use "Table 42-1, Event/Reading Type Code Ranges" from the specifications to decode "reading\_type" code. Most of the sensors in our example have "reading\_type:0x1" which means "threshold" sensor. "Table 42-3, Sensor Type Codes" shows that "type:0x1" means temperature sensor, "type:0x2" - voltage sensor, "type:0x4" - Fan etc. Threshold sensors sometimes are called "analog" sensors as they measure continuous parameters like temperature, voltage, revolutions per minute. Another example - a sensor with "reading\_type:0x3". "Table 42-1, Event/Reading Type Code Ranges" says that reading type codes 02h-0Ch mean "Generic Discrete" sensor. Discrete sensors have up to 15 possible states (in other words - up to 15 meaningful bits). For example, for sensor 'CATERR' with "type:0x7" the "Table 42-3, Sensor Type Codes" shows that this type means "Processor" and the meaning of individual bits is: 00h (the least significant bit) - IERR, 01h - Thermal Trip etc. There are few sensors with "reading\_type:0x6f" in our example. For these sensors the "Table 42-1, Event/Reading Type Code Ranges" advises to use "Table 42-3, Sensor Type Codes" for decoding meanings of bits. For example, sensor 'Power Unit Stat' has type "type:0x9" which means "Power Unit". Offset 00h means "PowerOff/Power Down". In other words if the least significant bit is 1, then server is powered off. To test this bit, the **bitand** [function](/manual/appendix/triggers/functions) with mask '1' can be used. The trigger expression could be like bitand(last(/www.example.com/Power Unit Stat,#1),1)=1 to warn about a server power off. #### Notes on IPMI discrete sensors Pour trouver des capteurs sur un hôte, démarrez le serveur Zabbix avec **DebugLevel=4** activé. Attendez quelques minutes et recherchez les enregistrements de détection de capteur dans le fichier de log du serveur Zabbix : $ grep 'Added sensor' zabbix_server.log 8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR' 8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat' 8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin' 8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3' 8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp' 8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH' Pour décoder les types et les états des capteurs IPMI, procurez-vous une copie des spécifications IPMI 2.0 à l' adresse <http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html> (Au moment de la rédaction le document le plus récent était <http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf>) Le premier paramètre avec lequel commencer est "read\_type". Utilisez "Tableau 42-1, Plages de codes de type d'événement/de lecture" dans les spécifications pour décoder le code "read\_type". La plupart des capteurs de notre exemple ont "read\_type:0x1" qui signifie capteur de "seuil". "Le tableau 42-3, Codes de type de capteur" montre que "type:0x1" signifie capteur de température, "type:0x2" - capteur de tension, "type:0x4" - ventilateur etc. Les capteurs de seuil sont parfois appelés "analogiques" car ils mesurent des paramètres continus comme la température, la tension, les révolutions par minute. Un autre exemple - un capteur avec "read\_type:0x3". "Tableau 42-1, Plages de codes de type événement/lecture" indique que les codes de type de lecture 02h-0Ch signifient "Generic Discrete". Les capteurs discrets ont jusqu'à 15 états possibles (en d'autres termes, jusqu'à 15 bits significatifs). Par exemple, pour le capteur 'CATERR' avec "type:0x7", le "Tableau 42-3, Codes de type de capteur" montre que ce type signifie "Processeur" et que la signification des bits individuels est : 00h (le bit le moins significatif) - IERR, 01h - Thermal Trip etc. Il y a peu de capteurs avec "reading\_type:0x6f" dans notre exemple. Pour ces capteurs, le "Tableau 42-1, Plages de codes de type d'événement/lecture" conseille d'utiliser "Tableau 42-3, Codes de type de capteur" pour décoder les significations des bits. Par exemple, le capteur 'Power Unit Stat' a le type "type:0x9" qui signifie "Power Unit". Offset 00h signifie "PowerOff/Power Down". En d'autres termes, si le bit le moins significatif est 1, le serveur est mis hors tension. Pour tester ce bit, la [fonction](/manual/appendix/triggers/functions) **band** avec le masque '1' peut être utilisée. L'expression de déclenchement pourrait être comme · bitand(last(/www.example.com/Power Unit Stat,#1),1)=1 pour avertir d'un serveur éteint. #### Notes on persistent files for log\*\[\] items #### Remarques sur les fichiers persistants pour les éléments log\*\[\] ##### Notes on threshold and discrete sensor simultaneous availability Some IPMI agents provide both a threshold sensor and a discrete sensor under the same name. In Zabbix versions prior to 2.2.8 and 2.4.3, the first provided sensor was chosen. Since versions 2.2.8 and 2.4.3, preference is always given to the threshold sensor. ##### Remarques sur la disponibilité simultanée du capteur de seuil et du capteur discret Certains agents IPMI fournissent à la fois un capteur de seuil et un capteur discret sous le même nom. Dans les versions de Zabbix antérieures à 2.2.8 et 2.4.3, le premier capteur fourni était choisi. Depuis les versions 2.2.8 et 2.4.3, la préférence est toujours donnée au capteur de seuil. ::: notetip Mostly the `maintenance.inc.php` file is located in `/conf` of Zabbix HTML document directory on the web server. However, the location of the directory may differ depending on the operating system and a web server it uses. For example, the location for: - SUSE and RedHat is `/etc/zabbix/web/maintenance.inc.php`. - Debian-based systems is `/usr/share/zabbix/conf/`. See also [Copying PHP files](/manual/installation/install#copying-php-files). ::: |Parameter|Details| |--|--------| |**ZBX\_DENY\_GUI\_ACCESS**|Enable maintenance mode:<br>1 – maintenance mode is enabled, disabled otherwise| |**ZBX\_GUI\_ACCESS\_IP\_RANGE**|Array of IP addresses, which are allowed to connect to frontend (optional).<br>For example:<br>`array('192.168.1.1', '192.168.1.2')`| |**ZBX\_GUI\_ACCESS\_MESSAGE**|A message you can enter to inform users about the maintenance (optional).| ::: notetip La plupart du temps, le fichier `maintenance.inc.php` se trouve dans `/conf` du répertoire de documents HTML de Zabbix sur le serveur Web. Cependant, l'emplacement du répertoire peut différer selon le système d'exploitation et le serveur Web qu'il utilise. Par exemple, l'emplacement pour : - SUSE et RedHat le fichier est `/etc/zabbix/web/maintenance.inc.php`. - Les systèmes basés sur Debian le répertoire est`/usr/share/zabbix/conf/`. Voir aussi [Copier les fichiers PHP](/manual/installation/install#copying-php-files). ::: |Paramètre|Détails| |--|--------| |**ZBX\_DENY\_GUI\_ACCESS**|Activer le mode maintenance :<br>1 – le mode maintenance est activé, sinon désactivé| |**ZBX\_GUI\_ACCESS\_IP\_RANGE**|Tableau d'adresses IP autorisées à se connecter à l'interface (facultatif).<br>Par exemple :<br>`array('192.168.1.1', ' 192.168.1.2')`| |**ZBX\_GUI\_ACCESS\_MESSAGE**|Un message que vous pouvez saisir pour informer les utilisateurs de la maintenance (facultatif).| #### Numeric (float) data type range with PostgreSQL 11 and earlier PostgreSQL 11 and earlier versions only support floating point value range of approximately -1.34E-154 to 1.34E+154. #### Plage de types de données numériques (float) avec PostgreSQL 11 et versions antérieures PostgreSQL 11 et les versions antérieures ne prennent en charge que la plage de valeurs à virgule flottante d\'environ -1,34E-154 à 1,34E+154. #### Numeric representation Windows maintains numeric representations (indexes) for object and performance counter names. Zabbix supports these numeric representations as parameters to the `perf_counter`, `perf_counter_en` item keys and in `PerfCounter`, `PerfCounterEn` configuration parameters. However, it's not recommended to use them unless you can guarantee your numeric indexes map to correct strings on specific hosts. If you need to create portable items that work across different hosts with various localized Windows versions, you can use the `perf_counter_en` key or `PerfCounterEn` configuration parameter which allow to use English names regardless of system locale. To find out the numeric equivalents, run **regedit**, then find *HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*. The registry entry contains information like this: 1 1847 2 System 4 Memory 6 % Processor Time 10 File Read Operations/sec 12 File Write Operations/sec 14 File Control Operations/sec 16 File Read Bytes/sec 18 File Write Bytes/sec .... Here you can find the corresponding numbers for each string part of the performance counter, like in '\\System\\% Processor Time': System → 2 % Processor Time → 6 Then you can use these numbers to represent the path in numbers: \2\6 #### Représentation numérique Windows conserve des représentations numériques (index) pour les noms d'objets et de compteurs de performances. Zabbix prend en charge ces représentations numériques en tant que paramètres des clés d'élément `perf_counter`, `perf_counter_en` et dans les paramètres de configuration `PerfCounter`, `PerfCounterEn`. Cependant, il n'est pas recommandé de les utiliser, sauf si vous pouvez garantir que votre carte d'index numérique corrige les chaînes sur des hôtes spécifiques. Si vous avez besoin de créer des éléments portables qui fonctionnent sur différents hôtes avec différentes versions localisées de Windows, vous pouvez utiliser la clé `perf_counter_en` ou le paramètre de configuration `PerfCounterEn` qui permettent d'utiliser des noms anglais indépendamment des paramètres régionaux du système. Pour connaître les équivalents numériques, exécutez **regedit**, puis recherchez *HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*. L'entrée de registre contient des informations comme celle-ci : 1 1847 2 System 4 Memory 6 % Processor Time 10 File Read Operations/sec 12 File Write Operations/sec 14 File Control Operations/sec 16 File Read Bytes/sec 18 File Write Bytes/sec .... Vous pouvez trouver ici les nombres correspondants pour chaque partie de chaîne du compteur de performances, comme dans '\\System\\% Processor Time' : System → 2 % Processor Time → 6 Ensuite, vous pouvez utiliser ces nombres pour représenter le chemin en chiffres : \2\6 # ODBC template operation Steps to ensure correct operation of templates that collect metrics via [ODBC monitoring](/manual/config/items/itemtypes/odbc_checks): 1\. Make sure that required ODBC driver is installed on Zabbix server or proxy.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to a target host (if the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\ 3. Adjust the values of mandatory macros as needed.\ If a password placed in the macro value contains semicolon (;) it should be wrapped in curly brackets, see [ODBC monitoring](https://www.zabbix.com/documentation/6.0/en/manual/config/items/itemtypes/odbc_checks?hl=ODBC%2Cmonitoring) for details. 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column. ::: notetip This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name). ::: |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[MSSQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mssql_odbc/README.md)|**{$MSSQL.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$MSSQL.PORT}** - the TCP port of Microsoft SQL Server (default: 1433)<br>**{$MSSQL.USER}, {$MSSQL.PASSWORD}** - Microsoft SQL login credentials (default: not set)|Create a Microsoft SQL user for monitoring and grant the user the following permissions: View Server State; View Any Definition (see Microsoft SQL [documentation](https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/grant-a-permission-to-a-principal?view=sql-server-ver15) for details).<br><br>The "Service's TCP port state" item uses {HOST.CONN} and {$MSSQL.PORT} macros to check the availability of the Microsoft SQL instance.| |[MySQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_odbc/README.md)|**{$MYSQL.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$MYSQL.USER}, {$MYSQL.PASSWORD}** - MySQL login credentials; password can be blank (default: not set)|To grant required privileges to MySQL user that will be used for monitoring, run:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br><br>See [MYSQL documentation](https://dev.mysql.com/doc/refman/8.0/en/grant.html) for details.| |[Oracle by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_odbc/README.md)|**{$ORACLE.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$ORACLE.PORT}** - the TCP port of Oracle DB (default: 1521)<br>**{$ORACLE.USER}, {$ORACLE.PASSWORD}** - Oracle login credentials (default: not set)|1\. To create an Oracle user for monitoring, run:<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Grant access to the zabbix_mon user.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon;`<br>`GRANT SELECT ON V_$instance TO zabbix_mon;`<br>`GRANT SELECT ON V_$database TO zabbix_mon;`<br>`GRANT SELECT ON v_$sysmetric TO zabbix_mon;`<br>`GRANT SELECT ON v$recovery_file_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$active_session_history TO zabbix_mon;`<br>`GRANT SELECT ON v$osstat TO zabbix_mon;`<br>`GRANT SELECT ON v$restore_point TO zabbix_mon;`<br>`GRANT SELECT ON v$process TO zabbix_mon;`<br>`GRANT SELECT ON v$datafile TO zabbix_mon;`<br>`GRANT SELECT ON v$pgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$sgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$log TO zabbix_mon;`<br>`GRANT SELECT ON v$archive_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$asm_diskgroup TO zabbix_mon;`<br>`GRANT SELECT ON sys.dba_data_files TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br><br>2. Make sure, that ODBC connects to Oracle with session parameter `NLS_NUMERIC_CHARACTERS= '.,'`<br><br>3. Add a new record to odbc.ini:<br>`[$ORACLE.DSN]`<br>`Driver = Oracle 19 ODBC driver`<br>`Servername = $ORACLE.DSN`<br>`DSN = $ORACLE.DSN`<br><br>4. Check the connection via isql:<br>`isql $TNS_NAME $DB_USER $DB_PASSWORD`<br><br>5. Configure Zabbix server or Zabbix proxy for Oracle ENV Usage. Edit or add a new file: */etc/sysconfig/zabbix-server*, or for the proxy: */etc/sysconfig/zabbix-proxy*. Then add the following lines to the file:<br>`export ORACLE_HOME=/usr/lib/oracle/19.6/client64`<br>`export PATH=$PATH:$ORACLE_HOME/bin`<br>`export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib64:/usr/lib:$ORACLE_HOME/bin`<br>`export TNS_ADMIN=$ORACLE_HOME/network/admin`<br><br>6. Restart Zabbix server or proxy.| # Fonctionnement du modèle ODBC Étapes pour garantir le bon fonctionnement des modèles qui collectent des métriques via la [surveillance ODBC](/manual/config/items/itemtypes/odbc_checks): 1\. Assurez-vous que le pilote ODBC requis est installé sur le serveur ou le proxy Zabbix.\ 2. [Liez](/manual/config/templates/linking#linking_a_template) le modèle à un hôte cible (si le modèle n'est pas disponible dans votre installation Zabbix, vous devrez peut-être d'abord importer le fichier .xml du modèle - voir la section des [Modèles prêts à l'emploi](/manual/config/templates_out_of_the_box) pour les connaitre les instructions).\ 3. Ajustez les valeurs des macros obligatoires selon vos besoins.\ Si un mot de passe placé dans la valeur de la macro contient un point-virgule (;), il doit être entouré d'accolades, voir la [Surveillance ODBC](https://www.zabbix.com/documentation/6.0/en/manual/config/items/itemtypes/odbc_checks?hl=ODBC%2Cmonitoring) pour plus de détails. 4. Configurez l'instance surveillée pour autoriser le partage de données avec Zabbix - voir les instructions dans la colonne *Étapes supplémentaires/commentaires*. ::: notetip Cette page ne contient qu'un ensemble minimal de macros et d'étapes de configuration nécessaires au bon fonctionnement du modèle. Une description détaillée d'un modèle, y compris la liste complète des macros, des éléments et des déclencheurs, est disponible dans le fichier Readme.md du modèle (accessible en cliquant sur un nom de modèle). ::: |Modèle|Macros obligatoires|Étapes/commentaires supplémentaires| |--------|----------------|-------------------------| |[MSSQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mssql_odbc/README.md)|**{\$MSSQL.DSN}** - le nom de la source de données système (par défaut : \<Put your DSN here\>)<br>**{\$MSSQL.PORT}** - le port TCP de Microsoft SQL Server (par défaut : 1433)<br>**{\$MSSQL.USER}, {\$MSSQL.PASSWORD}** - Identifiants de connexion Microsoft SQL (par défaut : non défini)|Créez un utilisateur Microsoft SQL pour la surveillance et accordez-lui les autorisations suivantes : Afficher l'état du serveur ; Afficher n'importe quelle définition (voir la [documentation](https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/grant-a-permission-to-a-principal?view=sql-server-ver15) Microsoft SQL pour plus de détails).<br><br>L'élément "Etat du port TCP du service" utilise les macros {HOST.CONN} et {$MSSQL.PORT} pour vérifier la disponibilité de l'instance Microsoft SQL.| |[MySQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_odbc/README.md)|**{\$MYSQL.DSN}** - le nom de la source de données système (par défaut : \<Put your DSN here\>)<br>**{\$MYSQL.USER}, {\$MYSQL.PASSWORD}** - Identifiants de connexion MySQL ; le mot de passe peut être vide (par défaut : non défini)|Pour accorder les privilèges requis à l'utilisateur MySQL qui sera utilisé pour la surveillance, exécutez :<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br><br>Voir la documentation [MYSQL](https://dev.mysql.com/doc/refman/8.0/en/grant.html) pour plus de details.| |[Oracle by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_odbc/README.md)|**{\$ORACLE.DSN}** - le nom de la source de données système (par défaut : \<Put your DSN here\>)<br>**{\$ORACLE.PORT}** - le port TCP de la base de données Oracle (par défaut : 1521)<br>**{\$ORACLE.USER}, {\$ORACLE.PASSWORD}** - Identifiants de connexion Oracle (par défaut : non définis)|1\. Pour créer un utilisateur Oracle pour la surveillance, exécutez :<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Accorder l'accès à l'utilisateur zabbix_mon.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon;`<br>`GRANT SELECT ON V_$instance TO zabbix_mon;`<br>`GRANT SELECT ON V_$database TO zabbix_mon;`<br>`GRANT SELECT ON v_$sysmetric TO zabbix_mon;`<br>`GRANT SELECT ON v$recovery_file_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$active_session_history TO zabbix_mon;`<br>`GRANT SELECT ON v$osstat TO zabbix_mon;`<br>`GRANT SELECT ON v$restore_point TO zabbix_mon;`<br>`GRANT SELECT ON v$process TO zabbix_mon;`<br>`GRANT SELECT ON v$datafile TO zabbix_mon;`<br>`GRANT SELECT ON v$pgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$sgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$log TO zabbix_mon;`<br>`GRANT SELECT ON v$archive_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$asm_diskgroup TO zabbix_mon;`<br>`GRANT SELECT ON sys.dba_data_files TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br><br>2. Assurez-vous qu'ODBC se connecte à Oracle avec le paramètre de session `NLS_NUMERIC_CHARACTERS= '.,'`<br><br>3. Ajoutez un nouvel enregistrement dans odbc.ini :<br>`[$ORACLE.DSN]`<br>`Driver = Oracle 19 ODBC driver`<br>`Servername = $ORACLE.DSN`<br>`DSN = $ORACLE.DSN`<br><br>4. Vérifiez la connexion via isql :<br>`isql $TNS_NAME $DB_USER $DB_PASSWORD`<br><br>5. Configurez le serveur Zabbix ou le proxy Zabbix pour Oracle ENV Usage. Modifiez ou ajoutez un nouveau fichier : */etc/sysconfig/zabbix-server*, ou pour le proxy : */etc/sysconfig/zabbix-proxy*. Ajoutez ensuite les lignes suivantes au fichier :<br>`export ORACLE_HOME=/usr/lib/oracle/19.6/client64`<br>`export PATH=$PATH:$ORACLE_HOME/bin`<br>`export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib64:/usr/lib:$ORACLE_HOME/bin`<br>`export TNS_ADMIN=$ORACLE_HOME/network/admin`<br><br>6. Redémarrez le serveur ou le proxy Zabbix.| #### OK events An OK event closes the related problem event(s) and may be created by 3 components: - triggers - based on 'OK event generation' and 'OK event closes' settings; - event correlation - task manager – when an event is [manually closed](/manual/config/events/manual_close) #### Événements OK Un événement OK ferme le ou les événement(s) problème lié(s) et peut être créé par 3 composants : - les déclencheurs - basés sur les paramètres 'Génération d’événement OK' et 'Un événement OK ferme' ; - la corrélation d'événements - le gestionnaire de tâches - lorsqu'un événement est [fermé manuellement](/fr/manual/config/events/manual_close) #### Older XML protocol ::: noteclassic Zabbix will take up to 16 MB of XML Base64-encoded data, but a single decoded value should be no longer than 64 KB otherwise it will be truncated to 64 KB while decoding. ::: #### Ancien protocole XML ::: noteclassic Zabbix prendra jusqu'à 16 Mo de données codées en XML Base64, mais une seule valeur décodée ne devrait pas dépasser 64 Ko, sinon elle sera tronquée à 64 Ko lors du décodage. ::: #### One side connects with certificate but other side accepts only PSK or vice versa In any log (with *GnuTLS*): failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\ -21 Could not negotiate a supported cipher suite. In any log (with *OpenSSL* 1.0.2c): failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\ file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\ TLS write fatal alert "handshake failure" #### Un côté se connecte avec le certificat mais l'autre côté n'accepte que PSK ou vice versa Dans n'importe quel journal (avec *GnuTLS*) : failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\ -21 Could not negotiate a supported cipher suite. Dans n'importe quel journal (avec *OpenSSL* 1.0.2c) : failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\ file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\ TLS write fatal alert "handshake failure" #### One side connects with PSK but other side uses LibreSSL or has been compiled without encryption support LibreSSL does not support PSK. In connecting-side log: ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success In accepting-side log: ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in In Zabbix frontend: Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success #### Un côté se connecte à PSK mais un autre utilise LibreSSL ou a été compilé sans support de chiffrement LibreSSL ne supporte pas PSK. Dans le journal côté connexion : ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success Dans journal de l'autre côté : ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in Dans l'interface Web Zabbix : Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success #### One side connects with PSK but other side uses OpenSSL with PSK support disabled In connecting-side log: ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure" In accepting-side log: ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure" #### Un côté se connecte à PSK mais un autre utilise OpenSSL avec le support PSK désactivé Dans le journal côté connexion : ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure" Dans le journal de l'autre côté : ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure" ##### On Linux 2.4: (Sensor readings are obtained from /proc/sys/dev/sensors directory) - **device** - device name (if <mode> is used, it is a regular expression); - **sensor** - sensor name (if <mode> is used, it is a regular expression); - **mode** - possible values: avg, max, min (if this parameter is omitted, device and sensor are treated verbatim). Example key: sensor\[w83781d-i2c-0-2d,temp1\] Prior to Zabbix 1.8.4, the sensor\[temp1\] format was used. ##### Sur Linux 2.4 : (Les lectures des capteurs sont obtenues à partir du répertoire /proc/sys/dev/sensors) - **device** - nom du périphérique (si <mode> est utilisé, c'est une expression régulière) ; - **sensor** - nom du capteur (si <mode> est utilisé, c'est une expression régulière) ; - **mode** - valeurs possibles : avg, max, min (si ce paramètre est omis, le périphérique et le capteur sont traités textuellement). Exemple de clé : sensor\[w83781d-i2c-0-2d,temp1\] Avant Zabbix 1.8.4, le format sensor\[temp1\] était utilisé. ##### On Linux 2.6+: (Sensor readings are obtained from /sys/class/hwmon directory) - **device** - device name (non regular expression). The device name could be the actual name of the device (e.g 0000:00:18.3) or the name acquired using sensors program (e.g. k8temp-pci-00c3). It is up to the user to choose which name to use; - **sensor** - sensor name (non regular expression); - **mode** - possible values: avg, max, min (if this parameter is omitted, device and sensor are treated verbatim). Example key: sensor\[k8temp-pci-00c3,temp,max\] or sensor\[0000:00:18.3,temp1\] sensor\[smsc47b397-isa-0880,in,avg\] or sensor\[smsc47b397.2176,in1\] ##### Sur Linux 2.6+ : (Les lectures des capteurs sont obtenues à partir du répertoire /sys/class/hwmon) - **device** - nom du périphérique (pas une expression régulière). Le nom du périphérique peut être le nom réel du périphérique (ex. 0000:00:18.3) ou le nom acquis en utilisant le programme de sensors (ex. k8temp-pci-00c3). Il appartient à l'utilisateur de choisir le nom à utiliser ; - **sensor** - nom du capteur (pas une expression régulière) ; - **mode** - valeurs possibles : avg, max, min (si ce paramètre est omis, le périphérique et le capteur sont traités textuellement). Exemples de clés : sensor\[k8temp-pci-00c3,temp, max\] ou sensor\[0000:00:18.3,temp1\] sensor\[smsc47b397-isa-0880,in, avg\] ou sensor\[smsc47b397.2176,in1\] ### Open file descriptor limit increase for Zabbix agent 2 The systemd service file shipped in Zabbix agent 2 packages now declares the open file descriptor limit of 8196. Previously, the system default limit of 1024 has been used. The new limit is sufficient for the default Zabbix agent 2 configuration. If you have a non-standard agent 2 configuration, for example, use additional plugins or extended features, this limit may need to be manually increased further. In this case, adjust the `LimitNOFILE` parameter in the systemd unit file. ### Augmentation de la limite des descripteurs de fichiers ouverts pour l'agent Zabbix 2 Le fichier de service systemd fourni dans les paquets de l'agent Zabbix 2 déclare désormais la limite de descripteur de fichier ouvert de 8196. Auparavant, la limite par défaut du système de 1024 était utilisée. La nouvelle limite est suffisante pour la configuration par défaut de l'agent Zabbix 2. Si vous avez une configuration d'agent 2 non standard, par exemple, utilisation de plug-ins supplémentaires ou de fonctionnalités étendues, cette limite devra peut-être être augmentée manuellement. Dans ce cas, ajustez le paramètre `LimitNOFILE` dans le fichier d'unité systemd. ### Open file descriptor limit increase for Zabbix agent 2 The systemd service file shipped in Zabbix agent 2 packages now declares the open file descriptor limit of 8196. Previously, the system default limit of 1024 has been used. The new limit is sufficient for the default Zabbix agent 2 configuration. If you have a non-standard agent 2 configuration, for example, use additional plugins or extended features, this limit may need to be manually increased further. In this case, adjust the `LimitNOFILE` parameter in the systemd unit file. ### Augmentation de la limite des descripteurs de fichiers ouverts pour l'agent Zabbix 2 Le fichier de service systemd fourni dans les paquets de l'agent Zabbix 2 déclare désormais la limite de descripteur de fichier ouvert de 8196. Auparavant, la limite par défaut du système de 1024 était utilisée. La nouvelle limite est suffisante pour la configuration par défaut de l'agent Zabbix 2. Si vous avez une configuration d'agent 2 non standard, par exemple, utilisation de plug-ins supplémentaires ou de fonctionnalités étendues, cette limite devra peut-être être augmentée manuellement. Dans ce cas, ajustez le paramètre `LimitNOFILE` dans le fichier d'unité systemd. ### OpenSSL 3.0 support OpenSSL 3.0.x is now supported. Note that this change does not affect frontend encryption (which uses its own openssl-php package) and Java gateway JMX encrypted connections to monitoring targets (which uses its own Java encrypted libraries). ### Prise en charge d'OpenSSL 3.0 OpenSSL 3.0.x est désormais pris en charge. Notez que ce changement n'affecte pas le cryptage de l'interface (qui utilise son propre package openssl-php) et les connexions cryptées de la passerelle Java JMX pour la surveillance des cibles (qui utilisent leurs propres bibliothèques cryptées Java). #### OpenSSL used with CRLs and for some CA in the certificate chain its CRL is not included in `TLSCRLFile` In TLS server log in case of *OpenSSL* peer: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \ file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \ TLS write fatal alert "unknown CA" In TLS server log in case of *GnuTLS* peer: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \ file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\ block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin #### OpenSSL utilisé avec les CRL et pour certaines autorités de certification dans la chaîne de certificats, sa CRL n'est pas incluse dans `TLSCRLFile` Dans le journal du serveur TLS en cas de peer *OpenSSL* : failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \ file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \ TLS write fatal alert "unknown CA" Dans le journal du serveur TLS en cas de peer *GnuTLS* : failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \ file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\ block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin #### Operating system - Use latest (stable!) version of OS - Exclude unnecessary functionality from kernel - Tune kernel parameters #### OS - Utilisez la dernière version (stable !) d'un OS - Exclure les fonctionnalités inutiles du noyau - Ajuster les paramètres du noyau #### Operation type: notify all involved |Parameter|Description| |--|--------| |*Custom message*|If selected, a custom message can be defined.| |*Subject*|Subject of the custom message. The subject may contain macros.| |*Message*|The custom message. The message may contain macros.| #### Type d'opération : notifier toutes les personnes concernées |Paramètre|Description| |--|--------| |*Message personnalisé*|Si sélectionné, un message personnalisé peut être défini.| |*Sujet*|Objet du message personnalisé. Le sujet peut contenir des macros.| |*Message*|Le message personnalisé. Le message peut contenir des macros.| #### Operation type: [remote command](/manual/config/notifications/action/operation/remote_command) |Parameter|Description| |--|--------| |*Target list*|Select targets to execute the command on:<br>**Current host** - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.<br>**Host** - select host(s) to execute the command on.<br>**Host group** - select host group(s) to execute the command on. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups.<br>A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).<br>The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.<br>Note that for global scripts, the target selection also depends on the *Host group* setting in global script [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script).| #### Type d'opération : [commande à distance](/manual/config/notifications/action/operation/remote_command) |Paramètre|Description| |--|--------| |*Liste des cibles*|Sélectionnez les cibles sur lesquelles exécuter la commande :<br>**Hôte actuel** : la commande est exécutée sur l'hôte du déclencheur à l'origine de l'événement problématique. Cette option ne fonctionnera pas s'il y a plusieurs hôtes dans le déclencheur.<br>**Hôte** - sélectionnez le ou les hôtes sur lesquels exécuter la commande.<br>**Groupe d'hôtes** - sélectionnez le ou les groupes d'hôtes sur lesquels exécuter la commande. La spécification d'un groupe d'hôtes parent sélectionne implicitement tous les groupes d'hôtes imbriqués. Ainsi, la commande à distance sera également exécutée sur les hôtes des groupes imbriqués.<br>Une commande sur un hôte n'est exécutée qu'une seule fois, même si l'hôte correspond plus d'une fois (par exemple, à partir de plusieurs groupes d'hôtes ; individuellement et à partir d'un groupe d'hôtes).<br>La liste des cibles n'a aucun sens si la commande est exécutée sur le serveur Zabbix. La sélection de plusieurs cibles dans ce cas entraîne uniquement l'exécution de la commande sur le serveur plusieurs fois.<br>Notez que pour les scripts globaux, la sélection de la cible dépend également du paramètre *Groupe d'hôtes* dans la [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script) globale du script.| #### Operation type: [send message](/manual/config/notifications/action/operation/message) |Parameter|Description| |--|--------| |*Send to user groups*|Click on *Add* to select user groups to send the recovery message to.<br>The user group must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |*Send to users*|Click on *Add* to select users to send the recovery message to.<br>The user must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |*Send only to*|Send default recovery message to all defined media types or a selected one only.| |*Custom message*|If selected, a custom message can be defined.| |*Subject*|Subject of the custom message. The subject may contain macros.| |*Message*|The custom message. The message may contain macros.| #### Type d'opération : [envoyer un message](/manual/config/notifications/action/operation/message) |Paramètre|Description| |--|--------| |*Envoyer aux groupes d'utilisateurs*|Cliquez sur *Ajouter* pour sélectionner les groupes d'utilisateurs auxquels envoyer le message de récupération.<br>Le groupe d'utilisateurs doit avoir au moins les [autorisations](/manual/config/users_and_usergroups/permissions) de "lecture" sur l'hôte afin d'être notifié.| |*Envoyer aux utilisateurs*|Cliquez sur *Ajouter* pour sélectionner les utilisateurs auxquels envoyer le message de récupération.<br>L'utilisateur doit avoir au moins les [autorisations](/manual/config/users_and_usergroups/permissions) de "lecture" sur l'hôte afin d'être notifié.| |*Envoyer uniquement à*|Envoyer le message de récupération par défaut à tous les types de médias définis ou à un seul sélectionné.| |*Message personnalisé*|Si sélectionné, un message personnalisé peut être défini.| |*Objet*|Objet du message personnalisé. Le sujet peut contenir des macros.| |*Message*|Le message personnalisé. Le message peut contenir des macros.| ### Optimized API queries API database queries, created when searching through names in the *hosts* and *items* tables, have been optimized and will now be processed more efficiently. As a result of this change, deterministic triggers need to be created during an upgrade. On MySQL and MariaDB, this requires `GLOBAL log_bin_trust_function_creators = 1` to be set if binary logging is enabled and there is no superuser privileges and `log_bin_trust_function_creators = 1` is not set in MySQL configuration file. To set the variable using MySQL console, run: mysql> SET GLOBAL log_bin_trust_function_creators = 1; Once the upgrade has been successfully completed, `log_bin_trust_function_creators` can be disabled: mysql> SET GLOBAL log_bin_trust_function_creators = 0; Triggers are also created for PostgreSQL and Oracle database. ### Requêtes API optimisées Les requêtes de base de données API, créées lors de la recherche de noms dans les tables *hosts* et *items*, ont été optimisées et seront désormais traitées plus efficacement. Suite à cette modification, des déclencheurs déterministes doivent être créés lors d'une mise à niveau. Sur MySQL et MariaDB, cela nécessite que `GLOBAL log_bin_trust_function_creators = 1` soit défini si la journalisation binaire est activée et qu'il n'y a pas de privilèges de superutilisateur et que `log_bin_trust_function_creators = 1` n'est pas défini dans le fichier de configuration MySQL. Pour définir la variable à l'aide de la console MySQL, exécutez : mysql> SET GLOBAL log_bin_trust_function_creators = 1 ; Une fois la mise à niveau terminée avec succès, `log_bin_trust_function_creators` peut être désactivé : mysql> SET GLOBAL log_bin_trust_function_creators = 0 ; Des déclencheurs sont également créés pour les bases de données PostgreSQL et Oracle. ### Optimized API queries API database queries, used when searching through names in *hosts* and *items* tables, have been optimized and will now be processed more efficiently. ### Requêtes API optimisées Les requêtes de base de données API, utilisées lors de la recherche de noms dans les tables *hosts* et *items*, ont été optimisées et seront désormais traitées plus efficacement. ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix agent in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Utiliser le *config-file* alternatif au lieu de celui par défaut. **-f**, **--foreground** Exécuter l'agent Zabbix au premier plan. **-R**, **--runtime-control** *runtime-option* Exécuter des fonctions administratives selon *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-f**, **--foreground** Run Zabbix proxy in foreground. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Utiliser le *config-file* alternatif au lieu de celui par défaut. **-f**, **--foreground** Exécuter le proxy Zabbix au premier plan. **-R**, **--runtime-control** *runtime-option* Exécuter des fonctions administratives selon *runtime-option*. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Utiliser le *config-file* alternatif au lieu de celui par défaut. **-h**, **--help** Afficher cette aide et quitter. **-V**, **--version** Afficher les informations de version et quitter. [ ]{#lbAF} ## OPTIONS **-c**, **--config** *config-file* Use the alternate *config-file* instead of the default one. **-R**, **--runtime-control** *runtime-option* Perform administrative functions according to *runtime-option*. ## OPTIONS **-c**, **--config** *config-file* Utiliser le *config-file* alternatif au lieu de celui par défaut. **-R**, **--runtime-control** *runtime-option* Exécuter des fonctions administratives selon *runtime-option*. #### Options |Parameter|Description| |---------|-----------| |-V --version|Print the plugin version and license information.| |-h --help|Print help information (shorthand).| #### Options |Paramètre|Description| |---------|-----------| |-V --version|Affiche la version du plug-in et les informations de licence.| |-h --help|Affiche les informations d'aide (sténographie).| ## OPTIONS **-s**, **--host** *host-name-or-IP* Specify host name or IP address of a host. **-p**, **--port** *port-number* Specify port number of agent running on the host. Default is 10050. **-I**, **--source-address** *IP-address* Specify source IP address. **-t**, **--timeout** *seconds* Specify timeout. Valid range: 1-30 seconds (default: 30) **-k**, **--key** *item-key* Specify key of item to retrieve value for. **--tls-connect** *value* How to connect to agent. Values: [ ]{#lbAF} ## OPTIONS **-s**, **--host** *host-name-or-IP* Spécifier le nom d'hôte ou l'adresse IP d'un hôte. **-p**, **--port** *port-number* Spécifier le numéro de port de l'agent en cours d'exécution sur l'hôte. La valeur par défaut est 10050. **-I**, **--source-address** *IP-address* Spécifier l'adresse IP source. **-t**, **--timeout** *seconds* Spécifier le délai d'attente. Plage valide : 1-30 secondes (par défaut : 30) **-k**, **--key** *item-key* Spécifier la clé de l'élément pour lequel récupérer la valeur. **--tls-connect** *value* Comment se connecter à l'agent. Valeurs: [ ]{#lbAF} ## OPTIONS **-s**, **--script** *script-file* Specify the file name of the script to execute. If '-' is specified as file name, the script will be read from stdin. **-p**, **--param** *input-param* Specify the input parameter. **-i**, **--input** *input-file* Specify the file name of the input parameter. If '-' is specified as file name, the input will be read from stdin. **-l**, **--loglevel** *log-level* Specify the log level. **-t**, **--timeout** *timeout* Specify the timeout in seconds. Valid range: 1\-60 seconds (default: 10) **-h**, **--help** Display this help and exit. **-V**, **--version** Output version information and exit. [ ]{#lbAF} ## OPTIONS **-s**, **--script** *script-file* Spécifier le nom de fichier du script à exécuter. Si '-' est spécifié comme nom de fichier, le script sera lu depuis stdin. **-p**, **--param** *input-param* Spécifier le paramètre d'entrée. **-i**, **--input** *input-file* Spécifier le nom de fichier du paramètre d'entrée. Si '-' est spécifié comme nom de fichier, l'entrée sera lue à partir de stdin. **-l**, **--loglevel** *log-level* Spécifier le niveau de journalisation. **-t**, **--timeout** *timeout* Spécifier le délai d'attente en secondes. Plage valide : 1\-60 secondes (par défault: 10)¶ **-h**, **--help** Afficher cette aide et quitter. **-V**, **--version** Afficher les informations de version et quitter. [ ]{#lbAF} #### Oracle Instructions for creating and configuring Oracle database are provided in a separate [section](/manual/appendix/install/oracle). #### Oracle Les instructions de création et de configuration d'Oracle sont fournies dans une [section](/manual/appendix/install/timescaledb) distincte. ### Oracle |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>,<diskgroup>\]|<|<|<| |Automatic Storage Management (ASM) disk groups statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**diskgroup** - name of the ASM disk group to query.| | |oracle.diskgroups.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |List of ASM disk groups. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.archive.info\[connString,<user>,<password>,<service>,<destination>\]|<|<|<| |Archive logs statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**destination** - name of the destination to query.| | |oracle.cdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Container Databases (CDBs) information.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**database** - name of the database to query.| | |oracle.custom.query\[connString,<user>,<password>,<service>,queryName,<args...>\]|<|<|<| |Result of a custom query.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**queryName** — name of a custom query (must be equal to a name of an sql file without an extension).<br>**args...** — one or several comma-separated arguments to pass to a query.| | |oracle.datafiles.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Data files statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.db.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |List of databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Fast Recovery Area (FRA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.instance.info\[connString,<user>,<password>,<service>\]|<|<|<| |Instance statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.pdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Pluggable Databases (PDBs) information.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**database** - name of the database to query.| | |oracle.pdb.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |List of PDBs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Program Global Area (PGA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.ping\[connString,<user>,<password>,<service>\]|<|<|<| |Tests whether a connection to Oracle can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.proc.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Processes statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.redolog.info\[connString,<user>,<password>,<service>\]|<|<|<| |Log file information from the control file.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |System Global Area (SGA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.sessions.stats\[connString,<user>,<password>,<service>,<lockMaxTime>\]|<|<|<| |Sessions statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**lockMaxTime** - maximum session lock duration in seconds to count the session as a prolongedly locked. Default: 600 seconds.| | |oracle.sys.metrics\[connString,<user>,<password>,<service>,<duration>\]|<|<|<| |A set of system metric values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**duration** - capturing interval (in seconds) of system metric values. Possible values: *60* — long duration (default), *15* — short duration.| | |oracle.sys.params\[connString,<user>,<password>,<service>\]|<|<|<| |A set of system parameter values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.ts.stats\[connString,<user>,<password>,<service>,<tablespace>,<type>\]|<|<|<| |Tablespaces statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**tablespace** - name of the tablespace to query. Default (if left empty and `type` is set):<br>- "TEMP" (if `type` is set to "TEMPORARY");<br>- "USERS" (if `type` is set to "PERMANENT").<br>**type** - type of the tablespace to query. Default (if `tablespace` is set): "PERMANENT".| | |oracle.ts.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |oracle.user.info\[connString,<user>,<password>,<service>,<username>\]|<|<|<| |List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**username** - a username, for which the information is needed. Lowercase usernames are not supported. Default: current user.| | ### Oracle |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques des groupes de disques Automatic Storage Management (ASM).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**diskgroup** - nom du groupe de disques ASM à interroger.| | |oracle.diskgroups.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |Liste des groupes de disques ASM. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.archive.info\[connString,<user>,<password>,<service>,<destination>\]|<|<|<| |Archiver les statistiques des journaux.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**destination** - nom de la destination à interroger.| | |oracle.cdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Informations sur les bases de données de conteneurs (CDB).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**database** - nom de la base de données à interroger.| | |oracle.custom.query\[connString,<user>,<password>,<service>, queryName, <args...>\]|<|<|<| |Résultat d'une requête personnalisée.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**queryName** — nom d'une requête personnalisée (doit être égal au nom d'un fichier sql sans extension).<br>**args...** — un ou plusieurs arguments séparés par des virgules à passer à un requête.| | |oracle.datafiles.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques des fichiers de données.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.db.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |Liste des bases de données. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques de la zone de récupération rapide (FRA).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.instance.info\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques d'instance.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.pdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Informations sur les bases de données enfichables (PDB).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**database** - nom de la base de données à interroger.| | |oracle.pdb.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |Liste des PDBs. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques de la zone globale du programme (PGA).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.ping\[connString,<user>,<password>,<service>\]|<|<|<| |Teste si une connexion à Oracle peut être établie.|0 - la connexion est interrompue (en cas d'erreur, y compris les problèmes d'authentification et de configuration)<br>1 - la connexion est réussie.|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.proc.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques des processus.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.redolog.info\[connString,<user>,<password>,<service>\]|<|<|<| |Informations sur le fichier journal à partir du fichier de contrôle.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Statistiques de la zone globale du système (SGA).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.sessions.stats\[connString,<user>,<password>,<service>,<lockMaxTime>\]|<|<|<| |Statistiques des sessions.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**lockMaxTime** - Durée maximale de verrouillage de session en secondes pour compter la session comme verrouillée de manière prolongée. Par défaut : 600 secondes.| | |oracle.sys.metrics\[connString,<user>,<password>,<service>,<duration>\]|<|<|<| |Un ensemble de valeurs de métriques système.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**duration** - Intervalle de capture (en secondes) des valeurs de métrique système. Valeurs possibles : *60* — longue durée (par défaut), *15* — courte durée.| | |oracle.sys.params\[connString,<user>,<password>,<service>\]|<|<|<| |Un ensemble de valeurs de paramètres système.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.ts.stats\[connString,<user>,<password>,<service>,<tablespace>,<type>\]|<|<|<| |Statistiques des tablespaces.|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**tablespace** - nom du tablespace à interroger. Par défaut (si laissé vide et `type` est défini) :<br>- "TEMP" (si `type` est défini sur "TEMPORARY");<br>- "USERS" (si `type` est défini sur "PERMANENT").<br>**type** - type de l'espace de table à interroger. Par défaut (si `tablespace` est défini) : "PERMANENT".| | |oracle.ts.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |Listes des tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.| | |oracle.user.info\[connString,<user>,<password>,<service>,<username>\]|<|<|<| |Liste des utilisateurs. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON|**connString** - URI ou nom de session.<br>**user, password** - Identifiants de connexion Oracle.<br>**service** - Nom du service Oracle.<br>**username** - Nom d'utilisateur, pour lequel les informations sont nécessaires. Les noms d'utilisateur en minuscules ne sont pas pris en charge. Par défaut : utilisateur actuel.| | #### Ordering shapes and lines To bring one shape in front of the other (or vice versa) click on the shape with the right mouse button bringing up the map shape menu.  #### Ordonner des formes et des lignes Pour amener une forme devant l'autre (ou vice versa), cliquez sur la forme avec le bouton droit de la souris pour faire apparaître le menu des formes de la carte.  ### Other changes and bug fixes ### Autres modifications et corrections de bogues #### Other details - An Admin level user with *Read-write* access to a host will not be able to link/unlink templates, if he has no access to the *Templates* group. With *Read* access to *Templates* group he will be able to link/unlink templates to the host, however, will not see any templates in the template list and will not be able to operate with templates in other places. - An Admin level user with *Read* access to a host will not see the host in the configuration section host list; however, the host triggers will be accessible in IT service configuration. - Any non-Super Admin user (including 'guest') can see network maps as long as the map is empty or has only images. When hosts, host groups or triggers are added to the map, permissions are respected. - Zabbix server will not send notifications to users defined as action operation recipients if access to the concerned host is explicitly "denied". #### Autres détails - Un utilisateur de niveau Admin avec un accès *Lecture-écriture* à un hôte ne pourra pas lier/dissocier des modèles, s'il n'a pas accès au groupe *Modèles*. Avec l'accès *Lecture* au groupe *Modèles*, il pourra lier/dissocier des modèles à l'hôte, cependant, il ne verra aucun modèle dans la liste des modèles et ne pourra pas opérer avec des modèles à d'autres endroits. - Un utilisateur de niveau Admin avec un accès *Lecture* à un hôte ne verra pas l'hôte dans la liste des hôtes de la section de configuration ; cependant, les déclencheurs de l'hôte seront accessibles dans la configuration du service informatique. - Tout utilisateur non Super Admin (y compris 'guest') peut voir les cartes du réseau tant que la carte est vide ou ne contient que des images. Lorsque des hôtes, des groupes d'hôtes ou des déclencheurs sont ajoutés à la carte, les autorisations sont respectées. - Le serveur Zabbix n'enverra pas de notifications aux utilisateurs définis comme destinataires de l'opération d'action si l'accès à l'hôte concerné est explicitement "refusé". ##### Other expressions Function parameters may contain other expressions, as in the following syntax: min(min(/host/key,1h),min(/host2/key2,1h)*10) Note that other expressions may not be used, if the function references item history. For example, the following syntax is not allowed: ~~`min(/host/key,#5*10)`~~ ##### Autres expressions Les paramètres de fonction peuvent contenir d'autres expressions, comme dans la syntaxe suivante : min(min(/host/key,1h),min(/host2/key2,1h)*10) Notez que d'autres expressions ne peuvent pas être utilisées si la fonction fait référence à l'historique de l'élément. Par exemple, la syntaxe suivante n'est pas autorisée : ~~`min(/host/key,#5*10)`~~ **Other hardware** A serial communication port and a serial GSM modem are required for using SMS notification support in Zabbix. USB-to-serial converter will also work. **Autre materiel** Un port série et un modem GSM sont requis pour l'utilisation des notifications par SMS dans Zabbix. Un convertisseur USB vers série fonctionnera également. #### Overview Aggregate calculations are a [calculated item](/manual/config/items/itemtypes/calculated) type allowing to collect information from several items by Zabbix server and then calculate an aggregate, depending on the aggregate function used. Only unsigned integer and float values (type of information) are supported for aggregate calculation items. Aggregate calculations do not require any agent running on the host being monitored. #### Aperçu Les calculs agrégés sont de type [élément calculé](/manual/config/items/itemtypes/calculated) et permettent de collecter les informations de plusieurs éléments par le serveur Zabbix puis de calculer un agrégat, selon la fonction d'agrégat utilisée. Seules les valeurs entières non signées et flottantes (type d'informations) sont prises en charge pour les éléments de calcul agrégés. Les calculs agrégés ne nécessitent aucun agent en cours d'exécution sur l'hôte surveillé. #### Overview All users in Zabbix access the Zabbix application through the web-based frontend. Each user is assigned a unique login name and a password. All user passwords are encrypted and stored in the Zabbix database. Users cannot use their user id and password to log directly into the UNIX server unless they have also been set up accordingly to UNIX. Communication between the web server and the user browser can be protected using SSL. With a flexible [user permission schema](/manual/config/users_and_usergroups/permissions) you can restrict and differentiate rights to: - access administrative Zabbix frontend functions - perform certain actions in the frontend - access monitored hosts in hostgroups - use specific API methods #### Aperçu Tous les utilisateurs de Zabbix accèdent à l'application Zabbix via l'interface Web. Chaque utilisateur se voit attribuer un nom de connexion unique et un mot de passe. Tous les mots de passe des utilisateurs sont cryptés et stockés dans la base de données Zabbix. Les utilisateurs ne peuvent pas utiliser leur ID utilisateur et leur mot de passe pour se connecter directement au serveur UNIX à moins qu'ils n'aient également été configurés conformément à UNIX. La communication entre le serveur Web et le navigateur de l'utilisateur peut être protégée par SSL. Avec un [schéma d'autorisation utilisateur](/manual/config/users_and_usergroups/permissions) flexible, vous pouvez restreindre et différencier les droits pour : - accéder aux fonctions d'administration de l'interface Zabbix - effectuer certaines actions dans l'interface Web - accéder aux hôtes surveillés dans les groupes d'hôtes - utiliser des méthodes API spécifiques #### Overview An optional context can be used in [user macros](/manual/config/macros/user_macros), allowing to override the default value with a context-specific one. The context is appended to the macro name; the syntax depends on whether the context is a static text value: {$MACRO:"static text"} or a regular expression: {$MACRO:regex:"regular expression"} Note that a macro with regular expression context can only be defined in user macro configuration. If the `regex:` prefix is used elsewhere as user macro context, like in a trigger expression, it will be treated as static context. Context quoting is optional (see also [important notes](#important_notes)). Macro context examples: |Example|Description| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|User macro without context.| |`{$LOW_SPACE_LIMIT:/tmp}`|User macro with context (static string).| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|User macro with context (regular expression). Same as `{$LOW_SPACE_LIMIT:/tmp}`.| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|User macro with context (regular expression). Matches all strings prefixed with /var/log/.| #### Aperçu Un contexte facultatif peut être utilisé dans les [macros utilisateur](/manual/config/macros/user_macros), permettant de remplacer la valeur par défaut par une valeur spécifique au contexte. Le contexte est ajouté au nom de la macro ; la syntaxe varie selon que le contexte est une valeur de texte statique : {$MACRO:"static text"} ou une expression régulière : {$MACRO:regex:"regular expression"} Notez qu'une macro avec un contexte d'expression régulière ne peut être définie que dans la configuration de la macro utilisateur. Si le préfixe `regex:` est utilisé ailleurs comme contexte de macro utilisateur, comme dans une expression de déclencheur, il sera traité comme un contexte statique. La citation contextuelle est facultative (voir aussi [notes importantes](#important_notes)). Exemples de contexte de macro : |Exemple|Description| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|Macro utilisateur sans contexte.| |`{$LOW_SPACE_LIMIT:/tmp}`|Macro utilisateur avec contexte (chaîne statique).| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|Macro utilisateur avec contexte (expression régulière). Identique à `{$LOW_SPACE_LIMIT:/tmp}`.| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|Macro utilisateur avec contexte (expression régulière). Correspond à toutes les chaînes préfixées par /var/log/.| #### Overview As an alternative to setting up manually or reusing an existing server for Zabbix, users may [download](http://www.zabbix.com/download_appliance) a Zabbix appliance or a Zabbix appliance installation CD image. Zabbix appliance and installation CD versions are based on AlmaLinux 8 (x86\_64). Zabbix appliance installation CD can be used for instant deployment of Zabbix server (MySQL). ::: noteimportant You can use this Appliance to evaluate Zabbix. The Appliance is not intended for serious production use. ::: #### Aperçu Au lieu de configurer manuellement ou de réutiliser un serveur existant pour Zabbix, les utilisateurs peuvent [télécharger](http://www.zabbix.com/download_appliance) une appliance Zabbix ou une image du CD d'installation de l'appliance Zabbix. Les versions de l'appliance Zabbix et du CD d'installation sont basées sur AlmaLinux 8 (x86\_64). Le CD d'installation de l'appliance Zabbix peut être utilisé pour un déploiement instantané du serveur Zabbix (MySQL). ::: noteimportant Vous pouvez utiliser cette appliance pour évaluer Zabbix. L'appliance n'est pas destinée à une utilisation en production. ::: #### Overview Assuming that we have configured some items and triggers and now are getting some events happening as a result of triggers changing state, it is time to consider some actions. To begin with, we would not want to stare at the triggers or events list all the time. It would be much better to receive notification if something significant (such as a problem) has happened. Also, when problems occur, we would like to see that all the people concerned are informed. That is why sending notifications is one of the primary actions offered by Zabbix. Who and when should be notified upon a certain event can be defined. To be able to send and receive notifications from Zabbix you have to: - [define some media](/manual/config/notifications/media) - [configure an action](/manual/config/notifications/action) that sends a message to one of the defined media Actions consist of *conditions* and *operations*. Basically, when conditions are met, operations are carried out. The two principal operations are sending a message (notification) and executing a remote command. For discovery and autoregistration created events, some additional operations are available. Those include adding or removing a host, linking a template etc. #### Aperçu En supposant que nous ayons configuré certains éléments et déclencheurs et que certains événements se produisent maintenant à la suite du changement d'état des déclencheurs, il est temps d'envisager certaines actions. Pour commencer, nous ne voudrions pas regarder les déclencheurs ou la liste des événements tout le temps. Il serait préférable de recevoir une notification si quelque chose d'important (comme un problème) s'est produit. Aussi, lorsque des problèmes surviennent, nous aimerions que toutes les personnes concernées soient informées. C'est pourquoi l'envoi de notifications est l'une des principales actions proposées par Zabbix. Qui et quand doit être notifié lors d'un certain événement peut être défini. Pour pouvoir envoyer et recevoir des notifications de Zabbix, vous devez : - [définir certains médias](/manual/config/notifications/media) - [configurer une action](/manual/config/notifications/action) qui envoie un message à l'un des médias définis Les actions consistent en *conditions* et *opérations*. Fondamentalement, lorsque les conditions sont remplies, les opérations sont effectuées. Les deux opérations principales sont l'envoi d'un message (notification) et l'exécution d'une commande à distance. Pour les événements créés par découverte et enregistrement automatique, certaines opérations supplémentaires sont disponibles. Ceux-ci incluent l'ajout ou la suppression d'un hôte, la liaison d'un modèle, etc. #### Overview A template is a set of entities that can be conveniently applied to multiple hosts. The entities may be: - items - triggers - graphs - dashboards - low-level discovery rules - web scenarios As many hosts in real life are identical or fairly similar so it naturally follows that the set of entities (items, triggers, graphs,...) you have created for one host, may be useful for many. Of course, you could copy them to each new host, but that would be a lot of manual work. Instead, with templates you can copy them to one template and then apply the template to as many hosts as needed. When a template is linked to a host, all entities (items, triggers, graphs,...) of the template are added to the host. Templates are assigned to each individual host directly (and not to a host group). Templates are often used to group entities for particular services or applications (like Apache, MySQL, PostgreSQL, Postfix...) and then applied to hosts running those services. Another benefit of using templates is when something has to be changed for all the hosts. Changing something on the template level once will propagate the change to all the linked hosts. Thus, the use of templates is an excellent way of reducing one's workload and streamlining the Zabbix configuration. Proceed to [creating and configuring a template](/manual/config/templates/template). #### Aperçu Un modèle est un ensemble d'entités qui peuvent être facilement appliquées à plusieurs hôtes. Les entités peuvent être : - éléments - déclencheurs - graphiques - tableaux de bord - règles de découverte de bas niveau - scénarios Web Comme de nombreux hôtes dans la vie réelle sont identiques ou assez similaires, il s'ensuit naturellement que l'ensemble d'entités (éléments, déclencheurs, graphiques, ...) que vous avez créé pour un hôte peut être utile pour plusieurs. Bien sûr, vous pouvez les copier sur chaque nouvel hôte, mais cela demanderait beaucoup de travail manuel. Au lieu de cela, avec les modèles, vous pouvez les copier dans un modèle, puis appliquer le modèle à autant d'hôtes que nécessaire. Lorsqu'un modèle est lié à un hôte, toutes les entités (éléments, déclencheurs, graphiques,...) du modèle sont ajoutées à l'hôte. Les modèles sont attribués directement à chaque hôte individuel (et non à un groupe d'hôtes). Les modèles sont souvent utilisés pour regrouper des entités pour des services ou des applications particuliers (comme Apache, MySQL, PostgreSQL, Postfix...), puis appliqués aux hôtes exécutant ces services. Un autre avantage de l'utilisation de modèles est lorsque quelque chose doit être changé pour tous les hôtes. Changer quelque chose au niveau du modèle une fois propagera le changement à tous les hôtes liés. Ainsi, l'utilisation de modèles est un excellent moyen de réduire sa charge de travail et de rationaliser la configuration de Zabbix. Passez à [la création et la configuration d'un modèle](/manual/config/templates/template). #### Overview A vertical menu in a sidebar provides access to various Zabbix frontend sections. The menu is dark blue in the default theme. {width="600"} #### Aperçu Un menu vertical dans une barre latérale permet d'accéder à diverses sections de l'interface Zabbix. Le menu est bleu foncé dans le thème par défaut. {width="600"} #### Overview By default, Zabbix provides a number of predefined themes. You may follow the step-by-step procedure provided here in order to create your own. Feel free to share the result of your work with Zabbix community if you created something nice. #### Aperçu Par défaut, Zabbix fournit un certain nombre de thèmes prédéfinis. Vous pouvez suivre la procédure étape par étape fournie ici afin de créer la vôtre. N'hésitez pas à partager le résultat de votre travail avec la communauté Zabbix si vous avez créé quelque chose de sympa. ##### Overview by item type In this screen it is easy to locate if the problem is related to one or several item types. {width="600"} Each line contains an item type. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively. ##### Aperçu par type d'élément Dans cet écran, il est facile de localiser si le problème est lié à un ou plusieurs types d'éléments. {width="600"} Chaque ligne contient un type d'élément. Chaque colonne indique le nombre d'éléments en attente - en attente de 5-10 secondes/10-30 secondes/30-60 secondes/1-5 minutes/5-10 minutes ou plus de 10 minutes respectivement. ##### Overview by proxy In this screen it is easy to locate if the problem is related to one of the proxies or the server. {width="600"} Each line contains a proxy, with the server last in the list. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively. ##### Aperçu par proxy Dans cet écran, il est facile de localiser si le problème est lié à l'un des proxies ou au serveur. {width="600"} Chaque ligne contient un proxy, avec le serveur en dernier dans la liste. Chaque colonne indique le nombre d'éléments en attente - en attente de 5-10 secondes/10-30 secondes/30-60 secondes/1-5 minutes/5-10 minutes ou plus de 10 minutes respectivement. #### Overview Change of trigger status is the most frequent and most important source of events. Each time the trigger changes its state, an event is generated. The event contains details of the trigger state's change - when it happened and what the new state is. Two types of events are created by triggers - Problem and OK. #### Aperçu Le changement de statut d'un déclencheur est la source d'événements la plus fréquente et la plus importante. Chaque fois que le déclencheur change d'état, un événement est généré. L'événement contient les détails de la modification de l'état du déclencheur - quand cela s'est produit et quel est le nouvel état. Deux types d'événements sont créés par des déclencheurs - Problème et OK. #### Overview Checking for a new item value in Zabbix is a cyclic process that is based on configured update intervals. While for many items the update intervals are quite short, there are others (including low-level discovery rules) for which the update intervals are quite long, so in real-life situations there may be a need to check for a new value quicker - to pick up changes in discoverable resources, for example. To accommodate such a necessity, it is possible to reschedule a passive check and retrieve a new value immediately. This functionality is supported for **passive** checks only. The following item types are supported: - Zabbix agent (passive) - SNMPv1/v2/v3 agent - IPMI agent - Simple check - Zabbix internal - External check - Database monitor - JMX agent - SSH agent - Telnet - Calculated - HTTP agent - Script ::: noteimportant The check must be present in the configuration cache in order to get executed; for more information see [CacheUpdateFrequency](/manual/appendix/config/zabbix_server). Before executing the check, the configuration cache is **not** updated, thus very recent changes to item/discovery rule configuration will not be picked up. Therefore, it is also not possible to check for a new value for an item/rule that is being created or has been created just now; use the *Test* option while configuring an item for that. ::: #### Aperçu La recherche d'une nouvelle valeur d'élément dans Zabbix est un processus cyclique basé sur des intervalles de mise à jour configurés. Alors que pour de nombreux éléments, les intervalles de mise à jour sont assez courts, il y en a d'autres (y compris les règles de découverte de bas niveau) pour lesquels les intervalles de mise à jour sont assez longs, donc dans des situations réelles, il peut être nécessaire de rechercher une nouvelle valeur plus rapidement - pour détecter les changements dans les ressources détectables, par exemple. Pour répondre à une telle nécessité, il est possible de reprogrammer une vérification passive et de récupérer immédiatement une nouvelle valeur. Cette fonctionnalité n'est prise en charge que pour les vérifications **passives**. Les types d'éléments suivants sont pris en charge : - Agent Zabbix (passif) - Agent SNMPv1/v2/v3 - Agent IPMI - Vérification simple - Interne Zabbix - Vérification externe - Database monitor - Agent JMX - Agent SSH - Telnet - Calculé - Agent HTTP - Script ::: noteimportant La vérification doit être présente dans le cache de configuration pour être exécutée ; pour plus d'informations, voir [CacheUpdateFrequency](/manual/appendix/config/zabbix_server). Avant d'exécuter la vérification, le cache de configuration n'est **pas** mis à jour, ainsi les modifications très récentes apportées à la configuration de l'élément/règle de découverte ne seront pas récupérées. Par conséquent, il n'est pas non plus possible de rechercher une nouvelle valeur pour un élément/une règle en cours de création ou qui vient d'être créée ; utilisez l'option *Test* lors de la configuration d'un élément pour cela. ::: #### Overview Configuring a map in Zabbix requires that you first create a map by defining its general parameters and then you start filling the actual map with elements and their links. You can populate the map with elements that are a host, a host group, a trigger, an image, or another map. Icons are used to represent map elements. You can define the information that will be displayed with the icons and set that recent problems are displayed in a special way. You can link the icons and define information to be displayed on the links. You can add custom URLs to be accessible by clicking on the icons. Thus you may link a host icon to host properties or a map icon to another map. Maps are managed in *Monitoring* → *[Maps](/manual/web_interface/frontend_sections/monitoring/maps)*, where they can be configured, managed and viewed. In the monitoring view, you can click on the icons and take advantage of the links to some scripts and URLs. Network maps are based on vector graphics (SVG) since Zabbix 3.4. #### Aperçu La configuration d'une carte dans Zabbix nécessite que vous créiez d'abord une carte en définissant ses paramètres généraux, puis que vous commenciez à remplir la carte réelle avec des éléments et leurs liens. Vous pouvez remplir la carte avec des éléments qui sont un hôte, un groupe d'hôtes, un déclencheur, une image ou une autre carte. Les icônes sont utilisées pour représenter les éléments de la carte. Vous pouvez définir les informations qui seront affichées avec les icônes et définir que les problèmes récents sont affichés d'une manière particulière. Vous pouvez lier les icônes et définir les informations à afficher sur les liens. Vous pouvez ajouter des URL personnalisées accessibles en cliquant sur les icônes. Ainsi, vous pouvez lier une icône d'hôte à des propriétés d'hôte ou une icône de carte à une autre carte. Les cartes sont gérées dans *Surveillance* → *[Cartes](/manual/web_interface/frontend_sections/monitoring/maps)*, où elles peuvent être configurées, gérées et visualisées. Dans la vue de surveillance, vous pouvez cliquer sur les icônes et profiter des liens vers certains scripts et URL. Les cartes réseau sont basées sur des graphiques vectoriels (SVG) depuis Zabbix 3.4. #### Overview Configuring a template requires that you first create a template by defining its general parameters and then you add entities (items, triggers, graphs, etc.) to it. #### Aperçu La configuration d'un modèle nécessite que vous créiez d'abord un modèle en définissant ses paramètres généraux puis vous ajouterez des entités (éléments, déclencheurs, graphiques, etc.). #### Overview Custom graphs, as the name suggests, offer customization capabilities. While simple graphs are good for viewing data of a single item, they do not offer configuration capabilities. Thus, if you want to change graph style or the way lines are displayed or compare several items, for example, incoming and outgoing traffic in a single graph, you need a custom graph. Custom graphs are configured manually. They can be created for a host or several hosts or for a single template. #### Aperçu Les graphiques personnalisés, comme leur nom l'indique, offrent des capacités de personnalisation. Alors que les graphiques simples sont utiles pour visualiser les données d'un seul élément, ils n'offrent pas de capacités de configuration. Ainsi, si vous souhaitez modifier le style de graphique ou la façon dont les lignes sont affichées ou comparer plusieurs éléments, par exemple, le trafic entrant et sortant dans un seul graphique, vous avez besoin d'un graphique personnalisé. Les graphiques personnalisés sont configurés manuellement. Ils peuvent être créés pour un ou plusieurs hôtes ou pour un seul modèle. #### Overview Data provided in Prometheus line format can be used for low-level discovery. See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for details how Prometheus data querying is implemented in Zabbix. #### Aperçu Les données fournies au format de ligne Prometheus peuvent être utilisées pour la découverte de bas niveau. Voir les [vérifications Prometheus](/manual/config/items/itemtypes/prometheus) pour plus de détails sur la façon dont l'interrogation des données Prometheus est implémentée dans Zabbix. #### Overview Debug mode may be used to diagnose performance problems with frontend pages. #### Aperçu Le mode Debug peut être utilisé pour diagnostiquer les problèmes de performance de l'interface web. #### Overview Depending on user role permissions, the *User settings* section may contain the following pages: - *User profile* - for customizing certain Zabbix frontend features; - *API tokens* - for managing API tokens assigned to the current user. The list of available pages appears upon pressing on the  user icon near the bottom of the Zabbix menu (not available for a guest user). It is also possible to switch between pages by using a title dropdown in the top left corner. | | | |---|---| |{width="300"}|{width="300"}| |Third-level menu.|Title dropdown.| #### Aperçu Selon les autorisations du rôle utilisateur, la section *Paramètres utilisateur* peut contenir les pages suivantes : - *Profil utilisateur* - pour personnaliser certaines fonctionnalités de l'interface Zabbix ; - *Jetons API* - pour gérer les jetons API attribués à l'utilisateur actuel. La liste des pages disponibles apparaît en appuyant sur l'icône utilisateur  en bas du menu Zabbix (non disponible pour un utilisateur invité). Il est également possible de passer d'une page à l'autre en utilisant une liste déroulante de titres dans le coin supérieur gauche. | | | |---|---| |{width="300"}|{width="300"}| |Menu de troisième niveau.|Liste déroulante du titre.| #### Overview Each pre-shared key (PSK) in Zabbix actually is a pair of: - non-secret PSK identity string, - secret PSK string value. PSK identity string is a non-empty UTF-8 string. For example, "PSK ID 001 Zabbix agentd". It is a unique name by which this specific PSK is referred to by Zabbix components. Do not put sensitive information in PSK identity string - it is transmitted over the network unencrypted. PSK value is a hard to guess string of hexadecimal digits, for example, "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9". #### Aperçu Chaque clé pré-partagée (PSK) de Zabbix est en fait une paire de : - chaîne d'identité PSK non secrète, - valeur de chaîne PSK secrète. La chaîne d'identité PSK est une chaîne UTF-8 non vide. Par exemple, "PSK ID 001 Zabbix agentd". C'est un nom unique par lequel ce composant PSK spécifique est désigné par les composants Zabbix. Ne placez pas d'informations sensibles dans la chaîne d'identité PSK - elles sont transmises non cryptées sur le réseau. La valeur PSK est une chaîne de caractères hexadécimaux difficile à deviner, par exemple "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9". #### Overview Event correlation allows to correlate problem events to their resolution in a manner that is very precise and flexible. Event correlation can be defined: - [on trigger level](/manual/config/event_correlation/trigger) - one trigger may be used to relate separate problems to their solution - [globally](/manual/config/event_correlation/global) - problems can be correlated to their solution from a different trigger/polling method using global correlation rules #### Aperçu La corrélation d'événements permet de corréler les événements problématiques à leur résolution de manière très précise et flexible. La corrélation des événements peut être définie : - [Au niveau du déclencheur](/fr/manual/config/event_correlation/trigger) - un déclencheur peut être utilisé pour relier des problèmes distincts à leur solution - [Globalement](/fr/manual/config/event_correlation/global) - les problèmes peuvent être corrélés à leur solution à partir d'une autre méthode de déclenchement ou d'interrogation à l'aide de règles de corrélation globales #### Overview For an easy access to Zabbix from anywhere and from any platform, the web-based interface is provided. ::: noteclassic If using more than one frontend instance make sure that the locales and libraries (LDAP, SAML etc.) are installed and configured identically for all frontends. ::: #### Aperçu Pour un accès facile à Zabbix depuis n'importe où et depuis n'importe quelle plate-forme, une interface Web est fournie. ::: noteclassic Si vous utilisez plus d'une instance frontale, assurez-vous que les paramètres régionaux et les bibliothèques (LDAP, SAML, etc.) sont installés et configurés de manière identique pour tous les frontends. ::: #### Overview Geomap widget displays hosts as markers on a geographical map using open-source JavaScript interactive maps library Leaflet. ::: noteclassic Zabbix offers multiple predefined map tile service providers and an option to add a custom tile service provider or even host tiles themselves (configurable in the *Administration → General → Geographical maps* [menu section](/manual/web_interface/frontend_sections/administration/general#geographical_maps)). ::: #### Aperçu Le widget Geocarte affiche les hôtes sous forme de marqueurs sur une carte géographique à l'aide de la bibliothèque de cartes interactives JavaScript open source Leaflet. ::: noteclassic Zabbix propose plusieurs fournisseurs de services de tuiles de carte prédéfinis et une option pour ajouter un fournisseur de services de tuiles personnalisé ou même héberger les tuiles elles-mêmes (configurable dans la section *Administration → Général → Cartes géographiques* [menu section](/manual/web_interface/frontend_sections/administration/general#geographical_maps)) ::: #### Overview Global event correlation allows to reach out over all metrics monitored by Zabbix and create correlations. It is possible to correlate events created by completely different triggers and apply the same operations to them all. By creating intelligent correlation rules it is actually possible to save yourself from thousands of repetitive notifications and focus on root causes of a problem! Global event correlation is a powerful mechanism, which allows you to untie yourself from one-trigger based problem and resolution logic. So far, a single problem event was created by one trigger and we were dependent on that same trigger for the problem resolution. We could not resolve a problem created by one trigger with another trigger. But with event correlation based on event tagging, we can. For example, a log trigger may report application problems, while a polling trigger may report the application to be up and running. Taking advantage of event tags you can tag the log trigger as *Status: Down* while tag the polling trigger as *Status: Up*. Then, in a global correlation rule you can relate these triggers and assign an appropriate operation to this correlation such as closing the old events. In another use, global correlation can identify similar triggers and apply the same operation to them. What if we could get only one problem report per network port problem? No need to report them all. That is also possible with global event correlation. Global event correlation is configured in **correlation rules**. A correlation rule defines how the new problem events are paired with existing problem events and what to do in case of a match (close the new event, close matched old events by generating corresponding OK events). If a problem is closed by global correlation, it is reported in the *Info* column of *Monitoring* → *Problems*. Configuring global correlation rules is available to Super Admin level users only. ::: noteimportant Event correlation must be configured very carefully, as it can negatively affect event processing performance or, if misconfigured, close more events than was intended (in the worst case even all problem events could be closed). ::: To configure global correlation **safely**, observe the following important tips: - Reduce the correlation scope. Always set a unique tag for the new event that is paired with old events and use the *New event tag* correlation condition; - Add a condition based on the old event when using the *Close old event* operation (or else all existing problems could be closed); - Avoid using common tag names that may end up being used by different correlation configurations; - Keep the number of correlation rules limited to the ones you really need. See also: [known issues](/manual/installation/known_issues#global_event_correlation). #### Aperçu La corrélation globale des événements permet d'atteindre toutes les métriques surveillées par Zabbix et de créer des corrélations. Il est possible de corréler des événements créés par des déclencheurs complètement différents et de leur appliquer les mêmes opérations à tous. En créant des règles de corrélation intelligentes, il est en fait possible de s'épargner des milliers de notifications répétitives et de se concentrer sur les causes profondes d'un problème ! La corrélation globale des événements est un mécanisme puissant qui vous permet de vous détacher d'un problème basé sur un déclencheur et d'une logique de résolution. Jusqu'à présent, un seul événement de problème était créé par un déclencheur et nous dépendions de ce même déclencheur pour la résolution du problème. Nous ne pouvions pas résoudre un problème créé par un déclencheur avec un autre déclencheur. Mais avec la corrélation d'événements basée sur le balisage d'événements, c'est possible. Par exemple, un déclencheur de journal peut signaler des problèmes d'application, tandis qu'un déclencheur d'interrogation peut signaler que l'application est opérationnelle. En tirant parti des tags d'événement, vous pouvez tagger le déclencheur de journal en tant que *Status : Down* tout en étiquetant le déclencheur d'interrogation en tant que *Status : Up*. Ensuite, dans une règle de corrélation globale, vous pouvez relier ces déclencheurs et affecter une opération appropriée à cette corrélation, telle que la fermeture des anciens événements. Dans une autre utilisation, la corrélation globale peut identifier des déclencheurs similaires et leur appliquer la même opération. Et si nous pouvions obtenir un seul rapport de problème par problème de port réseau ? Inutile de tous les déclarer. Cela est également possible avec la corrélation globale des événements. La corrélation globale des événements est configurée dans les **règles de corrélation**. Une règle de corrélation définit la manière dont les nouveaux événements problématiques sont appariés avec les événements problématiques existants et ce qu'il faut faire en cas de correspondance (fermer le nouvel événement, fermer les anciens événements correspondants en générant des événements OK correspondants). Si un problème est clos par corrélation globale, il est signalé dans la colonne *Info* de *Surveillance* → *Problèmes*. La configuration des règles de corrélation globales est disponible uniquement pour les utilisateurs de niveau super administrateur. ::: noteimportant La corrélation d'événements doit être configurée très soigneusement, car elle peut affecter négativement les performances de traitement des événements ou, si elle est mal configurée, fermer plus d'événements que prévu (dans le pire des cas, même tous les événements problématiques pourraient être fermés). ::: Pour configurer la corrélation globale **en toute sécurité**, suivez les conseils importants suivants : - Réduisez la portée de la corrélation. Définissez toujours une balise unique pour le nouvel événement associé aux anciens événements et utilisez la condition de corrélation *Nouvelle balise d'événement* ; - Ajoutez une condition basée sur l'ancien événement lors de l'utilisation de l'opération *Fermer l'ancien événement* (sinon tous les problèmes existants pourraient être fermés) ; - Évitez d'utiliser des noms de tag communs susceptibles d'être utilisés par différentes configurations de corrélation ; - Limitez le nombre de règles de corrélation à celles dont vous avez vraiment besoin. Voir aussi : [problèmes connus](/manual/installation/known_issues#global_event_correlation). #### Overview Global notifications are a way of displaying issues that are currently happening right on the screen you're at in Zabbix frontend. Without global notifications, working in some other location than *Problems* or the *Dashboard* would not show any information regarding issues that are currently happening. Global notifications will display this information regardless of where you are. Global notifications involve both showing a message and [playing a sound](sound). ::: noteimportant The auto play of sounds may be disabled in recent browser versions by default. In this case, you need to change this setting manually. ::: #### Aperçu Les notifications globales sont un moyen d’afficher les problèmes qui se produisent actuellement directement sur l’écran dans lequel vous vous trouvez dans l’interface Zabbix. Sans notifications globales, travailler dans des emplacements autres que *Problèmes* ou les *Tableau de bord* ne montrerait aucune information concernant les problèmes en cours. Les notifications globales afficheront ces informations quel que soit l'endroit où vous vous trouvez. Les notifications globales impliquent à la fois l'affichage d'un message et [jouer un son](sound). #### Overview Having to use some large numbers, for example '86400' to represent the number of seconds in one day, is both difficult and error-prone. This is why you can use some appropriate unit symbols (or suffixes) to simplify Zabbix trigger expressions and item keys. Instead of '86400' for the number of seconds you can simply enter '1d'. Suffixes function as multipliers. #### Aperçu Devoir utiliser des nombres élevés, par exemple '86400' pour représenter le nombre de secondes dans un jour, est à la fois difficile et source d'erreurs. C'est pourquoi vous pouvez utiliser des symboles d'unités appropriés (ou des suffixes) pour simplifier les expressions de déclencheur Zabbix et les clés d'élément. Au lieu de '86400' pour le nombre de secondes, vous pouvez simplement entrer '1d'. Les suffixes fonctionnent comme des multiplicateurs. ### Overview High availability (HA) is typically required in critical infrastructures that can afford virtually no downtime. So for any service that may fail there must be a failover option in place to take over should the current service fail. Zabbix offers a **native** high-availability solution that is easy to set up and does not require any previous HA expertise. Native Zabbix HA may be useful for an extra layer of protection against software/hardware failures of Zabbix server or to have less downtime due to maintenance. In the Zabbix high availability mode multiple Zabbix servers are run as nodes in a cluster. While one Zabbix server in the cluster is active, others are on standby, ready to take over if necessary.  Switching to Zabbix HA is non-committal. You may switch back to standalone operation at any point. See also: [Implementation details](#implementation-details) ### Aperçu La haute disponibilité (HA) est généralement requise dans les infrastructures critiques qui ne peuvent se permettre pratiquement aucun temps d'arrêt. Ainsi, pour tout service susceptible d'être en erreur, une option de basculement doit être en place pour prendre le relais en cas d'échec du service actuel. Zabbix propose une solution haute disponibilité **native** facile à configurer et ne nécessitant aucune expertise préalable en HA. Zabbix HA natif peut être utile pour une couche supplémentaire de protection contre les pannes logicielles/matérielles du serveur Zabbix ou pour avoir moins de temps d'arrêt en raison de la maintenance. En mode haute disponibilité Zabbix, plusieurs serveurs Zabbix sont exécutés en tant que nœuds dans un cluster. Pendant qu'un serveur Zabbix du cluster est actif, d'autres sont en veille, prêts à prendre le relais si nécessaire.  Le passage à Zabbix HA est sans engagement. Vous pouvez revenir à un fonctionnement autonome à tout moment. Voir aussi : [Détails de la mise en œuvre](#implementation-details) #### Overview History and trends are the two ways of storing collected data in Zabbix. Whereas history keeps each collected value, trends keep averaged information on hourly basis and therefore are less resource-hungry. #### Aperçu L'historique et les tendances sont les deux manières de stocker les données collectées dans Zabbix. Alors que l'historique conserve chaque valeur collectée, les tendances conservent des informations moyennes sur une base horaire et sont donc moins gourmandes en ressources. #### Overview Host dashboards look similar to [global dashboards](/manual/web_interface/frontend_sections/monitoring/dashboard), however, host dashboards display data about the host only. Host dashboards have no owner. Host dashboards are configured on the [template](/manual/config/templates/template#adding_dashboards) level and then are generated for a host, once the template is linked to the host. Widgets of host dashboards can only be copied to host dashboards of the same template. Widgets from global dashboards cannot be copied onto host dashboards. Host dashboards *cannot* be configured or directly accessed in the *Monitoring* → *[Dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard)* section, which is reserved for global dashboards. The ways to access host dashboards are listed below in this section. {width="600"} When viewing host dashboards you may switch between the configured dashboards using the dropdown in the upper right corner. To switch to *Monitoring→Hosts* section, click *All hosts* navigation link below the dashboard name in the upper left corner. Widgets of the host dashboards cannot be edited. Note that host dashboards used to be host screens before Zabbix 5.2. When importing an older template containing screens, the screen import will be ignored. #### Aperçu Les tableaux de bord d'hôte ressemblent aux [tableaux de bord globaux](/manual/web_interface/frontend_sections/monitoring/dashboard), cependant, les tableaux de bord d'hôte affichent uniquement des données sur l'hôte. Les tableaux de bord d'hôte n'ont pas de propriétaire. Les tableaux de bord d'hôte sont configurés au niveau du [modèle](/manual/config/templates/template#adding_dashboards) puis sont générés pour un hôte, une fois le modèle lié à l'hôte. Les widgets des tableaux de bord hôtes ne peuvent être copiés que dans les tableaux de bord hôtes du même modèle. Les widgets des tableaux de bord globaux ne peuvent pas être copiés sur les tableaux de bord hôtes. Les tableaux de bord hôtes *ne peuvent pas* être configurés ou directement accessibles dans la section *Surveillance* → *[Tableaux de bord](/manual/web_interface/frontend_sections/monitoring/dashboard)*, qui est réservée aux tableaux de bord globaux. Les moyens d'accéder aux tableaux de bord de l'hôte sont répertoriés ci-dessous dans cette section. {width="600"} Lors de l'affichage des tableaux de bord de l'hôte, vous pouvez basculer entre les tableaux de bord configurés à l'aide de la liste déroulante dans le coin supérieur droit. Pour passer à la section *Surveillance→Hôtes*, cliquez sur le lien de navigation *Tous les hôtes* sous le nom du tableau de bord dans le coin supérieur gauche. Les widgets des tableaux de bord hôtes ne peuvent pas être modifiés. Notez que les tableaux de bord hôtes étaient des écrans hôtes avant Zabbix 5.2. Lors de l'importation d'un ancien modèle contenant des écrans, l'importation d'écran sera ignorée. #### Overview Hosts are [exported](/manual/xml_export_import) with many related objects and object relations. Host export contains: - linked host groups - host data - template linkage - host group linkage - host interfaces - directly linked items - directly linked triggers - directly linked graphs - directly linked discovery rules with all prototypes - directly linked web scenarios - host macros - host inventory data - value maps #### Aperçu Les hôtes sont [exportés](/manual/xml_export_import) avec de nombreux objets et relations d'objets associés. L'exportation d'hôte contient : - les groupes d'hôtes liés - les données de l'hôte - les liens vers les modèles - les liens avec les groupes d'hôtes - les interfaces hôtes - les éléments directement liés - les déclencheurs directement liés - les graphiques directement liés - les règles de découverte directement liées à tous les prototypes - les scénarios Web directement liés - les macros d'hôte - les données d'inventaire d'hôte - les tables de correspondance de valeurs #### Overview If [installed](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation) from Debian/Ubuntu packages, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java). #### Aperçu Si elle est [installée](/fr/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation) depuis les packages Debian/Ubuntu, les informations suivantes vous aideront à configurer la [Passerelle Java](/fr/manual/concepts/java) de Zabbix. #### Overview If [installed](/manual/installation/install_from_packages/rhel#java_gateway_installation) from RHEL packages, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java). #### Aperçu Si elles sont [installées](/manual/installation/install_from_packages/rhel#installation-de-la-passerelle-java) depuis les paquets RHEL, les informations suivantes vous aideront à configurer la [Passerelle Java](/manual/concepts/java) de Zabbix. #### Overview If [installed](/manual/installation/install_from_packages/rhel#java_gateway_installation) from RHEL packages, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java). #### Aperçu Si elle est [installée](/fr/manual/installation/install_from_packages/rhel#java_gateway_installation) depuis les packages RHEL, les informations suivantes vous aideront à configurer la [Passerelle Java](/fr/manual/concepts/java) de Zabbix. #### Overview If [installed](/manual/installation/install#installing_java_gateway) from sources, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java). #### Aperçu Si elle est [installée](/fr/manual/installation/install#installation_de_la_passerelle_java) depuis les sources, les informations suivantes vous aideront à configurer la [Passerelle Java](/fr/manual/concepts/java) de Zabbix. #### Overview If you are not satisfied with existing media types for sending alerts there is an alternative way to do that. You can create a script that will handle the notification your way. Alert scripts are executed on Zabbix server. These scripts are located in the directory defined in the server [configuration file](/manual/appendix/config/zabbix_server) **AlertScriptsPath** variable. Here is an example alert script: ``` {.bash} #!/bin/bash to=$1 subject=$2 body=$3 cat <<EOF | mail -s "$subject" "$to" $body EOF ``` ::: noteimportant Starting from version 3.4 Zabbix checks for the exit code of the executed commands and scripts. Any exit code which is different from **0** is considered as a [command execution](/manual/appendix/command_execution) error. In such case Zabbix will try to repeat failed execution. ::: Environment variables are not preserved or created for the script, so they should be handled explicitly. #### Aperçu Si vous n'êtes pas satisfait des types de médias existants pour l'envoi d'alertes, il existe une autre façon de le faire. Vous pouvez créer un script qui gérera la notification à votre façon. Les scripts d'alerte sont exécutés sur le serveur Zabbix. Ces scripts sont situés dans le répertoire défini dans la variable **AlertScriptsPath** du [fichier de configuration](/manual/appendix/config/zabbix_server) serveur. Voici un exemple de script d'alerte : ``` {.bash} #!/bin/bash to=$1 subject=$2 body=$3 cat <<EOF | mail -s "$subject" "$to" $body EOF ``` ::: noteimportant À partir de la version 3.4, Zabbix vérifie le code de sortie des commandes et des scripts exécutés. Tout code de sortie différent de **0** est considéré comme une erreur d'[exécution de commande](/manual/appendix/command_execution). Dans ce cas, Zabbix essaiera de répéter l'exécution en échec. ::: Les variables d'environnement ne sont pas conservées ou créées pour le script, elles doivent donc être gérées explicitement. #### Overview If you have a network to look after, you may want to have an overview of your infrastructure somewhere. For that purpose, you can create maps in Zabbix - of networks and of anything you like. All users can create network maps. The maps can be public (available to all users) or private (available to selected users). Proceed to [configuring a network map](/manual/config/visualization/maps/map). #### Aperçu Si vous avez un réseau à gérer, vous voudrez peut-être avoir une vue d'ensemble de votre infrastructure quelque part. À cette fin, vous pouvez créer des cartes dans Zabbix - des réseaux et de tout ce que vous voulez. Tous les utilisateurs peuvent créer des cartes réseau. Les cartes peuvent être publiques (disponibles pour tous les utilisateurs) ou privées (disponibles pour certains utilisateurs). Passez à [configurer une carte réseau](/manual/config/visualization/maps/map). #### Overview If you want some operations taking place as a result of events (for example, notifications sent), you need to configure actions. Actions can be defined in response to events of all supported types: - Trigger actions - for events when trigger status changes from *OK* to *PROBLEM* and back - Service actions - for events when service status changes from *OK* to *PROBLEM* and back - Discovery actions - for events when network discovery takes place - Autoregistration actions - for events when new active agents auto-register (or host metadata changes for registered ones) - Internal actions - for events when items become unsupported or triggers go into an unknown state #### Aperçu Si vous souhaitez que certaines opérations se déroulent à la suite d'événements (par exemple, des notifications envoyées), vous devez configurer des actions. Des actions peuvent être définies en réponse à des événements de tous les types pris en charge : - Actions de déclencheur - pour les événements lorsque l'état du déclencheur passe de *OK* à *PROBLÈME* et inversement - Actions de service - pour les événements lorsque l'état du service passe de *OK* à *PROBLÈME* et inversement - Actions de découverte - pour les événements lors de la découverte du réseau - Actions d'enregistrement automatique - pour les événements lorsque de nouveaux agents actifs s'enregistrent automatiquement (ou modifient les métadonnées de l'hôte pour ceux qui sont enregistrés) - Actions internes - pour les événements lorsque les éléments ne sont plus pris en charge ou que les déclencheurs passent dans un état inconnu #### Overview In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover Windows services. #### Aperçu De la même manière que les [systèmes de fichiers](/manual/discovery/low_level_discovery#configuration-de-la-decouverte-de-bas-niveau) sont découverts, il est également possible de découvrir les services Windows. #### Overview In message subjects and message text you can use macros for more efficient problem reporting. In addition to a number of built-in macros, [user macros](/manual/config/macros/user_macros) and [expression macros](/manual/config/macros/expression_macros) are also supported. A [full list of macros](/manual/appendix/macros/supported_by_location) supported by Zabbix is available. #### Aperçu Dans les objets et le texte des messages, vous pouvez utiliser des macros pour un signalement plus efficace des problèmes. Outre un certain nombre de macros intégrées, les [macros utilisateur](/manual/config/macros/user_macros) et les [macros d'expression](/manual/config/macros/expression_macros) sont également prises en charge. Une [liste complète des macros](/manual/appendix/macros/supported_by_location) prises en charge par Zabbix est disponible. #### Overview In *Monitoring → Problems* you can see what problems you currently have. Problems are those triggers that are in the "Problem" state. {width="600"} |Column|Description| |--|-----------| |*Time*|Problem start time is displayed.| |*Severity*|Problem severity is displayed.<br>Problem severity is originally based on the severity of the underlying problem trigger, however, after the event has happened it can be updated using the *Update problem* [screen](/manual/acknowledges#updating_problems). Color of the problem severity is used as cell background during problem time.| |*Recovery time*|Problem resolution time is displayed.| |*Status*|Problem status is displayed:<br>**Problem** - unresolved problem<br>**Resolved** - recently resolved problem. You can hide recently resolved problems using the filter.<br>New and recently resolved problems blink for 2 minutes. Resolved problems are displayed for 5 minutes in total. Both of these values are configurable in *Administration* → *General* → *[Trigger displaying options](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*.| |*Info*|A green information icon is displayed if a problem is closed by global correlation or manually when updating the problem. Rolling a mouse over the icon will display more details:<br><br>The following icon is displayed if a suppressed problem is being shown (see *Show suppressed problems* option in the filter). Rolling a mouse over the icon will display more details:<br>| |*Host*|Problem host is displayed.| |*Problem*|Problem name is displayed.<br>Problem name is based on the name of the underlying problem trigger.<br>Macros in the trigger name are resolved at the time of the problem happening and the resolved values do not update any more.<br>*Note* that it is possible to append the problem name with [operational data](#operational_data_of_problems) showing some latest item values.<br>Clicking on the problem name brings up the [event menu](#event_menu).<br>Hovering on the  icon after the problem name will bring up the trigger description (for those problems that have it).| |*Operational data*|[Operational data](#operational_data_of_problems) are displayed containing latest item values.<br>Operational data can be a combination of text and item value macros if configured on a trigger level. If no operational data is configured on a trigger level, the latest values of all items from the expression are displayed.<br>This column is only displayed if *Separately* is selected for *Show operational data* in the filter.| |*Duration*|Problem duration is displayed.<br>See also: [Negative problem duration](#negative_problem_duration)| |*Ack*|The acknowledgment status of the problem is displayed:<br>**Yes** - green text indicating that the problem is acknowledged. A problem is considered to be acknowledged if all events for it are acknowledged.<br>**No** - a red link indicating unacknowledged events.<br>If you click on the link you will be taken to the [problem update](/manual/acknowledges#updating_problems) screen where various actions can be taken on the problem, including commenting and acknowledging the problem.| |*Actions*|History of activities about the problem is displayed using symbolic icons:<br> - comments have been made. The number of comments is also displayed.<br> - problem severity has been increased (e.g. Information → Warning)<br> - problem severity has been decreased (e.g. Warning → Information)<br> - problem severity has been changed, but returned to the original level (e.g. Warning → Information → Warning)<br> - actions have been taken. The number of actions is also displayed.<br> - actions have been taken, at least one is in progress. The number of actions is also displayed.<br> - actions have been taken, at least one has failed. The number of actions is also displayed.<br>When rolling the mouse over the icons, popups with details about the activity are displayed. See [viewing details](#Viewing_details) to learn more about icons used in the popup for actions taken.| |*Tags*|[Tags](/manual/config/tagging) are displayed (if any).<br>In addition, tags from an external ticketing system may also be displayed (see the *Process tags* option when configuring [webhooks](/manual/config/notifications/media/webhook)).| #### Aperçu Dans *Surveillance → Problèmes*, vous pouvez voir les problèmes que vous rencontrez actuellement. Les problèmes sont les déclencheurs qui sont dans l'état "Problème". {width="600"} |Colonne|Description| |--|-----------| |*Temps*|L'heure de début du problème est affichée.| |*Sévérité*|La sévérité du problème est affichée.<br>La sévérité du problème est initialement basée sur la sévérité du déclencheur de problème sous-jacent, cependant, une fois que l'événement s'est produit, il peut être mis à jour à l'aide de l'[écran](/manual/acknowledges#updating_problems) *Mise à jour du problème*. La couleur de la gravité du problème est utilisée comme arrière-plan de la cellule pendant la période du problème.| |*Moment de la récupération*|Le temps de résolution du problème est affiché.| |*État*|L'état du problème est affiché :<br>**Problème** - problème non résolu<br>**Résolu** - problème récemment résolu. Vous pouvez masquer les problèmes récemment résolus à l'aide du filtre.<br>Les problèmes nouveaux et récemment résolus clignotent pendant 2 minutes. Les problèmes résolus sont affichés pendant 5 minutes au total. Ces deux valeurs sont configurables dans *Administration* → *Général* → *[Option d'affichage des déclencheurs](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*.| |*Info*|Une icône d'information verte s'affiche si un problème est fermé par corrélation globale ou manuellement lors de la mise à jour du problème. Passez la souris sur l'icône pour afficher plus de détails :<br><br>L'icône suivante s'affiche si un problème supprimé est affiché (voir l'option *Afficher les problèmes supprimés* dans le filtre). Passez la souris sur l'icône pour afficher plus de détails :<br>| |*Hôte*|L'hôte problématique est affiché.| |*Problème*|Le nom du problème est affiché.<br>Le nom du problème est basé sur le nom du déclencheur de problème sous-jacent.<br>Les macros dans le nom du déclencheur sont résolues au moment où le problème survient et les valeurs résolues ne sont pas mises à jour plus.<br>*Notez* qu'il est possible d'ajouter au nom du problème des [données opérationnelles](#operational_data_of_problems) affichant les dernières valeurs d'éléments.<br>Cliquer sur le nom du problème fait apparaître le [menu des événements](#event_menu).<br>Survoler l'icône  après le nom du problème fera apparaître le déclencheur description (pour les problèmes qui l'ont).| |*Données opérationnelles*|[Les données opérationnelles](#operational_data_of_problems) sont affichées avec les dernières valeurs d'élément.<br>Les données opérationnelles peuvent être une combinaison de texte et de macros de valeur d'élément si elles sont configurées au niveau du déclencheur. Si aucune donnée opérationnelle n'est configurée au niveau du déclencheur, les dernières valeurs de tous les éléments de l'expression sont affichées.<br>Cette colonne s'affiche uniquement si *Séparément* est sélectionné pour *Afficher les données opérationnelles* dans le filtre.| |*Durée*|La durée du problème est affichée.<br>Voir aussi : [Durée négative du problème](#negative_problem_duration)| |*Acquitté*|L'état d'acquittement du problème s'affiche :<br>**Oui** - texte vert indiquant que le problème est acquitté. Un problème est considéré comme acquitté si tous les événements correspondants sont acquittés.<br>**Non** - un lien rouge indiquant les événements non acquittés.<br>Si vous cliquez sur le lien, vous serez redirigé vers la [mise à jour du problème](/manual/acknowledges#updating_problems) où diverses actions peuvent être effectuées sur le problème, y compris commenter et acquitter le problème.| |*Actions*|L'historique des activités concernant le problème est affiché à l'aide d'icônes symboliques :<br> - des commentaires ont été faits. Le nombre de commentaires est également affiché.<br> - la sévérité du problème a été augmentée (par exemple, Information → Avertissement)<br> - la sévérité du problème a été réduite (par exemple, Avertissement → Information)<br> - la sévérité du problème a été modifiée, mais est revenue au niveau d'origine (par exemple, Avertissement → Information → Avertissement)<br> - des actions ont été entreprises. Le nombre d'actions est également affiché.<br> - des actions ont été entreprises, au moins une est en cours. Le nombre d'actions est également affiché.<br> - des actions ont été entreprises, au moins une a échoué. Le nombre d'actions est également affiché.<br>Lorsque vous passez la souris sur les icônes, des fenêtres contextuelles contenant des détails sur l'activité s'affichent. Voir l'[affichage des détails](#Viewing_details) pour en savoir plus sur les icônes utilisées dans la fenêtre contextuelle pour les actions entreprises.| |*Tags*|Les [tags](/manual/config/tagging) sont affichés (le cas échéant).<br>De plus, les tags d'un système de ticket externe peuvent également être affichées (voir l'option *Traiter les tags* lors de la configuration des [webhooks](/manual/config/notifications/media/webhook)).| #### Overview In order to provide monitoring for network devices such as switches and routers, we have created two so-called models: for the network device itself (its chassis basically) and for network interface. Since Zabbix 3.4 templates for many families of network devices are provided. All templates cover (where possible to get these items from the device): - Chassis fault monitoring (power supplies, fans and temperature, overall status) - Chassis performance monitoring (CPU and memory items) - Chassis inventory collection (serial numbers, model name, firmware version) - Network interface monitoring with IF-MIB and EtherLike-MIB (interface status, interface traffic load, duplex status for Ethernet) These templates are available: - In new installations - in *Configuration* → *Templates*; - If you are upgrading from previous versions, you can find these templates in the `templates` directory of the downloaded latest Zabbix version. While in *Configuration* → *Templates* you can import them manually from this directory. If you are importing the new out-of-the-box templates, you may want to also update the `@Network interfaces for discovery` global regular expression to: Result is FALSE: ^Software Loopback Interface Result is FALSE: ^(In)?[lL]oop[bB]ack[0-9._]*$ Result is FALSE: ^NULL[0-9.]*$ Result is FALSE: ^[lL]o[0-9.]*$ Result is FALSE: ^[sS]ystem$ Result is FALSE: ^Nu[0-9.]*$ to filter out loopbacks and null interfaces on most systems. #### Aperçu Afin de surveiller les périphériques réseau tels que les commutateurs et les routeurs, nous avons créé deux modèles : le périphérique réseau lui-même (son châssis essentiellement) et l'interface réseau. Depuis Zabbix 3.4, des modèles sont fournis pour de nombreuses familles de périphériques réseau. Tous les modèles couvrent (s'il est possible d'obtenir ces éléments de l'équipement) : - La supervision des pannes de châssis (blocs d'alimentation, ventilateurs et température, état général) - La supervision des performances du châssis (éléments processeur et mémoire) - La récupération de l'inventaire du châssis (numéro de série, nom du modèle, version du micrologiciel) - La surveillance d'interfaces réseau avec IF-MIB et EtherLike-MIB (statut de l'interface, charge du trafic d'interface, statut duplex pour Ethernet) Ces modèles sont disponibles : - Dans les nouvelles installations - dans *Configuration* → *Modèles* ; - Si vous effectuez une mise à jour à partir de versions précédentes, vous pouvez trouver ces modèles dans le répertoire `templates` de la dernière version Zabbix téléchargée. Dans *Configuration* → *Modèles*, vous pouvez les importer manuellement à partir de ce répertoire. Si vous importez les nouveaux modèles prêts à l'emploi, vous devriez également mettre à jour l'expression régulière globale `@Network interfaces for discovery` pour : Result is FALSE: ^Software Loopback Interface Result is FALSE: ^(In)?[lL]oop[bB]ack[0-9._]*$ Result is FALSE: ^NULL[0-9.]*$ Result is FALSE: ^[lL]o[0-9.]*$ Result is FALSE: ^[sS]ystem$ Result is FALSE: ^Nu[0-9.]*$ pour filtrer les loopbacks et les interfaces nulles sur la plupart des systèmes. #### Overview In order to use any other language than English in Zabbix web interface, its locale should be installed on the web server. Additionally, the PHP gettext extension is required for the translations to work. #### Aperçu Pour utiliser une autre langue que l'anglais dans l'interface Web de Zabbix, ses paramètres régionaux doivent être installés sur le serveur Web. De plus, l'extension PHP gettext est requise pour que les traductions fonctionnent. #### Overview In *Reports → Availability report* you can see what proportion of time each trigger has been in problem/ok state. The percentage of time for each state is displayed. Thus it is easy to determine the availability situation of various elements on your system. {width="600"} From the drop-down in the upper right corner, you can choose the selection mode - whether to display triggers by hosts or by triggers belonging to a template. {width="600"} The name of the trigger is a link to the latest events of that trigger. #### Aperçu Dans *Rapports → Rapport de disponibilité*, vous pouvez voir la proportion de temps pendant laquelle chaque déclencheur a été en état de problème/ok. Le pourcentage de temps pour chaque état est affiché. Ainsi, il est facile de déterminer la situation de disponibilité des différents éléments de votre système. {width="600"} Dans la liste déroulante dans le coin supérieur droit, vous pouvez choisir le mode de sélection - que ce soit pour afficher les déclencheurs par hôtes ou par déclencheurs appartenant à un modèle. {width="600"} Le nom du déclencheur est un lien vers les derniers événements de ce déclencheur. #### Overview In *Reports → System information* a summary of key Zabbix server and system data is displayed. Note that in a high availability setup, it is possible to redirect the system information source (server instance) by editing the ui/conf/zabbix.conf.php file - uncomment and set $ZBX\_SERVER, $ZBX\_SERVER\_PORT to a server other than the one shown active. With the high availability setup enabled, a separate block is displayed below the system stats with details of high availability nodes. This block is visible to Zabbix Super Admin users only. *System information* is also available as a dashboard [widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets). #### Aperçu Dans *Rapports → Informations système*, un résumé des données clés du serveur Zabbix et du système est affiché. Notez que dans une configuration à haute disponibilité, il est possible de rediriger la source d'informations système (instance de serveur) en éditant le fichier ui/conf/zabbix.conf.php - décommentez et définissez $ZBX\_SERVER, $ZBX\_SERVER\_PORT sur un serveur autre que celui affiché actif. Lorsque la configuration de haute disponibilité est activée, un bloc séparé s'affiche sous les statistiques du système avec les détails des nœuds de haute disponibilité. Ce bloc est visible uniquement par les utilisateurs Zabbix Super Admin. Les *Informations système* sont également disponibles sous forme de [widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets) de tableau de bord. #### Overview Internal checks allow to monitor the internal processes of Zabbix. In other words, you can monitor what goes on with Zabbix server or Zabbix proxy. Internal checks are calculated: - on Zabbix server - if the host is monitored by server - on Zabbix proxy - if the host is monitored by proxy Internal checks are processed by server or proxy regardless of host maintenance status. To use this item, choose the **Zabbix internal** item type. ::: notetip Internal checks are processed by Zabbix pollers. ::: #### Aperçu Les contrôles internes permettent de surveiller les processus internes de Zabbix. En d'autres termes, vous pouvez surveiller ce qui se passe avec le serveur Zabbix ou le proxy Zabbix. Les contrôles internes sont calculés : - sur le serveur Zabbix - si l'hôte est surveillé par le serveur - sur le proxy Zabbix - si l'hôte est surveillé par le proxy Les contrôles internes sont traités par le serveur ou le proxy, quel que soit l'hôte l'état de maintenance de l'hôte. Pour utiliser cet élément, choisissez le type d'élément **Zabbix Interne**. ::: notetip Les vérifications internes sont traitées par les pollers Zabbix. ::: #### Overview In the action log widget, you can display details of action operations (notifications, remote commands). It replicates information from *Reports → Action log*. #### Aperçu Dans le widget du journal des actions, vous pouvez afficher les détails des opérations d'action (notifications, commandes à distance). Il réplique les informations de *Rapports → Audit*. #### Overview In the *Administration → Proxies* section proxies for [distributed monitoring](/manual/distributed_monitoring) can be configured in the Zabbix frontend. #### Aperçu Dans la section *Administration → Proxies*, les proxys pour une [surveillance distribuée](/manual/distributed_monitoring) peuvent être configurés dans l'interface Zabbix. #### Overview In the *Administration → User groups* section user groups of the system are maintained. #### Aperçu Dans la section *Administration → Groupes d'utilisateurs* les groupes d'utilisateurs du système sont maintenus. #### Overview In the *Administration → User roles* section roles that can be assigned to system users and specific permissions for each role are maintained. #### Aperçu Dans la section *Administration → Rôles utilisateur*, les rôles pouvant être attribués aux utilisateurs du système et les autorisations spécifiques pour chaque rôle sont conservés. #### Overview In the *Administration → Users* section users of the system are maintained. #### Aperçu Dans la section *Administration → Utilisateurs*, les utilisateurs du système sont maintenus. #### Overview In the classic graph widget, you can display a single custom graph or simple graph. #### Aperçu Dans le widget graphique classique, vous pouvez afficher un seul graphique personnalisé ou un graphique simple. #### Overview In the clock widget, you may display local, server, or specified host time. #### Aperçu Dans le widget horloge, vous pouvez afficher l'heure locale, du serveur ou de l'hôte spécifié. #### Overview In the *Configuration → Discovery* section users can configure and maintain discovery rules. A listing of existing discovery rules with their details is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the discovery rule. Clicking on the discovery rule name opens the discovery rule [configuration form](/manual/discovery/network_discovery/rule).| |*IP range*|The range of IP addresses to use for network scanning is displayed.| |*Proxy*|The proxy name is displayed, if discovery is performed by the proxy.| |*Interval*|The frequency of performing discovery displayed.| |*Checks*|The types of checks used for discovery are displayed.| |*Status*|Action status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| To configure a new discovery rule, click on the *Create discovery rule* button in the top right-hand corner. #### Aperçu Dans la section *Configuration → Découverte*, les utilisateurs peuvent configurer et gérer les règles de découverte. Une liste des règles de découverte existantes avec leurs détails s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom de la règle de découverte. Cliquer sur le nom de la règle de découverte ouvre le [formulaire de configuration](/manual/discovery/network_discovery/rule) de la règle de découverte.| |*Plage IP*|La plage d'adresses IP à utiliser pour le scan réseau s'affiche.| |*Proxy*|Le nom du proxy est affiché, si la découverte est effectuée par le proxy.| |*Intervalle*|La fréquence d'exécution de la découverte affichée.| |*Vérifications*|Les types de vérifications utilisés pour la découverte sont affichés.| |*Statut*|Le statut de l'action est affiché - *Activé* ou *Désactivé*.<br>En cliquant sur le statut, vous pouvez le modifier.| Pour configurer une nouvelle règle de découverte, cliquez sur le bouton *Créer une règle de découverte* dans le coin supérieur droit. #### Overview In the *Configuration → Event correlation* section users can configure and maintain global correlation rules for Zabbix events. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the correlation rule. Clicking on the correlation rule name opens the rule [configuration form](/manual/config/event_correlation/global#configuration).| |*Conditions*|Correlation rule conditions are displayed.| |*Operations*|Correlation rule operations are displayed.| |*Status*|Correlation rule status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| To configure a new correlation rule, click on the *Create correlation* button in the top right-hand corner. #### Aperçu Dans la section *Configuration → Corrélation d'événements*, les utilisateurs peuvent configurer et maintenir des règles de corrélation globales pour les événements Zabbix. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom de la règle de corrélation. Cliquer sur le nom de la règle de corrélation ouvre le[formulaire de configuration](/manual/config/event_correlation/global#configuration) de la règle .| |*Conditions*|Les conditions de la règle de corrélation sont affichées.| |*Opérations*|Les opérations de règle de corrélation sont affichées.| |*Statut*|Le statut de la règle de corrélation est affiché - *Activé* ou *Désactivé*.<br>En cliquant sur le statut, vous pouvez le modifier.| Pour configurer une nouvelle règle de corrélation, cliquez sur le bouton *Créer une corrélation* dans le coin supérieur droit. #### Overview In the *Configuration → Maintenance* section users can configure and maintain maintenance periods for hosts. A listing of existing maintenance periods with their details is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the maintenance period. Clicking on the maintenance period name opens the maintenance period [configuration form](/manual/maintenance#configuration).| |*Type*|The type of maintenance is displayed: *With data collection* or *No data collection*| |*Active since*|The date and time when executing maintenance periods becomes active.<br>Note: This time does not activate a maintenance period; maintenance periods need to be set separately.| |*Active till*|The date and time when executing maintenance periods stops being active.| |*State*|The state of the maintenance period:<br>**Approaching** - will become active soon<br>**Active** - is active<br>**Expired** - is not active any more| |*Description*|Description of the maintenance period is displayed.| To configure a new maintenance period, click on the *Create maintenance period* button in the top right-hand corner. #### Aperçu Dans la section *Configuration → Maintenance*, les utilisateurs peuvent configurer et gérer les périodes de maintenance des hôtes. Une liste des périodes de maintenance existantes avec leurs détails s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom de la période de maintenance. Cliquer sur le nom de la période de maintenance ouvre le [formulaire de configuration](/manual/maintenance#configuration) de la période de maintenance.| |*Type*|Le type de maintenance est affiché : *Avec collecte de données* ou *Sans collecte de données*| |*Actif depuis*|La date et l'heure auxquelles l'exécution des périodes de maintenance devient active.<br>Remarque : cette heure n'active pas une période de maintenance ; les périodes de maintenance doivent être définies séparément.| |*Actif jusqu'à*|La date et l'heure auxquelles l'exécution des périodes de maintenance cesse d'être actives.| |*État*|L'état de la période de maintenance :<br>**Approchant** - deviendra bientôt actif<br>**Actif** - est actif<br>**Expiré** - n'est plus actif| |*Description*|La description de la période de maintenance est affichée.| Pour configurer une nouvelle période de maintenance, cliquez sur le bouton *Créer une période de maintenance* dans le coin supérieur droit. #### Overview In the *Configuration → Templates* section users can configure and maintain templates. A listing of existing templates with their details is displayed. {width="600"} Displayed data: |Column|Description| |--|-----------| |*Name*|Name of the template. Clicking on the template name opens the template [configuration form](/manual/config/templates/template#creating_a_template).| |*Hosts*|Number of editable hosts to which the template is linked; read-only hosts are not included.<br>Clicking on *Hosts* will open the host list with only those hosts filtered that are linked to the template.| |*Entities (Items, Triggers, Graphs, Dashboards, Discovery, Web)*|Number of the respective entities in the template (displayed in gray). Clicking on the entity name will, in the whole listing of that entity, filter out those that belong to the template.| |*Linked templates*|Templates that are linked to the template, in a nested setup where the template will inherit all entities of the linked templates.| |*Linked to templates*|The templates that the template is linked to ("children" templates that inherit all entities from this template).<br>Since Zabbix 5.0.3, this column no longer includes hosts.| |*Tags*|[Tags](/manual/config/tagging) of the template, with macros unresolved.| To configure a new template, click on the *Create template* button in the top right-hand corner. To import a template from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner. #### Aperçu Dans la section *Configuration → Modèles*, les utilisateurs peuvent configurer et gérer des modèles. Une liste des modèles existants avec leurs détails s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|-----------| |*Nom*|Nom du modèle. Cliquer sur le nom du modèle ouvre le [formulaire de configuration](/manual/config/templates/template#creating_a_template) du modèle.| |*Hôtes*|Nombre d'hôtes modifiables auxquels le modèle est lié ; les hôtes en lecture seule ne sont pas inclus.<br>Cliquer sur *Hôtes* ouvrira la liste des hôtes avec uniquement les hôtes filtrés qui sont liés au modèle.| |*Entités (Items, Déclencheurs, Graphiques, Tableaux de bord, Découverte, Web)*|Nombre d'entités respectives dans le modèle (affichées en gris). Cliquer sur le nom de l'entité filtrera, dans toute la liste de cette entité, celles qui appartiennent au modèle.| |*Modèles liés*|Modèles liés au modèle, dans une configuration imbriquée où le modèle héritera de toutes les entités des modèles liés.| |*Lié aux modèles*|Les modèles auxquels le modèle est lié (modèles "enfants" qui héritent de toutes les entités de ce modèle).<br>Depuis Zabbix 5.0.3, cette colonne n'inclut plus les hôtes.| |*Tags*|[Tags](/manual/config/tagging) du modèle, avec les macros non résolues.| Pour configurer un nouveau modèle, cliquez sur le bouton *Créer un modèle* dans le coin supérieur droit. Pour importer un modèle à partir d'un fichier YAML, XML ou JSON, cliquez sur le bouton *Importer* dans le coin supérieur droit. #### Overview In the data overview widget, you can display the latest data for a group of hosts. The color of problem items is based on the problem severity color, which can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen. By default, only values that fall within the last 24 hours are displayed. This limit has been introduced with the aim of improving initial loading times for large pages of latest data. This limit is configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max history display period* option. Clicking on a piece of data offers links to some predefined graphs or latest values. Note that 50 records are displayed by default (configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max number of columns and rows in overview tables* option). If more records exist than are configured to display, a message is displayed at the bottom of the table, asking to provide more specific filtering criteria. There is no pagination. Note that this limit is applied first, before any further filtering of data, for example, by tags. #### Aperçu Dans le widget de présentation des données, vous pouvez afficher les dernières données pour un groupe d'hôtes. La couleur des éléments de problème est basée sur la couleur de sévérité du problème, qui peut être ajustée dans l'écran [mise à jour du problème](/manual/acknowledges#updating_problems). Par défaut, seules les valeurs qui se situent dans les dernières 24 heures sont affichées. Cette limite a été introduite dans le but d'améliorer les temps de chargement initiaux pour les grandes pages de données les plus récentes. Cette limite est configurable dans *Administration* → *Général* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, en utilisant l'option *Période d'affichage maximale de l'historique*. Cliquer sur une donnée offre des liens vers des graphiques prédéfinis ou les dernières valeurs. Notez que 50 enregistrements sont affichés par défaut (configurable dans *Administration* → *Général* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, en utilisant le *Nombre maximum de colonnes et de lignes dans les tableaux d'options d'aperçu*). S'il existe plus d'enregistrements qu'il n'est configuré pour en afficher, un message s'affiche au bas du tableau, demandant de fournir des critères de filtrage plus spécifiques. Il n'y a pas de pagination. Notez que cette limite est appliquée en premier, avant tout filtrage ultérieur des données, par exemple, par tags. #### Overview In the graph prototype widget, you can display a grid of graphs created from either a graph prototype or an item prototype by low-level discovery. #### Aperçu Dans le widget de prototype de graphique, vous pouvez afficher une grille de graphiques créés à partir d'un prototype de graphique ou d'un prototype d'élément par découverte de bas niveau. #### Overview In the host availability widget, high-level statistics about host availability are displayed in four colored columns/lines. | | | |---|---| ||Horizontal display (columns).| ||Vertical display (lines).| Host availability in each column/line is counted as follows: - *Available* - hosts with all interfaces available - *Not available* - hosts with at least one interface unavailable - *Unknown* - hosts with at least one interface unknown (none unavailable) - *Total* - total of all hosts #### Aperçu Dans le widget de disponibilité de l'hôte, des statistiques de haut niveau sur la disponibilité de l'hôte sont affichées dans quatre colonnes/lignes colorées. | | | |---|---| ||Affichage horizontal (colonnes).| ||Affichage vertical (lignes).| La disponibilité de l'hôte dans chaque colonne/ligne est comptabilisée comme suit : - *Disponible* - hôtes avec toutes les interfaces disponibles - *Non disponible* - hôtes avec au moins une interface indisponible - *Inconnu* - hôtes avec au moins une interface inconnue (aucune non disponible) - *Total* - total de tous les hôtes #### Overview In the *Monitoring → Discovery* section results of [network discovery](/manual/discovery/network_discovery) are shown. Discovered devices are sorted by the discovery rule. {width="600"} If a device is already monitored, the host name will be listed in the *Monitored host* column, and the duration of the device being discovered or lost after previous discovery is shown in the *Uptime/Downtime* column. After that follow the columns showing the state of individual services for each discovered device (red cells show services that are down). Service uptime or downtime is included within the cell. ::: noteimportant Only those services that have been found on at least one device will have a column showing their state. ::: #### Aperçu Dans la section *Surveillance → Découverte*, les résultats de la [découverte du réseau](/manual/discovery/network_discovery) sont affichés. Les appareils découverts sont triés selon la règle de découverte. {width="600"} Si un appareil est déjà surveillé, le nom d'hôte sera répertorié dans la colonne *Hôte surveillé*, et la durée de la découverte ou de la perte de l'appareil après la découverte précédente est indiquée dans la colonne *Temps de disponibilité/d'arrêt*. Après cela, suivez les colonnes indiquant l'état du service individuel pour chaque appareil découvert (les cellules rouges indiquent les services qui sont en panne). La disponibilité ou l'indisponibilité du service est incluse dans la cellule. ::: noteimportant Seuls les services qui ont été trouvés sur au moins un appareil auront une colonne indiquant leur état. ::: #### Overview In the *Monitoring → Maps* section you can configure, manage and view [network maps](/manual/config/visualization/maps). When you open this section, you will either see the last map you accessed or a listing of all maps you have access to. All maps can be either public or private. Public maps are available to all users, while private maps are accessible only to their owner and the users the map is shared with. #### Aperçu Dans la section *Surveillance→ Cartes*, vous pouvez configurer, gérer et afficher [les cartes du réseau](/manual/config/visualization/maps). Lorsque vous ouvrez cette section, vous verrez soit la dernière carte à laquelle vous avez accédé, soit une liste de toutes les cartes auxquelles vous avez accès. Toutes les cartes peuvent être publiques ou privées. Les cartes publiques sont disponibles pour tous les utilisateurs, tandis que les cartes privées ne sont accessibles qu'à leur propriétaire et aux utilisateurs avec lesquels la carte est partagée. #### Overview In the plain text widget, you can display the latest item data in plain text. #### Aperçu Dans le widget de texte brut, vous pouvez afficher les dernières données d'élément en texte brut. #### Overview In the problem host widget, you can display high-level information about host availability. #### Aperçu Dans le widget d'hôte problématique, vous pouvez afficher des informations de haut niveau sur la disponibilité de l'hôte. #### Overview In the *Reports → Notifications* section a report on the number of notifications sent to each user is displayed. From the dropdowns in the top right-hand corner you can choose the media type (or all), period (data for each day/week/month/year) and year for the notifications sent. {width="600"} Each column displays totals per one system user. #### Aperçu Dans la section *Rapports → Notifications*, un rapport sur le nombre de notifications envoyées à chaque utilisateur est affiché. Dans les menus déroulants situés dans le coin supérieur droit, vous pouvez choisir le type de média (ou tous), la période (données pour chaque jour/semaine/mois/année) et l'année pour les notifications envoyées. {width="600"} Chaque colonne affiche les totaux pour un utilisateur système. #### Overview In the trigger overview widget, you can display the trigger states for a group of hosts. - The trigger states are displayed as colored blocks (the color of the blocks for PROBLEM triggers depends on the problem severity color, which can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen). Note that recent trigger state changes (within the last 2 minutes) will be displayed as blinking blocks. - Gray up and down arrows indicate triggers that have dependencies. On mouseover, dependency details are revealed. - A checkbox icon indicates acknowledged problems. All problems or resolved problems of the trigger must be acknowledged for this icon to be displayed. Clicking on a trigger block provides context-dependent links to problem events of the trigger, the problem acknowledgment screen, trigger configuration, trigger URL or a simple graph/latest values list. Note that 50 records are displayed by default (configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max number of columns and rows in overview tables* option). If more records exist than are configured to display, a message is displayed at the bottom of the table, asking to provide more specific filtering criteria. There is no pagination. Note that this limit is applied first, before any further filtering of data, for example, by tags. #### Aperçu Dans le widget de présentation du déclencheur, vous pouvez afficher les états du déclencheur pour un groupe d'hôtes. - Les états des déclencheurs sont affichés sous forme de blocs de couleur (la couleur des déclencheurs de problème dépend de la couleur de la gravité du problème, qui peut être ajustée dans l'écran [mise à jour du problème](/manual/acknowledges#mise-à-jour-de-problèmes)). Notez que les modifications récentes du déclencheur (au cours des 2 dernières minutes) seront affichées sous forme de blocs clignotants. - Les flèches grises vers le haut et vers le bas indiquent les déclencheurs qui ont des dépendances. Au passage de la souris, les détails de la dépendance sont révélés. - Une icône de case à cocher indique des problèmes reconnus. Tous les problèmes ou problèmes résolus du déclencheur doivent être acquittés pour que cette icône s'affiche. Cliquer sur un bloc de déclencheur fournit des liens dépendants du contexte vers les événements problématiques du déclencheur, l'écran d'acquittement du problème, la configuration du déclencheur, l'URL du déclencheur ou un simple graphique/liste des dernières valeurs. Notez que 50 enregistrements sont affichés par défaut (configurable dans*Administration* → *Général* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, en utilisant l'option *Nombre maximal de colonnes et de lignes dans les tableaux d'aperçu*). S'il existe plus d'enregistrements qu'il n'est configuré pour en afficher, un message s'affiche au bas du tableau, demandant de fournir des critères de filtrage plus spécifiques. Il n'y a pas de pagination. Notez que cette limite est appliquée en premier, avant tout filtrage ultérieur des données, par exemple, par tags. #### Overview In this preprocessing step it is possible to convert CSV file data into JSON format. It's supported in: - items (item prototypes) - low-level discovery rules #### Aperçu Dans cette étape de prétraitement, il est possible de convertir les données du fichier CSV au format JSON. Il est pris en charge dans : - éléments (prototypes d'éléments) - règles de découverte de bas niveau #### Overview In this section the configured graph prototypes of a low-level discovery rule on the template are displayed. If the template is linked to the host, graph prototypes will become the basis of creating real host [graphs](/manual/web_interface/frontend_sections/configuration/hosts/graphs) during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the graph prototype, displayed as a blue link.<br>Clicking on the name opens the graph prototype [configuration form](/manual/discovery/low_level_discovery/graph_prototypes).<br>If the graph prototype belongs to a linked template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph prototype list on the linked template level.| |*Width*|Width of the graph prototype is displayed.| |*Height*|Height of the graph prototype is displayed.| |*Type*|Type of the graph prototype is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Discover*|Discover the graph based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| To configure a new graph prototype, click on the *Create graph prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes de graphique configurés d'une règle de découverte de bas niveau sur le modèle sont affichés. Si le modèle est lié à l'hôte, les prototypes de graphique deviendront la base de la création de véritables [graphiques d'hôtes](/manual/web_interface/frontend_sections/configuration/hosts/graphs) lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype de graphique, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery/graph_prototypes) du prototype de graphique.<br>Si le prototype de graphique appartient à un modèle lié, le nom du modèle s'affiche avant le nom du graphique, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes de graphique au niveau du modèle lié.| |*Largeur*|La largeur du prototype de graphique est affichée.| |*Hauteur*|La hauteur du prototype de graphique est affichée.| |*Type*|Le type de prototype de graphique est affiché - *Normal*, *Empilé*, *Camembert* ou *Explosé*.| |*Découvrir*|Découvrir le graphique basé sur ce prototype :<br>**Oui** - Découvrir<br>**Non** - Ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| Pour configurer un nouveau prototype de graphique, cliquez sur le bouton *Créer un prototype de graphique* dans le coin supérieur droit. #### Overview In this section the configured host prototypes of a low-level discovery rule on the template are displayed. If the template is linked to the host, host prototypes will become the basis of creating real [hosts](/manual/web_interface/frontend_sections/configuration/hosts) during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the host prototype, displayed as a blue link.<br>Clicking on the name opens the host prototype configuration form.<br>If the host prototype belongs to a linked template, the template name is displayed before the host name, as a gray link. Clicking on the template link will open the host prototype list on the linked template level.| |*Templates*|Templates of the host prototype are displayed.| |*Create enabled*|Create the host based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the host based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the host prototype are displayed.| To configure a new host prototype, click on the *Create host prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes d'hôtes configurés dans une règle de découverte de bas niveau du modèle sont affichés. Si le modèle est lié à l'hôte, les prototypes d'hôtes deviendront la base de la création de véritables [hôtes](/manual/web_interface/frontend_sections/configuration/hosts) lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype d'hôte, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le formulaire de configuration du prototype d'hôte.<br>Si le prototype d'hôte appartient à un modèle lié, le nom du modèle s'affiche avant le nom d'hôte, comme un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes hôtes au niveau du modèle lié.| |*Modèles*|Les modèles du prototype d'hôte sont affichés.| |*Créer activé*|Créez l'hôte basé sur ce prototype en tant que :<br>**Oui** - activé<br>**Non** - désactivé. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Découvrir*|Découvrir l'hôte basé sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Tags*|Les tags du prototype hôte sont affichées.| Pour configurer un nouveau prototype d'hôte, cliquez sur le bouton *Créer un prototype d'hôte* dans le coin supérieur droit. #### Overview In this section the configured item prototypes of a low-level discovery rule on the template are displayed. If the template is linked to the host, item prototypes will become the basis of creating real host [items](/manual/web_interface/frontend_sections/configuration/hosts/items) during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the item prototype, displayed as a blue link.<br>Clicking on the name opens the item prototype [configuration form](/manual/discovery/low_level_discovery/item_prototypes).<br>If the item prototype belongs to a linked template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item prototype list on the linked template level.| |*Key*|Key of the item prototype is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days to keep item data history is displayed.| |*Trends*|How many days to keep item trends history is displayed.| |*Type*|Type of the item prototype is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Create enabled*|Create the item based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the item based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the item prototype is displayed.| To configure a new item prototype, click on the *Create item prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes d'éléments configurés d'une règle de découverte de bas niveau sur le modèle sont affichés. Si le modèle est lié à l'hôte, les prototypes d'éléments deviendront la base de la création des [éléments](/manual/web_interface/frontend_sections/configuration/hosts/items) d'hôte réel lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype d'élément, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery/item_prototypes) du prototype d'élément .<br>Si le prototype d'élément appartient à un modèle lié, le nom du modèle s'affiche avant le nom de l'élément, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes d'éléments au niveau du modèle lié.| |*Clé*|La clé du prototype d'élément est affichée.| |*Intervalle*|La fréquence du contrôle est affichée.| |*Historique*|Le nombre de jours pour conserver l'historique des données de l'élément est affiché.| |*Tendances*|Le nombre de jours pour conserver l'historique des tendances des éléments est affiché.| |*Type*|Le type du prototype de l'élément est affiché (agent Zabbix, agent SNMP, vérification simple, etc.).| |*Créer activé*|Création de l'élément basée sur ce prototype comme :<br>**Oui** - activé<br>**Non** - désactivé. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Découvrir*|Découverte de l'élément basée sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Tags*|Les tags du prototype d'élément sont affichés.| Pour configurer un nouveau prototype d'élément, cliquez sur le bouton *Créer un prototype d'élément* dans le coin supérieur droit. #### Overview In this section the graph prototypes of a low-level discovery rule on the host are displayed. Graph prototypes are the basis of real host [graphs](/manual/web_interface/frontend_sections/configuration/hosts/graphs) that are created during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the graph prototype, displayed as a blue link.<br>Clicking on the name opens the graph prototype [configuration form](/manual/discovery/low_level_discovery/graph_prototypes).<br>If the graph prototype belongs to a linked template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph prototype list on the linked template level.| |*Width*|Width of the graph prototype is displayed.| |*Height*|Height of the graph prototype is displayed.| |*Type*|Type of the graph prototype is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Discover*|Discover the graph based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| To configure a new graph prototype, click on the *Create graph prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes de graphique d'une règle de découverte de bas niveau sur l'hôte sont affichés. Les prototypes de graphique sont à la base des [graphiques d'hôtes réels](/manual/web_interface/frontend_sections/configuration/hosts/graphs) qui sont créés lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype de graphique, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery/graph_prototypes) du prototype de graphique.<br>Si le prototype de graphique appartient à un modèle lié, le nom du modèle s'affiche avant le nom du graphique, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes de graphique au niveau du modèle lié.| |*Largeur*|La largeur du prototype de graphique est affichée.| |*Hauteur*|La hauteur du prototype de graphique est affichée.| |*Type de graphique*|Le type de prototype de graphique est affiché - *Normal*, *Empilé*, *Camembert* or *Explosé*.| |*Découvrir*|Découvrir le graphique basé sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| Pour configurer un nouveau prototype de graphique, cliquez sur le bouton *Créer un prototype de graphique* dans le coin supérieur droit. #### Overview In this section the host prototypes of a low-level discovery rule on the host are displayed. Host prototypes are the basis of real [hosts](/manual/web_interface/frontend_sections/configuration/hosts) that are created during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the host prototype, displayed as a blue link.<br>Clicking on the name opens the host prototype configuration form.<br>If the host prototype belongs to a linked template, the template name is displayed before the host name, as a gray link. Clicking on the template link will open the host prototype list on the linked template level.| |*Templates*|Templates of the host prototype are displayed.| |*Create enabled*|Create the host based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the host based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the host prototype are displayed.| To configure a new host prototype, click on the *Create host prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes d'hôte d'une règle de découverte de bas niveau sur l'hôte sont affichés. Les prototypes d'hôtes sont la base des véritables [hôtes](/manual/web_interface/frontend_sections/configuration/hosts) qui sont créés lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype d'hôte, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le formulaire de configuration du prototype d'hôte.<br>Si le prototype d'hôte appartient à un modèle lié, le nom du modèle s'affiche avant le nom d'hôte, comme un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes hôtes au niveau du modèle lié.| |*Modèles*|Les modèles du prototype hôte sont affichés.| |*Créer activé*|Créer l'hôte basé sur ce prototype en tant que :<br>**Oui** - activé<br>**Non** - désactivé. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Découvrir*|Découvrir l'hôte basé sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Tags*|Les balises du prototype hôte sont affichées.| Pour configurer un nouveau prototype d'hôte, cliquez sur le bouton *Créer un prototype d'hôte* dans le coin supérieur droit. #### Overview In this section the item prototypes of a low-level discovery rule on the host are displayed. Item prototypes are the basis of real host [items](/manual/web_interface/frontend_sections/configuration/hosts/items) that are created during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the item prototype, displayed as a blue link.<br>Clicking on the name opens the item prototype [configuration form](/manual/discovery/low_level_discovery/item_prototypes).<br>If the item prototype belongs to a template, the template name is displayed before the rule name, as a gray link. Clicking on the template link will open the item prototype list on the template level.| |*Key*|Key of the item prototype is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days to keep item data history is displayed.| |*Trends*|How many days to keep item trends history is displayed.| |*Type*|Type of the item prototype is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Create enabled*|Create the item based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the item based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the item prototype are displayed.| To configure a new item prototype, click on the *Create item prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes d'élément d'une règle de découverte de bas niveau sur l'hôte sont affichés. Les prototypes d'éléments sont à la base des [éléments](/manual/web_interface/frontend_sections/configuration/hosts/items) d'hôtes réels qui sont créés lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype d'élément, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery/item_prototypes) du prototype d'élément.<br>Si le prototype d'élément appartient à un modèle, le nom du modèle s'affiche avant le nom de la règle, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes d'éléments au niveau du modèle.| |*Clé*|La clé du prototype d'élément est affichée.| |*Intervalle*|La fréquence du contrôle est affichée.| |*Historique*|Le nombre de jours de conservation de l'historique des données de l'élément est affiché.| |*Tendances*|Le nombre de jours de conservation de l'historique des tendances des éléments est affiché.| |*Type*|Le type du prototype de l'élément est affiché (agent Zabbix, agent SNMP, vérification simple, etc.).| |*Créer activé*|Création de l'élément basée sur ce prototype comme :<br>**Oui** - activé<br>**Non** - désactivé. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Découvrir*|Découverte de l'objet basé sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Tags*|Les tags du prototype d'élément sont affichés.| Pour configurer un nouveau prototype d'élément, cliquez sur le bouton *Créer un prototype d'élément* dans le coin supérieur droit. #### Overview In this section the trigger prototypes of a low-level discovery rule on the host are displayed. Trigger prototypes are the basis of real host [triggers](/manual/web_interface/frontend_sections/configuration/hosts/triggers) that are created during low-level discovery. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the trigger prototype, displayed as a blue link.<br>Clicking on the name opens the trigger prototype [configuration form](/manual/discovery/low_level_discovery/trigger_prototypes).<br>If the trigger prototype belongs to a linked template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger prototype list on the linked template level.| |*Operational data*|Format of the operational data of the trigger is displayed, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Create enabled*|Create the trigger based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the trigger based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the trigger prototype are displayed.| To configure a new trigger prototype, click on the *Create trigger prototype* button at the top right corner. #### Aperçu Dans cette section, les prototypes de déclencheur d'une règle de découverte de bas niveau sur l'hôte sont affichés. Les prototypes de déclencheurs sont à la base des [déclencheurs](/manual/web_interface/frontend_sections/configuration/hosts/triggers) de l'hôte réel qui sont créés lors de la découverte de bas niveau. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du prototype de déclencheur, affiché sous forme de lien bleu.<br>Cliquer sur le nom ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery/trigger_prototypes) du prototype de déclencheur .<br>Si le prototype de déclencheur appartient à un modèle lié, le nom du modèle s'affiche avant le nom du déclencheur, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des prototypes de déclencheur au niveau du modèle lié.| |*Donnée opérationnelle*|Le format des données opérationnelles du déclencheur est affiché, contenant des chaînes arbitraires et des macros qui seront résolues dynamiquement dans *Surveillance* → *Problèmes*.| |*Créer activé*|Création du déclencheur basé sur ce prototype comme :<br>**Oui** - activé<br>**Non** - désactivé. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Découvrir*|Découverte du déclencheur basé sur ce prototype :<br>**Oui** - découvrir<br>**Non** - ne pas découvrir. Vous pouvez basculer entre 'Oui' et 'Non' en cliquant dessus.| |*Tags*|Les tags du prototype de déclencheur sont affichés.| Pour configurer un nouveau prototype de déclencheur, cliquez sur le bouton *Créer un prototype de déclencheur* dans le coin supérieur droit. #### Overview In this section we will perform an SNMP [discovery](/manual/discovery/low_level_discovery) on a switch. #### Overview Dans cette section, nous allons effectuer une [découverte](/manual/discovery/low_level_discovery) SNMP sur un switch. #### Overview In this section you can learn the meaning of some terms commonly used in Zabbix. #### Aperçu Dans cette section vous apprendrez la signification de certains termes couramment utilisés dans Zabbix. ### Overview In this section you can see a high-level status of whole services that have been configured in Zabbix, based on your infrastructure. A service may be a hierarchy consisting if several levels of other services, called "child" services, which are attributes to the overall status of the service (see also an overview of the [service monitoring](/manual/it_services) functionality.) The main categories of service status are *OK* or *Problem*, where the *Problem* status is expressed by the corresponding problem severity name and color. While the view mode allows to monitor services with their status and other details, you can also configure the service hierarchy in this section (add/edit services, child services) by switching to the edit mode. To switch from the view to the edit mode (and back) click on the respective button in the upper right corner: -  - view services -  - add/edit services, and child services Note that access to editing depends on [user role](/manual/web_interface/frontend_sections/administration/user_roles) settings. ### Aperçu Dans cette section, vous pouvez voir un état de haut niveau de l'ensemble des services qui ont été configurés dans Zabbix, en fonction de votre infrastructure. Un service peut être une hiérarchie composée de plusieurs niveaux d'autres services, appelés services "enfants", qui sont des attributs de l'état global du service (voir également un aperçu de la fonctionnalité [surveillance des services](/manual/it_services).) Les principales catégories d'état de service sont *OK* ou *Problème*, où l'état *Problème* est exprimé par le nom et la couleur de la gravité du problème correspondant. Alors que le mode d'affichage permet de surveiller les services avec leur statut et d'autres détails, vous pouvez également configurer la hiérarchie des services dans cette section (ajouter/modifier des services, services enfants) en passant en mode d'édition. Pour passer de la vue au mode édition (et retour), cliquez sur le bouton correspondant dans le coin supérieur droit : -  - voir les services -  - ajouter/modifier des services et des services enfants Notez que l'accès à la modification dépend des paramètres de [rôle utilisateur](/manual/web_interface/frontend_sections/administration/user_roles). ### Overview In this section you can see a high-level status of whole services that have been configured in Zabbix, based on your infrastructure. A service may be a hierarchy consisting of several levels of other services, called "child" services, which are attributes to the overall status of the service (see also an overview of the [service monitoring](/manual/it_services) functionality.) The main categories of service status are *OK* or *Problem*, where the *Problem* status is expressed by the corresponding problem severity name and color. While the view mode allows to monitor services with their status and other details, you can also [configure](/manual/it_services/service) the service hierarchy in this section (add/edit services, child services) by switching to the edit mode. To switch from the view to the edit mode (and back) click on the respective button in the upper right corner: -  - view services -  - add/edit services, and child services Note that access to editing depends on [user role](/manual/web_interface/frontend_sections/administration/user_roles) settings. ### Aperçu Dans cette section, vous pouvez voir un état de haut niveau de l'ensemble des services qui ont été configurés dans Zabbix, en fonction de votre infrastructure. Un service peut être une hiérarchie composée de plusieurs niveaux d'autres services, appelés services "enfants", qui sont des attributs de l'état général du service (voir également une présentation de la fonctionnalité [surveillance des services](/manual/it_services)). Les principales catégories d'état de service sont *OK* ou *Problème*, où l'état *Problème* est exprimé par le nom et la couleur de la gravité du problème correspondant. Alors que le mode d'affichage permet de surveiller les services avec leur statut et d'autres détails, vous pouvez également [configurer](/manual/it_services/service) la hiérarchie des services dans cette section (ajouter/modifier des services, services enfants) en passant en mode édition . Pour passer de la vue au mode édition (et inversement), cliquez sur le bouton correspondant dans le coin supérieur droit : -  - voir les services -  - ajouter/modifier des services et des services enfants Notez que l'accès à la modification dépend des paramètres de [rôle d'utilisateur](/manual/web_interface/frontend_sections/administration/user_roles). ### Overview In this section you can see a high-level status of whole services that have been configured in Zabbix, based on your infrastructure. A service may be a hierarchy consisting of several levels of other services, called "child" services, which are attributes to the overall status of the service (see also an overview of the [service monitoring](/manual/it_services) functionality.) The main categories of service status are *OK* or *Problem*, where the *Problem* status is expressed by the corresponding problem severity name and color. While the view mode allows to monitor services with their status and other details, you can also [configure](/manual/web_interface/frontend_sections/services/service#editing-services) the service hierarchy in this section (add/edit services, child services) by switching to the edit mode. To switch from the view to the edit mode (and back) click on the respective button in the upper right corner: -  - view services -  - add/edit services, and child services Note that access to editing depends on [user role](/manual/web_interface/frontend_sections/administration/user_roles) settings. ### Aperçu Dans cette section, vous pouvez voir un état de haut niveau de l'ensemble des services qui ont été configuré dans Zabbix, en fonction de votre infrastructure. Un service peut être une hiérarchie composée de plusieurs niveaux d'autres services, services dits "enfants", qui sont des attributs de l'état global du service (voir également un aperçu de la fonctionnalité [surveillance de service](/manual/it_services).) Les principales catégories d'état de service sont *OK* ou *Problème*, où l'état *Problème* est exprimé par le nom et la couleur de la gravité du problème correspondant. Alors que le mode d'affichage permet de surveiller les services avec leur statut et d'autres détails, vous pouvez également [configurer](/manual/web_interface/frontend_sections/services/service#editing-services) la hiérarchie des services dans cette section (ajouter/modifier des services, services enfants) en passant en mode édition. Pour passer de la vue au mode d'édition (et retour), cliquez sur le bouton correspondant dans le coin supérieur droit : -  - voir les services -  - ajouter/modifier des services et des services enfants Notez que l'accès à l'édition dépend de [rôle d'utilisateur](/manual/web_interface/frontend_sections/administration/user_roles) paramètres. #### Overview In this section you may find some details of [additional operations](/manual/config/notifications/action/operation) for discovery/autoregistration events. #### Aperçu Dans cette section, vous trouverez quelques détails sur des [opérations supplémentaires](/fr/manual/config/notifications/action/operation) pour les événements de découverte/enregistrement automatique. #### Overview In this section, you will learn how to log in and set up a system user in Zabbix. #### Aperçu Dans cette section vous apprendrez comment vous identifier et configurer un utilisateur système dans Zabbix. #### Overview In this section you will learn how to set up a new host. A host in Zabbix is a networked entity (physical, virtual) that you wish to monitor. The definition of what can be a "host" in Zabbix is quite flexible. It can be a physical server, a network switch, a virtual machine or some application. #### Aperçu Dans cette section, vous apprendrez comment configurer un nouvel hôte. Un hôte dans Zabbix est une entité en réseau (physique, virtuelle) que vous souhaitez superviser. La définition de ce qui peut être un "hôte" dans Zabbix est assez flexible. Il peut s'agir d'un serveur physique, d'un commutateur réseau, d'une machine virtuelle ou d'une application. #### Overview In this section, you will learn how to set up an item. Items are the basis of gathering data in Zabbix. Without items, there is no data - because only an item defines a single metric or what kind of data to collect from a host. #### Aperçu Dans cette section, vous apprendrez à configurer un élément. Les éléments sont à la base de la collecte de données dans Zabbix. Sans éléments, il n'y a pas de données, car seul un élément définit une seule métrique ou le type de données à collecter auprès d'un hôte. #### Overview In this section you will learn how to set up a template. Previously we learned how to set up an item, a trigger and how to get a problem notification for the host. While all of these steps offer a great deal of flexibility in themselves, it may appear like a lot of steps to take if needed for, say, a thousand hosts. Some automation would be handy. This is where templates come to help. Templates allow to group useful items, triggers and other entities so that those can be reused again and again by applying to hosts in a single step. When a template is linked to a host, the host inherits all entities of the template. So, basically a pre-prepared bunch of checks can be applied very quickly. #### Aperçu Dans cette section, vous allez apprendre comment configurer un modèle. Précédemment nous avons appris comment configurer un élément, un déclencheur et comment recevoir une notification de problème pour un hôte. Bien que toutes ces étapes offrent une grande souplesse en elles-mêmes, il peut sembler nécessaire de prendre de nombreuses mesures pour, par exemple, un millier d\'hôtes. Une certaine automatisation serait pratique. C\'est là que les modèles viennent en aide. Les modèles permettent de regrouper les éléments utiles, les déclencheurs et d\'autres entités afin que ceux-ci puissent être réutilisés à plusieurs reprises en l\'appliquant aux hôtes en une seule étape. Lorsqu\'un modèle est lié à un hôte, l\'hôte hérite de toutes les entités du modèle. Donc, une poignée de vérifications préparées à l\'avance peut être appliquée très rapidement. #### Overview In this section you will learn how to set up a trigger. Items only collect data. To automatically evaluate incoming data we need to define triggers. A trigger contains an expression that defines a threshold of what is an acceptable level for the data. If that level is surpassed by the incoming data, a trigger will "fire" or go into a 'Problem' state - letting us know that something has happened that may require attention. If the level is acceptable again, trigger returns to an 'Ok' state. #### Aperçu Dans cette section, vous apprendrez comment configurer un déclencheur. Seuls les éléments collectent les données. Pour évaluer automatiquement les données entrantes nous avons besoin de définir un déclencheur. Un déclencheur contient une expression qui défini un seuil de niveau de données acceptable. Si ce niveau est dépassé par la données entrante, un déclencheur s’activera pour passera en état de ‘problème’ – pour nous faire savoir qu'il s'est passé quelque chose qui pourrait nécessiter de l'attention. Si le niveau est de nouveau acceptable, le déclencheur revient à l'état 'Ok'. #### Overview In this widget you can display current problems. The information in this widget is similar to *Monitoring* → *Problems*. #### Aperçu Dans ce widget, vous pouvez afficher les problèmes actuels. Les informations de ce widget sont similaires à *Surveillance* → *Problèmes*. #### Overview In this widget, you can display problems by severity. You can limit what hosts and triggers are displayed in the widget and define how the problem count is displayed. #### Aperçu Dans ce widget, vous pouvez afficher les problèmes par sévérité. Vous pouvez limiter les hôtes et les déclencheurs affichés dans le widget et définir le mode d'affichage du nombre de problèmes. ### Overview In Zabbix 6.0, [service monitoring](/manual/it_services) functionality has been reworked significantly (see [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction/whatsnew600#services) for the list of changes). This page describes how services and SLAs, defined in earlier Zabbix versions, are changed during an upgrade to Zabbix 6.0 or newer. ### Aperçu Dans Zabbix 6.0, la fonctionnalité [surveillance des services](/manual/it_services) a été retravaillée de manière significative (voir [Quoi de neuf dans Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction /whatsnew600#services) pour la liste des modifications). Cette page décrit comment les services et les SLA, définis dans les versions antérieures de Zabbix, sont modifiés lors d'une mise à niveau vers Zabbix 6.0 ou une version plus récente. #### Overview Item types cover various methods of acquiring data from your system. Each item type comes with its own set of supported item keys and required parameters. The following items types are currently offered by Zabbix: - [Zabbix agent checks](/manual/config/items/itemtypes/zabbix_agent) - [SNMP agent checks](/manual/config/items/itemtypes/snmp) - [SNMP traps](/manual/config/items/itemtypes/snmptrap) - [IPMI checks](/manual/config/items/itemtypes/ipmi) - [Simple checks](/manual/config/items/itemtypes/simple_checks) - [VMware monitoring](/manual/config/items/itemtypes/simple_checks/vmware_keys) - [Log file monitoring](/manual/config/items/itemtypes/log_items) - [Calculated items](/manual/config/items/itemtypes/calculated) - [Aggregate calculations](/manual/config/items/itemtypes/calculated/aggregate) - [Zabbix internal checks](/manual/config/items/itemtypes/internal) - [SSH checks](/manual/config/items/itemtypes/ssh_checks) - [Telnet checks](/manual/config/items/itemtypes/telnet_checks) - [External checks](/manual/config/items/itemtypes/external) - [Trapper items](/manual/config/items/itemtypes/trapper) - [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) - [ODBC checks](/manual/config/items/itemtypes/odbc_checks) - [Dependent items](/manual/config/items/itemtypes/dependent_items) - [HTTP checks](/manual/config/items/itemtypes/http) - [Prometheus checks](/manual/config/items/itemtypes/prometheus) - [Script items](/manual/config/items/itemtypes/script) Details for all item types are included in the subpages of this section. Even though item types offer a lot of options for data gathering, there are further options through [user parameters](/manual/config/items/userparameters) or [loadable modules](/manual/config/items/loadablemodules). Some checks are performed by Zabbix server alone (as agent-less monitoring) while others require Zabbix agent or even Zabbix Java gateway (with JMX monitoring). ::: noteimportant If a particular item type requires a particular interface (like an IPMI check needs an IPMI interface on the host) that interface must exist in the host definition. ::: Multiple interfaces can be set in the host definition: Zabbix agent, SNMP agent, JMX and IPMI. If an item can use more than one interface, it will search the available host interfaces (in the order: Agent→SNMP→JMX→IPMI) for the first appropriate one to be linked with. All items that return text (character, log, text types of information) can return whitespace only as well (where applicable) setting the return value to an empty string (supported since 2.0). #### Aperçu Les types d'élément couvrent diverses méthodes d'acquisition de données à partir de votre système. Chaque type d'élément est fourni avec son propre ensemble de clés d'élément prises en charge et de paramètres requis. Les types d'élément suivants sont actuellement proposés par Zabbix : - [Vérifications d'agent Zabbix](/manual/config/items/itemtypes/zabbix_agent) - [Vérifications d'agent SNMP](/manual/config/items/itemtypes/snmp) - [Traps SNMP](/manual/config/items/itemtypes/snmptrap) - [Vérifications IPMI](/manual/config/items/itemtypes/ipmi) - [Vérifications simples](/manual/config/items/itemtypes/simple_checks) - [Surveillance VMware](/manual/config/items/itemtypes/simple_checks/vmware_keys) - [Surveillance des fichiers journaux](/manual/config/items/itemtypes/log_items) - [Éléments calculés](/manual/config/items/itemtypes/calculated) - [Calculs agrégés](/manual/config/items/itemtypes/calculated/aggregate) - [Vérifications internes de Zabbix](/manual/config/items/itemtypes/internal) - [Vérifications SSH](/manual/config/items/itemtypes/ssh_checks) - [Vérifications Telnet](/manual/config/items/itemtypes/telnet_checks) - [Vérifications externes](/manual/config/items/itemtypes/external) - [Éléments trapper](/manual/config/items/itemtypes/trapper) - [Surveillance JMX](/manual/config/items/itemtypes/jmx_monitoring) - [Vérifications ODBC](/manual/config/items/itemtypes/odbc_checks) - [Éléments dépendants](/manual/config/items/itemtypes/dependent_items) - [Vérifications HTTP](/manual/config/items/itemtypes/http) - [Vérifications Prometheus](/manual/config/items/itemtypes/prometheus) - [Éléments script](/manual/config/items/itemtypes/script) Les détails de tous les types d'éléments sont inclus dans les sous-pages de cette section. Même si les types d'éléments offrent de nombreuses options pour la collecte de données, il existe d'autres options via les [paramètres utilisateur](/manual/config/items/userparameters) ou les [modules chargeables](/manual/config/items/loadablemodules). Certaines vérifications sont effectuées par le serveur Zabbix seul (en tant que surveillance sans agent) tandis que d'autres nécessitent un agent Zabbix ou même une passerelle Java Zabbix (avec surveillance JMX). ::: noteimportant Si un type d'élément particulier nécessite une interface particulière (par exemple, une vérification IPMI nécessite une interface IPMI sur l'hôte), cette interface doit exister dans la définition de l'hôte. ::: Plusieurs interfaces peuvent être définies dans la définition d'hôte : agent Zabbix, agent SNMP, JMX et IPMI. Si un élément peut utiliser plus d'une interface, il recherchera parmi les interfaces hôtes disponibles (dans l'ordre : Agent→SNMP→JMX→IPMI) la première interface appropriée à lier. Tous les éléments qui renvoient du texte (caractère, journal, types d'informations textuelles) peuvent également renvoyer uniquement des espaces blancs (le cas échéant) en définissant la valeur de retour sur une chaîne vide (prise en charge depuis la version 2.0). #### Overview It is possible to allow active Zabbix agent autoregistration, after which the server can start monitoring them. This way new hosts can be added for monitoring without configuring them manually on the server. Autoregistration can happen when a previously unknown active agent asks for checks. The feature might be very handy for automatic monitoring of new Cloud nodes. As soon as you have a new node in the Cloud Zabbix will automatically start the collection of performance and availability data of the host. Active agent autoregistration also supports the monitoring of added hosts with passive checks. When the active agent asks for checks, providing it has the 'ListenIP' or 'ListenPort' configuration parameters defined in the configuration file, these are sent along to the server. (If multiple IP addresses are specified, the first one is sent to the server.) Server, when adding the new autoregistered host, uses the received IP address and port to configure the agent. If no IP address value is received, the one used for the incoming connection is used. If no port value is received, 10050 is used. It is possible to specify that the host should be autoregistered with a [DNS name](#using_dns_as_default_interface) as the default agent interface. Autoregistration is rerun: - if host [metadata](#using_host_metadata) information changes: - due to HostMetadata changed and agent restarted - due to value returned by HostMetadataItem changed - for manually created hosts with metadata missing - if a host is manually changed to be monitored by another Zabbix proxy - if autoregistration for the same host comes from a new Zabbix proxy #### Aperçu Il est possible d'autoriser l'enregistrement automatique d'agents Zabbix actifs, après quoi le serveur pourra commencer à les surveiller. De cette façon, de nouveaux hôtes peuvent être ajoutés pour la surveillance sans les configurer manuellement sur le serveur. L'enregistrement automatique peut se produire lorsqu'un agent actif précédemment inconnu demande des vérifications. Cette fonctionnalité peut s'avérer très pratique pour la supervision automatique de nouveaux nœuds Cloud. Dès que vous avez un nouveau nœud dans le cloud, Zabbix lance automatiquement la collecte des données de performance et de disponibilité de l'hôte. L'enregistrement automatique des agents actifs prend également en charge la surveillance des hôtes ajoutés avec des vérifications passives. Lorsque l'agent actif demande des vérifications, à condition qu'il dispose des paramètres de configuration 'ListenIP' ou 'ListenPort' définis dans le fichier de configuration, celles-ci sont envoyées au serveur. (Si plusieurs adresses IP sont spécifiées, la première est envoyée au serveur.) Le serveur, lors de l'ajout du nouvel hôte enregistré automatiquement, utilise l'adresse IP et le port reçus pour configurer l'agent. Si aucune valeur d'adresse IP n'est reçue, celle utilisée pour la connexion entrante est utilisée. Si aucune valeur de port n'est reçue, 10050 est utilisé. Il est possible de spécifier que l'hôte doit être enregistré automatiquement avec un [nom DNS](#using_dns_as_default_interface) comme interface d'agent par défaut. L'enregistrement automatique est relancé : - si les [metadonnées](#using_host_metadata) de l'hôte changent : - en raison de la modification de HostMetadata et du redémarrage de l'agent - en raison de la valeur modifiée renvoyée par HostMetadataItem - pour les hôtes créés manuellement avec des métadonnées manquantes - si un hôte est modifié manuellement pour être surveillé par un autre proxy Zabbix - si l'enregistrement automatique pour le même hôte provient d'un nouveau proxy Zabbix #### Overview It is possible to automatically discover IPMI sensors. To do that, you may use a combination of: - the `ipmi.get` IPMI item (supported since Zabbix **5.0.0**) as the master item - dependent low-level discovery rule and item prototypes #### Aperçu Il est possible de découvrir automatiquement les capteurs IPMI. Pour ce faire, vous pouvez utiliser une combinaison de : - l'élément IPMI `ipmi.get` (supporté depuis Zabbix **5.0.0**) comme élément maître - règle de découverte de bas niveau dépendante et prototypes d'éléments #### Overview It is possible to create custom rules regarding the times when an item is checked. The two methods for that are *Flexible intervals*, which allow to redefine the default update interval, and *Scheduling*, whereby an item check can be executed at a specific time or sequence of times. #### Aperçu Il est possible de créer des règles personnalisées concernant le temps où un élément est vérifié. Les deux méthodes pour cela sont les *intervalles flexibles*, qui permettent de redéfinir l'intervalle de mise à jour par défaut, et la *planification*, grâce à laquelle une vérification d'élément peut être exécutée à un moment ou une séquence de temps spécifique. #### Overview It is possible to define that an action is executed only if the event matches a defined set of conditions. Conditions are set when configuring the [action](/manual/config/notifications/action#configuring_an_action). Condition matching is case-sensitive. #### Aperçu Il est possible de définir qu'une action est exécutée uniquement si l'événement correspond à un ensemble défini de conditions. Les conditions sont définies lors de la configuration de l'[action](/manual/config/notifications/action#configuring_an_action). La correspondance des conditions est sensible à la casse. #### Overview It is possible to [discover](/manual/discovery/low_level_discovery) all interfaces configured in Zabbix frontend for a host. #### Aperçu Il est possible de [découvrir](/manual/discovery/low_level_discovery) toutes les interfaces configurées dans l'interface web de Zabbix pour un hôte. #### Overview It is possible to [discover](/manual/discovery/low_level_discovery) all JMX MBeans or MBean attributes or to specify a pattern for the discovery of these objects. It is mandatory to understand the difference between an MBean and MBean attributes for discovery rule configuration. An MBean is an object which can represent a device, an application, or any resource that needs to be managed. For example, there is an MBean which represents a web server. Its attributes are connection count, thread count, request timeout, http file cache, memory usage, etc. Expressing this thought in human comprehensive language we can define a coffee machine as an MBean which has the following attributes to be monitored: water amount per cup, average consumption of water for a certain period of time, number of coffee beans required per cup, coffee beans and water refill time, etc. #### Aperçu Il est possible de [découvrir](/manual/discovery/low_level_discovery) tous les attributs MBeans ou MBean JMX ou de spécifier un modèle pour la découverte de ces objets. Il est indispensable de comprendre la différence entre Mbean et les attributs Mbean pour la configuration des règles de découverte. Un MBean est un objet pouvant représenter un périphérique, une application ou toute ressource devant être gérée. Par exemple, il existe un Mbean qui représente un serveur Web. Ses attributs sont : nombre de connexions, nombre de threads, délai de requête, cache de fichier http, utilisation de la mémoire, etc. En exprimant cette pensée en langage humain compréhensif, nous pouvons définir une machine à café comme un Mbean dont les attributs à surveiller sont les suivants : quantité d'eau par tasse, consommation moyenne d'eau pendant une certaine période, nombre de grains de café requis par tasse, grains de café et temps de remplissage en eau, etc. ### Overview It is possible to [discover](/manual/discovery/low_level_discovery) systemd units (services, by default) with Zabbix. ### Aperçu Il est possible de [découvrir](/manual/discovery/low_level_discovery) des unités systemd (services, par défaut) avec Zabbix. #### Overview It is possible to enhance Zabbix frontend functionality by adding 3rd party modules or by developing your own modules without the need to change the source code of Zabbix. Note that the module code will run with the same privileges as Zabbix source code. This means: - 3rd party modules can be harmful. You must trust the modules you are installing; - Errors in a 3rd party module code may crash the frontend. If this happens, just remove the module code from the frontend. As soon as you reload Zabbix frontend, you'll see a note saying that some modules are absent. Go to [Module administration](/manual/web_interface/frontend_sections/administration/general#modules) (in *Administration* → *General* → *Modules*) and click *Scan directory* again to remove non-existent modules from the database. #### Aperçu Il est possible d'améliorer la fonctionnalité frontale de Zabbix en ajoutant des modules tiers ou en développant vos propres modules sans avoir à modifier le code source de Zabbix. Notez que le code du module s'exécutera avec les mêmes privilèges que le code source Zabbix. Ça signifie: - Les modules tiers peuvent être dangereux. Vous devez faire confiance aux modules que vous installez ; - Des erreurs dans le code d'un module tiers peuvent faire planter l'interface. Si cela se produit, supprimez simplement le code du module de l'interface. Dès que vous rechargez l'interface Zabbix, vous verrez une note indiquant que certains modules sont absents. Allez dans [Administration du module](/manual/web_interface/frontend_sections/administration/general#modules) (dans *Administration* → *Général* → *Modules*) et cliquez à nouveau sur *Scanner le répertoire* pour supprimer les modules inexistants de la base de données . #### Overview It is possible to make some internal metrics of Zabbix server and proxy accessible remotely by another Zabbix instance or a third party tool. This can be useful so that supporters/service providers can monitor their client Zabbix servers/proxies remotely or, in organizations where Zabbix is not the main monitoring tool, that Zabbix internal metrics can be monitored by a third party system in an umbrella-monitoring setup. Zabbix internal stats are exposed to a configurable set of addresses listed in the new 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter. Requests will be accepted only from these addresses. #### Aperçu Il est possible de rendre quelques métriques internes du serveur et du proxy Zabbix accessibles à distance par une autre instance Zabbix ou un outil tiers. Cela peut être utile pour que les services de supports ou de fournisseurs puissent surveiller les serveurs/proxy Zabbix à distance ou, dans les organisations où Zabbix n'est pas le principal outil de surveillance, pour que les métriques internes de Zabbix puissent être surveillées par un système tiers dans une configuration de surveillance parapluie. Les statistiques internes de Zabbix sont exposées à un ensemble configurable d'adresses listé dans le nouveau paramètre [serveur](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 'StatsAllowedIP'. Les demandes seront acceptées uniquement à partir de ces adresses. #### Overview It is possible to store some sensitive information secretly in HashiCorp Vault KV Secrets Engine - Version 2. Secrets can be saved for: - user macro values - database access credentials Zabbix provides read-only access to the secrets in Vault, assuming that secrets are managed by someone else. #### Aperçu Il est possible de stocker secrètement certaines informations sensibles dans HashiCorp Vault KV Secrets Engine - Version 2. Les secrets peuvent être enregistrés pour : - les valeurs de macro utilisateur - les identifiants d'accès à la base de données Zabbix fournit un accès en lecture seule aux secrets de Vault, en supposant que les secrets sont gérés par quelqu'un d'autre. #### Overview It is very important to have Zabbix system properly tuned for maximum performance. #### Aperçu Il est très important que le système Zabbix soit correctement réglé pour des performances optimales. #### Overview JMX monitoring can be used to monitor JMX counters of a Java application. JMX monitoring has native support in Zabbix in the form of a Zabbix daemon called "Zabbix Java gateway", introduced since Zabbix 2.0. To retrieve the value of a particular JMX counter on a host, Zabbix server queries the Zabbix **Java gateway**, which in turn uses the [JMX management API](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/) to query the application of interest remotely. For more details and setup see the [Zabbix Java gateway](/manual/concepts/java) section. ::: notewarning Communication between Java gateway and the monitored JMX application should not be firewalled. ::: #### Aperçu La supervision JMX peut être utilisée pour surveiller les compteurs JMX d'une application Java. La supervision JMX a un support natif sous Zabbix sous la forme d'un démon Zabbix appelé "Zabbix Java gateway", introduit depuis Zabbix 2.0. Pour récupérer la valeur d'un compteur JMX particulier sur un hôte, le serveur Zabbix interroge la **passerelle Java** Zabbix, qui à son tour utilise l'[API de gestion JMX](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/) pour interroger l'application à distance. Pour plus de détails et des informations sur l'installation, voir la section de la [passerelle Java Zabbix](/manual/concepts/java). ::: notewarning La communication entre la passerelle Java et l'application JMX surveillée ne doit pas passée par un pare-feu. ::: #### Overview Kerberos authentication can be used in web monitoring and HTTP items in Zabbix since version 4.4.0. This section describes an example of configuring Kerberos with Zabbix server to perform web monitoring of `www.example.com` with user 'zabbix'. #### Aperçu L'authentification Kerberos peut être utilisée dans la surveillance Web et les éléments HTTP dans Zabbix depuis la version 4.4.0. Cette section décrit un exemple de configuration de Kerberos avec le serveur Zabbix pour effectuer la surveillance Web de `www.example.com` avec l'utilisateur 'zabbix'. #### Overview Linking is a process whereby templates are applied to hosts, whereas unlinking removes the association with the template from a host. ::: noteimportant Templates are linked directly to individual hosts and not to host groups. Simply adding a template to a host group will not link it. Host groups are used only for logical grouping of hosts and templates. ::: #### Aperçu La liaison est un processus par lequel les modèles sont appliqués aux hôtes, tandis que la suppression de la liaison supprime l'association avec le modèle d'un hôte. ::: note importante Les modèles sont liés directement à des hôtes individuels et non à des groupes d'hôtes. Ajouter simplement un modèle à un groupe hôte ne le liera pas. Les groupes d'hôtes ne sont utilisés que pour le regroupement logique d'hôtes et de modèles ::: #### Overview Media types are [exported](/manual/xml_export_import) with all related objects and object relations. #### Aperçu Les types de média sont [exportés](/manual/xml_export_import) avec tous les objets et relations d'objet associés. #### Overview Most Zabbix web interface pages support various HTTP GET parameters that control what will be displayed. They may be passed by specifying parameter=value pairs after the URL, separated from the URL by a question mark (?) and from each other by ampersands (&). #### Aperçu La plupart des pages de l'interface Web Zabbix prennent en charge divers paramètres HTTP GET qui contrôlent ce qui sera affiché. Ils peuvent être passés en spécifiant des paires paramètre=valeur après l'URL, séparés de l'URL par un point d'interrogation (?) et les uns des autres par des esperluettes (&). #### Overview Nesting is a way of one template encompassing one or more other templates. As it makes sense to separate out entities on individual templates for various services, applications, etc., you may end up with quite a few templates all of which may need to be linked to quite a few hosts. To simplify the picture, it is possible to link some templates together in a single template. The benefit of nesting is that you have to link only one template ("nest", parent template) to the host and the host will inherit all entities of the linked templates ("nested", child templates) automatically. For example, if we link templates T1 and T2 to template T3, we supplement T3 with entities from T1 and T2, and not vice versa. If we link template A to templates B and C, we supplement B and C with entities from A. #### Aperçu L'imbrication est un moyen d'englober un modèle dans un ou plusieurs autres modèles. Comme il est logique de séparer les entités sur des modèles individuels pour divers services, applications, etc., vous pouvez vous retrouver avec un certain nombre de modèles qui peuvent tous devoir être liés à un certain nombre d'hôtes. Pour simplifier l'image, il est possible de lier certains modèles ensemble dans un seul modèle. L'avantage de l'imbrication est que vous n'avez à lier qu'un seul modèle (« imbriqué », modèle parent) à l'hôte et l'hôte héritera automatiquement de toutes les entités des modèles liés (« imbriqués », modèles enfants). Par exemple, si nous lions les modèles T1 et T2 au modèle T3, nous complétons T3 avec des entités de T1 et T2, et non l'inverse. Si nous lions le modèle A aux modèles B et C, nous complétons B et C avec des entités de A. #### Overview Network map [export](/manual/xml_export_import) contains: - all related images - map structure - all map settings, all contained elements with their settings, map links and map link status indicators ::: notewarning Any host groups, hosts, triggers, other maps or other elements that may be related to the exported map are not exported. Thus, if at least one of the elements the map refers to is missing, importing it will fail. ::: Network map export/import is supported since Zabbix 1.8.2. #### Aperçu [L'exportation](/manual/xml_export_import) des cartes réseau contient : - Toutes les images liées - La structure de la carte - tous les paramètres de carte, tous les éléments contenus avec leurs paramètres, liens de carte et indicateurs d'état de lien de carte ::: notewarning Les groupes d'hôtes, hôtes, déclencheurs, autres cartes ou tout autre élément pouvant être lié à la carte exportée ne sont pas exportés. Ainsi, si au moins un des éléments mentionnés dans la carte est manquant, son importation échouera. ::: L'exportation/importation de cartes réseau est supporté depuis Zabbix 1.8.2. #### Overview ODBC monitoring corresponds to the *Database monitor* item type in the Zabbix frontend. ODBC is a C programming language middle-ware API for accessing database management systems (DBMS). The ODBC concept was developed by Microsoft and later ported to other platforms. Zabbix may query any database, which is supported by ODBC. To do that, Zabbix does not directly connect to the databases, but uses the ODBC interface and drivers set up in ODBC. This function allows for more efficient monitoring of different databases for multiple purposes - for example, checking specific database queues, usage statistics and so on. Zabbix supports unixODBC, which is one of the most commonly used open source ODBC API implementations. ::: noteimportant See also the [known issues](/manual/installation/known_issues#odbc_checks) for ODBC checks. ::: #### Aperçu La surveillance ODBC correspond au type d'élément *surveillance de base de donées* dans l'interface Zabbix. ODBC est une API intermédiaire en langage de programmation C permettant d'accéder aux systèmes de gestion de base de données (SGBD). Le concept ODBC a été développé par Microsoft et plus tard porté sur d'autres plates-formes. Zabbix peut interroger n'importe quelle base de données prise en charge par ODBC. Pour ce faire, Zabbix ne se connecte pas directement aux bases de données, mais utilise l'interface ODBC et les pilotes configurés dans ODBC. Cette fonction permet une surveillance plus efficace de différentes bases de données à des fins multiples - par exemple, la vérification de files d'attente de bases de données spécifiques, les statistiques d'utilisation, etc. Zabbix prend en charge unixODBC, qui est l'une des implémentations d'API ODBC open source les plus couramment utilisées. ::: noteimportant Consultez également les [problèmes connus](/manual/installation/known_issues#odbc_checks) pour les vérifications ODBC. ::: ### Overview Official Zabbix packages are available for: | | | |---|---| |Debian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11&components=server_frontend_agent&db=mysql&ws=apache)| |Debian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 22.04 (Jammy Jellyfish) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 20.04 (Focal Fossa) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04&components=server_frontend_agent&db=mysql&ws=apache)| |Raspbian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11&components=server_frontend_agent&db=mysql&ws=apache)| |Raspbian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10&components=server_frontend_agent&db=mysql&ws=apache)| Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support. Additionally, Zabbix agent packages are available for [Ubuntu 16.04](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04&components=agent&db=&ws=) and [Ubuntu 14.04](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04&components=agent&db=&ws=). ### Aperçu Les packages officiels Zabbix sont disponibles pour : | | | |---|---| |Debian 11 (Bullseye)|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11&components=server_frontend_agent&db=mysql&ws=apache)| |Debian 10 (Buster)|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 22.04 (Jammy Jellyfish) LTS|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 20.04 (Focal Fossa) LTS|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04&components=server_frontend_agent&db=mysql&ws=apache)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04&components=server_frontend_agent&db=mysql&ws=apache)| |Raspbian 11 (Bullseye)|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11&components=server_frontend_agent&db=mysql&ws=apache)| |Raspbian 10 (Buster)|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10&components=server_frontend_agent&db=mysql&ws=apache)| Les packages sont disponibles avec la prise en charge de la base de données MySQL/PostgreSQL et du serveur Web Apache/Nginx. De plus, les packages d'agent Zabbix sont disponibles pour [Ubuntu 16.04](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04&components=agent&db=&ws=) et [Ubuntu 14.04](https:// www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04&components=agent&db=&ws=). ### Overview Official Zabbix packages are available for: | | | |---|---| |RHEL 8, CentOS 8 and Oracle Linux 8|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=9&components=server_frontend_agent&db=mysql&ws=apache)| Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support. *Zabbix agent* packages and utilities *Zabbix get* and *Zabbix sender* are available for [RHEL 7](https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/), [RHEL 6](https://repo.zabbix.com/zabbix/6.0/rhel/6/x86_64/) and [RHEL 5](https://repo.zabbix.com/zabbix/6.0/rhel/5/x86_64) as well. Zabbix official repository provides fping and libssh2 packages as well. These packages are located in the [non-supported](https://repo.zabbix.com/non-supported/) directory. ### Aperçu Les packages officiels Zabbix sont disponibles pour : | | | |---|---| |RHEL 8, CentOS 8 et Oracle Linux 8|[Télécharger](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=9&components=server_frontend_agent&db=mysql&ws=apache)| Les packages sont disponibles avec la prise en charge de la base de données MySQL/PostgreSQL et du serveur Web Apache/Nginx. Les packages et utilitaires *Agent Zabbix* *Zabbix get* et *Zabbix sender* sont disponibles pour [RHEL 7](https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/), [RHEL 6] (https://repo.zabbix.com/zabbix/6.0/rhel/6/x86_64/) et [RHEL 5](https://repo.zabbix.com/zabbix/6.0/rhel/5/x86_64) aussi . Le dépôt officiel Zabbix fournit également les packages fping et libssh2. Ces packages se trouvent dans le répertoire [non-supported](https://repo.zabbix.com/non-supported/). ### Overview Once the [services](/manual/it_services/service_tree) are created, you can start monitoring whether their performance is on track with service level agreement (SLA). *Services->SLA* menu section allows to configure SLAs for various services. An SLA in Zabbix defines service level objective (SLO), expected uptime schedule and planned downtimes. SLAs and services are matched by [service tags](/manual/it_services/service_tree#tags). The same SLA may be applied to multiple services - performance will be measured for each matching service separately. A single service may have multiple SLAs assigned - data for each of the SLAs will be displayed separately. In SLA reports Zabbix provides Service level indicator (SLI) data, which measures real service availability. Whether a service meets the SLA targets is determined by comparing SLO (expected availability in %) with SLI (real-life availability in %). ### Aperçu Une fois les [services](/manual/it_services/service_tree) créés, vous pouvez commencer à surveiller si leurs performances sont conformes au contrat de niveau de service (SLA). La section de menu *Services->SLA* permet de configurer les SLA pour divers services. Un SLA dans Zabbix définit l'objectif de niveau de service (SLO), le calendrier de disponibilité prévu et les temps d'arrêt planifiés. Les SLA et les services correspondent aux [tags de service](/manual/it_services/service_tree#tags). Le même SLA peut être appliqué à plusieurs services - les performances seront mesurées séparément pour chaque service correspondant. Un seul service peut avoir plusieurs SLA attribués - les données pour chacun des SLA seront affichées séparément. Dans les rapports SLA, Zabbix fournit des données d'indicateur de niveau de service (SLI), qui mesurent la disponibilité réelle du service. La conformité d'un service aux objectifs du SLA est déterminée en comparant le SLO (disponibilité attendue en %) au SLI (disponibilité réelle en %). ### Overview Packages for minor Zabbix version (i.e. Zabbix 6.0.x) release candidates are provided starting with Zabbix 6.0.9. The instructions below are for enabling unstable Zabbix release repositories (disabled by default). First, install or update to the latest zabbix-release package. To enable rc packages on your system do the following: ### Aperçu Les packages pour les versions candidates mineures de Zabbix (c'est-à-dire Zabbix 6.0.x) sont fournis à partir de Zabbix 6.0.9. Les instructions ci-dessous permettent d'activer les référentiels de versions instables de Zabbix (désactivés par défaut). Tout d'abord, installez ou mettez à jour le dernier package zabbix-release. Pour activer les packages rc sur votre système, procédez comme suit : #### Overview [Perl Compatible Regular Expressions](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE, PCRE2) are supported in Zabbix. There are two ways of using regular expressions in Zabbix: - manually entering a regular expression - using a global regular expression created in Zabbix #### Aperçu [Perl Compatible Regular Expressions](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE, PCRE2) sont pris en charge dans Zabbix. Il existe deux manières d'utiliser les expressions régulières dans Zabbix : - saisie manuelle d'une expression régulière - en utilisant une expression régulière globale créée dans Zabbix ### Overview Plugins provide an option to extend the monitoring capabilities of Zabbix. Plugins are written in Go programming language and are supported by Zabbix agent 2 only. Plugins provide an alternative to [loadable modules](/manual/config/items/loadablemodules) (written in C), and other methods for extending Zabbix functionality, such as [user parameters](userparameters) (agent metrics), [external checks](/manual/config/items/itemtypes/external) (agent-less monitoring), and `system.run[]` Zabbix [agent item](/manual/config/items/itemtypes/zabbix_agent). The following features are specific to Zabbix agent 2 and its plugins: - support of scheduled and flexible intervals for both passive and active checks; - task queue management with respect to schedule and task concurrency; - plugin-level timeouts; - compatibility check of Zabbix agent 2 and its plugin on start up. Since Zabbix 6.0.0, plugins don't have to be integrated into the agent 2 directly and can be added as loadable plugins, thus making the creation process of additional plugins for gathering new monitoring metrics easier. This page lists Zabbix native and loadable plugins, and describes plugin configuration principles from the user perspective. For instructions about writing your own plugins, please see [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/en/plugins). ### Aperçu Les plugins offrent une option pour étendre les capacités de surveillance de Zabbix. Les plugins sont écrits en langage de programmation Go et ne sont pris en charge que par l'agent Zabbix 2. Les plugins fournissent une alternative aux [modules chargeables](/manual/config/items/loadablemodules) (écrits en C) et à d'autres méthodes pour étendre les fonctionnalités de Zabbix, telles que les [paramètres utilisateur](userparameters) (métriques de l'agent), les [vérifications externes ](/manual/config/items/itemtypes/external) (surveillance sans agent) et l'[élément d'agent Zabbix](/manual/config/items/itemtypes/zabbix_agent) `system.run[]`. Les fonctionnalités suivantes sont spécifiques à l'agent Zabbix 2 et à ses plugins : - prise en charge d'intervalles programmés et flexibles pour les contrôles passifs et actifs ; - gestion de la file d'attente des tâches en ce qui concerne le calendrier et la simultanéité des tâches ; - délais d'attente au niveau du plugin ; - vérification de la compatibilité de l'agent Zabbix 2 et de son plugin au démarrage. Depuis Zabbix 6.0.0, les plugins n'ont pas besoin d'être intégrés directement dans l'agent 2 et peuvent être ajoutés en tant que plugins chargeables, facilitant ainsi le processus de création de plugins supplémentaires pour collecter de nouvelles métriques de surveillance. Cette page répertorie les plugins natifs et chargeables de Zabbix et décrit les principes de configuration des plugins du point de vue de l'utilisateur. Pour obtenir des instructions sur l'écriture de vos propres plugins, veuillez consulter les [Directives de développement de plugins](https://www.zabbix.com/documentation/guidelines/en/plugins). #### Overview Preprocessing allows to define transformation rules for the received item values. One or several transformations are possible before saving to the database. Transformations are executed in the order in which they are defined. Preprocessing is done by Zabbix server or proxy (if items are monitored by proxy). Note that all values passed to preprocessing are of the string type, conversion to desired value type (as defined in item configuration) is performed at the end of the preprocessing pipeline; conversions, however, may also take place if required by the corresponding preprocessing step. See [preprocessing details](/manual/config/items/preprocessing/preprocessing_details) for more technical information. See also: [Usage examples](/manual/config/items/preprocessing/examples) #### Aperçu Le prétraitement permet de définir des règles de transformation pour les valeurs des items reçus. Une ou plusieurs transformations sont possibles avant l'enregistrement dans la base de données. Les transformations sont exécutées dans l'ordre dans lequel elles sont définies. Le prétraitement est effectué par le serveur ou le proxy Zabbix (si les éléments sont surveillés par proxy). Notez que toutes les valeurs transmises au prétraitement sont de type chaîne, la conversion vers le type de valeur souhaité (tel que défini dans la configuration de l'élément) est effectuée à la fin du pipeline de prétraitement ; cependant, des conversions peuvent également avoir lieu si cela est requis par le étape de prétraitement correspondante. Voir [détails de prétraitement](/manual/config/items/preprocessing/preprocessing_details) pour plus d'informations techniques. Voir aussi : [Exemples d'utilisation](/manual/config/items/preprocessing/examples) #### Overview Problem events in Zabbix can be acknowledged by users. If a user gets notified about a problem event, they can go to Zabbix frontend, open the problem update popup window of that problem using one of the ways listed below and acknowledge the problem. When acknowledging, they can enter their comment for it, saying that they are working on it or whatever else they may feel like saying about it. This way, if another system user spots the same problem, they immediately see if it has been acknowledged and the comments so far. This way the workflow of resolving problems with more than one system user can take place in a coordinated way. Acknowledgment status is also used when defining [action operations](/manual/config/notifications/action/operation). You can define, for example, that a notification is sent to a higher level manager only if an event is not acknowledged for some time. To acknowledge events and comment on them, a user must have at least read permissions to the corresponding triggers. To change problem severity or close problem, a user must have read-write permissions to the corresponding triggers. There are **several** ways to access the problem update popup window, which allows acknowledging a problem. - You may select problems in *Monitoring* → *Problems* and then click on *Mass update* below the list - You can click in the *Ack* column showing the acknowledgment status of problems in: - *Monitoring → Dashboard* (*Problems* and *Problems by severity* widgets) - *Monitoring → Problems* - *Monitoring → Problems → Event details* The *Ack* column contains either a 'Yes' or a 'No' link, indicating an acknowledged or an unacknowledged problem respectively. Clicking on the links will take you to the problem update popup window. - You can click on an unresolved problem cell in: - *Monitoring → Dashboard* (*Trigger overview* widget) The popup menu contains an *Acknowledge* option that will take you to the problem update window. #### Aperçu Les événements problématiques dans Zabbix peuvent être acquittés par les utilisateurs. Si un utilisateur est averti d'un événement problématique, il peut accéder à l'interface Zabbix, ouvrir la fenêtre contextuelle de mise à jour du problème en utilisant l'une des méthodes répertoriées ci-dessous et acquitter le problème. Lorsqu'il acquitte, l'utilisateur peut saisir ses commentaires, indiquant qu'il travaille à la résolution du problème ou toutes autres choses qu'il pourrait avoir envie de dire. Ainsi, si un autre utilisateur détecte le même problème, il voit immédiatement s'il a déjà été acquitté et commenté. Aussi, le flux de travail pour la résolution des problèmes à plusieurs utilisateurs peut s'effectuer de manière plus coordonnée. Le statut d'acquittement est également utilisé lors de la définition des [opérations d'action](/manual/config/notifications/action/operation). Vous pouvez définir, par exemple, qu'une notification sera envoyée à un responsable de niveau supérieur uniquement si un événement n'est pas acquitté pendant un certain temps. Pour acquitter des événements et les commentés, l'utilisateur devra avoir au moins une autorisation de lecture sur le déclencheur correspondant. Pour modifier la sévérité ou fermer le problème, cet utilisateur devra avoir une autorisation en lecture-écriture sur le déclencheur correspondant. Il existe **plusieurs** manières d'accéder à la fenêtre contextuelle de mise à jour d'un problème afin de permette l'acquittement d'un problème. - Vous pouvez sélectionner les problèmes dans *Surveillance* → *Problèmes* et cliquer sur *Modification collective* en bas de la liste - Vous pouvez cliquer dans la colonne *Acquitté* indiquant le statut de l'acquittement des problèmes dans : - *Surveillance → Tableau de bord* (widgets *Problèmes* et *Problèmes par gravité*) - *Surveillance → Problèmes* - *Surveillance → Problèmes → Détails de l'événement* La colonne *Acquitté* contient un lien 'Oui' ou 'Non', indiquant respectivement un problème acquitté ou non acquitté. En cliquant sur les liens, vous accédez à l'écran de mise à jour du problème. - Vous pouvez cliquer sur la cellule d'un problème non résolu dans : - *Surveillance → Tableau de bord* (widget *Aperçu des déclencheurs*) La fenêtre contextuelle contient une option *Acquittement* qui vous dirigera vers la fenêtre contextuelle de mise à jour du problème. #### Overview Receiving notifications on unsupported items is supported since Zabbix 2.2. It is part of the concept of internal events in Zabbix, allowing users to be notified on these occasions. [Internal events](/manual/config/events/sources#internal-events) reflect a change of state: - when items go from 'normal' to 'unsupported' (and back) - when triggers go from 'normal' to 'unknown' (and back) - when low-level discovery rules go from 'normal' to 'unsupported' (and back) This section presents a how-to for **receiving notification** when an item turns unsupported. #### Aperçu La réception de notifications sur des éléments non supportés est prise en charge depuis Zabbix 2.2. Cela fait partie du concept d'événements internes à Zabbix, permettant aux utilisateurs d'être avertis à ces occasions. Les [événements internes](/manual/config/events/sources#internal-events) reflètent un changement d'état : - lorsque les éléments passent de "normal" à "non pris en charge" (et inversement) - lorsque les déclencheurs passent de "normal" à "inconnu" (et inversement) - lorsque les règles de découverte de bas niveau passent de "normales" à "non prises en charge" (et inversement) Cette section présente un guide pour **recevoir une notification** lorsqu'un élément n'est plus pris en charge. ### Overview Recovery operations allow you to be notified when problems are resolved. Both messages and remote commands are supported in recovery operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously. ### Aperçu Les opérations de récupération vous permettent d'être averti lorsque les problèmes sont résolus. Les messages et les commandes à distance sont pris en charge dans les opérations de récupération. Bien que plusieurs opérations puissent être ajoutées, l'escalade n'est pas prise en charge - toutes les opérations sont affectées à une seule étape et seront donc exécutées simultanément. #### Overview Sending a message is one of the best ways of notifying people about a problem. That is why it is one of the primary actions offered by Zabbix. #### Aperçu L'envoi d'un message est l'un des meilleurs moyens d'informer les personnes d'un problème. C'est pourquoi c'est l'une des principales actions proposées par Zabbix. #### Overview Server - proxy data exchange is based on JSON format. Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen). #### Aperçu L'échange de données serveur - proxy est basé sur le format JSON. Les messages de requête et de réponse doivent commencer par un [en-tête et une longueur des données](/manual/appendix/protocols/header_datalen). #### Overview Several configuration [parameters](/manual/appendix/config/zabbix_server) define how Zabbix server should behave when an agent check (Zabbix, SNMP, IPMI, JMX) fails and a host interface becomes unreachable. #### Aperçu Plusieurs [paramètres](/manual/appendix/config/zabbix_server) de configuration définissent le comportement du serveur Zabbix lorsqu'une vérification d'agent (Zabbix, SNMP, IPMI, JMX) échoue et qu'une interface hôte devient inaccessible. #### Overview Simple checks are normally used for remote agent-less checks of services. Note that Zabbix agent is not needed for simple checks. Zabbix server/proxy is responsible for the processing of simple checks (making external connections, etc). Examples of using simple checks: net.tcp.service[ftp,,155] net.tcp.service[http] net.tcp.service.perf[http,,8080] net.udp.service.perf[ntp] ::: noteclassic *User name* and *Password* fields in simple check item configuration are used for VMware monitoring items; ignored otherwise. ::: #### Aperçu Les vérifications simples sont normalement utilisées pour les vérifications de services à distance sans agent. Notez que l'agent Zabbix n'est pas nécessaire pour les vérifications simples. Le serveur/proxy Zabbix est responsable du traitement des vérifications simples (établissement de connexions externes, etc.). Exemples d'utilisation de vérifications simples : net.tcp.service[ftp,,155] net.tcp.service[http] net.tcp.service.perf[http,,8080] net.udp.service.perf[ntp] ::: noteclassic Les champs *Nom d'utilisateur* et *Mot de passe* dans la configuration de l'élément de vérification simple sont utilisés pour les éléments de surveillance VMware ; ignoré sinon. ::: #### Overview Simple graphs are provided for the visualization of data gathered by items. No configuration effort is required on the user part to view simple graphs. They are freely made available by Zabbix. Just go to *Monitoring → Latest data* and click on the Graph link for the respective item and a graph will be displayed. {width="600"} ::: noteclassic Simple graphs are provided for all numeric items. For textual items, a link to History is available in *Monitoring → Latest data*. ::: #### Aperçu Des graphiques simples sont fournis pour la visualisation des données recueillies par les éléments. Aucun effort de configuration n'est requis de la part de l'utilisateur pour visualiser des graphiques simples. Ils sont librement mis à disposition par Zabbix. Allez simplement dans *Surveillance → Dernières données* et cliquez sur le lien Graphique de l'élément souhaité et un graphique s'affichera. {width="600"} ::: noteclassic Des graphiques simples sont fournis pour tous les éléments numériques. Pour les éléments textuels, un lien vers l'Historique est disponible dans *Surveillance → Dernières données*. ::: #### Overview Some new items are automatically added for monitoring when web scenarios are created. All items inherit tags from the web scenario. #### Aperçu Certains nouveaux éléments sont automatiquement ajoutés pour la supervision lors de la création de scénarios Web. Tous les éléments héritent des tags du scénario Web. #### Overview Sometimes there are signs of the upcoming problem. These signs can be spotted so that actions may be taken in advance to prevent or at least minimize the impact of the problem. Zabbix has tools to predict the future behavior of the monitored system based on historic data. These tools are realized through predictive trigger functions. #### Aperçu Parfois, il y a des signes du problème à venir. Ces signes peuvent être repérés afin que des actions puissent être prises à l'avance pour prévenir ou au moins minimiser l'impact du problème. Zabbix dispose d’outils permettant de prédire le comportement futur du système supervisé sur la base de données historiques. Ces outils sont exécutées via des fonctions prédictives de déclenchement. #### Overview Sometimes you may want to change some attribute for a number of hosts at once. Instead of opening each individual host for editing, you may use the mass update function for that. #### Aperçu Parfois, vous voudrez peut-être changer certains attributs pour un certain nombre d'hôtes en une seule fois. Au lieu d'ouvrir chaque hôte individuellement pour l'édition, vous pouvez utiliser la fonction de modification collective pour cela. #### Overview Sometimes you may want to change some attribute for a number of items at once. Instead of opening each individual item for editing, you may use the mass update function for that. #### Aperçu Parfois, vous voudrez peut-être modifier un attribut pour un certain nombre d'éléments à la fois. Au lieu d'ouvrir chaque élément individuel pour le modifier, vous pouvez utiliser la fonction de mise à jour en masse pour cela. #### Overview Sometimes you may want to change some attribute for a number of templates at once. Instead of opening each individual template for editing, you may use the mass update function for that. #### Aperçu Parfois, vous souhaiterez peut-être modifier un attribut pour plusieurs modèles à la fois. Au lieu d'ouvrir chaque modèle individuel pour le modifier, vous pouvez utiliser la fonction de mise à jour en masse pour cela. #### Overview SSH checks are performed as agent-less monitoring. Zabbix agent is not needed for SSH checks. To perform SSH checks Zabbix server must be initially [configured](/manual/installation/install#from_the_sources) with SSH2 support (libssh2 or libssh). See also: [Requirements](/manual/installation/requirements#server). ::: noteimportant Only libssh is supported starting with RHEL 8. ::: #### Aperçu Les vérifications SSH sont effectuées en tant que supervision sans agent. L'agent Zabbix n'est pas nécessaire pour les vérifications SSH. Pour effectuer des vérifications SSH, le serveur Zabbix doit être [initialement configuré](/manual/installation/install#from_the_sources) avec le support SSH2 (libssh2 ou libssh). Voir également : [Pré-requis](/manual/installation/requirements#server).. ::: noteimportant Seul libssh est pris en charge à partir de RHEL 8. ::: ### Overview Starting from version 5.0, Zabbix frontend requires PHP version 7.2 or later. Unfortunately, older versions of Debian & Ubuntu provide only PHP versions below 7.2. ### Aperçu À partir de la version 5.0, l'interface Zabbix nécessite PHP version 7.2 ou ultérieure. Malheureusement, les anciennes versions de Debian et Ubuntu ne fournissent que des versions PHP inférieures à 7.2. #### Overview Support of monitoring VMware environments is available in Zabbix starting with version 2.2.0. Zabbix can use low-level discovery rules to automatically discover VMware hypervisors and virtual machines and create hosts to monitor them, based on pre-defined host prototypes. The default dataset in Zabbix offers several ready-to-use templates for monitoring VMware vCenter or ESX hypervisor. The minimum required VMware vCenter or vSphere version is 5.1. #### Aperçu La prise en charge de la supervision des environnements VMware est disponible dans Zabbix à partir de la version 2.2.0. Zabbix peut utiliser des règles de découverte de bas niveau pour découvrir automatiquement les hyperviseurs VMware et les machines virtuelles et créer des hôtes pour les surveiller, sur la base de prototypes d'hôtes prédéfinis. Par défaut, Zabbix propose propose plusieurs modèles prêts à l'emploi pour la supervision de l'hyperviseur VMware vCenter ou ESX. La version minimale requise de VMware vCenter ou vSphere est 5.1. #### Overview Telnet checks are performed as agent-less monitoring. Zabbix agent is not needed for Telnet checks. #### Aperçu Les vérifications Telnet sont effectuées en tant que surveillance sans agent. L'agent Zabbix n'est pas nécessaire pour les vérifications Telnet. #### Overview Templates are [exported](/manual/xml_export_import) with many related objects and object relations. Template export contains: - linked host groups - template data - linkage to other templates - linkage to host groups - directly linked items - directly linked triggers - directly linked graphs - directly linked dashboards - directly linked discovery rules with all prototypes - directly linked web scenarios - value maps #### Aperçu Les modèles sont [exportés](/manual/xml_export_import) avec de nombreux objets liés et relations d'objet. L'export de modèle contient : - les groupes d'hôtes liés - les données du modèle - les liens vers d'autres modèles - les liens vers les groupes d'hôtes - les éléments directement liés - les déclencheurs directement liés - les graphiques directement liés - les tableaux de bord directement liés - les règles de découverte directement liées à tous leurs prototypes - les scénarios Web directement liés - les tables de correspondance de valeurs ### Overview The *Administration → Authentication* section allows to specify the global user authentication method to Zabbix and internal password requirements. The available methods are internal, HTTP, LDAP, and SAML authentication. ### Aperçu La section *Administration → Authentification* permet de spécifier la méthode d'authentification globale de l'utilisateur à Zabbix et les conditions du mot de passe interne. Les méthodes disponibles sont internes, HTTP, LDAP et authentification SAML. #### Overview The *Administration → General* section contains a number of subsections for setting frontend-related defaults and customizing Zabbix. The list of available subsections appears upon pressing on *General* in the *Administration* menu section. It is also possible to switch between subsections by using the title dropdown in the top left corner. #### Aperçu La section *Administration → Général* contient un certain nombre de sous-sections pour définir les paramètres par défaut liés au frontend et personnaliser Zabbix. La liste des sous-sections disponibles apparaît en appuyant sur *Général* dans la section du menu *Administration*. Il est également possible de basculer entre sous-sections en utilisant la liste déroulante des titres dans le coin supérieur gauche. #### Overview The Administration menu is for administrative functions of Zabbix. This menu is available to users of [Super Administrators](/manual/config/users_and_usergroups/permissions) type only. #### Aperçu Le menu Administration est destiné aux fonctions administratives de Zabbix. Ce menu est réservé aux utilisateurs de type [super administrateurs](/fr/manual/config/users_and_usergroups/permissions) uniquement. #### Overview The aggregation functions, available in the graph widget of the dashboard, allow displaying an aggregated value for the chosen interval (5 minutes, an hour, a day), instead of all values. The aggregation options are as follows: - min - max - avg - count - sum - first (first value displayed) - last (last value displayed) The most exciting use of data aggregation is the possibility to create nice side-by-side comparisons of data for some period: {width="600"} When hovering over a point in time in the graph, date and time is displayed, in addition to items and their aggregated values. Items are displayed in parentheses, prefixed by the aggregation function used. Note that this is the date and time of the point in the graph, not of the actual values. #### Aperçu Les fonctions d'agrégation, disponibles dans le widget graphique du tableau de bord, permettent d'afficher une valeur agrégée pour l'intervalle choisi (5 minutes, une heure, un jour), au lieu de toutes les valeurs. Les options d'agrégation sont les suivantes : - min - max - avg - count - sum - first (première valeur affichée) - last (dernière valeur affichée) L'utilisation la plus excitante de l'agrégation de données est la possibilité de créer de belles comparaisons côte à côte de données pendant une certaine période : {width="600"} Lorsque vous survolez un point dans le temps dans le graphique, la date et l'heure s'affichent, en plus des éléments et de leurs valeurs agrégées. Les éléments sont affichés entre parenthèses, préfixés par la fonction d'agrégation utilisée. Notez qu'il s'agit de la date et de l'heure du point dans le graphique, et non des valeurs réelles. #### Overview The Configuration menu contains sections for setting up major Zabbix functions, such as hosts and host groups, data gathering, data thresholds, sending problem notifications, creating data visualization and others. #### Aperçu Le menu Configuration contient des sections permettant de configurer les principales fonctions de Zabbix, telles que les hôtes et les groupes d'hôtes, la collecte de données, les seuils de données, l'envoi de notifications de problèmes, la création de visualisation de données et autres. #### Overview The custom graph list for a host can be accessed from *Configuration → Hosts* by clicking on *Graphs* for the respective host. A list of existing graphs is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the custom graph, displayed as a blue link to graph details.<br>Clicking on the graph name link opens the graph [configuration form](/manual/config/visualization/graphs/custom#configuring_custom_graphs).<br>If the host graph belongs to a template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph list on the template level.<br>If the graph has been created from a graph prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the graph prototype list.| |*Width*|Graph width is displayed.| |*Height*|Graph height is displayed.| |*Graph type*|Graph type is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Info*|If the graph is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.| To configure a new graph, click on the *Create graph* button at the top right corner. #### Overview La liste des graphiques personnalisés pour un hôte est accessible depuis *Configuration → Hôtes* en cliquant sur *Graphiques* de l'hôte respectif. Une liste des graphiques existants s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du graphique personnalisé, affiché sous forme de lien bleu vers les détails du graphique.<br>Cliquer sur le lien du nom du graphique ouvre le [formulaire de configuration](/manual/config/visualization/graphs/custom#configuring_custom_graphs) du graphique.<br>Si le graphique hôte appartient à un modèle, le nom du modèle s'affiche avant le nom du graphique, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des graphiques au niveau du modèle.<br>Si le graphique a été créé à partir d'un prototype de graphique, son nom est précédé du nom de la règle de découverte de bas niveau, en orange. Cliquer sur le nom de la règle de découverte ouvrira la liste des prototypes de graphe.| |*Largeur*|La largeur du graphique est affichée.| |*Hauteur*|La hauteur du graphique est affichée.| |*Type de graphique*|Le type de graphique est affiché - *Normal*, *Empilé*, *Camembert* ou *Explosé*.| |*Info*|Si le graphique fonctionne correctement, aucune icône n'est affichée dans cette colonne. En cas d'erreur, une icône carrée avec la lettre "i" s'affiche. Passez la souris sur l'icône pour voir une info-bulle avec la description de l'erreur.| Pour configurer un nouveau graphique, cliquez sur le bouton *Créer un graphique* dans le coin supérieur droit. #### Overview The custom graph list for a template can be accessed from *Configuration → Templates* by clicking on *Graphs* for the respective template. A list of existing graphs is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Template*|Template the graph belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the custom graph, displayed as a blue link to graph details.<br>Clicking on the graph name link opens the graph [configuration form](/manual/config/visualization/graphs/custom#configuring_custom_graphs).<br>If the graph is inherited from another template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph list on that template level.| |*Width*|Graph width is displayed.| |*Height*|Graph height is displayed.| |*Graph type*|Graph type is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| To configure a new graph, click on the *Create graph* button at the top right corner. #### Aperçu La liste des graphiques personnalisés pour un modèle est accessible à partir de *Configuration → Modèles* en cliquant sur *Graphiques* pour le modèle respectif. Une liste des graphiques existants s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Modèle*|Modèle auquel appartient le graphique.<br>Cette colonne s'affiche uniquement si plusieurs modèles sont sélectionnés dans le filtre.| |*Nom*|Nom du graphique personnalisé, affiché sous forme de lien bleu vers les détails du graphique.<br>Cliquer sur le lien du nom du graphique ouvre le [formulaire de configuration](/manual/config/visualization/graphs/custom#configuring_custom_graphs) du graphique.<br>Si le graphique est hérité d'un autre modèle, le nom du modèle s'affiche avant le nom du graphique, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des graphiques à ce niveau de modèle.| |*Largeur*|La largeur du graphique est affichée.| |*Hauteur*|La hauteur du graphique est affichée.| |*Type de graphique*|Le type de graphique est affiché - *Normal*, *Empilé*, *Camembert* ou *Éclaté*.| Pour configurer un nouveau graphique, cliquez sur le bouton *Créer un graphique* dans le coin supérieur droit. #### Overview The graph widget provides a modern and versatile way of visualizing data collected by Zabbix using a vector image drawing technique. This graph widget is supported since Zabbix 4.0. Note that the graph widget supported before Zabbix 4.0 can still be used as [Graph (classic)](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic). #### Aperçu Le widget graphique offre une manière moderne et polyvalente de visualiser les données collectées par Zabbix à l'aide d'une technique de dessin d'image vectorielle. Le widget graphique est pris en charge depuis Zabbix 4.0. Notez que le widget graphique pris en charge avant Zabbix 4.0 peut toujours être utilisé comme [Graphique (classique)](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic). #### Overview The header is present in all request and response messages between Zabbix components. It is required to determine the message length, if it is compressed or not, if it is a large packet or not. Zabbix communications protocol has 1GB packet size limit per connection. The limit of 1GB is applied to both the received packet data length and the uncompressed data length. When sending configuration to Zabbix proxy, the packet size limit is increased to 4GB to allow syncing large configurations. When data length before compression exceeds 4GB, Zabbix server automatically starts using the large packet format (0x04 flag) which increases the packet size limit to 16GB. Note that while a large packet format can be used for sending any data, currently only the Zabbix proxy configuration syncer can handle packets that are larger than 1GB. #### Aperçu L'en-tête est présent dans tous les messages de requête et de réponse entre les composants Zabbix. Il est nécessaire de déterminer la longueur du message, s'il est compressé ou non, s'il s'agit d'un gros paquet ou non. Le protocole de communication Zabbix a une limite de taille de paquet de 1 Go par connexion. La limite de 1 Go s'applique à la fois à la longueur des données du paquet reçu et à la longueur des données non compressées. Lors de l'envoi de la configuration au proxy Zabbix, la limite de taille de paquet est augmentée à 4 Go pour permettre la synchronisation de grandes configurations. Lorsque la longueur des données avant compression dépasse 4 Go, le serveur Zabbix démarre automatiquement en utilisant le grand format de paquet (flag 0x04) qui augmente la limite de taille de paquet à 16 Go. Notez que bien qu'un grand format de paquet puisse être utilisé pour envoyer des données, actuellement seul le synchroniseur de configuration du proxy Zabbix peut gérer les paquets supérieurs à 1 Go. #### Overview The Inventory menu features sections providing an overview of host inventory data by a chosen parameter as well as the ability to view host inventory details. #### Aperçu Le menu Inventaire comprend des sections offrant un aperçu des données d'inventaire de l'hôte selon un paramètre choisi, ainsi que la possibilité d'afficher les détails de l'inventaire de l'hôte. #### Overview The *Inventory → Overview* section provides ways of having an overview of [host inventory](/manual/config/hosts/inventory) data. For an overview to be displayed, choose host groups (or none) and the inventory field by which to display data. The number of hosts corresponding to each entry of the chosen field will be displayed. {width="600"} The completeness of an overview depends on how much inventory information is maintained with the hosts. Numbers in the *Host count* column are links; they lead to these hosts being filtered out in the *Host Inventories* table. {width="600"} #### Aperçu La section *Inventaire → Aperçu* fournit des moyens d'avoir un aperçu des données d'[inventaire d'hôte](/fr/manual/config/hosts/inventory). Pour qu'un aperçu puisse être affiché, choisissez un groupe d'hôtes (ou aucun) et le champ d'inventaire dont vous souhaitez afficher des données. Le nombre d'hôtes correspondant à chaque entrée du champ choisi sera affiché. {width="600"} L'intégralité de l'aperçu dépend de la quantité d'informations d'inventaire conservées concernant les hôtes. Les nombres dans la colonne *Nombre d'hôtes* sont des liens, ils mènent à un filtre basé sur ces hôtes dans le tableau *Inventaire d'hôte*. {width="600"} #### Overview The item list for a template can be accessed from *Configuration → Templates* by clicking on *Items* for the respective template. A list of existing items is displayed. {width="600"} Displayed data: |Column|Description| |--|-----------| |*Item menu*|Click on the three-dot icon to open the menu for this specific item with these options:<br>**Create trigger** - create a trigger based on this item<br>**Triggers** - click to see a list with links to already-configured trigger of this item<br>**Create dependent item** - create a dependent item for this item<br>**Create dependent discovery rule** - create a dependent discovery rule for this item| |*Template*|Template the item belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the item is inherited from another template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item list on that template level.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| To configure a new item, click on the *Create item* button at the top right corner. #### Aperçu La liste des éléments d'un modèle est accessible depuis *Configuration → Modèles* en cliquant sur *Éléments* pour le modèle respectif. Une liste des éléments existants s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|-----------| |*Menu de l'élément*|Cliquez sur l'icône à trois points pour ouvrir le menu de cet élément spécifique avec ces options :<br>**Créer un déclencheur** : créez un déclencheur basé sur cet élément<br>**Déclencheurs** : cliquez pour afficher une liste avec des liens vers le déclencheur déjà configuré de cet élément<br>**Créer un élément dépendant** : créer un élément dépendant pour cet élément<br>**Créer une règle de découverte dépendante** : créer une règle de découverte dépendante pour cet élément| |*Modèle*|Modèle auquel appartient l'élément.<br>Cette colonne s'affiche uniquement si plusieurs modèles sont sélectionnés dans le filtre.| |*Nom*|Nom de l'élément affiché sous forme de lien bleu vers les détails de l'élément.<br>Cliquer sur le lien du nom de l'élément ouvre le [formulaire de configuration](/manual/config/items/item#configuration) de l'élément.<br>Si l'élément est hérité d'un autre modèle, le nom du modèle s'affiche avant le nom de l'élément, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des éléments à ce niveau de modèle.| |*Déclencheurs*|Déplacer la souris sur Déclencheurs affichera une infobox affichant les déclencheurs associés à l'élément.<br>Le nombre de déclencheurs est affiché en gris.| |*Clé*|La clé de l'élément est affichée.| |*Intervalle*|La fréquence du contrôle est affichée.| |*Historique*|Le nombre de jours de conservation de l'historique des données de l'élément est affiché.| |*Tendances*|Le nombre de jours de conservation de l'historique des tendances des éléments est affiché.| |*Type*|Le type d'élément est affiché (agent Zabbix, agent SNMP, vérification simple, etc.).| |*État*|L'état de l'élément est affiché - *Activé* ou *Désactivé*. En cliquant sur le statut, vous pouvez le changer - de Activé à Désactivé (et inversement).| |*Tags*|Les tags d'élément sont affichés.<br>Jusqu'à trois tags (paires nom:valeur) peuvent être affichés. S'il y a plus de tags, un lien "..." s'affiche qui permet de voir tous les tags au passage de la souris.| Pour configurer un nouvel élément, cliquez sur le bouton *Créer un élément* dans le coin supérieur droit. #### Overview The list of low-level discovery rules for a template can be accessed from *Configuration → Templates* by clicking on *Discovery* for the respective template. A list of existing low-level discovery rules is displayed. It is also possible to see all discovery rules independently of the template, or all discovery rules of a specific host group by changing the filter settings. {width="600"} Displayed data: |Column|Description| |--|--------| |*Template*|The template discovery rule belongs to.| |*Name*|Name of the rule, displayed as a blue link.<br>Clicking on the rule name opens the low-level discovery rule [configuration form](/manual/discovery/low_level_discovery#discovery_rule).<br>If the discovery rule is inherited from another template, the template name is displayed before the rule name, as a gray link. Clicking on the template link will open the discovery rule list on that template level.| |*Items*|A link to the list of item prototypes is displayed.<br>The number of existing item prototypes is displayed in gray.| |*Triggers*|A link to the list of trigger prototypes is displayed.<br>The number of existing trigger prototypes is displayed in gray.| |*Graphs*|A link to the list of graph prototypes displayed.<br>The number of existing graph prototypes is displayed in gray.| |*Hosts*|A link to the list of host prototypes displayed.<br>The number of existing host prototypes is displayed in gray.| |*Key*|The item key used for discovery is displayed.| |*Interval*|The frequency of performing discovery is displayed.| |*Type*|The item type used for discovery is displayed (Zabbix agent, SNMP agent, etc).| |*Status*|Discovery rule status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| To configure a new low-level discovery rule, click on the *Create discovery rule* button at the top right corner. #### Aperçu La liste des règles de découverte de bas niveau pour un modèle est accessible depuis *Configuration → Modèles* en cliquant sur *Découverte* pour le modèle respectif. Une liste des règles de découverte de bas niveau existantes s'affiche. Il est aussi possible de voir toutes les règles de découverte indépendamment du modèle, ou toutes les règles de découverte d'un groupe d'hôtes spécifique en modifiant les réglages du filtre. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Modèle*|Le modèle auquel appartient la règle de découverte.| |*Nom*|Nom de la règle, affiché sous forme de lien bleu.<br>Cliquer sur le nom de la règle ouvre le [formulaire de configuration](/manual/discovery/low_level_discovery#discovery_rule) de la règle de découverte de bas niveau .<br>Si la règle de découverte est héritée d'un autre modèle, le nom du modèle s'affiche avant le nom de la règle, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des règles de découverte à ce niveau de modèle.| |*Éléments*|Un lien vers la liste des prototypes d'éléments s'affiche.<br>Le nombre de prototypes d'éléments existants est affiché en gris.| |*Déclencheurs*|Un lien vers la liste des prototypes de déclencheur s'affiche.<br>Le nombre de prototypes de déclencheur existants est affiché en gris.| |*Graphiques*|Un lien vers la liste des prototypes de graphiques s'affiche.<br>Le nombre de prototypes de graphiques existants est affiché en gris.| |*Hôtes*|Un lien vers la liste des prototypes d'hôtes s'affiche.<br>Le nombre de prototypes d'hôtes existants est affiché en gris.| |*Clé*|La clé d'élément utilisée pour la découverte s'affiche.| |*Intervalle*|La fréquence d'exécution de la découverte est affichée.| |*Type*|Le type d'élément utilisé pour la découverte est affiché (agent Zabbix, agent SNMP, etc.).| |*État*|L'état de la règle de découverte est affiché - *Activé* ou *Désactivé*. En cliquant sur l'état, vous pouvez le changer - d'Activé à Désactivé (et inversement).| Pour configurer une nouvelle règle de découverte de bas niveau, cliquez sur le bouton *Créer une règle de découverte* dans le coin supérieur droit. #### Overview The **memtype** parameter is supported on Linux, AIX, FreeBSD, and Solaris platforms. Three common values of 'memtype' are supported on all of these platforms: `pmem`, `rss` and `vsize`. Additionally, platform-specific 'memtype' values are supported on some platforms. #### Aperçu Le paramètre **memtype** est pris en charge sur les plateformes Linux, AIX, FreeBSD et Solaris. Trois valeurs communes de 'memtype' sont prises en charge sur toutes ces plates-formes : `pmem`, `rss` et `vsize`. De plus, les valeurs 'memtype' spécifiques à la plate-forme sont prises en charge sur certaines plates-formes. #### Overview The *Monitoring → Hosts* section displays a full list of monitored hosts with detailed information about host interface, availability, tags, current problems, status (enabled/disabled), and links to easily navigate to the host's latest data, problem history, graphs, dashboards and web scenarios. {width="600"} |Column|Description| |--|--------| |*Name*|The visible host name. Clicking on the name brings up the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).<br>An orange wrench icon  after the name indicates that this host is in maintenance.<br>Click on the column header to sort hosts by name in ascending or descending order.| |*Interface*|The main interface of the host is displayed.| |*Availability*|Host [availability](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability) per configured interface.<br>Icons represent only those interface types (Zabbix agent, SNMP, IPMI, JMX) that are configured. If you position the mouse on the icon, a popup list of all interfaces of this type appears with each interface details, status and errors.<br>The column is empty for hosts with no interfaces.<br>The current status of all interfaces of one type is displayed by the respective icon color:<br>**Green** - all interfaces available<br>**Yellow** - at least one interface available and at least one unavailable; others can have any value including 'unknown'<br>**Red** - no interfaces available<br>**Gray** - at least one interface unknown (none unavailable)<br>Note that active Zabbix agent items do not affect host availability.| |*Tags*|[Tags](/manual/config/tagging) of the host and all linked templates, with macros unresolved.| |*Status*|Host status - *Enabled* or *Disabled*.<br>Click on the column header to sort hosts by status in ascending or descending order.| |*Latest data*|Clicking on the link will open the *Monitoring - Latest data* page with all the latest data collected from the host.<br> The number of items with latest data is displayed in gray (displayed since Zabbix 6.0.5).| |*Problems*| The number of open host problems sorted by severity. The color of the square indicates problem severity. The number on the square means the number of problems for the given severity.<br>Clicking on the icon will open *Monitoring - Problems* page for the current host. <br>If a host has no problems, a link to the Problems section for this host is displayed as text. <br>Use the filter to select whether suppressed problems should be included (not included by default).| |*Graphs*|Clicking on the link will display graphs configured for the host. The number of graphs is displayed in gray.<br>If a host has no graphs, the link is disabled (gray text) and no number is displayed.| |*Dashboards*|Clicking on the link will display dashboards configured for the host. The number of dashboards is displayed in gray.<br>If a host has no dashboards, the link is disabled (gray text) and no number is displayed.| |*Web*|Clicking on the link will display web scenarios configured for the host. The number of web scenarios is displayed in gray.<br>If a host has no web scenarios, the link is disabled (gray text) and no number is displayed.| #### Aperçu La section * Surveillance → Hôtes * affiche une liste complète des hôtes surveillés avec des informations détaillées sur l'interface hôte, la disponibilité, les balises, les problèmes actuels, l'état (activé/désactivé) et des liens pour naviguer facilement vers les dernières données de l'hôte, l'historique des problèmes, les graphiques , tableaux de bord et scénarios web. {width="600"} |Colonne|Description| |--|--------| |*Name*|Le nom d'hôte visible. Cliquer sur le nom fait apparaître le [menu hôte](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).<br>Une icône de clé orange  après le nom indique que cet hôte est en maintenance.<br>Cliquez sur l'en-tête de colonne pour trier les hôtes par nom dans l'ordre croissant ou décroissant.| |*Interface*|L'interface principale de l'hôte s'affiche.| |*Disponibilité*|[Disponibilité](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability) de l'hôte par interface configurée.<br>Les icônes représentent uniquement les types d'interface (agent Zabbix, SNMP, IPMI, JMX) qui sont configurés. Si vous positionnez la souris sur l'icône, une liste contextuelle de toutes les interfaces de ce type apparaît avec les détails, l'état et les erreurs de chaque interface.<br>La colonne est vide pour les hôtes sans interface.<br>L'état actuel de toutes les interfaces d'un type est affiché par la couleur de l'icône correspondante :<br>**Vert** - toutes les interfaces disponibles<br>**Jaune** - au moins une interface disponible et au moins une indisponible ; d'autres peuvent avoir n'importe quelle valeur, y compris 'inconnu'<br>**Rouge** - aucune interface disponible<br>**Gris** - au moins une interface inconnue (aucune indisponible)<br>Notez que les éléments actifs de l'agent Zabbix ne le font pas affecter la disponibilité de l'hôte.| |*Tags*|[Balises](/manual/config/tagging) de l'hôte et de tous les modèles liés, avec les macros non résolues.| |*État*|État de l'hôte - *Activé* ou *Désactivé*.<br>Cliquez sur l'en-tête de colonne pour trier les hôtes par statut dans l'ordre croissant ou décroissant.| |*Dernières données*|Cliquer sur le lien ouvrira la page *Surveillance - Dernières données* avec toutes les dernières données collectées auprès de l'hôte.<br> Le nombre d'éléments avec les dernières données est affiché en gris (affiché depuis Zabbix 6.0.5).| |*Problèmes*| Nombre de problèmes d'hôte ouverts triés par sévérité. La couleur du carré indique la sévérité du problème. Le nombre sur le carré signifie le nombre de problèmes pour la sévérité donnée.<br>Cliquer sur l'icône ouvrira la page *Surveillance - Problèmes* pour l'hôte actuel. <br>Si un hôte ne rencontre aucun problème, un lien vers la section Problèmes de cet hôte s'affiche sous forme de texte. <br>Utilisez le filtre pour sélectionner si les problèmes supprimés doivent être inclus (non inclus par défaut).| |*Graphiques*|Cliquer sur le lien affichera les graphiques configurés pour l'hôte. Le nombre de graphiques est affiché en gris.<br>Si un hôte n'a pas de graphiques, le lien est désactivé (texte gris) et aucun nombre n'est affiché.| |*Tableaux de bord*|Cliquer sur le lien affichera les tableaux de bord configurés pour l'hôte. Le nombre de tableaux de bord est affiché en gris.<br>Si un hôte n'a pas de tableaux de bord, le lien est désactivé (texte gris) et aucun numéro n'est affiché.| |*Web*|Cliquer sur le lien affichera les scénarios Web configurés pour l'hôte. Le nombre de scénarios Web est affiché en gris.<br>Si un hôte n'a pas de scénarios Web, le lien est désactivé (texte grisé) et aucun numéro n'est affiché.| #### Overview The Monitoring menu is all about displaying data. Whatever information Zabbix is configured to gather, visualize and act upon, it will be displayed in the various sections of the Monitoring menu. #### Aperçu Le menu Surveillance regroupe les aspects concernant l'affichage des données. Quelques soient les informations pour lesquelles Zabbix est configuré (collecte, visualisation et utilisation), elles seront affichées dans les différentes sections du menu Surveillance. #### Overview There are four ways of getting Zabbix: - Install it from the [packages](/manual/installation/install_from_packages) - Download the latest source archive and [compile it yourself](/manual/installation/install) - Install it from the [containers](/manual/installation/containers) - Download the [virtual appliance](/manual/appliance) To download the latest distribution packages, pre-compiled sources or the virtual appliance, go to the [Zabbix download page](https://www.zabbix.com/download), where direct links to latest versions are provided. #### Aperçu Il existe quatre façons d'obtenir Zabbix : - L'installer à partir des [paquets de distribution](/manual/installation/install_from_packages) - Télécharger la dernière archive source et la [compiler soi-même](/manual/installation/install) - L'installer à partir de [conteneurs](/manual/installation/containers) - Télécharger l'[appliance virtuelle](/manual/appliance) Pour télécharger les derniers packages de distribution, les sources précompilées ou l'appliance virtuelle, accédez à la [page de téléchargement Zabbix](https://www.zabbix.com/download), où des liens directs vers les dernières versions sont fournis. #### Overview There are several types of events generated in Zabbix: - trigger events - whenever a trigger changes its status (*OK→PROBLEM→OK*) - service events - whenever a service changes its status (*OK→PROBLEM→OK*) - discovery events - when hosts or services are detected - autoregistration events - when active agents are auto-registered by server - internal events - when an item/low-level discovery rule becomes unsupported or a trigger goes into an unknown state ::: noteclassic Internal events are supported starting with Zabbix 2.2 version. ::: Events are time-stamped and can be the basis of actions such as sending notification e-mail etc. To view details of events in the frontend, go to *Monitoring* → *Problems*. There you can click on the event date and time to view details of an event. More information is available on: - [trigger events](/manual/config/events/trigger_events) - [other event sources](/manual/config/events/sources) #### Aperçu Il existe plusieurs types d'événements générés dans Zabbix : - événements déclencheurs - chaque fois qu'un déclencheur change d'état (*OK→PROBLÈME→OK*) - événements de service - chaque fois qu'un service change d'état (*OK→PROBLÈME→OK*) - événements de découverte - lorsque des hôtes ou des services sont détectés - événements d'enregistrement automatique - lorsque les agents actifs sont enregistrés automatiquement par le serveur - événements internes - lorsqu'un élément/règle de découverte de bas niveau n'est plus pris en charge ou qu'un déclencheur passe dans un état inconnu ::: noteclassic Les événements internes sont pris en charge à partir de la version Zabbix 2.2. ::: Les événements sont horodatés et peuvent être à la base d'actions telles que l'envoi d'e-mails de notification, etc. Pour afficher les détails des événements dans l'interface, accédez à *Surveillance* → *Problèmes*. Là, vous pouvez cliquer sur la date et l'heure de l'événement pour afficher les détails d'un événement. Plus d'informations sont disponibles sur : - les [événements déclencheurs](/manual/config/events/trigger_events) - les [autres sources d'événements](/manual/config/events/sources) #### Overview There are situations when one item gathers multiple metrics at a time or it even makes more sense to collect related metrics simultaneously, for example: - CPU utilization of individual cores - Incoming/outgoing/total network traffic To allow for bulk metric collection and simultaneous use in several related items, Zabbix supports dependent items. Dependent items depend on the master item that collects their data simultaneously, in one query. A new value for the master item automatically populates the values of the dependent items. Dependent items cannot have a different update interval than the master item. Zabbix preprocessing options can be used to extract the part that is needed for the dependent item from the master item data. Preprocessing is managed by a `preprocessing manager` process, which has been added in Zabbix 3.4, along with workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is used between data gatherers (pollers, trappers, etc) and the preprocessing process. Zabbix server or Zabbix proxy (if host is monitored by proxy) are performing preprocessing steps and processing dependent items. Item of any type, even dependent item, can be set as master item. Additional levels of dependent items can be used to extract smaller parts from the value of an existing dependent item. #### Aperçu Il existe des situations où un élément rassemble plusieurs métriques à la fois ou il est même plus logique de collecter simultanément des métriques associées, par exemple : - Utilisation du processeur des cœurs individuels - Trafic réseau entrant/sortant/total Pour permettre la collecte de métriques en masse et l'utilisation simultanée dans plusieurs éléments connexes, Zabbix prend en charge les éléments dépendants. Les éléments dépendants dépendent de l'élément principal qui collecte leurs données simultanément, dans une requête. Une nouvelle valeur pour l'élément principal renseigne automatiquement les valeurs des éléments dépendants. Les éléments dépendants ne peuvent pas avoir un intervalle de mise à jour différent de celui de l'élément principal. Les options de prétraitement de Zabbix peuvent être utilisées pour extraire la partie nécessaire pour l'élément dépendant à partir des données de l'élément principal. Le prétraitement est géré par un processus de `gestionnaire de prétraitement`, qui a été ajouté dans Zabbix 3.4, ainsi que par les agents qui effectuent les étapes de prétraitement. Toutes les valeurs (avec ou sans prétraitement) des différents collecteurs de données passent par le gestionnaire de prétraitement avant d'être ajoutées au cache de l'historique. La communication IPC basée sur les sockets est utilisée entre les collecteurs de données (pollers, trappers, etc.) et le processus de prétraitement. Le serveur Zabbix ou le proxy Zabbi x (si l'hôte est surveillé par un proxy) effectuent des étapes de prétraitement et traitent les éléments dépendants. Un élément de n'importe quel type, même un élément dépendant, peut être défini comme élément principal. Des niveaux supplémentaires d'éléments dépendants peuvent être utilisés pour extraire des parties plus petites de la valeur d'un élément dépendant existant. #### Overview There is an option to tag various entities in Zabbix. Tags can be defined for: - templates - hosts - items - web scenarios - triggers - services - template items and triggers - host, item and trigger prototypes Tags have several uses, most notably, to mark events. If entities are tagged, the corresponding new events get marked accordingly: - with tagged templates - any host problems created by relevant entities (items, triggers, etc) from this template will be marked - with tagged hosts - any problem of the host will be marked - with tagged items, web scenarios - any data/problem of this item or web scenario will be marked - with tagged triggers - any problem of this trigger will be marked A problem event inherits all tags from the whole chain of templates, hosts, items, web scenarios, triggers. Completely identical `tag:value` combinations (after resolved macros) are merged into one rather than being duplicated, when marking the event. Having custom event tags allows for more flexibility. Importantly, events can be [correlated](/manual/config/event_correlation) based on event tags. In other uses, actions can be defined based on tagged events. Item problems can be grouped based on tags. Problem tags can also be used to map problems to [services](/manual/it_services/service_tree#problem-tags). Tagging is realized as a pair of *tag name* and *value*. You can use only the name or pair it with a value: MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High An entity (template, host, item, web scenario, trigger or event) may be tagged with the same name, but different values - these tags will not be considered 'duplicates'. Similarly, a tag without value and the same tag with value can be used simultaneously. #### Aperçu Il existe une option pour tagger diverses entités dans Zabbix. Les tags peuvent être définies pour : - modèles - hôtes - éléments - scenarios web - déclencheurs - services - éléments et déclencheurs de modèle - prototypes d'hôte, d'élément et de déclencheur Les tags ont plusieurs utilisations, notamment pour taguer des événements. Si les entités sont taguées, les nouveaux événements correspondants sont tagués en conséquence : - avec des modèles tagués - tout problème d'hôte créé par des entités pertinentes (éléments, déclencheurs, etc.) à partir de ce modèle sera tagué - avec des hôtes tagués - tout problème de l'hôte sera tagué - avec des éléments tagués, des scénarios Web - toute donnée/problème de cet élément ou scénario Web sera tagué - avec des déclencheurs tagués - tout problème de ce déclencheur sera tagué Un événement problématique hérite de tous les tags de toute la chaîne de modèles, d'hôtes, d'éléments, de scénarios Web et de déclencheurs. Les combinaisons `tag:valeur` complètement identiques (après les macros résolues) sont fusionnées en une seule plutôt que d'être dupliquées, lors du taguage de l'événement. Avoir des tags d'événement personnalisés offre plus de flexibilité. Il est important de noter que les événements peuvent être [corrélés](/manual/config/event_correlation) en fonction des tags d'événement. Dans d'autres utilisations, des actions peuvent être définies en fonction d'événements tagués. Les problèmes d'éléments peuvent être regroupés en fonction de tags. Les tags de problème peuvent également être utilisées pour mapper les problèmes aux [services](/manual/it_services/service_tree#problem-tags). Le taguage est réalisé sous la forme d'une paire de *nom de tag* et de *valeur*. Vous pouvez utiliser uniquement le nom ou l'associer à une valeur : MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High Une entité (modèle, hôte, élément, scénario Web, déclencheur ou événement) peut être taguée avec le même nom, mais avec des valeurs différentes - ces tags ne seront pas considérés comme des "doublons". De même, un tag sans valeur et le même tag avec valeur peuvent être utilisés simultanément. #### Overview The Reports menu features several sections that contain a variety of predefined and user-customizable reports focused on displaying an overview of such parameters as system information, triggers and gathered data. #### Aperçu Le menu Rapports comprend plusieurs sections contenant une variété de rapports prédéfinis et personnalisables par l'utilisateur, qui affichent une vue d'ensemble de paramètres tels que les informations système, les déclencheurs et les données collectées. #### Overview These checks use the communication with Zabbix agent for data gathering. There are [passive and active](/manual/appendix/items/activepassive) agent checks. When configuring an item, you can select the required type: - *Zabbix agent* - for passive checks - *Zabbix agent (active)* - for active checks #### Aperçu Ces vérifications utilisent la communication avec l'agent Zabbix pour la collecte de données. Il existe des vérifications d'agent [passifs et actifs](/manual/appendix/items/activepassive). Lors de la configuration d'un élément, vous pouvez sélectionner le type requis : - *Agent Zabbix* - pour les vérifications passives - *Agent Zabbix (actif)* - pour les vérifications actives #### Overview The Services menu is for the [service monitoring](/manual/it_services) functions of Zabbix. #### Aperçu Le menu Services concerne les fonctions [surveillance du service](/manual/it_services) de Zabbix. #### Overview The table contains a complete list of macros supported by Zabbix out-of-the-box. ::: notetip To see all macros supported in a location (for example, in "map URL"), you may paste the location name into the search box at the bottom of your browser window (accessible by pressing CTRL+F) and do a search for *next*. ::: |Macro|Supported in|Description| |--|------|------| |{ACTION.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications|*Numeric ID of the triggered action.*| |{ACTION.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications|*Name of the triggered action.*| |{ALERT.MESSAGE}|→ Alert script parameters|*'Default message' value from action configuration.*<br>Supported since 3.0.0.| |{ALERT.SENDTO}|→ Alert script parameters|*'Send to' value from user media configuration.*<br>Supported since 3.0.0.| |{ALERT.SUBJECT}|→ Alert script parameters|*'Default subject' value from action configuration.*<br>Supported since 3.0.0.| |{DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current date in yyyy.mm.dd. format.*| |{DISCOVERY.DEVICE.IPADDRESS}|→ Discovery notifications and commands|*IP address of the discovered device.*<br>Available always, does not depend on host being added.| |{DISCOVERY.DEVICE.DNS}|→ Discovery notifications and commands|*DNS name of the discovered device.*<br>Available always, does not depend on host being added.| |{DISCOVERY.DEVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered device*: can be either UP or DOWN.| |{DISCOVERY.DEVICE.UPTIME}|→ Discovery notifications and commands|*Time since the last change of discovery status for a particular device*, with precision down to a second.<br>For example: 1h 29m 01s.<br>For devices with status DOWN, this is the period of their downtime.| |{DISCOVERY.RULE.NAME}|→ Discovery notifications and commands|*Name of the discovery rule that discovered the presence or absence of the device or service.*| |{DISCOVERY.SERVICE.NAME}|→ Discovery notifications and commands|*Name of the service that was discovered.*<br>For example: HTTP.| |{DISCOVERY.SERVICE.PORT}|→ Discovery notifications and commands|*Port of the service that was discovered.*<br>For example: 80.| |{DISCOVERY.SERVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered <service://> can be either UP or DOWN. \| \|{DISCOVERY.SERVICE.UPTIME} \|→ Discovery notifications and commands \|*Time since the last change of discovery status for a particular service*, with precision down to a second.<br>For example: 1h 29m 01s.<br>For services with status DOWN, this is the period of their downtime. \| \|{ESC.HISTORY} \|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Internal notifications \|*Escalation history. Log of previously sent messages.*<br>Shows previously sent notifications, on which escalation step they were sent and their status (*sent*, *in progress* or *failed*).| |{EVENT.ACK.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Acknowledgment status of the event (Yes/No)*.| |{EVENT.AGE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Age of the event that triggered an action*, with precision down to a second.<br>Useful in escalated messages.| |{EVENT.DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Date of the event that triggered an action.*| |{EVENT.DURATION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Duration of the event (time difference between problem and recovery events)*, with precision down to a second.<br>Useful in problem recovery messages.<br><br>Supported since 5.0.0.| |{EVENT.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric ID of the event that triggered an action.*| |{EVENT.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the problem event that triggered an action.*<br>Supported since 4.0.0.| |{EVENT.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event severity.* Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.<br>Supported since 4.0.0.| |{EVENT.OBJECT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event object.* Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.<br>Supported since 4.4.0.| |{EVENT.OPDATA}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Operational data of the underlying trigger of a problem.*<br>Supported since 4.4.0.| |{EVENT.RECOVERY.DATE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Date of the recovery event.*| |{EVENT.RECOVERY.ID}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Numeric ID of the recovery event.*| |{EVENT.RECOVERY.NAME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Name of the recovery event.*<br>Supported since 4.4.1.| |{EVENT.RECOVERY.STATUS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Verbal value of the recovery event.*| |{EVENT.RECOVERY.TAGS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*A comma separated list of recovery event tags.* Expanded to an empty string if no tags exist.<br>Supported since 3.2.0.| |{EVENT.RECOVERY.TAGSJSON}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*A JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag).* Expanded to an empty array if no tags exist.<br>Supported since 5.0.0.| |{EVENT.RECOVERY.TIME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Time of the recovery event.*| |{EVENT.RECOVERY.VALUE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Numeric value of the recovery event.*| |{EVENT.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the event severity.*<br>Supported since 4.0.0.| |{EVENT.SOURCE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event source.* Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal.<br>Supported since 4.4.0.| |{EVENT.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Verbal value of the event that triggered an action.*| |{EVENT.TAGS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A comma separated list of event tags.* Expanded to an empty string if no tags exist.<br>Supported since 3.2.0.| |{EVENT.TAGSJSON}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag).* Expanded to an empty array if no tags exist.<br>Supported since 5.0.0.| |{EVENT.TAGS.<tag name>}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Webhook media type URL names and URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Event tag value referenced by the tag name.*<br>A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) should be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.<br>Supported since 4.4.2.| |{EVENT.TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Time of the event that triggered an action.*| |{EVENT.UPDATE.ACTION}|→ Problem update notifications and commands|*Human-readable name of the action(s)* performed during [problem update](/manual/acknowledges#updating_problems).<br>Resolves to the following values: *acknowledged*, *commented*, *changed severity from (original severity) to (updated severity)* and *closed* (depending on how many actions are performed in one update).<br>Supported since 4.0.0.| |{EVENT.UPDATE.DATE}|→ Problem update notifications and commands<br>→ Service update notifications and commands|*Date of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*<br>Deprecated name: {ACK.DATE}| |{EVENT.UPDATE.HISTORY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Log of problem updates (acknowledgments, etc).*<br>Deprecated name: {EVENT.ACK.HISTORY}| |{EVENT.UPDATE.MESSAGE}|→ Problem update notifications and commands|*Problem update message.*<br>Deprecated name: {ACK.MESSAGE}| |{EVENT.UPDATE.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the problem update status.* Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.<br>Supported since 4.4.0.| |{EVENT.UPDATE.TIME}|→ Problem update notifications and commands<br>→ Service update notifications and commands|*Time of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*<br>Deprecated name: {ACK.TIME}| |{EVENT.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event that triggered an action (1 for problem, 0 for recovering).*| |{FUNCTION.VALUE<1-9>}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Event names|*Results of the Nth item-based function in the trigger expression at the time of the event.*<br>Only functions with */host/key* as the first parameter are counted. See [indexed macros](supported_by_location#indexed_macros).| |{FUNCTION.RECOVERY.VALUE<1-9>}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Results of the Nth item-based function in the recovery expression at the time of the event.*<br>Only functions with */host/key* as the first parameter are counted. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.CONN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host IP address or DNS name, depending on host settings*^[2](supported_by_location#footnotes)^.<br><br>May be used with a numeric index as {HOST.CONN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host description.*<br><br>This macro may be used with a numeric index e.g. {HOST.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.DNS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host DNS name*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.DNS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.HOST}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Item key parameters<br>→ Map element labels, map URL names and values<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host name.*<br><br>This macro may be used with a numeric index e.g. {HOST.HOST[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{HOSTNAME<1-9>}` is deprecated.| |{HOST.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host ID.*<br><br>May be used with a numeric index as {HOST.ID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.IP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host IP address*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.IP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{IPADDRESS<1-9>}` is deprecated.| |{HOST.METADATA}|→ Autoregistration notifications and commands|*Host metadata.*<br>Used only for active agent autoregistration.| |{HOST.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Visible host name.*<br><br>This macro may be used with a numeric index e.g. {HOST.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.PORT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ JMX item endpoint field<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host (agent) port*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.PORT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.TARGET.CONN}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|IP address or DNS name of the target host, depending on host settings.<br>Supported since 5.4.0.| |{HOST.TARGET.DNS}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|DNS name of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.HOST}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|Technical name of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.IP}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|IP address of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.NAME}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|Visible name of the target host.<br>Supported since 5.4.0.| |{HOSTGROUP.ID}|→ Map element labels, map URL names and values|*Host group ID.*| |{INVENTORY.ALIAS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Alias field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.ALIAS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.ASSET.TAG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Asset tag field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.ASSET.TAG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CHASSIS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Chassis field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CHASSIS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CONTACT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Contact field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CONTACT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.CONTACT<1-9>}` is deprecated.| |{INVENTORY.CONTRACT.NUMBER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Contract number field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CONTRACT.NUMBER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.DEPLOYMENT.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Deployment status field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.DEPLOYMENT.STATUS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HARDWARE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.HARDWARE<1-9>}` is deprecated.| |{INVENTORY.HARDWARE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETMASK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host subnet mask field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETMASK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETWORKS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host networks field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETWORKS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.ROUTER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host router field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.ROUTER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.ARCH}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware architecture field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.ARCH[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.DECOMM}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware decommissioned field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.DECOMM[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.EXPIRY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware maintenance expires field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.EXPIRY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.INSTALL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware installed field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.INSTALL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.PURCHASE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware purchased field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.PURCHASE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.INSTALLER.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Installer name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.INSTALLER.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.LOCATION<1-9>}` is deprecated.| |{INVENTORY.LOCATION.LAT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location latitude field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LAT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION.LON}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location longitude field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LON[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MACADDRESS.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*MAC address A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.MACADDRESS<1-9>}` is deprecated.| |{INVENTORY.MACADDRESS.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*MAC address B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MODEL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Model field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MODEL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NAME<1-9>}` is deprecated.| |{INVENTORY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NOTES<1-9>}` is deprecated.| |{INVENTORY.OOB.IP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB IP address field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.IP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.NETMASK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB subnet mask field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.NETMASK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.ROUTER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB router field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.ROUTER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.OS<1-9>}` is deprecated.| |{INVENTORY.OS.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS.SHORT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS (Short) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS.SHORT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.CELL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC cell field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.CELL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.EMAIL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC email field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC phone A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC phone B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.SCREEN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC screen name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.CELL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC cell field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.CELL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.EMAIL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC email field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC phone A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC phone B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.SCREEN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC screen name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SERIALNO.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Serial number A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.SERIALNO<1-9>}` is deprecated.| |{INVENTORY.SERIALNO.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Serial number B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.CITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site city field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.CITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.COUNTRY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site country field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.COUNTRY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.RACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site rack location field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.RACK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.STATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site state/province field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.STATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ZIP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site ZIP/postal field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ZIP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.SOFTWARE<1-9>}` is deprecated.| |{INVENTORY.SOFTWARE.APP.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.D}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application D field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.D[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.E}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application E field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.E[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.TAG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Tag field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TAG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.TAG<1-9>}` is deprecated.| |{INVENTORY.TYPE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Type field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TYPE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.DEVICETYPE<1-9>}` is deprecated.| |{INVENTORY.TYPE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Type (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TYPE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.VENDOR}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Vendor field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.VENDOR[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Description of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.DESCRIPTION.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Description (with macros unresolved) of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.DESCRIPTION.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>Supported since 5.2.0.| |{ITEM.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Numeric ID of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.ID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.KEY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Key of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.KEY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{TRIGGER.KEY}` is deprecated.| |{ITEM.KEY.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.^[6](supported_by_location#footnotes)^<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Original key (with macros not expanded) of the Nth item in the trigger expression that caused a notification ^[4](supported_by_location#footnotes)^.*<br><br>This macro may be used with a numeric index e.g. {ITEM.KEY.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LASTVALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, event names, operational data and descriptions<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*The latest value of the Nth item in the trigger expression that caused a notification.*<br>It will resolve to \*UNKNOWN\* in the frontend if the latest history value has been collected more than the *Max history display period* time ago (set in the [Administration→General](/manual/web_interface/frontend_sections/administration/general#gui) menu section).<br>Note that since 4.0, when used in the problem name, it will not resolve to the latest item value when viewing problem events, instead it will keep the item value from the time of problem happening.<br>It is alias to `last(/{HOST.HOST}/{ITEM.KEY})`.<br><br>The resolved value is truncated to 20 characters to be usable, for example, in trigger URLs. To resolve to a full value, you may use [macro functions](/manual/config/macros/macro_functions#seeing-full-item-values).<br><br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro; starting with Zabbix 3.2.0.<br><br>This macro may be used with a numeric index e.g. {ITEM.LASTVALUE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. item in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.AGE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Age of the log item event*, with precision down to a second.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.AGE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date of the log item event.*<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.DATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.EVENTID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*ID of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.EVENTID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Numeric severity of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.NSEVERITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Verbal severity of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.SEVERITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.SOURCE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Source of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.SOURCE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Time of the log item event.*<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.TIME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Name of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.NAME.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|This macros is deprecated since Zabbix 6.0. It used to resolve to the *original name (i.e. without macros resolved) of the item* in pre-6.0 Zabbix versions when user macros and positional macros were supported in the item name.<br><br>This macro may be used with a numeric index e.g. {ITEM.NAME.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.STATE}|→ Item-based internal notifications<br>→ Description of item value widget|*The latest state of the Nth item in the trigger expression that caused a notification.* Possible values: **Not supported** and **Normal**.<br><br>This macro may be used with a numeric index e.g. {ITEM.STATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.STATE.ERROR}|→ Item-based internal notifications|*Error message with details why an item became unsupported.* <br> <br> If an item goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{ITEM.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, event names, operational data and descriptions<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|Resolved to either:<br>1) the historical (at-the-time-of-event) value of the Nth item in the trigger expression, if used in the context of trigger status change, for example, when displaying events or sending notifications.<br>2) the latest value of the Nth item in the trigger expression, if used without the context of trigger status change, for example, when displaying a list of triggers in a pop-up selection window. In this case works the same as {ITEM.LASTVALUE}<br>In the first case it will resolve to \*UNKNOWN\* if the history value has already been deleted or has never been stored.<br>In the second case, and in the frontend only, it will resolve to \*UNKNOWN\* if the latest history value has been collected more than the *Max history display period* time ago (set in the [Administration→General](/manual/web_interface/frontend_sections/administration/general#gui) menu section).<br><br>The resolved value is truncated to 20 characters to be usable, for example, in trigger URLs. To resolve to a full value, you may use [macro functions](/manual/config/macros/macro_functions#seeing-full-item-values).<br><br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 3.2.0.<br><br>This macro may be used with a numeric index e.g. {ITEM.VALUE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. item in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.VALUETYPE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Value type of the Nth item in the trigger expression that caused a notification.* Possible values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text.<br><br>This macro may be used with a numeric index e.g. {ITEM.VALUETYPE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>Supported since 5.4.0.| |{LLDRULE.DESCRIPTION}|→ LLD-rule based internal notifications|*Description of the low-level discovery rule which caused a notification.*| |{LLDRULE.DESCRIPTION.ORIG}|→ LLD-rule based internal notifications|*Description (with macros unresolved) of the low-level discovery rule which caused a notification.*<br>Supported since 5.2.0.| |{LLDRULE.ID}|→ LLD-rule based internal notifications|*Numeric ID of the low-level discovery rule which caused a notification.*| |{LLDRULE.KEY}|→ LLD-rule based internal notifications|*Key of the low-level discovery rule which caused a notification.*| |{LLDRULE.KEY.ORIG}|→ LLD-rule based internal notifications|*Original key (with macros not expanded) of the low-level discovery rule which caused a notification.*| |{LLDRULE.NAME}|→ LLD-rule based internal notifications|*Name of the low-level discovery rule (with macros resolved) that caused a notification.*| |{LLDRULE.NAME.ORIG}|→ LLD-rule based internal notifications|*Original name (i.e. without macros resolved) of the low-level discovery rule that caused a notification.*| |{LLDRULE.STATE}|→ LLD-rule based internal notifications|*The latest state of the low-level discovery rule.* Possible values: **Not supported** and **Normal**.| |{LLDRULE.STATE.ERROR}|→ LLD-rule based internal notifications|*Error message with details why an LLD rule became unsupported.* <br> <br> If an LLD rule goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{MAP.ID}|→ Map element labels, map URL names and values|*Network map ID.*| |{MAP.NAME}|→ Map element labels, map URL names and values<br>→ Text field in map shapes|*Network map name.*<br>Supported since 3.4.0.| |{PROXY.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Description of the proxy*. Resolves to either:<br>1) proxy of the Nth item in the trigger expression (in trigger-based notifications). You may use [indexed](/manual/appendix/macros/supported_by_location#indexed_macros) macros here.<br>2) proxy, which executed discovery (in discovery notifications). Use {PROXY.DESCRIPTION} here, without indexing.<br>3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.DESCRIPTION} here, without indexing.<br><br>This macro may be used with a numeric index e.g. {PROXY.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{PROXY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the proxy*. Resolves to either:<br>1) proxy of the Nth item in the trigger expression (in trigger-based notifications). You may use [indexed](/manual/appendix/macros/supported_by_location#indexed_macros) macros here.<br>2) proxy, which executed discovery (in discovery notifications). Use {PROXY.NAME} here, without indexing.<br>3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.NAME} here, without indexing.<br><br>This macro may be used with a numeric index e.g. {PROXY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{SERVICE.DESCRIPTION}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Description of the service* (with macros resolved).| |{SERVICE.NAME}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Name of the service* (with macros resolved).| |{SERVICE.ROOTCAUSE}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*List of trigger problem events that caused a service to fail*, sorted by severity and host name. Includes the following details: host name, event name, severity, age, service tags and values.| |{SERVICE.TAGS}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*A comma separated list of service event tags.* Service event tags can be defined in the service configuration section Tags. Expanded to an empty string if no tags exist.| |{SERVICE.TAGSJSON}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*A JSON array containing service event tag objects.* Service event tags can be defined in the service configuration section Tags. Expanded to an empty array if no tags exist.| |{SERVICE.TAGS.<tag name>}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Service event tag value referenced by the tag name.* Service event tags can be defined in the service configuration section Tags.<br>A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) should be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.| |{TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger event names<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current time in hh:mm:ss.*| |{TRIGGER.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger description.*<br>All macros supported in a trigger description will be expanded if `{TRIGGER.DESCRIPTION}` is used in notification text.<br>`{TRIGGER.COMMENT}` is deprecated.| |{TRIGGER.EXPRESSION.EXPLAIN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Event names|*Partially evaluated trigger expression.*<br>Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger expressions.| |{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Partially evaluated trigger recovery expression.*<br>Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger recovery expressions.| |{TRIGGER.EVENTS.ACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of acknowledged events for a map element in maps, or for the trigger which generated current event in notifications.*| |{TRIGGER.EVENTS.PROBLEM.ACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of acknowledged PROBLEM events for all triggers disregarding their state.*| |{TRIGGER.EVENTS.PROBLEM.UNACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of unacknowledged PROBLEM events for all triggers disregarding their state.*| |{TRIGGER.EVENTS.UNACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of unacknowledged events for a map element in maps, or for the trigger which generated current event in notifications.*| |{TRIGGER.HOSTGROUP.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A sorted (by SQL query), comma-space separated list of host groups in which the trigger is defined.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}|→ Map element labels|*Number of acknowledged PROBLEM events for triggers in PROBLEM state.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}|→ Map element labels|*Number of unacknowledged PROBLEM events for triggers in PROBLEM state.*| |{TRIGGER.EXPRESSION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger expression.*| |{TRIGGER.EXPRESSION.RECOVERY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger recovery expression* if *OK event generation* in [trigger configuration](/manual/config/triggers/trigger) is set to 'Recovery expression'; otherwise an empty string is returned.<br>Supported since 3.2.0.| |{TRIGGER.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Map element labels, map URL names and values<br>→ Trigger URLs<br>→ Trigger tag value<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric trigger ID which triggered this action.*<br>Supported in trigger tag values since 4.4.1.| |{TRIGGER.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the trigger* (with macros resolved).<br>Note that since 4.0.0 {EVENT.NAME} can be used in actions to display the triggered event/problem name with macros resolved.| |{TRIGGER.NAME.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Original name of the trigger* (i.e. without macros resolved).| |{TRIGGER.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numerical trigger severity.* Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.| |{TRIGGER.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger severity name.* Can be defined in *Administration → General → Trigger displaying options*.| |{TRIGGER.STATE}|→ Trigger-based internal notifications|*The latest state of the trigger.* Possible values: **Unknown** and **Normal**.| |{TRIGGER.STATE.ERROR}|→ Trigger-based internal notifications|*Error message with details why a trigger became unsupported.* <br> <br> If a trigger goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{TRIGGER.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger value at the time of operation step execution.* Can be either PROBLEM or OK.<br>`{STATUS}` is deprecated.| |{TRIGGER.TEMPLATE.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A sorted (by SQL query), comma-space separated list of templates in which the trigger is defined, or \*UNKNOWN\* if the trigger is defined in a host.*| |{TRIGGER.URL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger URL.*| |{TRIGGER.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger expressions<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current trigger numeric value*: 0 - trigger is in OK state, 1 - trigger is in PROBLEM state.| |{TRIGGERS.UNACK}|→ Map element labels|*Number of unacknowledged triggers for a map element, disregarding trigger state.*<br>A trigger is considered to be unacknowledged if at least one of its PROBLEM events is unacknowledged.| |{TRIGGERS.PROBLEM.UNACK}|→ Map element labels|*Number of unacknowledged PROBLEM triggers for a map element.*<br>A trigger is considered to be unacknowledged if at least one of its PROBLEM events is unacknowledged.| |{TRIGGERS.ACK}|→ Map element labels|*Number of acknowledged triggers for a map element, disregarding trigger state.*<br>A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.| |{TRIGGERS.PROBLEM.ACK}|→ Map element labels|*Number of acknowledged PROBLEM triggers for a map element.*<br>A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.| |{USER.FULLNAME}|→ Problem update notifications and commands<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Name, surname and username of the user* who added event acknowledgment or started the script.<br>Supported for problem updates since 3.4.0, for global scripts since 5.0.2| |{USER.NAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Name of the user* who started the script.<br>Supported since 5.0.2.| |{USER.SURNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Surname of the user* who started the script.<br>Supported since 5.0.2.| |{USER.USERNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Username of the user* who started the script.<br>Supported since 5.0.2.<br>{USER.ALIAS}, supported before Zabbix 5.4.0, is now deprecated.| |{$MACRO}|→ See: [User macros supported by location](/manual/appendix/macros/supported_by_location_user)|*[User-definable](/manual/config/macros/user_macros) macros.*| |{\#MACRO}|→ See: [Low-level discovery macros](/manual/config/macros/lld_macros)|*Low-level discovery macros.*<br><br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 4.0.0.| |{?EXPRESSION}|→ Trigger event names<br>→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels^[3](supported_by_location#footnotes)^<br>→ Map shape labels^[3](supported_by_location#footnotes)^<br>→ Link labels in maps^[3](supported_by_location#footnotes)^<br>→ Graph names^[5](supported_by_location#footnotes)^|See [expression macros](/manual/config/macros/expression_macros).<br>Supported since 5.2.0.| #### Aperçu Le tableau contient une liste complète des macros prises en charge par Zabbix prêtes à l'emploi. ::: notetip Pour voir toutes les macros prises en charge dans un emplacement (par exemple, dans "URL de carte"), vous pouvez coller le nom de l'emplacement dans la zone de recherche en bas de la fenêtre de votre navigateur (accessible en appuyant sur CTRL+F) et effectuer une recherche pour le *Suivant*. ::: |Macro|Prise en charge dans|Description| |--|------|------| |{ACTION.ID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes|*ID numérique de l'action déclenchée.*| |{ACTION.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes|*Nom de l'action déclenchée..*| |{ALERT.MESSAGE}|→ Paramètres du script d'alerte|*Valeur 'Message par défaut' de la configuration de l'action.*<br>Pris en charge depuis 3.0.0.| |{ALERT.SENDTO}|→ Paramètres du script d'alerte|*Valeur 'Envoyer à' de la configuration des médias de l'utilisateur.*<br>Pris en charge depuis 3.0.0.|* |{ALERT.SUBJECT}|→ Paramètres du script d'alerte|*Valeur 'Sujet par défaut' de la configuration de l'action.*<br>Pris en charge depuis 3.0.0.| |{DATE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Date actuelle au format aaaa.mm.jj. format.*| |{DISCOVERY.DEVICE.IPADDRESS}|→ Notifications et commandes de découverte|*Adresse IP du périphérique découvert.*<br>Toujours disponible, ne dépend pas de l'hôte ajouté.| |{DISCOVERY.DEVICE.DNS}|→ Notifications et commandes de découverte|*DNS name of the discovered device.*<br>Available always, does not depend on host being added.| |{DISCOVERY.DEVICE.STATUS}|→ Notifications et commandes de découverte|*Statut de l'appareil découvert* : peut être UP ou DOWN.| |{DISCOVERY.DEVICE.UPTIME}|→ Notifications et commandes de découverte|*Temps écoulé depuis le dernier changement d'état de découverte pour un appareil particulier*, avec une précision à la seconde près.<br>Par exemple : 1h 29m 01s.<br>Pour les appareils dont l'état est DOWN, il s'agit de la période d'indisponibilité.| |{DISCOVERY.RULE.NAME}|→ Notifications et commandes de découverte|*Nom de la règle de découverte qui a découvert la présence ou l'absence de l'appareil ou du service.*| |{DISCOVERY.SERVICE.NAME}|→ Notifications et commandes de découverte|*Nom du service découvert.*<br>Par exemple : HTTP.| |{DISCOVERY.SERVICE.PORT}|→ Notifications et commandes de découverte|*Port du service qui a été découvert.*<br>Par exemple : 80.| |{DISCOVERY.SERVICE.STATUS}|→ Notifications et commandes de découverte|*L'état du <service://> découvert* peut être UP ou DOWN. | |{DISCOVERY.SERVICE.UPTIME}|→ Notifications et commandes de découverte|*Temps écoulé depuis le dernier changement d'état de découverte pour un service particulier*, avec une précision à la seconde près.<br>Par exemple : 1h 29m 01s.<br>Pour les services en statut DOWN, il s'agit de la durée de leur indisponibilité. | |{ESC.HISTORY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications internes|*Historique de l'escalade. Journal des messages envoyés précédemment.*<br>Affiche les notifications envoyées précédemment, à quelle étape d'escalade elles ont été envoyées et leur statut (*sent*, *in progress* ou *failed*).| |{EVENT.ACK.STATUS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*État d'acquittement de l'événement (Yes/No)*.| |{EVENT.AGE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Âge de l'événement qui a déclenché une action*, avec une précision à la seconde près.<br>Utile dans les messages escaladés.| |{EVENT.DATE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Date de l'événement qui a déclenché une action.*| |{EVENT.DURATION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Durée de l'événement (différence de temps entre les événements de problème et de récupération)*, avec une précision jusqu'à une seconde.<br>Utile dans les messages de récupération de problème.<br><br>Pris en charge depuis la version 5.0.0.| |{EVENT.ID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ URLs de déclencheur<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*ID numérique de l'événement qui a déclenché une action.*| |{EVENT.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom de l'événement problème qui a déclenché une action.*<br>Pris en charge depuis 4.0.0.| |{EVENT.NSEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique de la sévérité de l'événement.* Valeurs possibles : 0 - Non classé, 1 - Information, 2 - Avertissement, 3 - Moyenne, 4 - Haut, 5 - Désastre.<br>Pris en charge depuis la version 4.0.0.| |{EVENT.OBJECT}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique de l'objet événement.* Valeurs possibles : 0 - Déclencheur, 1 - Hôte découvert, 2 - Service découvert, 3 - Enregistrement automatique, 4 - Élément, 5 - Règle de découverte de bas niveau.<br>Pris en charge depuis la version 4.4.0 .| |{EVENT.OPDATA}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Données opérationnelles du déclencheur sous-jacent d'un problème.*<br>Pris en charge depuis la version 4.4.0.| |{EVENT.RECOVERY.DATE}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Date de l'événement de récupération.*| |{EVENT.RECOVERY.ID}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*ID numérique de l'événement de récupération.*| |{EVENT.RECOVERY.NAME}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Nom de l'événement de récupération.*<br>Pris en charge depuis la version 4.4.1.| |{EVENT.RECOVERY.STATUS}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Valeur verbale de l'événement de récupération.*| |{EVENT.RECOVERY.TAGS}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Une liste de tags d'événement de récupération séparés par des virgules.* Développée en une chaîne vide si aucun tag n'existe.<br>Pris en charge depuis la version 3.2.0.| |{EVENT.RECOVERY.TAGSJSON}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Un tableau JSON contenant des [objets](/manual/api/reference/event/object#event_tag) tag d'événement.* Développé en un tableau vide s'il n'existe aucun tag.<br>Pris en charge depuis la version 5.0.0.| |{EVENT.RECOVERY.TIME}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Heure de l'événement de récupération.*| |{EVENT.RECOVERY.VALUE}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes (si la récupération a eu lieu)<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (si la récupération a eu lieu)|*Valeur numérique de l'événement de récupération.*| |{EVENT.SEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom de la sévérité de l'événement.*<br>Pris en charge depuis la version 4.0.0.| |{EVENT.SOURCE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique de la source de l'événement.* Valeurs possibles : 0 - Déclencheur, 1 - Découverte, 2 - Enregistrement automatique, 3 - Interne.<br>Pris en charge depuis la version 4.4.0.| |{EVENT.STATUS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur verbale de l'événement qui a déclenché une action.*| |{EVENT.TAGS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Une liste de tags d'événement séparées par des virgules.* Développée en une chaîne vide si aucun tag n'existe.<br>Pris en charge depuis la version 3.2.0.| |{EVENT.TAGSJSON}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Un tableau JSON contenant des [objets](/manual/api/reference/event/object#event_tag) de tag d'événement.* Développé en un tableau vide s'il n'existe aucun tag.<br>Pris en charge depuis la version 5.0.0.| |{EVENT.TAGS.\<tag name\>}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Noms d'URL de type de média Webhook et URLs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur de tag d'événement référencée par le nom de tag.*<br>Un nom de tag contenant des caractères non alphanumériques (y compris des caractères UTF multioctets non anglais) doit être placé entre guillemets doubles. Les guillemets et les barres obliques inverses à l'intérieur d'un nom de tag entre guillemets doivent être protégés par une barre oblique inverse.<br>Pris en charge depuis la version 4.4.2.| |{EVENT.TIME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Heure de l'événement qui a déclenché une action.*| |{EVENT.UPDATE.ACTION}|→ Notifications et commandes de mise à jour des problèmes||*Nom lisible par l'homme de l'action(s)* effectuée(s) pendant la [mise à jour du problème](/manual/acknowledges#updating_problems).<br>Résout les valeurs suivantes : *acknowledged*, *commented*, *changed severity from (original severity) to (updated severity)* et *closed* (selon le nombre d'actions effectuées dans une mise à jour).<br>Pris en charge depuis la version 4.0.0.| |{EVENT.UPDATE.DATE}|→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes de mise à jour de service|*Date de l'événement [mise à jour](/manual/config/notifications/action/update_operations) (acquittements, etc.).*<br>Nom obsolète : {ACK.DATE}| |{EVENT.UPDATE.HISTORY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Journal des mises à jour des problèmes (acquittements, etc.).*<br>Nom obsolète : {EVENT.ACK.HISTORY}| |{EVENT.UPDATE.MESSAGE}|→ Notifications et commandes de mise à jour des problèmes|*Message de mise à jour du problème.*<br>Nom obsolète : {ACK.MESSAGE}| |{EVENT.UPDATE.STATUS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique de l'état de la mise à jour du problème.* Valeurs possibles : 0 - Webhook a été appelé en raison d'un événement de problème/récupération, 1 - Opération de mise à jour.<br>Pris en charge depuis la version 4.4.0.| |{EVENT.UPDATE.TIME}|→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes de mise à jour de service|*Heure de l'événement [mis à jour](/manual/config/notifications/action/update_operations) (acquittements, etc.).*<br>Nom obsolète : {ACK.TIME}| |{EVENT.VALUE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de récupération de service<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique de l'événement qui a déclenché une action (1 pour problème, 0 pour récupération).*| |{FUNCTION.VALUE<1-9>}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Noms des événements|*Résultats de la Nième fonction basée sur un élément dans l'expression du déclencheur au moment de l'événement.*<br>Seules les fonctions avec */host/key* comme premier paramètre sont comptées. Voir les [macros indexées](supported_by_location#indexed_macros).| |{FUNCTION.RECOVERY.VALUE<1-9>}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Résultats de la Nième fonction basée sur l'élément dans l'expression de récupération au moment de l'événement.*<br>Seules les fonctions avec */host/key* comme premier paramètre sont comptées. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.CONN}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Paramètres clé de l'élément^[1](supported_by_location#footnotes)^<br>→ IP/DNS de l'interface hôte<br>→ Champ "Hôtes autorisés" de l'élément Trapper<br>→ Paramètres supplémentaires de la surveillance de la base de données<br>→ Scripts SSH et Telnet<br>→ Champ de point de terminaison d'élément JMX<br>→ Surveillance Web^[4](supported_by_location#footnotes)^<br>→ Expressions régulières de filtre de règle de découverte de bas niveau<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)<br>→ Description du widget de valeur d'élément*Adresse IP de l'hôte ou nom DNS, selon les paramètres de l'hôte*^[2](supported_by_location#footnotes)^.<br><br>Peut être utilisé avec un index numérique tel que {HOST.CONN[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.DESCRIPTION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ Libellés des éléments de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Description de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.DNS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Paramètres clé de l'élément^[1](supported_by_location#footnotes)^<br>→ IP/DNS de l'interface hôte<br>→ Champ "Hôtes autorisés" de l'élément Trapper<br>→ Paramètres supplémentaires de la surveillance de la base de données<br>→ Scripts SSH et Telnet<br>→ Champ de point de terminaison d'élément JMX<br>→ Surveillance Web^[4](supported_by_location#footnotes)^<br>→ Expressions régulières de filtre de règle de découverte de bas niveau<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)<br>→ Description du widget de valeur d'élément|*Nom DNS de l'hôte*^[2](supported_by_location#footnotes)^.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.DNS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.HOST}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ Paramètres de la clé de l'élément<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ IP/DNS de l'interface hôte<br>→ Champ "Hôtes autorisés" de l'élément Trapper<br>→ Paramètres supplémentaires de la surveillance de la base de données<br>→ Scripts SSH et Telnet<br>→ Champ de point de terminaison d'élément JMX<br>→ Surveillance Web^[4](supported_by_location#footnotes)^<br>→ Expressions régulières de filtre de règle de découverte de bas niveau<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)<br>→ Description du widget de valeur d'élément|*Nom d'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.HOST[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>`{HOSTNAME<1-9>}` est obsolète.| |{HOST.ID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*ID d'hôte.*<br><br>Peut être utilisé avec un index numérique comme {HOST.ID[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclenchement. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.IP}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Paramètres clé de l'élément^[1](supported_by_location#footnotes)^<br>→ IP/DNS de l'interface hôte<br>→ Champ "Hôtes autorisés" de l'élément Trapper<br>→ Paramètres supplémentaires de la surveillance de la base de données<br>→ Scripts SSH et Telnet<br>→ Champ de point de terminaison d'élément JMX<br>→ Surveillance Web^[4](supported_by_location#footnotes)^<br>→ Expressions régulières de filtre de règle de découverte de bas niveau<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)<br>→ Description du widget de valeur d'élément|*Adresse IP de l'hôte*^[2](supported_by_location#footnotes)^.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.IP[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>`{IPADDRESS<1-9>}` est obsolète.| |{HOST.METADATA}|→ Notifications et commandes d'enregistrement automatique|*Métadonnées de l'hôte.*<br>Utilisé uniquement pour l'enregistrement automatique des agents actifs.| |{HOST.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Paramètres de la clé de l'élément<br>→ IP/DNS de l'interface hôte<br>→ Champ "Hôtes autorisés" de l'élément Trapper<br>→ Paramètres supplémentaires de la surveillance de la base de données<br>→ Scripts SSH et Telnet<br>→ Surveillance Web^[4](supported_by_location#footnotes)^<br>→ Expressions régulières de filtre de règle de découverte de bas niveau<br>→ Champ URL du widget de tableau de bord d'URL dynamique<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)<br>→ Description du widget de valeur d'élément|*Nom d'hôte visible.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.PORT}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ URLs de déclencheur<br>→ Champ de point de terminaison d'élément JMX<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Port hôte (agent)*^[2](supported_by_location#footnotes)^.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {HOST.PORT[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{HOST.TARGET.CONN}|→ Commandes basées sur les déclencheurs<br>→ Commandes de mise à jour de problème<br>→ Commandes de découverte<br>→ Commandes d'enregistrement automatique|Adresse IP ou nom DNS de l'hôte cible, selon les paramètres de l'hôte.<br>Pris en charge depuis 5.4.0.| |{HOST.TARGET.DNS}|→ Commandes basées sur les déclencheurs<br>→ Commandes de mise à jour de problème<br>→ Commandes de découverte<br>→ Commandes d'enregistrement automatique|Nom DNS de l'hôte cible.<br>Pris en charge depuis 5.4.0.| |{HOST.TARGET.HOST}|→ Commandes basées sur les déclencheurs<br>→ Commandes de mise à jour de problème<br>→ Commandes de découverte<br>→ Commandes d'enregistrement automatique|Nom technique de l'hôte cible.<br>Pris en charge depuis 5.4.0.| |{HOST.TARGET.IP}|→ Commandes basées sur les déclencheurs<br>→ Commandes de mise à jour de problème<br>→ Commandes de découverte<br>→ Commandes d'enregistrement automatique|Adresse IP de l'hôte cible.<br>Pris en charge depuis 5.4.0.| |{HOST.TARGET.NAME}|→ Commandes basées sur les déclencheurs<br>→ Commandes de mise à jour de problème<br>→ Commandes de découverte<br>→ Commandes d'enregistrement automatique|Nom visible de l'hôte cible.<br>Pris en charge depuis 5.4.0.| |{HOSTGROUP.ID}|→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte|*Identifiant du groupe d'hôtes.*| |{INVENTORY.ALIAS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Alias de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.ALIAS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{INVENTORY.ASSET.TAG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Asset Tag de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.ASSET.TAG[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{INVENTORY.CHASSIS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Chassis de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.CHASSIS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{INVENTORY.CONTACT}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.CONTACT[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>`{PROFILE.CONTACT<1-9>}` est obsolète.| |{INVENTORY.CONTRACT.NUMBER}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contract number de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.CONTRACT.NUMBER[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{INVENTORY.DEPLOYMENT.STATUS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Deployment status de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.DEPLOYMENT.STATUS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{INVENTORY.HARDWARE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Matériel de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HARDWARE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.HARDWARE<1-9>}` est obsolète.| |{INVENTORY.HARDWARE.FULL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Matéiel (détails complets) de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HARDWARE.FULL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HOST.NETMASK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Masque de sous-réseau de l'hôte de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HOST.NETMASK[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HOST.NETWORKS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Réseaux de l'hôte de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HOST.NETWORKS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HOST.ROUTER}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Hôte - Routeur de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HOST.ROUTER[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HW.ARCH}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Architecture matérielle de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HW.ARCH[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HW.DATE.DECOMM}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Matériel - Date de retrait de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HW.DATE.DECOMM[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HW.DATE.EXPIRY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Matériel - Date de fin de maintenance de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HW.DATE.EXPIRY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HW.DATE.INSTALL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*-Champ Matériel - Date d'installation de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HW.DATE.INSTALL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.HW.DATE.PURCHASE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Matériel - Date d'achat de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.HW.DATE.PURCHASE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.INSTALLER.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Nom de l'installeur de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.INSTALLER.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.LOCATION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Emplacement de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.LOCATION[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.LOCATION<1-9>}` est obsolète.| |{INVENTORY.LOCATION.LAT}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Latitude de l'emplacement de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.LOCATION.LAT[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.LOCATION.LON}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*-Champ Longitude de l'emplacement de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.LOCATION.LON[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.MACADDRESS.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Adresse MAC A de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.MACADDRESS.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.MACADDRESS<1-9>}` est obsolète.| |{INVENTORY.MACADDRESS.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Adresse MAC B de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.MACADDRESS.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.MODEL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Modèle de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.MODEL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Nom de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.NAME<1-9>}` est oboslète.| |{INVENTORY.NOTES}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Notes de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.NOTES[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.NOTES<1-9>}` est obsolète.| |{INVENTORY.OOB.IP}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Hôte - Adresse IP OOB de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OOB.IP[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.OOB.NETMASK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Hôte - Masque de sous-réseau OOB de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OOB.NETMASK[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.OOB.ROUTER}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Hôte - Routeur OOB de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OOB.ROUTER[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.OS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ OS de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OS[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.OS<1-9>}` est obsolète.| |{INVENTORY.OS.FULL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ OS (détails complets) de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OS.FULL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.OS.SHORT}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ OS (Court) de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.OS.SHORT[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.CELL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Mobile de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.CELL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.EMAIL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Courriel de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Nom de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.NOTES}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Notes de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.NOTES[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.PHONE.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Téléphone 1 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.PHONE.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Téléphone 2 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.PRIMARY.SCREEN}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Principal - Identifiant de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.PRIMARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.CELL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Mobile de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.CELL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.EMAIL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Courriel de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Nom de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.NOTES}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Notes de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.NOTES[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.PHONE.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Téléphone 1 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.PHONE.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Téléphone 2 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.POC.SECONDARY.SCREEN}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Contact Secondaire - Identifiant de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.POC.SECONDARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SERIALNO.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Numéro de série A de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SERIALNO.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.SERIALNO<1-9>}` est obsolète.| |{INVENTORY.SERIALNO.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Numéro de série B de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SERIALNO.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.ADDRESS.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Adresse 1 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.ADDRESS.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.ADDRESS.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Adresse 2 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.ADDRESS.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.ADDRESS.C}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Adresse 3 de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.ADDRESS.C[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.CITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Ville de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.CITY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.COUNTRY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Pays de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.COUNTRY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.NOTES}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Notes de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.NOTES[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.RACK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Localisation baie de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.RACK[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.STATE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - État / province de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.STATE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SITE.ZIP}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Site - Code postal de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SITE.ZIP[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Logiciel de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.SOFTWARE<1-9>}` est obsolète.| |{INVENTORY.SOFTWARE.APP.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Application logicielle A de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.APP.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE.APP.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Application logicielle B de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.APP.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE.APP.C}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Application logicielle C de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.APP.C[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE.APP.D}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Application logicielle D de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.APP.D[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE.APP.E}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Application logicielle E de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.APP.E[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.SOFTWARE.FULL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*-Champ Logiciel (détails complet) de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.SOFTWARE.FULL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.TAG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Étiquette de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.TAG[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.TAG<1-9>}` est obsolète.| |{INVENTORY.TYPE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Type de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.TYPE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)<br><br>`{PROFILE.DEVICETYPE<1-9>}` est obsolète.| |{INVENTORY.TYPE.FULL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Type (détails complet) de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.TYPE.FULL[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.URL.A}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ URL A de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.URL.A[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.URL.B}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ URL B de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.URL.B[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.URL.C}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ URL C de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.URL.C[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{INVENTORY.VENDOR}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Champ Fabricant de l'inventaire de l'hôte.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {INVENTORY.VENDOR[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros)| |{ITEM.DESCRIPTION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Description du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.DESCRIPTION.ORIG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Description (avec les macros non résolues) du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.DESCRIPTION.ORIG[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>Prise en charge depuis 5.2.0.| |{ITEM.ID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte^[6](supported_by_location#footnotes)^<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*ID numérique du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.ID[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.KEY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte^[6](supported_by_location#footnotes)^<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Clé du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.KEY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>`{TRIGGER.KEY}` est obsolète.| |{ITEM.KEY.ORIG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→Noms et valeurs des éléments de type de script, des prototypes d'éléments et des paramètres de règle de découverte^[6](supported_by_location#footnotes)^<br>→ Champs d'élément de type d'agent HTTP, de prototype d'élément et de règle de découverte :<br> URL, champs de requête, corps de la requête, en-têtes, proxy, fichier de certificat SSL, fichier de clé SSL, hôtes autorisés.^[6](supported_by_location#footnotes)^<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Clé d'origine (avec les macros non développées) du Nième élément dans l'expression du déclencheur qui a provoqué une notification^[4](supported_by_location#footnotes)^.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.KEY.ORIG[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LASTVALUE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ URLs de déclencheur<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*La dernière valeur du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br>Il sera résolu en \*UNKNOWN\* dans le frontend si la dernière valeur de l'historique a été collectée plus qu'il y a la *Période d'affichage maximale de l'historique* (défini dans la section de menu [Administration→Général](/manual/web_interface/frontend_sections/administration/general#gui)).<br>Notez que depuis la version 4.0, lorsqu'il est utilisé dans le nom du problème, il ne sera pas résolu à la dernière valeur de l'élément lors de l'affichage des événements de problème, à la place, il conservera la valeur de l'élément à partir du moment où le problème se produit.<br>C'est un alias de `last(/{HOST.HOST}/{ITEM.KEY})`.<br><br>La valeur résolue est tronquée à 20 caractères pour être utilisable, par exemple, dans les URL de déclencheur. Pour obtenir une valeur complète, vous pouvez utiliser les [fonctions de macro](/manual/config/macros/macro_functions#seeing-full-item-values).<br><br>La [personnalisation](/manual/config/macros/macro_functions) de la valeur de la macro est prise en charge pour cette macro ; à partir de Zabbix 3.2.0.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LASTVALUE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. élément dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.AGE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Âge de l'événement d'élément de journal*, avec une précision jusqu'à une seconde.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.AGE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.DATE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Date de l'événement de l'élément de journal.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.DATE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.EVENTID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*ID de l'événement dans le journal des événements.*<br>Pour la surveillance du journal des événements Windows uniquement.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.EVENTID[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.NSEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Sévérité numérique de l'événement dans le journal des événements.*<br>Pour la surveillance du journal des événements Windows uniquement.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.NSEVERITY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.SEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Sévérité verbale de l'événement dans le journal des événements.*<br>Pour la surveillance du journal des événements Windows uniquement.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.SEVERITY[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.SOURCE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Source de l'événement dans le journal des événements.*<br>Pour la surveillance du journal des événements Windows uniquement.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.SOURCE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.LOG.TIME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms, données opérationnelles et descriptions des déclencheurs<br>→ URLs de déclencheur<br>→ Tags et valeurs de tags d'événement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Heure de l'événement de l'élément de journal.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.LOG.TIME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Nom du Nième élément dans l'expression du déclencheur qui a provoqué une notification.*<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.NAME.ORIG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|Cette macro est obsolète depuis Zabbix 6.0. Elle résolvait le *nom d'origine (c'est-à-dire sans macros résolues) de l'élément* dans les versions antérieures à la version 6.0 de Zabbix lorsque les macros utilisateur et les macros positionnelles étaient prises en charge dans le nom de l'élément.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.NAME.ORIG[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.STATE}|→ Notifications internes basées sur les éléments<br>→ Description du widget de valeur d'élément|*Le dernier état du Nième élément dans l'expression du déclencheur qui a provoqué une notification.* Valeurs possibles : **Non supporté** et **Normal**.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.STATE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.STATE.ERROR}|→ Notifications internes basées sur les éléments|*Message d'erreur expliquant pourquoi un élément n'est plus pris en charge.* <br> <br> Si un élément passe à l'état non supporté, puis est immédiatement à nouveau supporté, le champ d'erreur peut être vide.| |{ITEM.VALUE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Noms des déclencheurs, noms des événements, données opérationnelles et descriptions<br>→ [Noms et valeurs des tags](/manual/config/tagging#macro_support)<br>→ URLs de déclencheur<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|Résolue en l'une des valeurs suivantes :<br>1) la valeur historique (au moment de l'événement) du Nième élément dans l'expression du déclencheur, s'il est utilisé dans le contexte d'un changement d'état du déclencheur, par exemple, lors de l'affichage d'événements ou de l'envoi notifications.<br>2) la dernière valeur du Nième élément dans l'expression du déclencheur, si elle est utilisée sans le contexte de changement d'état du déclencheur, par exemple, lors de l'affichage d'une liste de déclencheurs dans une fenêtre de sélection contextuelle. Dans ce cas, fonctionne de la même manière que {ITEM.LASTVALUE}<br>Dans le premier cas, il sera résolu en \*UNKNOWN\* si la valeur de l'historique a déjà été supprimée ou n'a jamais été stockée.<br>Dans le second cas, et dans le frontend uniquement, il se résoudra à \*UNKNOWN\* si la dernière valeur d'historique a été collectée il y a plus de temps que la *Période maximale d'affichage de l'historique* (définie dans [Administration→Général](/manual/web_interface/frontend_sections/administration/general#gui)).<br><br>La valeur résolue est tronquée à 20 caractères pour être utilisable, par exemple, dans les URL de déclencheur. Pour obtenir une valeur complète, vous pouvez utiliser les [fonctions de macro](/manual/config/macros/macro_functions#seeing-full-item-values).<br><br>[La personnalisation](/manual/config/macros/macro_functions) de la valeur de la macro est prise en charge pour cette macro, à partir de Zabbix 3.2.0.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {ITEM.VALUE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. élément dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{ITEM.VALUETYPE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Description du widget de valeur d'élément|*Type de valeur du Nième élément dans l'expression du déclencheur qui a provoqué une notification.* Valeurs possibles : 0 - nombre flottant, 1 - caractère, 2 - journal, 3 - numérique non signé, 4 - texte.<br><br>Cette macro peut être utilisé avec un index numérique, par ex. {ITEM.VALUETYPE[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).<br><br>Pris en charge depuis 5.4.0.| |{LLDRULE.DESCRIPTION}|→ Notifications internes basées sur les règles LLD|*Description de la règle de découverte de bas niveau qui a provoqué une notification.*| |{LLDRULE.DESCRIPTION.ORIG}|→ Notifications internes basées sur les règles LLD|*Description (avec macros non résolues) de la règle de découverte de bas niveau qui a provoqué une notification.*<br>Pris en charge depuis 5.2.0.| |{LLDRULE.ID}|→ Notifications internes basées sur les règles LLD|*ID numérique de la règle de découverte de bas niveau qui a provoqué une notification.*| |{LLDRULE.KEY}|→ Notifications internes basées sur les règles LLD|*Clé de la règle de découverte de bas niveau qui a provoqué une notification.*| |{LLDRULE.KEY.ORIG}|→ Notifications internes basées sur les règles LLD|*Clé d'origine (avec les macros non résolues) de la règle de découverte de bas niveau qui a provoqué une notification.*| |{LLDRULE.NAME}|→ Notifications internes basées sur les règles LLD|*Nom de la règle de découverte de bas niveau (avec les macros résolues) qui a provoqué une notification.*| |{LLDRULE.NAME.ORIG}|→ Notifications internes basées sur les règles LLD|*Nom d'origine (c'est-à-dire sans macros résolues) de la règle de découverte de bas niveau qui a provoqué une notification.*| |{LLDRULE.STATE}|→ Notifications internes basées sur les règles LLD|*Le dernier état de la règle de découverte de bas niveau.* Valeurs possibles : **Non supporté** et **Normal**.| |{LLDRULE.STATE.ERROR}|→ Notifications internes basées sur les règles LLD|*Message d'erreur expliquant pourquoi une règle LLD n'est plus supportée.* <br> <br> Si une règle LLD passe à l'état non supporté, puis est immédiatement à nouveau supportée, le champ d'erreur peut être vide.| |{MAP.ID}|→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte|*Identifiant de la carte du réseau.*| |{MAP.NAME}|→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ Champ de texte dans les formes de carte|*Nom de la carte réseau.*<br>Pris en charge depuis la version 3.4.0.| |{PROXY.DESCRIPTION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Description du proxy*. Résout soit :<br>1) le proxy du Nième élément dans l'expression du déclencheur (dans les notifications basées sur le déclencheur). Vous pouvez utiliser des [macros indexées](/manual/appendix/macros/supported_by_location#indexed_macros) ici.<br>2) le proxy, qui a exécuté la découverte (dans les notifications de découverte). Utilisez {PROXY.DESCRIPTION} ici, sans indexation.<br>3) le proxy auprès duquel un agent actif s'est enregistré (dans les notifications d'enregistrement automatique). Utilisez {PROXY.DESCRIPTION} ici, sans indexation.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {PROXY.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{PROXY.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom du proxy*. Résout soit :<br>1) le proxy du Nième élément dans l'expression du déclencheur (dans les notifications basées sur le déclencheur). Vous pouvez utiliser des [macros indexées](/manual/appendix/macros/supported_by_location#indexed_macros) ici.<br>2) le proxy, qui a exécuté la découverte (dans les notifications de découverte). Utilisez {PROXY.NAME} ici, sans indexation.<br>3) le proxy auquel un agent actif s'est enregistré (dans les notifications d'enregistrement automatique). Utilisez {PROXY.NAME} ici, sans indexation.<br><br>Cette macro peut être utilisée avec un index numérique, par ex. {PROXY.NAME[<1-9>](supported_by_location#indexed_macros)} pour pointer vers le premier, deuxième, troisième, etc. hôte dans une expression de déclencheur. Voir les [macros indexées](supported_by_location#indexed_macros).| |{SERVICE.DESCRIPTION}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Description du service* (avec macros résolues).| |{SERVICE.NAME}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Nom du service* (avec macros résolues).| |{SERVICE.ROOTCAUSE}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Liste des événements déclencheurs de problèmes qui ont provoqué l'échec d'un service*, triés par sévérité et nom d'hôte. Inclut les détails suivants : nom d'hôte, nom de l'événement, sévérité, âge, tags de service et valeurs de tags de service.| |{SERVICE.TAGS}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Une liste de tags d'événement de service séparés par des virgules.* Les tags d'événement de service peuvent être définis dans la section Tags de la configuration du service. Développé en une chaîne vide si aucun tag n'existe.| |{SERVICE.TAGSJSON}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Un tableau JSON contenant des objets de tag d'événement de service.* Les tags d'événement de service peuvent être définis dans la section Tags de la configuration du service. Développé en un tableau vide si aucun tag n'existe.| |{SERVICE.TAGS.\<nom tag\>}|→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service|*Valeur de tag d'événement de service référencée par le nom du tag.* Les tags d'événement de service peuvent être définis dans la section de configuration de service Tags.<br>Un nom de tag contenant des caractères non alphanumériques (y compris des caractères UTF multioctets non anglais) doit être placé entre guillemets doubles. Les guillemets et les barres obliques inverses à l'intérieur d'un nom de tag entre guillemets doivent être protégés par une barre oblique inverse.| |{TIME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications et commandes basées sur le service<br>→ Notifications et commandes de mise à jour de service<br>→ Notifications et commandes de découverte<br>→ Notifications et commandes d'enregistrement automatique<br>→ Notifications internes<br>→ Noms des événements déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Heure actuelle au format hh:mm:ss.*| |{TRIGGER.DESCRIPTION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Description du déclencheur.*<br>Toutes les macros prises en charge dans une description de déclencheur seront développées si `{TRIGGER.DESCRIPTION}` est utilisé dans le texte de notification.<br>`{TRIGGER.COMMENT}` est obsolète.| |{TRIGGER.EXPRESSION.EXPLAIN}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle <br>→ Noms des événements|*Expression de déclenchement partiellement évaluée.*<br>Les fonctions basées sur les éléments sont évaluées et remplacées par les résultats au moment de la génération de l'événement, tandis que toutes les autres fonctions sont affichées telles qu'elles sont écrites dans l'expression. Peut être utilisé pour le débogage des expressions de déclencheur.| |{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN}|→ [Notifications de récupération](/manual/config/notifications/action/recovery_operations) de problème et commandes<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Expression de récupération de déclencheur partiellement évaluée. Peut être utilisé pour le débogage des expressions de récupération de déclencheur.| |{TRIGGER.EVENTS.ACK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Libellés des éléments de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nombre d'événements reconnus pour un élément cartographique dans les cartes ou pour le déclencheur qui a généré l'événement actuel dans les notifications.*| |{TRIGGER.EVENTS.PROBLEM.ACK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Libellés des éléments de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nombre d'événements PROBLÈME acquittés pour tous les déclencheurs, quel que soit leur état.*| |{TRIGGER.EVENTS.PROBLEM.UNACK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Libellés des éléments de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nombre d'événements PROBLÈME non acquittés pour tous les déclencheurs, quel que soit leur état.*| |{TRIGGER.EVENTS.UNACK}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Libellés des éléments de carte<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nombre d'événements non acquittés pour un élément cartographique dans les cartes ou pour le déclencheur qui a généré l'événement actuel dans les notifications.*| |{TRIGGER.HOSTGROUP.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Une liste triée (par requête SQL), séparée par des virgules, des groupes d'hôtes dans lesquels le déclencheur est défini.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}|→ Libellés des éléments de carte|*Nombre d'événements PROBLÈME acquittés pour les déclencheurs en état PROBLÈME.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}|→ Libellés des éléments de carte|*Nombre d'événements PROBLÈME non acquittés pour les déclencheurs en état PROBLÈME.*| |{TRIGGER.EXPRESSION}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Expression de déclenchement.*| |{TRIGGER.EXPRESSION.RECOVERY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Expression de déclenchement de récupération* si *Génération d'événement OK* dans [la configuration du déclencheur](/manual/config/triggers/trigger) est défini sur 'Expression de récupération' ; sinon une chaîne vide est renvoyée.<br>Supporté depuis 3.2.0.| |{TRIGGER.ID}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ Étiquettes d'élément de carte, noms et valeurs d'URL de carte<br>→ URLs de déclencheur<br>→ Valeur de tag de déclencheur<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Identifiant numérique du déclencheur qui a déclenché cette action.*<br>Pris en charge dans les valeurs des tags de déclencheur depuis la version 4.4.1.| |{TRIGGER.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom du déclencheur* (avec les macros résolues).<br>Notez que depuis la version 4.0.0, {EVENT.NAME} peut être utilisé dans les actions pour afficher le nom de l'événement/du problème déclenché avec les macros résolues.| |{TRIGGER.NAME.ORIG}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom d'origine du déclencheur* (c'est-à-dire sans macros résolues).| |{TRIGGER.NSEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Sévérité numérique du déclencheur.* Valeurs possibles : 0 - Non classifié, 1 - Information, 2 - Avertissement, 3 - Moyen, 4 - Haut, 5 - Désastre.| |{TRIGGER.SEVERITY}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Nom de la sévérité du déclencheur.* Peut être défini dans *Administration → Général → Options d'affichage du déclencheur*.| |{TRIGGER.STATE}|→ Notifications internes basées sur des déclencheurs|*Le dernier état du déclencheur.* Valeurs possibles : **Inconnu** et **Normal**.| |{TRIGGER.STATE.ERROR}|→ Notifications internes basées sur des déclencheurs|*Message d'erreur expliquant pourquoi un déclencheur n'est plus supporté.* <br> <br> Si un déclencheur passe à l'état non supporté, puis est immédiatement à nouveau supporté, le champ d'erreur peut être vide.| |{TRIGGER.STATUS}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur de déclenchement au moment de l'exécution de l'étape d'opération.* Peut être PROBLÈME ou OK.<br>`{STATUS}` est obsolète.| |{TRIGGER.TEMPLATE.NAME}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Une liste triée (par requête SQL), séparée par des virgules de modèles dans laquelle le déclencheur est défini, ou \*UNKNOWN\* si le déclencheur est défini dans un hôte.*| |{TRIGGER.URL}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Notifications internes basées sur des déclencheurs<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*URL du déclencheur.*| |{TRIGGER.VALUE}|→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Expressions de déclenchement<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle |*Valeur numérique actuelle du déclencheur* : 0 - le déclencheur est à l'état OK, 1 - le déclencheur est à l'état PROBLÈME.| |{TRIGGERS.UNACK}|→ Libellés des éléments de carte|*Nombre de déclencheurs non acquittés pour un élément cartographique, sans tenir compte de l'état du déclencheur.*<br>Un déclencheur est considéré comme non acquitté si au moins un de ses événements PROBLÈME n'est pas acquitté.| |{TRIGGERS.PROBLEM.UNACK}|→ Libellés des éléments de carte|*Nombre de déclencheurs PROBLÈME non acquittés pour un élément cartographique.*<br>Un déclencheur est considéré comme non acquitté si au moins un de ses événements PROBLÈME n'est pas acquitté.| |{TRIGGERS.ACK}|→ Libellés des éléments de carte|*Nombre de déclencheurs acquittés pour un élément de la carte, sans tenir compte de l'état du déclencheur.*<br>Un déclencheur est considéré comme acquitté si tous ses événements PROBLÈME sont acquittés.| |{TRIGGERS.PROBLEM.ACK}|→ Libellés des éléments de carte|*Nombre de déclencheurs de PROBLÈME acquittés pour un élément de la carte.*<br>Un déclencheur est considéré comme acquitté si tous ses événements PROBLÈME sont acquittés.| |{USER.FULLNAME}|→ Notifications et commandes de mise à jour des problèmes<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)|*Nom, prénom et nom d'utilisateur de l'utilisateur* qui a ajouté l'acquittement de l'événement ou lancé le script.<br>Pris en charge pour les mises à jour des problèmes depuis la version 3.4.0, pour les scripts globaux depuis la version 5.0.2| |{USER.NAME}|→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)|*Prénom de l'utilisateur* qui a lancé le script.<br>Pris en charge depuis la version 5.0.2.| |{USER.SURNAME}|→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)|*Nom de l'utilisateur* qui a lancé le script.<br>Prise en charge depuis la version 5.0.2.| |{USER.USERNAME}|→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action manuelle de l'hôte (y compris le texte de confirmation)<br>→ [Scripts](/manual/web_interface/frontend_sections/administration/scripts) d'action d'événement manuelle (y compris le texte de confirmation)|*Nom d'utilisateur de l'utilisateur* qui a lancé le script.<br>Pris en charge depuis la version 5.0.2.<br>{USER.ALIAS}, pris en charge avant Zabbix 5.4.0, est désormais obsolète.| |{$MACRO}|→ Voir : [Macros utilisateur prises en charge par emplacement](/manual/appendix/macros/supported_by_location_user)|*[Macros définies par l'utilisateur](/manual/config/macros/user_macros).*| |{\#MACRO}|→ Voir : [Macros de découverte de bas niveau](/manual/config/macros/lld_macros)|*Macros de découverte de bas niveau.*<br><br>[La personnalisation](/manual/config/macros/macro_functions) de la valeur de la macro est prise en charge pour cette macro, à partir de Zabbix 4.0.0.| |{?EXPRESSION}|→ Noms des événements déclencheurs<br>→ Notifications et commandes basées sur des déclencheurs<br>→ Notifications et commandes de mise à jour des problèmes<br>→ Libellés des éléments de carte^[3](supported_by_location#footnotes)^<br>→ Étiquettes de forme de carte^[3](supported_by_location#footnotes)^<br>→ Étiquettes de lien de carte^[3](supported_by_location#footnotes)^<br>→ Noms des graphiques^[5](supported_by_location#footnotes)^|Voir les [macros d'expression](/manual/config/macros/expression_macros).<br>Pris en charge depuis 5.2.0.| #### Overview The trigger list for a host can be accessed from *Configuration → Hosts* by clicking on *Triggers* for the respective host. {width="600"} Displayed data: |Column|Description| |--|--------| |*Severity*|Severity of the trigger is displayed by both name and cell background color.| |*Value*|Trigger value is displayed:<br>**OK** - the trigger is in the OK state<br>**PROBLEM** - the trigger is in the Problem state| |*Host*|Host of the trigger.<br>This column is displayed only if multiple hosts are selected in the filter.| |*Name*|Name of the trigger, displayed as a blue link to trigger details.<br>Clicking on the trigger name link opens the trigger [configuration form](/manual/config/triggers/trigger#configuration).<br>If the host trigger belongs to a template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger list on the template level.<br>If the trigger has been created from a trigger prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the trigger prototype list.| |*Operational data*|Operational data definition of the trigger, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Expression*|Trigger expression is displayed. The host-item part of the expression is displayed as a link, leading to the item configuration form.| |*Status*|Trigger status is displayed - *Enabled*, *Disabled* or *Unknown*. By clicking on the status you can change it - from Enabled to Disabled (and back); from Unknown to Disabled (and back).<br>Problems of a disabled trigger are no longer displayed in the frontend, but are not deleted.| |*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.| |*Tags*|If a trigger contains tags, tag name and value are displayed in this column.| To configure a new trigger, click on the *Create trigger* button at the top right corner. #### Aperçu La liste des déclencheurs pour un hôte est accessible depuis *Configuration → Hôtes* en cliquant sur *Déclencheurs* pour l'hôte respectif. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Sévérité*|La sévérité du déclencheur est affichée à la fois par le nom et la couleur d'arrière-plan de la cellule.| |*Valeur*|La valeur du déclencheur s'affiche :<br>**OK** - le déclencheur est à l'état OK<br>**PROBLÈME** - le déclencheur est à l'état Problème| |*Hôte*|Hôte du déclencheur.<br>Cette colonne s'affiche uniquement si plusieurs hôtes sont sélectionnés dans le filtre.| |*Nom*|Nom du déclencheur, affiché sous forme de lien bleu vers les détails du déclencheur.<br>Cliquer sur le lien du nom du déclencheur ouvre le [formulaire de configuration](/manual/config/triggers/trigger#configuration) du déclencheur.<br>Si le déclencheur hôte appartient à un modèle, le nom du modèle s'affiche avant le nom du déclencheur, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des déclencheurs au niveau du modèle.<br>Si le déclencheur a été créé à partir d'un prototype de déclencheur, son nom est précédé du nom de la règle de découverte de bas niveau, en orange. Cliquer sur le nom de la règle de découverte ouvrira la liste des prototypes de déclencheur.| |*Données opérationnelles*|Définition des données opérationnelles du déclencheur, contenant des chaînes arbitraires et des macros qui seront résolues dynamiquement dans *Surveillance* → *Problèmes*.| |*Expression*|L'expression de déclenchement s'affiche. La partie élément hôte de l'expression est affichée sous forme de lien, menant au formulaire de configuration de l'élément.| |*État*|L'état du déclencheur est affiché - *Activé*, *Désactivé* ou *Inconnu*. En cliquant sur le statut, vous pouvez le changer - de Activé à Désactivé (et inversement) ; de Inconnu à Désactivé (et inversement).<br>Les problèmes d'un déclencheur désactivé ne sont plus affichés dans l'interface, mais ne sont pas supprimés.| |*Info*|Si tout fonctionne correctement, aucune icône n'est affichée dans cette colonne. En cas d'erreur, une icône carrée avec la lettre "i" s'affiche. Survolez l'icône pour voir une info-bulle avec la description de l'erreur.| |*Tags*|Si un déclencheur contient des tags, le nom et la valeur du tag sont affichés dans cette colonne.| Pour configurer un nouveau déclencheur, cliquez sur le bouton *Créer un déclencheur* dans le coin supérieur droit. #### Overview The trigger list for a template can be accessed from *Configuration → Templates* by clicking on *Triggers* for the respective template. {width="600"} Displayed data: |Column|Description| |--|--------| |*Severity*|Severity of the trigger is displayed by both name and cell background color.| |*Template*|Template the trigger belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the trigger displayed as a blue link to trigger details.<br>Clicking on the trigger name link opens the trigger [configuration form](/manual/config/triggers/trigger#configuration).<br>If the trigger is inherited from another template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger list on that template level.| |*Operational data*|Operational data definition of the trigger, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Expression*|Trigger expression is displayed. The template-item part of the expression is displayed as a link, leading to the item configuration form.| |*Status*|Trigger status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|If a trigger contains tags, tag name and value are displayed in this column.| To configure a new trigger, click on the *Create trigger* button at the top right corner. #### Aperçu La liste des déclencheurs pour un modèle est accessible depuis *Configuration → Modèles* en cliquant sur *Déclencheurs* pour le modèle respectif. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Sévérité*|La gravité du déclencheur est affichée à la fois par le nom et la couleur d'arrière-plan de la cellule.| |*Modèle*|Modèle auquel appartient le déclencheur.<br>Cette colonne s'affiche uniquement si plusieurs modèles sont sélectionnés dans le filtre.| |*Nom*|Nom du déclencheur affiché sous forme de lien bleu vers les détails du déclencheur.<br>Cliquer sur le lien du nom du déclencheur ouvre le [formulaire de configuration](/manual/config/triggers/trigger#configuration) du déclencheur.<br> Si le déclencheur est hérité d'un autre modèle, le nom du modèle s'affiche avant le nom du déclencheur, sous la forme d'un lien gris. Cliquer sur le lien du modèle ouvrira la liste des déclencheurs à ce niveau de modèle.| |*Donnée opérationnelle*|Définition des données opérationnelles du déclencheur, contenant des chaînes arbitraires et des macros qui seront résolues dynamiquement dans *Surveillance* → *Problèmes*.| |*Expression*|L'expression de déclenchement est affichée. La partie élément de modèle de l'expression est affichée sous forme de lien, menant au formulaire de configuration de l'élément.| |*État*|L'état du déclencheur est affiché - *Activé* ou *Désactivé*. En cliquant sur le statut, vous pouvez le changer - d'Activé à Désactivé (et inversement).| |*Tags*|Si un déclencheur contient des tags, le nom et la valeur du tag sont affichés dans cette colonne.| Pour configurer un nouveau déclencheur, cliquez sur le bouton *Créer un déclencheur* dans le coin supérieur droit. #### Overview The webhook media type is useful for making HTTP calls using custom JavaScript code for straightforward integration with external software such as helpdesk systems, chats, or messengers. You may choose to import an integration provided by Zabbix or create a custom integration from scratch. #### Aperçu Le type de média webhook est utile pour effectuer des appels HTTP à l'aide de codes JavaScript personnalisés pour une intégration simple avec un logiciel externe tels que les systèmes d'assistance, les chats ou les messageries. Vous pouvez choisir d'importer une intégration fournie par Zabbix ou créez une intégration personnalisée à partir de zéro. #### Overview The [web scenario](/manual/web_monitoring) list for a host can be accessed from *Configuration → Hosts* by clicking on *Web* for the respective host. A list of existing web scenarios is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the web scenario. Clicking on the web scenario name opens the web scenario [configuration form](/manual/web_monitoring#configuring-a-web-scenario).<br>If the host web scenario belongs to a template, the template name is displayed before the web scenario name as a gray link. Clicking on the template link will open the web scenario list on the template level.| |*Number of steps*|The number of steps the scenario contains.| |*Update interval*|How often the scenario is performed.| |*Attempts*|How many attempts for executing web scenario steps are performed.| |*Authentication*|Authentication method is displayed - Basic, NTLM, or None.| |*HTTP proxy*|Displays HTTP proxy or 'No' if not used.| |*Status*|Web scenario status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| |*Tags*|Web scenario tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| |*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.| To configure a new web scenario, click on the *Create web scenario* button at the top right corner. #### Aperçu La liste [scénario Web](/manual/web_monitoring) d'un hôte est accessible depuis *Configuration → Hôtes* en cliquant sur *Web* pour l'hôte respectif. Une liste des scénarios Web existants s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du scénario Web. Cliquer sur le nom du scénario Web ouvre le [formulaire de configuration](/manual/web_monitoring#configuring-a-web-scenario) du scénario Web.<br>Si le scénario Web hôte appartient à un modèle, le nom du modèle s'affiche avant le nom du scénario sous forme de lien gris. Cliquer sur le lien du modèle ouvrira la liste des scénarios Web au niveau du modèle.| |*Nombre d'étapes*|Le nombre d'étapes que contient le scénario.| |*Intervalle*|Fréquence d'exécution du scénario.| |*Tentatives*|Combien de tentatives d'exécution d'étapes de scénario Web sont effectuées.| |*Authentication*|La méthode d'authentification est affichée - Basic, NTLM ou Aucune.| |*Proxy HTTP*|Affiche le proxy HTTP ou 'Non' s'il n'est pas utilisé.| |*État*|Le statut du scénario Web est affiché - *Activé* ou *Désactivé*.<br>En cliquant sur le statut, vous pouvez le modifier.| |*Tags*|Les tags du scénario Web sont affichés.<br>Jusqu'à trois tags (paires nom:valeur) peuvent être affichés. S'il y a plus de tags, un lien "..." s'affiche qui permet de voir tous les tags au passage de la souris.| |*Info*|Si tout fonctionne correctement, aucune icône n'est affichée dans cette colonne. En cas d'erreur, une icône carrée avec la lettre "i" s'affiche. Passez la souris sur l'icône pour voir une info-bulle avec la description de l'erreur.| Pour configurer un nouveau scénario Web, cliquez sur le bouton *Créer un scénario Web* dans le coin supérieur droit. #### Overview The [web scenario](/manual/web_monitoring) list for a template can be accessed from *Configuration → Templates* by clicking on *Web* for the respective template. A list of existing web scenarios is displayed. {width="600"} Displayed data: |Column|Description| |--|--------| |*Name*|Name of the web scenario. Clicking on the web scenario name opens the web scenario [configuration form](/manual/web_monitoring#configuring-a-web-scenario).<br>If the web scenario is inherited from another template, the template name is displayed before the web scenario name, as a gray link. Clicking on the template link will open the web scenarios list on that template level.| |*Number of steps*|The number of steps the scenario contains.| |*Update interval*|How often the scenario is performed.| |*Attempts*|How many attempts for executing web scenario steps are performed.| |*Authentication*|Authentication method is displayed - Basic, NTLM on None.| |*HTTP proxy*|Displays HTTP proxy or 'No' if not used.| |*Status*|Web scenario status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| |*Tags*|Web scenario tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| To configure a new web scenario, click on the *Create web scenario* button at the top right corner. #### Aperçu La liste des [scénario Web](/manual/web_monitoring) d'un modèle est accessible depuis *Configuration → Modèles* en cliquant sur *Web* pour le modèle respectif. Une liste des scénarios Web existants s'affiche. {width="600"} Données affichées : |Colonne|Description| |--|--------| |*Nom*|Nom du scénario Web. Cliquer sur le nom du scénario Web ouvre le [formulaire de configuration](/manual/web_monitoring#configuring-a-web-scenario) du scénario Web.<br>Si le scénario Web est hérité d'un autre modèle, le nom du modèle s'affiche avant le nom du scénario, sous forme de lien gris. Cliquer sur le lien du modèle ouvrira la liste des scénarios Web à ce niveau de modèle.| |*Nombre d'étapes*|Le nombre d'étapes que contient le scénario.| |*Intervalle*|Fréquence d'exécution du scénario.| |*Tentatives*|Combien de tentatives d'exécution d'étapes de scénario Web sont effectuées.| |*Authentication*|La méthode d'authentification est affichée - Basic, NTLM ou Aucune.| |*Proxy HTTP*|Affiche le proxy HTTP ou 'Non' s'il n'est pas utilisé.| |*État*|Le statut du scénario Web est affiché - *Activé* ou *Désactivé*.<br>En cliquant sur le statut, vous pouvez le modifier.| |*Tags*|Les tags du scénario Web sont affichés.<br>Jusqu'à trois tags (paires nom:valeur) peuvent être affichés. S'il y a plus de tags, un lien "..." s'affiche qui permet de voir tous les tags au passage de la souris.| Pour configurer un nouveau scénario Web, cliquez sur le bouton *Créer un scénario Web* dans le coin supérieur droit. #### Overview This item type allows data polling using the HTTP/HTTPS protocol. Trapping is also possible using Zabbix sender or Zabbix sender protocol. HTTP item check is executed by Zabbix server. However, when hosts are monitored by a Zabbix proxy, HTTP item checks are executed by the proxy. HTTP item checks do not require any agent running on a host being monitored. HTTP agent supports both HTTP and HTTPS. Zabbix will optionally follow redirects (see the *Follow redirects* option below). Maximum number of redirects is hard-coded to 10 (using cURL option CURLOPT\_MAXREDIRS). See also [known issues](/manual/installation/known_issues#https_checks) for when using HTTPS protocol. ::: noteimportant Zabbix server/proxy must be initially configured with cURL (libcurl) support. ::: #### Aperçu Ce type d'élément autorise l'interrogation des données à l'aide du protocole HTTP/HTTPS. Le trap est également possible à l’aide de Zabbix Sender ou du protocole Zabbix Sender. La vérification d'éléments HTTP est exécutée par le serveur Zabbix. Toutefois, lorsque les hôtes sont surveillés par un proxy Zabbix, les vérifications d’éléments HTTP sont exécutées par le proxy. Les vérifications d'éléments HTTP n'exigent pas que l'agent s'exécute sur un hôte surveillé. L'agent HTTP prend en charge HTTP et HTTPS. Zabbix suivra éventuellement les redirections (voir l’option *Suivre les redirections* ci-dessous). Le nombre maximum de redirections est codé en dur à 10 (à l'aide de l'option cURL CURLOPT\_MAXREDIRS). Voir également les [problèmes connus](/manual/installation/known_issues#verifications_https) liés à l'utilisation du protocole HTTPS. ::: noteimportant Le serveur/proxy Zabbix doit être configuré initialement avec le support cURL (libcurl). ::: ### Overview This page provides the steps required to build a loadable plugin binary from the sources. If the source tarball is downloaded, it is possible to build the plugin offline, i.e. without the internet connection. The PostgreSQL plugin is used as an example. Other loadable plugins can be built in a similar way. ### Aperçu Cette page fournit les étapes nécessaires pour créer un binaire de plugin chargeable à partir des sources. Si l'archive source est téléchargée, il est possible de créer le plugin hors ligne, c'est-à-dire sans connexion Internet. Le plugin PostgreSQL est utilisé comme exemple. D'autres plugins chargeables peuvent être construits de la même manière. ### Overview This section allows to view and [configure](/manual/it_services/sla) SLAs. ### Aperçu Cette section permet de visualiser et de [configurer](/manual/it_services/sla) les SLA. #### Overview This section contains a list of locations, where [user-definable](/manual/config/macros/user_macros) macros are supported. ::: noteclassic Only global-level user macros are supported for *Actions*, *Network discovery*, *Proxies* and all locations listed under *Other locations* section of this page. In the mentioned locations, host-level and template-level macros will not be resolved. ::: #### Aperçu Cette section contient une liste des emplacements où les macros [définissables par l'utilisateur](/manual/config/macros/user_macros) sont prises en charge. ::: noteclassic Seules les macros utilisateur de niveau global sont prises en charge pour les *Actions*, la *Découverte du réseau*, les *Proxies* et tous les emplacements répertoriés dans la section *Autres emplacements* de cette page. Dans les emplacements mentionnés, les macros au niveau de l'hôte et du modèle ne seront pas résolues. ::: ### Overview This section contains best practices that should be observed in order to set up Zabbix in a secure way. The practices contained here are not required for the functioning of Zabbix. They are recommended for better security of the system. ### Aperçu Cette section contient les bonnes pratiques à respecter pour configurer Zabbix de manière sécurisée. Les pratiques contenues ici ne sont pas nécessaires au fonctionnement de Zabbix. Elles sont recommandées pour une meilleure sécurité du système. #### Overview This section contains descriptions of configuration file parameters for Zabbix agent 2 plugins. Please use the sidebar to access information about the specific plugin. #### Aperçu Cette section contient des descriptions des paramètres du fichier de configuration pour les plugins de l'agent Zabbix 2. Veuillez utiliser la barre latérale pour accéder aux informations sur le plugin spécifique. #### Overview This section contains instructions for creating Oracle database and configuring connections between the database and Zabbix server, proxy, and frontend. #### Aperçu Cette section contient des instructions pour créer une base de données Oracle et configurer les connexions entre la base de données et le serveur Zabbix, le proxy et l'interface. #### Overview This section demonstrates how to build Zabbix agent 2 (Windows) from sources. #### Aperçu Cette section montre comment construire l'agent Zabbix 2 (Windows) à partir des sources. #### Overview This section demonstrates how to build Zabbix macOS agent binaries from sources with or without TLS. #### Aperçu Cette section montre comment créer des binaires d'agent Zabbix macOS à partir de sources avec ou sans TLS. #### Overview This section demonstrates how to build Zabbix Windows agent binaries from sources with or without TLS. #### Aperçu Cette section montre comment construire l'agent Zabbix (Windows) à partir des sources avec ou sans TLS. ### Overview This section describes a simple setup for monitoring Zabbix high availability cluster as a service. ### Aperçu Cette section décrit une configuration simple pour surveiller le cluster haute disponibilité Zabbix en tant que service. ### Overview This section describes Zabbix additions to the JavaScript language implemented with Duktape and supported global JavaScript functions. ### Aperçu Cette section décrit les ajouts de Zabbix au langage JavaScript implémentés avec Duktape et les fonctions JavaScript globales prises en charge. #### Overview This section explains how to add a “Host group” type element when configuring a [network map](/manual/config/ visualization/maps/map). #### Aperçu Cette section explique comment ajouter un élément de type "Groupe d'hôte" durant le configuration d'une [carte réseau](/manual/config/visualization/maps/map). #### Overview This section lists parameters supported in a Zabbix agent configuration file (zabbix\_agentd.conf). Note that: - The default values reflect daemon defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration de l'agent Zabbix (zabbix\_agentd.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du démon, pas les valeurs du fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in a Zabbix proxy configuration file (zabbix\_proxy.conf). Note that: - The default values reflect daemon defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du proxy Zabbix (zabbix\_proxy.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du démon, pas les valeurs du fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in a Zabbix server configuration file (zabbix\_server.conf). Note that: - The default values reflect daemon defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du server Zabbix (zabbix\_server.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du démon, pas les valeurs du fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in the Ceph Zabbix agent 2 plugin configuration file (ceph.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du plugin Ceph Zabbix agent 2 (ceph.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in the Docker Zabbix agent 2 plugin configuration file (docker.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du plug-in Docker Zabbix agent 2 (docker.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in the Memcached Zabbix agent 2 plugin configuration file (memcached.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du plugin Memcached Zabbix agent 2 (memcached.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in the Modbus Zabbix agent 2 plugin configuration file (modbus.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du plug-in Modbus Zabbix agent 2 (modbus.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section lists parameters supported in the MySQL Zabbix agent 2 plugin configuration file (mysql.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Cette section répertorie les paramètres pris en charge dans le fichier de configuration du plug-in MySQL Zabbix agent 2 (mysql.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview This section presents a step-by-step real-life example of how web monitoring can be used. Let's use Zabbix web monitoring to monitor the web interface of Zabbix. We want to know if it is available, provides the right content and how quickly it works. To do that we also must log in with our user name and password. #### Aperçu Cette section présente un exemple concret, étape par étape, de l’utilisation de la supervision Web. Utilisons la supervision Web de Zabbix pour surveiller l’interface Web Zabbix. Nous voulons savoir si elle est disponible, fournit le bon contenu et à quelle vitesse elle fonctionne. Pour ce faire, nous devons également nous connecter avec notre nom d'utilisateur et notre mot de passe. #### Overview This section provides details of preprocessing by JavaScript. #### Aperçu Cette section fournit des détails sur le prétraitement par JavaScript. #### Overview This section provides details of supported JSONPath functionality in item value preprocessing steps. JSONPath consists of segments separated with dots. A segment can be either a simple word like a JSON value name, `*` or a more complex construct enclosed within square brackets `[` `]`. The separating dot before bracket segment is optional and can be omitted. For example: |Path|Description| |----|-----------| |`$.object.name`|Return the object.name contents.| |`$.object['name']`|Return the object.name contents.| |`$.object.['name']`|Return the object.name contents.| |`$["object"]['name']`|Return the object.name contents.| |`$.['object'].["name"]`|Return the object.name contents.| |`$.object.history.length()`|Return the number of object.history array elements.| |`$[?(@.name == 'Object')].price.first()`|Return the price field of the first object with name 'Object'.| |`$[?(@.name == 'Object')].history.first().length()`|Return the number of history array elements of the first object with name 'Object'.| |`$[?(@.price > 10)].length()`|Return the number of objects with price being greater than 10.| See also: [Escaping special characters from LLD macro values in JSONPath](/manual/config/items/preprocessing/jsonpath_functionality/escaping_lld_macros). #### Aperçu Cette section fournit des détails sur la fonctionnalité JSONPath prise en charge dans les étapes de prétraitement de la valeur de l'élément. JSONPath se compose de segments séparés par des points. Un segment peut être soit un mot simple comme un nom de valeur JSON, `*` ou une construction plus complexe entre crochets `[` `]`. Le point de séparation avant le segment entre crochets est facultatif et peut être omis. Par exemple: |Chemin|Description| |----|-----------| |`$.object.name`|Renvoie le contenu de object.name.| |`$.object['name']`|Renvoie le contenu de object.name.| |`$.object.['name']`|Renvoie le contenu de object.name.| |`$["object"]['name']`|Renvoie le contenu de object.name.| |`$.['object'].["name"]`|Renvoie le contenu de object.name.| |`$.object.history.length()`|Renvoie le nombre d'éléments du tableau object.history.| |`$[?(@.name == 'Object')].price.first()`|Renvoie le champ price du premier objet avec le nom 'Object'.| |`$[?(@.name == 'Object')].history.first().length()`|Renvoie le nombre d'éléments du tableau history du premier objet avec le nom 'Object'.| |`$[?(@.price > 10)].length()`|Renvoie le nombre d'objets dont le prix est supérieur à 10.| Voir aussi : [Echapper les caractères spéciaux des valeurs de macro LLD dans JSONPath](/manual/config/items/preprocessing/jsonpath_functionality/escaping_lld_macros). #### Overview This section provides details on passive and active checks performed by [Zabbix agent](/manual/config/items/itemtypes/zabbix_agent). Zabbix uses a JSON based communication protocol for communicating with Zabbix agent. See also: [Zabbix agent 2](/manual/appendix/protocols/zabbix_agent2) protocol details. #### Aperçu Cette section fournit des détails sur les vérifications passives et actives effectuées par l'[agent Zabbix](/manual/config/items/itemtypes/zabbix_agent). Zabbix utilise un protocole de communication basé sur JSON pour communiquer avec l'agent Zabbix. Voir aussi les détails de protocole de l'[Agent Zabbix 2](/manual/appendix/protocols/zabbix_agent2). ### Overview This section provides information on: * Agent2 -> Server : active checks request * Server -> Agent2 : active checks response * Agent2 -> Server : agent data request * Server -> Agent2 : agent data response ### Aperçu Cette rubrique fournit des informations sur : * Agent2 -> Serveur : demande de vérifications actives * Serveur -> Agent2 : réponse de vérifications actives * Agent2 -> Serveur : demande de données agent * Serveur -> Agent2 : réponse des données agent #### Overview This section provides item value preprocessing details. Item value preprocessing allows to define and execute [transformation rules](/manual/config/items/preprocessing) for the received item values. Preprocessing is managed by a preprocessing manager process, which was added in Zabbix 3.4, along with preprocessing workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is used between data gatherers (pollers, trappers, etc) and the preprocessing process. Either Zabbix server or Zabbix proxy (for items monitored by the proxy) is performing preprocessing steps. #### Aperçu Cette section fournit des détails sur le prétraitement de la valeur de l'élément. Le prétraitement des valeurs d'éléments permet de définir et d'exécuter des [règles de transformation](/manual/config/items/preprocessing) pour les valeurs d'éléments reçues. Le prétraitement est géré par un processus de gestionnaire de prétraitement, qui a été ajouté dans Zabbix 3.4, ainsi que par des agents de prétraitement qui exécutent les étapes de prétraitement. Toutes les valeurs (avec ou sans prétraitement) des différents collecteurs de données passent par le gestionnaire de prétraitement avant d'être ajoutées au cache de l'historique. La communication IPC basée sur les sockets est utilisée entre les collecteurs de données (pollers, trappers, etc.) et le processus de prétraitement. Le serveur Zabbix ou le proxy Zabbix (pour les éléments surveillés par le proxy) effectue des étapes de prétraitement. ### Overview This section provides several encryption configuration examples for CentOS 8.2 and MySQL 8.0.21 and can be used as a quickstart guide for encrypting the connection to the database.  ::: noteimportant If MySQL host is set to localhost, encryption options will not be available. In this case a connection between Zabbix frontend and the database uses a socket file (on Unix) or shared memory (on Windows) and cannot be encrypted. ::: ::: noteclassic List of encryption combinations is not limited to the ones listed on this page. There are a lot more combinations available. ::: ### Aperçu Cette section fournit plusieurs exemples de configuration de chiffrement pour CentOS 8.2 et MySQL 8.0.21 et peut être utilisé comme guide de démarrage rapide pour chiffrer la connexion à la base de données. ::: noteimportant Si l'hôte MySQL est défini sur localhost, les options de chiffrement ne seront pas disponible. Dans ce cas, une connexion entre l'interface Zabbix et la base de données utilise un fichier socket (sous Unix) ou une mémoire partagée (sous Windows) et ne peut pas être crypté. ::: ::: noteclassic La liste de combinaisons de cryptage ne se limitent pas à celles répertoriées sur cette page. Il y a beaucoup plus de combinaisons disponibles. ::: ### Overview This section provides several encryption configuration examples for CentOS 8.2 and PostgreSQL 13. ::: noteclassic Connection between Zabbix frontend and PostgreSQL cannot be encrypted (parameters in GUI are disabled), if the value of *Database host* field begins with a slash or the field is empty. ::: ### Aperçu Cette section fournit plusieurs exemples de configuration de chiffrement pour CentOS 8.2 et PostgreSQL 13. ::: noteclassic La connexion entre l'interface Zabbix et PostgreSQL ne peut pas être chiffrée (les paramètres dans l'interface graphique sont désactivés), si la valeur du champ *Hôte de la base de données* commence par une barre oblique ou si le champ est vide. ::: #### Overview This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Red Hat Enterprise Linux. While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server. Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically. Depending on database size the database upgrade to version 6.0 may take a long time. ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** ::: The following upgrade notes are available: |Upgrade from|Read full upgrade notes|Most important changes between versions| |--|--|------| |5.4.x |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'| You may also want to check the [requirements](/manual/installation/requirements) for 6.0. ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. ::: #### Aperçu Cette section fournit les étapes requises pour une [mise à niveau](/manual/installation/upgrade) réussie de Zabbix **5.4**.x vers Zabbix **6.0**.x à l'aide des packages Zabbix officiels pour Red Hat Enterprise Linux. Bien que la mise à niveau des agents Zabbix ne soit pas obligatoire (mais recommandée), le serveur Zabbix et les proxys doivent être de la [même version majeure](/manual/appendix/compatibility). Par conséquent, dans une configuration serveur-proxy, le serveur Zabbix et tous les proxys doivent être arrêtés et mis à niveau. Garder les proxys en cours d'exécution pendant la mise à niveau du serveur n'apportera plus aucun avantage car lors de la mise à niveau du proxy, leurs anciennes données seront supprimées et aucune nouvelle donnée ne sera collectée jusqu'à ce que la configuration du proxy soit synchronisée avec le serveur. Notez qu'avec la base de données SQLite sur les proxys, les données d'historique des proxys avant la mise à niveau seront perdues, car la mise à niveau de la base de données SQLite n'est pas prise en charge et le fichier de base de données SQLite doit être supprimé manuellement. Lorsque le proxy est démarré pour la première fois et que le fichier de base de données SQLite est manquant, le proxy le crée automatiquement. Selon la taille de la base de données, la mise à niveau de la base de données vers la version 6.0 peut prendre un certain temps. ::: notewarning Avant la mise à niveau, assurez-vous de lire les **notes de mise à niveau** adéquates ! ::: Les notes de mise à niveau suivantes sont disponibles |Mise à niveau depuis|Lire les notes de mise à niveau complètes|Modifications les plus importantes entre les versions| |--|--|------| |5.4.x |Pour :<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Versions minimales requises de la base de données augmentées ;<br> Le serveur/proxy ne démarre pas si la base de données est obsolète ;<br> Enregistrements du journal d'audit perdus en raison d'un changement de structure de la base de données.| |5.2.x |Pour :<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Versions de base de données minimales requises augmentées ;<br> Éléments agrégés supprimés en tant que type distinct.| |5.0.x LTS|Pour :<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La version PHP minimale requise est passée de 7.2.0 à 7.2.5.| |4.4.x |Pour :<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La prise en charge d'IBM DB2 a été abandonnée ;<br> La version PHP minimale requise est passée de 5.4.0 à 7.2.0 ;<br> Les versions de base de données minimales requises ont été augmentées ;<br> Le répertoire de fichiers PHP de Zabbix a été modifié.| |4.2.x |Pour :<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Suppression des types de médias Jabber, Ez Texting.| |4.0.x LTS|Pour :<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Les anciens proxys ne peuvent plus transmettre de données à un serveur mis à niveau ;<br>Les nouveaux agents ne pourront plus travailler avec un ancien serveur Zabbix.| |3.4.x |Pour :<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Les bibliothèques 'libpthread' et 'zlib' sont désormais obligatoires ;<br> La prise en charge du protocole de texte brut a été abandonnée et l'en-tête est obligatoire ;<br> Les agents Zabbix de la version antérieure à 1.4 ne sont plus pris en charge ;<br> Le paramètre Server dans la configuration du proxy passif est désormais obligatoire.| |3.2.x |Pour :<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Prise en charge de SQLite en tant que base de données principale abandonnée pour le serveur/frontend Zabbix ;<br>Expressions régulières compatibles Perl (PCRE) prises en charge au lieu de POSIX étendu ;<br>Bibliothèques 'libpcre' et 'libevent' obligatoires pour le serveur Zabbix ;<br>Vérifications du code de sortie ajouté pour les paramètres utilisateur, les commandes à distance et les éléments system.run\[\] sans le drapeau 'nowait' ainsi que les scripts exécutés par le serveur Zabbix ;<br>La passerelle Java Zabbix doit être mise à niveau pour prendre en charge les nouvelles fonctionnalités.| |3.0.x LTS|Pour :<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La mise à niveau de la base de données peut être lente, selon la taille de la table d'historique.| |2.4.x |Pour :<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Version PHP minimale requise passée de 5.3.0 à 5.4.0 ;<br>Le paramètre de l'agent LogFile doit être spécifié.| |2.2.x LTS|Pour :<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Suppression de la surveillance distribuée basée sur les nœuds.| |2.0.x |Pour :<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Version PHP minimale requise passée de 5.1.6 à 5.3.0 ;<br>Base de données MySQL sensible à la casse requise pour le bon fonctionnement du serveur ;<br>Le jeu de caractères utf8 et le classement utf8\_bin sont requis pour que le serveur Zabbix fonctionne correctement avec la base de données MySQL. Voir les [scripts de création de base de données](/manual/appendix/install/db_scripts#mysql) ;<br>Extension PHP 'mysqli' requise au lieu de 'mysql'.| Vous pouvez également vérifier les [exigences](/manual/installation/requirements) pour 6.0. ::: notetip Il peut être pratique d'exécuter deux sessions SSH parallèles pendant la mise à niveau, en exécutant les étapes de mise à niveau dans une et en surveillant les journaux du serveur/proxy dans une autre. Par exemple, exécutez `tail -f zabbix_server.log` ou `tail -f zabbix_proxy.log` dans la deuxième session SSH pour afficher les dernières entrées du fichier journal et les erreurs possibles en temps réel. Cela peut être critique pour les instances de production. ::: #### Overview This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix sources. While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server. ::: noteimportant It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. ::: Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically. Depending on database size the database upgrade to version 6.0 may take a long time. ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** ::: The following upgrade notes are available: |Upgrade from|Read full upgrade notes|Most important changes between versions| |--|--|------| |5.4.x |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'| You may also want to check the [requirements](/manual/installation/requirements) for 6.0. ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. ::: #### Aperçu Cette section fournit les étapes requises pour une [mise à niveau](/manual/installation/upgrade) réussie de Zabbix **5.4**.x vers Zabbix **6.0**.x en utilisant les sources Zabbix officielles. Bien que la mise à niveau des agents Zabbix ne soit pas obligatoire (mais recommandée), le serveur Zabbix et les proxys doivent être de la [même version majeure](/manual/appendix/compatibility). Par conséquent, dans une configuration serveur-proxy, le serveur Zabbix et tous les proxys doivent être arrêtés et mis à niveau. Garder les proxys en cours d'exécution pendant la mise à niveau du serveur n'apportera plus aucun avantage car lors de la mise à niveau du proxy, leurs anciennes données seront supprimées et aucune nouvelle donnée ne sera collectée jusqu'à ce que la configuration du proxy soit synchronisée avec le serveur. ::: noteimportant Il n'est plus possible de démarrer le serveur mis à niveau et de faire en sorte que des proxys plus anciens, mais non mis à niveau, transmettent des données à un serveur plus récent. Cette approche, qui n'a jamais été recommandée ni prise en charge par Zabbix, est désormais officiellement désactivée, car le serveur ignorera les données des proxys non mis à niveau. ::: Notez qu'avec la base de données SQLite sur les proxys, les données d'historique des proxys avant la mise à niveau seront perdues, car la mise à niveau de la base de données SQLite n'est pas prise en charge et le fichier de base de données SQLite doit être supprimé manuellement. Lorsque le proxy est démarré pour la première fois et que le fichier de base de données SQLite est manquant, le proxy le crée automatiquement. Selon la taille de la base de données, la mise à niveau de la base de données vers la version 6.0 peut prendre un certain temps. ::: notewarning Avant la mise à niveau, assurez-vous de lire les **notes de mise à niveau** pertinentes ! ::: Les notes de mise à niveau suivantes sont disponibles : |Mise à niveau depuis|Lire les notes de mise à niveau complètes|Modifications les plus importantes entre les versions| |--|--|------| |5.4.x |Pour :<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Versions minimales requises de la base de données augmentées ;<br> Le serveur/proxy ne démarre pas si la base de données est obsolète ;<br> Enregistrements du journal d'audit perdus en raison d'un changement de structure de la base de données.| |5.2.x |Pour :<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Versions de base de données minimales requises augmentées ;<br> Éléments agrégés supprimés en tant que type distinct.| |5.0.x LTS|Pour :<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La version PHP minimale requise est passée de 7.2.0 à 7.2.5.| |4.4.x |Pour :<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La prise en charge d'IBM DB2 a été abandonnée ;<br> La version PHP minimale requise est passée de 5.4.0 à 7.2.0 ;<br> Les versions de base de données minimales requises ont été augmentées ;<br> Le répertoire de fichiers PHP de Zabbix a été modifié.| |4.2.x |Pour :<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Suppression des types de médias Jabber, Ez Texting.| |4.0.x LTS|Pour :<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Les anciens proxys ne peuvent plus transmettre de données à un serveur mis à niveau ;<br>Les nouveaux agents ne pourront plus travailler avec un ancien serveur Zabbix.| |3.4.x |Pour :<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Les bibliothèques 'libpthread' et 'zlib' sont désormais obligatoires ;<br> La prise en charge du protocole de texte brut a été abandonnée et l'en-tête est obligatoire ;<br> Les agents Zabbix de la version antérieure à 1.4 ne sont plus pris en charge ;<br> Le paramètre Server dans la configuration du proxy passif est désormais obligatoire.| |3.2.x |Pour :<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Prise en charge de SQLite en tant que base de données principale abandonnée pour le serveur/frontend Zabbix ;<br>Expressions régulières compatibles Perl (PCRE) prises en charge au lieu de POSIX étendu ;<br>Bibliothèques 'libpcre' et 'libevent' obligatoires pour le serveur Zabbix ;<br>Vérifications du code de sortie ajouté pour les paramètres utilisateur, les commandes à distance et les éléments system.run\[\] sans le drapeau 'nowait' ainsi que les scripts exécutés par le serveur Zabbix ;<br>La passerelle Java Zabbix doit être mise à niveau pour prendre en charge les nouvelles fonctionnalités.| |3.0.x LTS|Pour :<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|La mise à niveau de la base de données peut être lente, selon la taille de la table d'historique.| |2.4.x |Pour :<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Version PHP minimale requise passée de 5.3.0 à 5.4.0 ;<br>Le paramètre de l'agent LogFile doit être spécifié.| |2.2.x LTS|Pour :<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Suppression de la surveillance distribuée basée sur les nœuds.| |2.0.x |Pour :<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Version PHP minimale requise passée de 5.1.6 à 5.3.0 ;<br>Base de données MySQL sensible à la casse requise pour le bon fonctionnement du serveur ;<br>Le jeu de caractères utf8 et le classement utf8\_bin sont requis pour que le serveur Zabbix fonctionne correctement avec la base de données MySQL. Voir les [scripts de création de base de données](/manual/appendix/install/db_scripts#mysql) ;<br>Extension PHP 'mysqli' requise au lieu de 'mysql'.| Vous pouvez également vérifier les [exigences](/manual/installation/requirements) pour 6.0. ::: notetip Il peut être pratique d'exécuter deux sessions SSH parallèles pendant la mise à niveau, en exécutant les étapes de mise à niveau dans une et en surveillant les journaux du serveur/proxy dans une autre. Par exemple, exécutez `tail -f zabbix_server.log` ou `tail -f zabbix_proxy.log` dans la deuxième session SSH pour afficher les dernières entrées du fichier journal et les erreurs possibles en temps réel. Cela peut être critique pour les instances de production. ::: #### Overview This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) using official RPM and DEB packages provided by Zabbix for: - [Red Hat Enterprise Linux](/manual/installation/upgrade/packages/rhel) - [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu) #### Aperçu Cette section fournit les étapes nécessaires à une [mise à jour](/fr/manual/installation/upgrade) réussie en utilisant les packages officiels RPM et DEB fournis par Zabbix pour : - [Red Hat Enterprise Linux](/manual/installation/upgrade/packages/rhel) - [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu) #### Overview This section provides upgrade information for Zabbix **6.0**: - using packages: - for [Red Hat Enterprise Linux](/manual/installation/upgrade/packages/rhel) - for [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu) ```{=html} <!-- --> ``` - using [sources](/manual/installation/upgrade/sources) Direct upgrade to Zabbix 6.0.x is possible from Zabbix **5.4**.x, **5.2**.x, **5.0**.x, **4.4**.x, **4.2**.x, **4.0**.x, **3.4**.x, **3.2**.x, **3.0**.x, **2.4**.x, **2.2**.x and **2.0**.x. For upgrading from earlier versions consult Zabbix documentation for 2.0 and earlier. #### Aperçu Cette section fournit des informations de mise à niveau pour Zabbix **6.0** : - en utilisant des packages : - pour [Red Hat Enterprise Linux](/manual/installation/upgrade/packages/rhel) - pour [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu) ```{=html} <!-- --> ``` - en utilisant les [sources](/manual/installation/upgrade/sources) La mise à niveau directe vers Zabbix 6.0.x est possible depuis Zabbix **5.4**.x, **5.2**.x, **5.0**.x, **4.4**.x, **4.2**.x, **4.0**.x, **3.4**.x, **3.2**.x, **3.0**.x, **2.4**.x, **2.2**.x et **2.0**.x. Pour la mise à niveau à partir de versions antérieures, consultez la documentation Zabbix pour les versions 2.0 et antérieures. #### Overview This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using SQL queries, whose results get automatically transformed into a JSON object suitable for low-level discovery. #### Aperçu Ce type de [découverte](/manual/discovery/low_level_discovery) de bas niveau est effectué à l'aide de requêtes SQL, dont les résultats sont automatiquement transformés en un objet JSON adapté à la découverte de bas niveau. #### Overview This widget contains shortcuts to the most needed graphs, sorted alphabetically. The list of shortcuts is populated when you view a graph in Monitoring -> Latest data -> Graphs, and then click on its  *Add to favorites* button. {width="600"} All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets. #### Aperçu Ce widget contient des raccourcis vers les graphiques les plus importants, triés par ordre alphabétique. La liste des raccourcis est remplie lorsque vous affichez un graphique dans Surveillance -> Dernières données -> Graphiques, puis cliquez sur son bouton  *Ajouter aux favoris*. Tous les paramètres de configuration sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets. #### Overview This widget contains shortcuts to the most needed maps, sorted alphabetically. The list of shortcuts is populated when you [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) a map and then click on its  *Add to favorites* button. All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets. #### Aperçu Ce widget contient des raccourcis vers les cartes les plus importantes, triées par ordre alphabétique. La liste des raccourcis est remplie lorsque vous [visualisez](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) une carte, puis cliquez sur son  bouton *Ajouter aux favoris*. Tous les paramètres de configuration sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets. #### Overview This widget displays a status summary of the active network discovery rules.  All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) for all widgets. #### Aperçu Ce widget affiche un résumé de l'état des règles de découverte de réseau actives.  Tous les paramètres de configuration sont [communs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) à tous les widgets. #### Overview This widget displays a status summary of the active web monitoring scenarios. #### Aperçu Ce widget affiche un résumé de l'état des scénarios de surveillance Web actifs. #### Overview This widget displays the content retrieved from the specified URL. #### Aperçu Ce widget affiche le contenu récupéré à partir de l'URL spécifiée. #### Overview This widget displays the same information as in *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*, however, a single dashboard widget can only display either the system stats or the high availability nodes at a time (not both). #### Aperçu Ce widget affiche les mêmes informations que dans *Rapports* → *[Informations système](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*, cependant, un seul widget de tableau de bord ne peut afficher que les statistiques système ou les nœuds de haute disponibilité à un moment donné (pas les deux). #### Overview This widget is useful for displaying [SLA reports](/manual/web_interface/frontend_sections/services/sla_report). Functionally it is similar to the *Services* -> *SLA report* section. #### Aperçu Ce widget est utile pour afficher les [rapports SLA](/manual/web_interface/frontend_sections/services/sla_report). Fonctionnellement, il est similaire à la section *Services* -> *Rapport SLA*. #### Overview This widget is useful for displaying the value of a single item prominently.  Besides the value itself, additional elements can be displayed, if desired: - time of the metric - item description - change indicator for the value - item unit The widget can display numeric and string values. String values are displayed on a single line and truncated, if needed. "No data" is displayed, if there is no value for the item. Clicking on the value leads to an ad-hoc graph for numeric items or latest data for string items. The widget and all elements in it can be visually fine-tuned using [advanced configuration](#advanced-configuration) options, allowing to create a wide variety of visual styles:  #### Aperçu Ce widget est utile pour mettre en évidence la valeur d'un seul élément.  Outre la valeur elle-même, des éléments supplémentaires peuvent être affichés, si vous le souhaitez : - temps de la métrique - descriptif de l'élément - indicateur de changement de la valeur - unité de l'élément Le widget peut afficher des valeurs numériques et des chaînes de caractères. Les valeurs de chaîne sont affichées sur une seule ligne et tronquées, si nécessaire. "Aucune donnée" s'affiche s'il n'y a pas de valeur pour l'élément. Cliquer sur la valeur conduit à un graphique ad hoc pour les éléments numériques ou aux dernières données pour les éléments de chaîne. Le widget et tous ses éléments peuvent être visuellement affinés à l'aide des options de [configuration avancée](#configuration-avancée), ce qui permet de créer une grande variété de styles visuels :  #### Overview This widget provides a way to create custom tables for displaying the data situation, allowing to display *Top N*-like reports and progress-bar reports useful for capacity planning. The maximum number of hosts that can be displayed is 100. {width="527"}  #### Aperçu Ce widget permet de créer des tableaux personnalisés pour afficher la situation des données, permettant d'afficher des rapports de type *Top N* et des rapports de barre de progression utiles pour la planification des capacités. Le nombre maximum d'hôtes pouvant être affichés est de 100. {width="527"}  #### Overview Though Zabbix offers a large number of webhook integrations available out-of-the-box, you may want to create your own webhooks instead. This section provides examples of custom webhook scripts (used in the *Script* parameter). See [webhook](/manual/config/notifications/media/webhook) section for description of other webhook parameters. #### Aperçu Bien que Zabbix propose un grand nombre d'intégrations de webhooks prêtes à l'emploi, vous pouvez créer vos propres webhooks à la place. Cette section fournit des exemples de scripts webhook personnalisés (utilisés dans le paramètre *Script*). Voir la section [webhook](/manual/config/notifications/media/webhook) pour une description des autres paramètres du webhook. #### Overview To configure a network discovery rule used by Zabbix to discover hosts and services: - Go to *Configuration → Discovery* - Click on *Create rule* (or on the rule name to edit an existing one) - Edit the discovery rule attributes #### Aperçu Pour configurer une règle de découverte de réseau utilisée par Zabbix pour découvrir des hôtes et des services : - Accédez à *Configuration → Découverte* - Cliquez sur *Créer une règle* (ou sur le nom de la règle pour modifier une règle existante). - Modifiez les attributs de la règle de découverte #### Overview To configure a trigger, do the following: - Go to: *Configuration* → *Hosts* - Click on *Triggers* in the row of the host - Click on *Create trigger* to the right (or on the trigger name to edit an existing trigger) - Enter parameters of the trigger in the form See also [general information](/manual/config/triggers) on triggers and their calculation times. #### Aperçu Pour configurer un déclencheur, procédez comme suit : - Allez dans : *Configuration* → *Hôtes* - Cliquez sur *Déclencheurs* dans la ligne de l'hôte - Cliquez sur *Créer un déclencheur* à droite (ou sur le nom du déclencheur pour modifier un déclencheur existant) - Entrez les paramètres du déclencheur dans le formulaire Voir aussi [informations générales](/manual/config/triggers) sur les déclencheurs et leurs temps de calcul. #### Overview To configure e-mail as the delivery channel for messages, you need to configure e-mail as the media type and assign specific addresses to users. ::: noteclassic Multiple notifications for single event will be grouped together on the same email thread. ::: #### Aperçu Pour configurer le courrier électronique comme canal de remise des messages, vous devez configurer le courrier électronique comme type de support et attribuer des adresses spécifiques aux utilisateurs. ::: noteclassic Plusieurs notifications pour un seul événement seront regroupées sur le même traitement d'email. ::: #### Overview To create an item in Zabbix frontend, do the following: - Go to: *Configuration* → *Hosts* - Click on *Items* in the row of the host - Click on *Create item* in the upper right corner of the screen - Enter parameters of the item in the form You can also create an item by opening an existing one, pressing the *Clone* button and then saving under a different name. #### Aperçu Pour créer un élément dans l'interface web Zabbix, procédez comme suit : - Allez dans : *Configuration* → *Hôtes* - Cliquez sur *Eléments* dans la rangée correspondant à l\'hôte - Cliquez sur *Créer un élément* dans le coin supérieur droit de l\'écran - Entrez les paramètres de l\'élément dans le formulaire Vous pouvez également créer un élément en ouvrant un élément existant, en appuyant sur le bouton *Cloner*, puis en enregistrant sous un autre nom. #### Overview To make the calculation of trigger expressions, calculated items and some macros much faster, a value cache option is supported by the Zabbix server. This in-memory cache can be used for accessing historical data, instead of making direct SQL calls to the database. If historical values are not present in the cache, the missing values are requested from the database and the cache updated accordingly. To enable the value cache functionality, an optional **ValueCacheSize** parameter is supported by the Zabbix server [configuration](/manual/appendix/config/zabbix_server) file. Two internal items are supported for monitoring the value cache: **zabbix\[vcache,buffer,<mode>\]** and **zabbix\[vcache,cache,<parameter>\]**. See more details with [internal items](/manual/config/items/itemtypes/internal). #### Aperçu Pour effectuer le calcul des déclencheurs, des éléments calculés et de certaines macros beaucoup plus rapidement, une option de cache de valeur est prise en charge par le serveur Zabbix. Ce cache mémoire peut être utilisé pour des données d'historiques, au lieu de passer des appels SQL directs à la base de données. Si les valeurs d'historiques ne sont pas présentes dans le cache, les valeurs manquantes de la base de données sont requises et le cache est mis à jour en conséquence. Pour activer la fonctionnalité de cache de valeurs, un paramètre optionnel **ValueCacheSize** est pris en charge par le fichier de [configuration](/fr/manual/appendix/config/zabbix_server) du serveur Zabbix. Deux éléments internes sont supportés pour superviser le cache de valeur : **zabbix\[vcache,buffer,<mode>\]** et **zabbix\[vcache,cache,<parameter>\]**. Voir plus de détails avec les [éléments internes](/fr/manual/config/items/itemtypes/internal). #### Overview Trapper items accept incoming data instead of querying for it. It is useful for any data you might want to "push" into Zabbix. To use a trapper item you must: - have a trapper item set up in Zabbix - send in the data into Zabbix #### Aperçu Les éléments Trapper acceptent les données entrantes au lieu de les interroger. C'est utile pour toutes les données que vous pourriez vouloir "pousser" dans Zabbix. Pour utiliser un élément trappeur, vous devez : - avoir un élément trapper mis en place dans Zabbix - envoyer les données dans Zabbix #### Overview Update operations are available in actions with the following event sources: - *Triggers* - when problems are [updated](/manual/acknowledges#updating_problems) by other users, i.e. commented upon, acknowledged, severity has been changed, closed (manually); - *Services* - when the severity of a service has changed but the service is still not recovered. Both messages and remote commands are supported in update operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously. #### Aperçu Les opérations de mise à jour sont disponibles dans les actions avec les sources d'événements suivantes : - *Déclencheurs* - lorsque les problèmes sont [mis à jour](/manual/acknowledges#updating_problems) par d'autres utilisateurs, c'est-à-dire commentés, acquittés, la sévérité a été modifiée, fermés (manuellement) ; - *Services* - lorsque la sévérité d'un service a changé mais que le service n'est toujours pas récupéré. Les messages et les commandes à distance sont pris en charge dans les opérations de mise à jour. Bien que plusieurs opérations puissent être ajoutées, l'escalade n'est pas prise en charge - toutes les opérations sont affectées à une seule étape et seront donc exécutées simultanément. #### Overview User groups allow to group users both for organizational purposes and for assigning permissions to data. Permissions to monitoring data of host groups are assigned to user groups, not individual users. It may often make sense to separate what information is available for one group of users and what - for another. This can be accomplished by grouping users and then assigning varied permissions to host groups. A user can belong to any number of groups. #### Aperçu Les groupes d'utilisateurs permettent de regrouper les utilisateurs à la fois à des fins d'organisation et pour attribuer des autorisations aux données. Les autorisations de surveillance des données des groupes d'hôtes sont attribuées à des groupes d'utilisateurs, et non à des utilisateurs individuels. Il peut souvent être judicieux de séparer les informations disponibles pour un groupe d'utilisateurs et celles pour un autre. Cela peut être accompli en regroupant les utilisateurs, puis en attribuant diverses autorisations aux groupes d'hôtes. Un utilisateur peut appartenir à n'importe quel nombre de groupes. #### Overview User macros are supported in Zabbix for greater flexibility, in addition to the macros [supported](/manual/appendix/macros/supported_by_location) out-of-the-box. User macros can be defined on global, template and host level. These macros have a special syntax: {$MACRO} Zabbix resolves macros according to the following precedence: 1. host level macros (checked first) 2. macros defined for first level templates of the host (i.e., templates linked directly to the host), sorted by template ID 3. macros defined for second level templates of the host, sorted by template ID 4. macros defined for third level templates of the host, sorted by template ID, etc. 5. global macros (checked last) In other words, if a macro does not exist for a host, Zabbix will try to find it in the host templates of increasing depth. If still not found, a global macro will be used, if exists. ::: notewarning If a macro with the **same name** exists on multiple linked templates of the same level, the macro from the template with the lowest ID will be used. Thus having macros with the same name in multiple templates is a configuration risk. ::: If Zabbix is unable to find a macro, the macro will not be resolved. ::: noteimportant Macros (including user macros) are left unresolved in the Configuration section (for example, in the trigger list) by design to make complex configuration more transparent. ::: User macros can be used in: - item key parameter - item update intervals and flexible intervals - trigger name and description - trigger expression parameters and constants (see [examples](#examples)) - many other locations - see the [full list](/manual/appendix/macros/supported_by_location_user) #### Aperçu Les macros utilisateur sont prises en charge dans Zabbix pour une plus grande flexibilité, en plus des macros [supportées](/manual/appendix/macros/supported_by_location) prêtes à l'emploi. Les macros utilisateur peuvent être définies au niveau global, au niveau modèle et de l'hôte. Ces macros ont une syntaxe spéciale : {$MACRO} Zabbix résout les macros selon la priorité suivante : 1. macros au niveau de l'hôte (vérifiées en premier) 2. macros définies pour les modèles de premier niveau de l'hôte (c'est-à-dire les modèles liés directement à l'hôte), triées par ID de modèle 3. macros définies pour les modèles de deuxième niveau de l'hôte, triées par ID de modèle 4. macros définies pour les modèles de troisième niveau de l'hôte, triées par ID de modèle, etc. 5. macros globales (vérifiées en dernier) En d'autres termes, si une macro n'existe pas pour un hôte, Zabbix essaiera de la trouver dans les modèles d'hôte de profondeur croissante. Si elle n'est toujours pas trouvée, une macro globale sera utilisée, si elle existe. ::: notewarning Si une macro avec le **même nom** existe sur plusieurs modèles liés du même niveau, la macro du modèle avec l'ID le plus bas sera utilisée. Ainsi, avoir des macros avec le même nom dans plusieurs modèles est un risque de configuration. ::: Si Zabbix ne parvient pas à trouver une macro, la macro ne sera pas résolue. ::: noteimportant Les macros (y compris les macros utilisateur) sont laissées non résolues dans la section Configuration (par exemple, dans la liste des déclencheurs) par conception pour rendre la configuration complexe plus transparente. ::: Les macros utilisateur peuvent être utilisées dans : - le paramètre clé de l'élément - les intervalles de mise à jour des éléments et intervalles flexibles - les nom et description du déclencheur - les paramètres d'expression de déclenchement et constantes (voir les [exemples](#exemples)) - de nombreux autres emplacements - voir la [liste complète](/manual/appendix/macros/supported_by_location_user) #### Overview When monitoring systems using an agent, a good practice is to obtain metrics from the host on which the agent is installed. To use the principle of least privilege, it is necessary to determine what metrics are obtained from the agent. The table in this document allows you to select the minimum rights for guaranteed correct operation of Zabbix agent. If a different user is selected for the agent to work, rather than 'LocalSystem', then for the operation of agent as a Windows service, the new user must have the rights "Log on as a service" from "Local Policy→User Rights Assignment" and the right to create, write and delete the Zabbix agent log file. An Active Directory user must be added to the *Performance Monitor Users* group. ::: noteclassic When working with the rights of an agent based on the "minimum technically acceptable" group, prior provision of rights to objects for monitoring is required. ::: #### Aperçu Lors de la surveillance de systèmes à l'aide d'un agent, une bonne pratique consiste à obtenir des métriques de l'hôte sur lequel l'agent est installé. Pour utiliser le principe du moindre privilège, il est nécessaire de déterminer quelles métriques sont obtenues de l'agent. Le tableau de ce document vous permet de sélectionner les droits minimaux pour garantir le bon fonctionnement de l'agent Zabbix. Si un autre utilisateur est sélectionné pour que l'agent fonctionne, plutôt que "LocalSystem", alors pour le fonctionnement de l'agent en tant que service Windows, le nouvel utilisateur doit avoir les droits "Se connecter en tant que service" de "Local Policy→User Rights Assignment" et le droit de créer, d'écrire et de supprimer le fichier journal de l'agent Zabbix. Un utilisateur Active Directory doit être ajouté au groupe *Performance Monitor Users*. ::: noteclassic Lorsque vous travaillez avec les droits d'un agent basés sur le groupe "minimum techniquement acceptable", la fourniture préalable de droits sur les objets à surveiller est requise. ::: #### Overview While a [simple graph](simple) is great for accessing data of one item and [custom graphs](custom) offer customization options, none of the two allow to quickly create a comparison graph for multiple items with little effort and no maintenance. To address this issue, since Zabbix 2.4 it is possible to create ad-hoc graphs for several items in a very quick way. #### Aperçu Bien qu'un [graphique simple](simple) soit idéal pour accéder aux données d'un élément et que les [graphiques personnalisés](custom) offrent des options de personnalisation, aucun des deux ne permet de créer rapidement un graphique de comparaison pour plusieurs éléments avec peu d'effort et sans maintenance. Pour résoudre ce problème, depuis Zabbix 2.4, il est possible de créer des graphiques ad hoc pour plusieurs éléments de manière très rapide. #### Overview While many things in the frontend can be configured using the frontend itself, some customisations are currently only possible by editing a definitions file. This file is `defines.inc.php` located in /include of the Zabbix HTML document directory. #### Aperçu Alors que de nombreuses choses dans l'interface peuvent être configurées à l'aide de l'interface elle-même, certaines personnalisations ne sont actuellement possibles qu'en éditant un fichier de définitions. Ce fichier est `defines.inc.php` situé dans /include du répertoire de documents HTML de Zabbix. #### Overview While you may find the required index number (for example, of a network interface) among the SNMP OIDs, sometimes you may not completely rely on the index number always staying the same. Index numbers may be dynamic - they may change over time and your item may stop working as a consequence. To avoid this scenario, it is possible to define an OID which takes into account the possibility of an index number changing. For example, if you need to retrieve the index value to append to **ifInOctets** that corresponds to the **GigabitEthernet0/1** interface on a Cisco device, use the following OID: ifInOctets["index","ifDescr","GigabitEthernet0/1"] #### Aperçu Bien que vous puissiez trouver le numéro d'index nécessaire (par exemple, d'une interface réseau) parmi les OID SNMP, il se peut que vous ne puissiez pas toujours compter sur le numéro d'index qui ne reste pas toujours identique. Les numéros d'index peuvent être dynamiques - ils peuvent changer au fil du temps et votre élément peut, en conséquence, cesser de fonctionner. Pour éviter ce scénario, il est possible de définir un OID qui prend en compte la possibilité de changement du numéro d'index. Par exemple, si vous devez extraire la valeur d'index pour l'ajouter à **ifInOctets** correspondant à l'interface **GigabitEthernet0/1** sur un périphérique Cisco, utilisez l'OID : ifInOctets["index","ifDescr","GigabitEthernet0/1"] #### Overview With calculated items it is possible to create calculations based on the values of other items. Calculations may use both: - single values of individual items - complex filters to select multiple items for aggregations (see [aggregate calculations](/manual/config/items/itemtypes/calculated/aggregate) for details) Thus, calculated items are a way of creating virtual data sources. All calculations are done by Zabbix server only. The values are periodically calculated based on the arithmetical expression used. The resulting data is stored in the Zabbix database as for any other item; both history and trend values are stored and graphs can be generated. ::: noteclassic If the calculation result is a float value it will be trimmed to an integer if the calculated item type of information is *Numeric (unsigned)*. ::: Calculated items share their syntax with trigger [expressions](/manual/config/triggers/expression). Comparison to strings is allowed in calculated items. Calculated items may be referenced by macros or other entities same as any other item type. To use calculated items, choose the item type **Calculated**. #### Aperçu Avec les éléments calculés, il est possible de créer des calculs basés sur les valeurs d'autres éléments. Les calculs peuvent utiliser à la fois : - des valeurs uniques d'éléments individuels - des filtres complexes pour sélectionner plusieurs éléments pour les agrégations (voir [calculs agrégés](/manual/config/items/itemtypes/calculated/aggregate) pour plus de détails) Ainsi, les éléments calculés sont un moyen de créer des sources de données virtuelles. Tous les calculs sont effectués par le serveur Zabbix uniquement. Les valeurs sont calculées périodiquement en fonction de l'expression arithmétique utilisée. Les données résultantes sont stockées dans la base de données Zabbix comme pour tout autre élément ; les valeurs d'historique et de tendance sont stockées et des graphiques peuvent être générés. ::: noteclassique Si le résultat du calcul est une valeur flottante, il sera réduit à un nombre entier si le type d'information de l'élément calculé est *Numérique (non signé)*. ::: Les éléments calculés partagent leur syntaxe avec les [expressions](/manual/config/triggers/expression) de déclencheur. La comparaison avec des chaînes est autorisée dans les éléments calculés. Les éléments calculés peuvent être référencés par des macros ou d'autres entités identiques à tout autre type d'élément. Pour utiliser des éléments calculés, choisissez le type d'élément **Calculé**. #### Overview With escalations you can create custom scenarios for sending notifications or executing remote commands. In practical terms it means that: - Users can be informed about new problems immediately - Notifications can be repeated until the problem is resolved - Sending a notification can be delayed - Notifications can be escalated to another "higher" user group - Remote commands can be executed immediately or when a problem is not resolved for a lengthy period Actions are escalated based on the **escalation step**. Each step has a duration in time. You can define both the default duration and a custom duration of an individual step. The minimum duration of one escalation step is 60 seconds. You can start actions, such as sending notifications or executing commands, from any step. Step one is for immediate actions. If you want to delay an action, you can assign it to a later step. For each step, several actions can be defined. The number of escalation steps is not limited. Escalations are defined when [configuring an operation](operation#configuring_an_operation). Escalations are supported for problem operations only, not recovery. #### Aperçu Avec les escalades, vous pouvez créer des scénarios personnalisés pour envoyer des notifications ou exécuter des commandes à distance. Concrètement cela signifie que : - Les utilisateurs peuvent être informés immédiatement des nouveaux problèmes - Les notifications peuvent être répétées jusqu'à ce que le problème soit résolu - L'envoi d'une notification peut être retardé - Les notifications peuvent être transmises à un autre groupe d'utilisateurs "supérieur" - Les commandes à distance peuvent être exécutées immédiatement ou lorsqu'un problème n'est pas résolu pendant une longue période Les actions sont escaladées en fonction de l'**étape d'escalade**. Chaque étape a une durée dans le temps. Vous pouvez définir à la fois la durée par défaut et une durée personnalisée d'une étape individuelle. La durée minimale d'une étape d'escalade est de 60 secondes. Vous pouvez démarrer des actions, telles que l'envoi de notifications ou l'exécution de commandes, à partir de n'importe quelle étape. La première étape concerne les actions immédiates. Si vous souhaitez retarder une action, vous pouvez l'affecter à une étape ultérieure. Pour chaque étape, plusieurs actions peuvent être définies. Le nombre d'étapes d'escalade n'est pas limité. Les escalades sont définies lors de la [configuration d'une opération](operation#configuring_an_operation). Les escalades sont prises en charge uniquement pour les opérations problématiques, pas pour la récupération. #### Overview With lots of data flowing into Zabbix, it becomes much easier for the users if they can look at a visual representation of what is going on rather than only numbers. This is where graphs come in. Graphs allow to grasp the data flow at a glance, correlate problems, discover when something started or make a presentation of when something might turn into a problem. Zabbix provides users with: - built-in [simple graphs](/manual/config/visualization/graphs/simple) of one item data - the possibility to create more complex [customized graphs](/manual/config/visualization/graphs/custom) - access to a comparison of several items quickly in [ad-hoc graphs](/manual/config/visualization/graphs/adhoc) - modern customizable [vector graphs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph) #### Aperçu Avec beaucoup de données circulant dans Zabbix, il devient beaucoup plus facile pour les utilisateurs de regarder une représentation visuelle de ce qui se passe plutôt que seulement des chiffres. C'est là que les graphiques entrent en jeu. Les graphiques permettent de saisir le flux de données en un coup d'œil, de corréler les problèmes, de découvrir quand quelque chose a commencé ou de faire une présentation du moment où quelque chose pourrait devenir un problème. Zabbix fournit aux utilisateurs : - des [graphiques simples](/manual/config/visualization/graphs/simple) des données d'un élément - la possibilité de créer des [graphiques personnalisés](/manual/config/visualization/graphs/custom) plus complexes - un accès à une comparaison de plusieurs éléments rapidement dans les [graphiques ad-hoc](/manual/config/visualization/graphs/adhoc) - des [graphiques vectoriels](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph) personnalisables modernes #### Overview With mass update you may change some attribute for a number of triggers at once, saving you the need to open each individual trigger for editing. #### Aperçu Avec la modification collective, vous pouvez modifier certains attributs pour un certain nombre de déclencheurs à la fois, ce qui vous évite d'avoir à ouvrir chaque déclencheur pour le modifier. #### Overview With remote commands you can define that a certain pre-defined command is automatically executed on the monitored host upon some condition. Thus remote commands are a powerful mechanism for smart pro-active monitoring. In the most obvious uses of the feature you can try to: - Automatically restart some application (web server, middleware, CRM) if it does not respond - Use IPMI 'reboot' command to reboot some remote server if it does not answer requests - Automatically free disk space (removing older files, cleaning /tmp) if running out of disk space - Migrate a VM from one physical box to another depending on the CPU load - Add new nodes to a cloud environment upon insufficient CPU (disk, memory, whatever) resources Configuring an action for remote commands is similar to that for sending a message, the only difference being that Zabbix will execute a command instead of sending a message. Remote commands can be executed by Zabbix server, proxy or agent. Remote commands on Zabbix agent can be executed directly by Zabbix server or through Zabbix proxy. Both on Zabbix agent and Zabbix proxy remote commands are disabled by default. They can be enabled by: - adding an `AllowKey=system.run[*]` parameter in agent configuration; - setting the EnableRemoteCommands parameter to '1' in proxy configuration. Remote commands executed by Zabbix server are run as described in [Command execution](/manual/appendix/command_execution) including exit code checking. Remote commands are executed even if the target host is in maintenance. #### Aperçu Avec les commandes à distance, vous pouvez définir qu’une certaine commande prédéfinie est automatiquement exécutée sur l’hôte surveillé sous certaines conditions. Ainsi, les commandes à distance constituent un mécanisme puissant pour la supervision proactive intelligente. Dans les utilisations les plus évidentes de cette fonctionnalité, vous pouvez essayer de : - Redémarrer automatiquement certaines applications (serveur Web, middleware, CRM) si elles ne répondent pas - Utiliser la commande 'reboot' IPMI pour redémarrer un serveur distant s'il ne répond pas aux demandes - Libérer automatiquement de l'espace disque (suppression des anciens fichiers, nettoyage de /tmp) si vous manquez d'espace disque - Migrer une VM d'un boîtier physique à un autre en fonction de la charge du processeur - Ajouter de nouveaux nœuds à un environnement cloud en cas de ressources CPU insuffisantes (disque, mémoire, etc.) La configuration d'une action pour les commandes à distance est similaire à celle pour l'envoi d'un message, la seule différence étant que Zabbix exécutera une commande au lieu d'envoyer un message. Les commandes à distance peuvent être exécutées par un serveur, un proxy ou un agent Zabbix. Les commandes à distance sur l'agent Zabbix peuvent être exécutées directement par le serveur Zabbix ou via un proxy Zabbix. Les commandes distantes de l'agent Zabbix et du proxy Zabbix sont désactivées par défaut. Elles peuvent être activées en : - ajoutant le paramètre `AllowKey=system.run[*]` dans la configuration de l'agent; - définissant le paramètre EnableRemoteCommands à '1' dans la configuration du proxy. Les commandes distantes exécutées par le serveur Zabbix sont exécutées comme décrit dans [Exécution de commandes](/manual/appendix/command_execution) y compris la vérification du code de sortie. Les commandes à distance sont exécutées même si l'hôte cible est en maintenance. #### Overview With Zabbix you can check several availability aspects of web sites.\ ::: noteimportant To perform web monitoring Zabbix server must be initially [configured](/manual/installation/install#from_the_sources) with cURL (libcurl) support. ::: To activate web monitoring you need to define web scenarios. A web scenario consists of one or several HTTP requests or "steps". The steps are periodically executed by Zabbix server in a pre-defined order. If a host is monitored by proxy, the steps are executed by the proxy. Web scenarios are attached to hosts/templates in the same way as items, triggers, etc. That means that web scenarios can also be created on a template level and then applied to multiple hosts in one move. The following information is collected in any web scenario: - average download speed per second for all steps of whole scenario - number of the step that failed - last error message The following information is collected in any web scenario step: - download speed per second - response time - response code For more details, see [web monitoring items](/manual/web_monitoring/items). Data collected from executing web scenarios is kept in the database. The data is automatically used for graphs, triggers and notifications. Zabbix can also check if a retrieved HTML page contains a pre-defined string. It can execute a simulated login and follow a path of simulated mouse clicks on the page. Zabbix web monitoring supports both HTTP and HTTPS. When running a web scenario, Zabbix will optionally follow redirects (see option *Follow redirects* below). Maximum number of redirects is hard-coded to 10 (using cURL option [CURLOPT\_MAXREDIRS](http://curl.haxx.se/libcurl/c/CURLOPT_MAXREDIRS.html)). All cookies are preserved during the execution of a single scenario. See also [known issues](/manual/installation/known_issues#https_checks) for web monitoring using HTTPS protocol. #### Aperçu Avec Zabbix, vous pouvez vérifier plusieurs aspects de la disponibilité des sites Web. ::: noteimportant Pour effectuer une supervision Web, le serveur Zabbix doit être initialement [configuré](https://www.zabbix.com/documentation/4.0/fr/manual/installation/install) avec le support cURL (libcurl). ::: Pour activer la supervision Web, vous devez définir des scénarios Web. Un scénario Web consiste en une ou plusieurs requêtes HTTP ou "étapes". Les étapes sont exécutées périodiquement par le serveur Zabbix dans un ordre prédéfini. Si un hôte est supervisé par proxy, les étapes sont exécutées par le proxy. Les scénarios Web sont associés aux hôtes/modèles de la même manière que les éléments, les déclencheurs, etc. Cela signifie que les scénarios Web peuvent également être créés au niveau du modèle, puis appliqués à plusieurs hôtes en même temps. Les informations suivantes sont collectées pour tout le scénario Web : - vitesse moyenne de téléchargement par seconde pour toutes les étapes du scénario - numéro de l'étape qui a échoué - dernier message d'erreur Les informations suivantes sont collectées pour chaque étape de scénario Web : - vitesse de téléchargement par seconde - temps de réponse - code retour Pour plus de détails, voir les [éléments de supervision web](https://www.zabbix.com/documentation/4.0/fr/manual/web_monitoring/items). Les données collectées lors de l'exécution de scénarios Web sont conservées dans la base de données. Les données sont automatiquement utilisées pour les graphiques, les déclencheurs et les notifications. Zabbix peut également vérifier si une page HTML récupérée contient une chaîne prédéfinie. Il peut exécuter une connexion simulée et suivre un chemin de clics simulés sur la page. La supervision Web Zabbix prend en charge à la fois HTTP et HTTPS. Lors de l'exécution d'un scénario Web, Zabbix suit éventuellement les redirections (voir l'option *Suivre les redirections* en dessous). Le nombre maximal de redirections est codé en dur à 10 (en utilisant l'option cURL [CURLOPT_MAXREDIRS](http://curl.haxx.se/libcurl/c/CURLOPT_MAXREDIRS.html)). Tous les cookies sont conservés lors de l'exécution d'un scénario unique. Voir aussi les [problèmes connus](/manual/installation/known_issues#https_checks) pour la supervision Web à l'aide du protocole HTTPS. #### Overview [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) is a powerful interface in Windows that can be used for retrieving various information about Windows components, services, state and software installed. It can be used for physical disk discovery and their performance data collection, network interface discovery, Hyper-V guest discovery, monitoring Windows services and many other things in Windows OS. This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using WQL queries whose results get automatically transformed into a JSON object suitable for low-level discovery. #### Aperçu [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) est une interface puissante de Windows qui peut être utilisée pour récupérer diverses informations sur les composants, les services, l'état et les logiciels installés de Windows. Il peut être utilisé pour la découverte de disques physiques et leur collecte de données de performances, la découverte d'interfaces réseau, la découverte d'invités Hyper-V, la surveillance des services Windows et bien d'autres choses dans le système d'exploitation Windows. Ce type de [découverte](/manual/discovery/low_level_discovery) de bas niveau est effectué à l'aide de requêtes WQL dont les résultats sont automatiquement transformés en un objet JSON adapté à la découverte de bas niveau. #### Overview You can assign some triggers to a [link](/manual/config/visualization/maps/map#linking_elements) between elements in a network map. When these triggers go into a problem state, the link can reflect that. When you configure a link, you set the default link type and color. When you assign triggers to a link, you can assign different link types and colors with these triggers. Should any of these triggers go into a problem state, their link style and color will be displayed on the link. So maybe your default link was a green line. Now, with the trigger in the problem state, your link may become bold red (if you have defined it so). #### Aperçu Vous pouvez attribuer certains déclencheurs à un [lien](/manual/config/visualization/maps/map#linking_elements) entre les éléments d'une carte réseau. Lorsque ces déclencheurs entrent dans un état problématique, le lien peut le refléter. Lorsque vous configurez un lien, vous définissez le type et la couleur du lien par défaut. Lorsque vous affectez des déclencheurs à un lien, vous pouvez affecter différents types et couleurs de lien avec ces déclencheurs. Si l'un de ces déclencheurs rencontre un problème, son style et sa couleur de lien seront affichés sur le lien. Alors peut-être que votre lien par défaut était une ligne verte, maintenant, avec le déclencheur en état de problème, votre lien peut devenir rouge gras (si vous l'avez défini ainsi). #### Overview You can define the following operations for all events: - send a message - execute a remote command ::: noteimportant Zabbix server does not create alerts if access to the host is explicitly "denied" for the user defined as action operation recipient or if the user has no rights defined to the host at all. ::: For discovery and autoregistration events, there are additional operations available: - [add host](/manual/config/notifications/action/operation/other#adding_host) - remove host - enable host - disable host - add to host group - remove from host group - link to template - unlink from template - set host inventory mode #### Aperçu Vous pouvez définir les opérations suivantes pour tous les événements : - envoyer un message - exécuter une commande à distance ::: noteimportant Le serveur Zabbix ne crée pas d'alertes si l'accès à l'hôte est explicitement "refusé" pour l'utilisateur défini comme destinataire de l'opération d'action ou si l'utilisateur n'a aucun droit défini sur l'hôte. ::: Pour les événements de découverte et d'enregistrement automatique, des opérations supplémentaires sont disponibles : - [ajouter un hôte](/manual/config/notifications/action/operation/other#adding_host) - supprimer l'hôte - activer l'hôte - désactiver l'hôte - ajouter au groupe d'hôtes - supprimer du groupe d'hôtes - lier au modèle - dissocier du modèle - définir le mode d'inventaire de l'hôte #### Overview You can differentiate user permissions in Zabbix by defining the respective user role. Then the unprivileged users need to be included in user groups that have access to host group data. #### Aperçu Vous pouvez différencier les autorisations des utilisateurs dans Zabbix en définissant le rôle utilisateur respectif. Ensuite, les utilisateurs sans priviléges doivent être inclus dans des groupes d'utilisateurs ayant accès aux données du groupe d'hôtes. #### Overview You can effectively monitor Windows performance counters using the *perf\_counter\[\]* key. For example: perf_counter["\Processor(0)\Interrupts/sec"] or perf_counter["\Processor(0)\Interrupts/sec", 10] For more information on using this key or its English-only equivalent `perf_counter_en`, see [Windows-specific item keys](/manual/config/items/itemtypes/zabbix_agent/win_keys). In order to get a full list of performance counters available for monitoring, you may run: typeperf -qx You may also use low-level discovery to discover multiple [object instances](/manual/discovery/low_level_discovery/examples/windows_perf_instances) of Windows performance counters and automate the creation of perf\_counter items for multiple instance objects. #### Aperçu Vous pouvez surveiller efficacement les compteurs de performances Windows à l'aide de la clé *perf\_counter\[\]*. Par exemple : perf_counter["\Processor(0)\Interrupts/sec"] ou perf_counter["\Processor(0)\Interrupts/sec", 10] Pour plus d'informations sur l'utilisation de cette clé ou de son équivalent en anglais uniquement perf_counter_en`, consultez [Clés d'éléments spécifiques à Windows](/manual/config/items/itemtypes/zabbix_agent/win_keys). Afin d'obtenir une liste complète des compteurs de performances disponibles pour la surveillance, vous pouvez exécuter : typeperf -qx Vous pouvez également utiliser la découverte de bas niveau pour découvrir plusieurs [instances d'objet](/manual/discovery/low_level_discovery/examples/windows_perf_instances) de compteurs de performances Windows et automatiser la création d'éléments perf\_counter pour plusieurs objets d'instance. #### Overview You can keep the inventory of networked devices in Zabbix. There is a special *Inventory* menu in the Zabbix frontend. However, you will not see any data there initially and it is not where you enter data. Building inventory data is done manually when configuring a host or automatically by using some automatic population options. #### Aperçu Vous pouvez conserver l'inventaire des périphériques réseau dans Zabbix. Il y a un menu spécial *Inventaire* dans l'interface Zabbix. Cependant, vous ne verrez aucune donnée initialement et ce n'est pas là que vous entrez les données. Construire les données d'inventaire est fait manuellement lors de la configuration d'un hôte ou automatiquement en utilisant certaines options de peuplement automatique. #### Overview You can monitor the health and availability of Intelligent Platform Management Interface (IPMI) devices in Zabbix. To perform IPMI checks Zabbix server must be initially [configured](/manual/installation/install#configure_the_sources) with IPMI support. IPMI is a standardized interface for remote "lights-out" or "out-of-band" management of computer systems. It allows to monitor hardware status directly from the so-called "out-of-band" management cards, independently from the operating system or whether the machine is powered on at all. Zabbix IPMI monitoring works only for devices having IPMI support (HP iLO, DELL DRAC, IBM RSA, Sun SSP, etc). Since Zabbix 3.4, a new IPMI manager process has been added to schedule IPMI checks by IPMI pollers. Now a host is always polled by only one IPMI poller at a time, reducing the number of open connections to BMC controllers. With those changes it's safe to increase the number of IPMI pollers without worrying about BMC controller overloading. The IPMI manager process is automatically started when at least one IPMI poller is started. See also [known issues](/manual/installation/known_issues#ipmi_checks) for IPMI checks. #### Aperçu Vous pouvez superviser l'intégrité et la disponibilité des périphériques IPMI (Intelligent Platform Management Interface) dans Zabbix. Pour effectuer les vérifications IPMI, le serveur Zabbix doit initialement être [configuré](/fr/manual/installation/install) avec le support IPMI. IPMI est une interface normalisée pour la gestion à distance de systèmes informatiques. Il permet de surveiller l'état du matériel directement à partir des cartes de gestion dites «out-of-band», indépendamment du système d'exploitation ou de la mise sous tension de la machine. La surveillance IPMI de Zabbix ne fonctionne que pour les périphériques prenant en charge IPMI (HP iLO, DELL DRAC, IBM RSA, Sun SSP, etc.). Depuis Zabbix 3.4, un nouveau processus de gestion IPMI a été ajouté pour planifier les vérifications IPMI par les pollers IPMI. Maintenant, un hôte est toujours interrogé par un seul poller IPMI à la fois, ce qui réduit le nombre de connexions ouvertes aux contrôleurs BMC. Avec ces modifications, il est sûr d'augmenter le nombre de pollers IPMI sans se soucier de la surcharge du contrôleur BMC. Le processus du gestion IPMI est automatiquement démarré lorsqu'au moins un poller IPMI est démarré. Voir aussi les [problèmes connus](/fr/manual/installation/known_issues#verifications_ipmi) pour les vérifications IPMI. #### Overview You may want to use SNMP monitoring on devices such as printers, network switches, routers or UPS that usually are SNMP-enabled and on which it would be impractical to attempt setting up complete operating systems and Zabbix agents. To be able to retrieve data provided by SNMP agents on these devices, Zabbix server must be [initially configured](/manual/installation/install#configure_the_sources) with SNMP support. SNMP checks are performed over the UDP protocol only. Zabbix server and proxy daemons query SNMP devices for multiple values in a single request. This affects all kinds of SNMP items (regular SNMP items, SNMP items with dynamic indexes, and SNMP low-level discovery) and should make SNMP processing much more efficient. See the [bulk processing](#internal_workings_of_bulk_processing) section for technical details on how it works internally. Bulk requests can also be disabled for devices that cannot handle them properly using the "Use bulk requests" setting for each interface. Zabbix server and proxy daemons log lines similar to the following if they receive an incorrect SNMP response: SNMP response from host "gateway" does not contain all of the requested variable bindings While they do not cover all the problematic cases, they are useful for identifying individual SNMP devices for which bulk requests should be disabled. Zabbix server/proxy will always retry at least one time after an unsuccessful query attempt: either through the SNMP library's retrying mechanism or through the internal [bulk processing](#internal_workings_of_bulk_processing) mechanism. ::: notewarning If monitoring SNMPv3 devices, make sure that msgAuthoritativeEngineID (also known as snmpEngineID or "Engine ID") is never shared by two devices. According to [RFC 2571](http://www.ietf.org/rfc/rfc2571.txt) (section 3.1.1.1) it must be unique for each device. ::: ::: notewarning RFC3414 requires the SNMPv3 devices to persist their engineBoots. Some devices do not do that, which results in their SNMP messages being discarded as outdated after being restarted. In such situation, SNMP cache needs to be manually cleared on a server/proxy (by using [-R snmp\_cache\_reload](/manual/concepts/server#runtime_control)) or the server/proxy needs to be restarted. ::: #### Aperçu Vous pouvez utiliser la supervision SNMP sur des périphériques tels que des imprimantes, des commutateurs réseau, des routeurs ou des onduleurs qui sont généralement compatibles SNMP et sur lesquels il serait impossible d'installer des systèmes d'exploitation complets et des agents Zabbix. Pour pouvoir récupérer les données fournies par les agents SNMP sur ces périphériques, le serveur Zabbix doit être [configuré initialement](/manual/installation/install#configure_the_sources) avec le support SNMP. Les vérifications SNMP sont effectuées uniquement par le protocole UDP. Les démons du serveur Zabbix et des proxys interrogent les périphériques SNMP pour plusieurs valeurs dans une seule requête. Cela affecte tous les types d'éléments SNMP (éléments SNMP standard, éléments SNMP avec index dynamiques et découverte SNMP de bas niveau) et rend le traitement SNMP beaucoup plus efficace. Veuillez consulter la [section des détails techniques](#internal_workings_of_bulk_processing) ci-dessous pour savoir comment cela fonctionne en interne. Il existe également un paramètre "Utiliser les requêtes de masse" pour chaque interface qui permet de désactiver les requêtes groupées pour les périphériques qui ne peuvent pas les gérer correctement. Les démons des serveurs Zabbix et des proxys inscrivent dans les logs zabbix les lignes similaires à ce qui suit s'ils reçoivent une réponse SNMP incorrecte : SNMP response from host "gateway" does not contain all of the requested variable bindings Bien qu'ils ne couvrent pas tous les cas problématiques, ils sont utiles pour identifier les périphériques SNMP individuels pour lesquels les requêtes de masse doivent être désactivées. Le serveur Zabbix et les proxy vont toujours réessayer au moins une fois : soit via le mécanisme de nouvelle tentative de la bibliothèque SNMP, soit via le [mécanisme interne de traitement des requêtes de masse](#internal_workings_of_bulk_processing). ::: notewarning Si vous surveillez les périphériques SNMPv3, assurez-vous que msgAuthoritarianEngineID (également appelé snmpEngineID ou "Engine ID") n'est jamais partagé par deux périphériques. Selon la [RFC 2571](http://www.ietf.org/rfc/rfc2571.txt) (section 3.1.1.1), il doit être unique pour chaque périphérique. ::: ::: notewarning La RFC3414 exige que les appareils SNMPv3 conservent leur engineBoots. Certains périphériques ne le font pas, ce qui entraîne la suppression de leurs messages SNMP comme obsolètes après le redémarrage. Dans une telle situation, le cache SNMP doit être effacé manuellement sur un serveur/proxy (en utilisant [-R snmp\_cache\_reload](/manual/concepts/server#runtime_control)) ou le serveur/proxy doit être redémarré. ::: #### Overview Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent. This section lists parameters supported in a Zabbix agent 2 configuration file (zabbix\_agent2.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported in the beginning of the line. #### Aperçu L'agent Zabbix 2 est une nouvelle génération d'agent Zabbix et peut être utilisé à la place de l'agent Zabbix. Cette section répertorie les paramètres pris en charge dans un fichier de configuration de l'agent Zabbix 2 (zabbix\_agent2.conf). Notez que: - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent. Zabbix agent 2 has been developed to: - reduce the number of TCP connections - provide improved concurrency of checks - be easily extendible with plugins. A plugin should be able to: - provide trivial checks consisting of only a few simple lines of code - provide complex checks consisting of long-running scripts and standalone data gathering with periodic sending back of the data - be a drop-in replacement for Zabbix agent (in that it supports all the previous functionality) Agent 2 is written in Go programming language (with some C code of Zabbix agent reused). A configured Go environment with a currently supported [Go version](https://golang.org/doc/devel/release#policy) is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; it can be run as a [Windows service](/manual/appendix/install/windows_agent). Passive checks work similarly to Zabbix agent. Active checks support scheduled/flexible intervals and check concurrency within one active server. ::: noteclassic By default, Zabbix agent 2 will schedule the first data collection for active checks at a conditionally random time within the item's update interval to prevent spikes in resource usage. To perform active checks that do not have *Scheduling* [update interval](/manual/config/items/item/custom_intervals#scheduling-interval) immediately after the agent restart, set `ForceActiveChecksOnStart` parameter (global-level) or `Plugins.<Plugin name>.System.ForceActiveChecksOnStart` (affects only specific plugin checks) in the [configuration file](/manual/appendix/config/zabbix_agent2). Plugin-level parameter, if set, will override the global parameter. Forcing active checks on start is supported since Zabbix 6.0.2. ::: **Check concurrency** Checks from different plugins can be executed concurrently. The number of concurrent checks within one plugin is limited by the plugin capacity setting. Each plugin may have a hardcoded capacity setting (100 being default) that can be lowered using the `Plugins.<PluginName>.System.Capacity=N` setting in the *Plugins* configuration [parameter](#configuration_file). Former name of this parameter `Plugins.<PluginName>.Capacity` is still supported, but has been deprecated in Zabbix 6.0. See also: [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/en/plugins). #### Aperçu L'agent Zabbix 2 est une nouvelle génération d'agent Zabbix et peut être utilisé à la place de l'agent Zabbix. L'agent Zabbix 2 a été développé pour : - réduire le nombre de connexions TCP - améliorer la simultanéité des vérifications - être facilement extensible avec des plugins. Un plugin doit être capable de : - fournir des vérifications triviales composées de quelques lignes de code simples - fournir des contrôles complexes consistant en des scripts de longue durée et une collecte de données autonome avec renvoi périodique des données - être un remplaçant direct de l'agent Zabbix (en ce sens qu'il prend en charge toutes les fonctionnalités précédentes) L'agent 2 est écrit en langage de programmation Go (avec du code C de l'agent Zabbix réutilisé). Un environnement Go configuré avec une [version Go](https://golang.org/doc/devel/release#policy) actuellement prise en charge est requis pour créer l'agent Zabbix 2. L'agent 2 n'a pas de prise en charge intégrée de la démonisation sous Linux ; il peut être exécuté en tant que [service Windows](/manual/appendix/install/windows_agent). Les vérifications passives fonctionnent de la même manière que l'agent Zabbix. Les vérifications actives prennent en charge les intervalles planifiés/flexibles et vérifient la simultanéité au sein d'un serveur actif. ::: noteclassic Par défaut, l'agent Zabbix 2 planifiera la première collecte de données pour les vérifications actives à une heure conditionnellement aléatoire dans l'intervalle de mise à jour de l'élément pour éviter les pics d'utilisation des ressources. Pour effectuer des vérifications actives qui n'ont pas d'[intervalle de mise à jour](/manual/config/items/item/custom_intervals#scheduling-interval) *planifié* immédiatement après le redémarrage de l'agent, définissez le paramètre `ForceActiveChecksOnStart` (niveau global) ou `Plugins .<Plugin name>.System.ForceActiveChecksOnStart` (affecte uniquement les vérifications de plugins spécifiques) dans le [fichier de configuration](/manual/appendix/config/zabbix_agent2). Le paramètre au niveau du plugin, s'il est défini, remplacera le paramètre global. Forcer les vérifications actives au démarrage est pris en charge depuis Zabbix 6.0.2. ::: **Vérifier la simultanéité** Les vérifications de différents plugins peuvent être exécutées simultanément. Le nombre de vérifications simultanées dans un plugin est limité par le paramètre de capacité du plugin. Chaque plug-in peut avoir un paramètre de capacité codé en dur (100 étant la valeur par défaut) qui peut être réduit à l'aide du paramètre `Plugins.<PluginName>.System.Capacity=N` dans la configuration le [paramètre](#configuration_file) *Plugins*. L'ancien nom de ce paramètre `Plugins.<PluginName>.Capacity` est toujours pris en charge, mais a été déprécié dans Zabbix 6.0. Voir aussi : [Directives de développement de plugins](https://www.zabbix.com/documentation/guidelines/en/plugins). #### Overview Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc). The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server can actively alert the administrators of the particular machine that reported the failure. Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information. #### Aperçu L'agent Zabbix est déployé sur une cible de surveillance pour superviser activement les ressources locales et les applications (disques durs, mémoire, statistiques de processeur, etc.). L'agent rassemble les informations opérationnelles localement et transmet les données au serveur Zabbix pour un traitement ultérieur. En cas d'échec (par exemple, un disque dur plein ou un service en panne), le serveur Zabbix peut alerter activement les administrateurs de la machine particulière qui a signalé la panne. Les agents Zabbix sont extrêmement efficaces en raison de l'utilisation d'appels système natifs pour collecter des informations statistiques. #### Overview Zabbix can be used for centralized monitoring and analysis of log files with/without log rotation support. Notifications can be used to warn users when a log file contains certain strings or string patterns. To monitor a log file you must have: - Zabbix agent running on the host - log monitoring item set up ::: noteimportant The size limit of a monitored log file depends on [large file support](/manual/appendix/items/large_file_support). ::: #### Aperçu Zabbix peut être utilisé pour la surveillance centralisée et l'analyse des fichiers journaux avec/sans support de rotation des fichiers journaux. Les notifications peuvent être utilisées pour avertir les utilisateurs lorsqu'un fichier journal contient certaines chaînes ou certains modèles de chaîne. Pour superviser un fichier journal, vous devez avoir : - Un agent Zabbix en cours d'exécution sur l'hôte - Un paramètre de supervision de fichier journal mis en place ::: noteimportant La taille limite d'un fichier de logs supervisé dépend du [support des fichiers volumineux](/manual/appendix/items/large_file_support). ::: #### Overview Zabbix can query metrics exposed in the Prometheus line format. Two steps are required to start gathering Prometheus data: - an [HTTP master item](/manual/config/items/itemtypes/http) pointing to the appropriate data endpoint, e.g. `https://<prometheus host>/metrics` - dependent items using a Prometheus preprocessing option to query required data from the metrics gathered by the master item There are two Prometheus data preprocessing options: - *Prometheus pattern* - used in normal items to query Prometheus data - *Prometheus to JSON* - used in normal items and for low-level discovery. In this case queried Prometheus data are returned in a JSON format. #### Aperçu Zabbix peut interroger les métriques exposées dans le format de ligne Prometheus. Deux étapes sont nécessaires pour commencer à collecter les données Prometheus : - un [élément principal HTTP](/manual/config/items/itemtypes/http) pointant vers le point de terminaison de données approprié, par ex. `https://<prometheus host>/metrics` - des éléments dépendants utilisant une option de prétraitement Prometheus pour interroger les données requises à partir des métriques recueillies par l'élément principal Il existe deux options de prétraitement des données Prometheus : - *Motif Prometheus* - utilisé dans les éléments normaux pour interroger les données Prometheus - * Prometheus vers JSON * - utilisé dans les éléments normaux et pour la découverte de bas niveau. Dans ce cas, les données Prometheus interrogées sont renvoyées au format JSON. #### Overview Zabbix is a highly integrated network monitoring solution, offering a multiplicity of features in a single package. **[Data gathering](/manual/config/items)** - availability and performance checks - support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring - custom checks - gathering desired data at custom intervals - performed by server/proxy and by agents **[Flexible threshold definitions](/manual/config/triggers)** - you can define very flexible problem thresholds, called triggers, referencing values from the backend database **[Highly configurable alerting](/manual/config/notifications)** - sending notifications can be customized for the escalation schedule, recipient, media type - notifications can be made meaningful and helpful using macro variables - automatic actions include remote commands **[Real-time graphing](/manual/config/visualization/graphs/simple)** - monitored items are immediately graphed using the built-in graphing functionality **[Web monitoring capabilities](/manual/web_monitoring)** - Zabbix can follow a path of simulated mouse clicks on a web site and check for functionality and response time **[Extensive visualization options](/manual/config/visualization)** - ability to create custom graphs that can combine multiple items into a single view - network maps - slideshows in a dashboard-style overview - reports - high-level (business) view of monitored resources **[Historical data storage](/manual/installation/requirements#database_size)** - data stored in a database - configurable history - built-in housekeeping procedure **[Easy configuration](/manual/config/hosts)** - add monitored devices as hosts - hosts are picked up for monitoring, once in the database - apply templates to monitored devices **[Use of templates](/manual/config/templates)** - grouping checks in templates - templates can inherit other templates **[Network discovery](/manual/discovery)** - automatic discovery of network devices - agent autoregistration - discovery of file systems, network interfaces and SNMP OIDs **[Fast web interface](/manual/web_interface)** - a web-based frontend in PHP - accessible from anywhere - you can click your way through - audit log **[Zabbix API](/manual/api)** - Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party software integration and other purposes. **[Permissions system](/manual/config/users_and_usergroups)** - secure user authentication - certain users can be limited to certain views **[Full featured and easily extensible agent](/manual/concepts/agent)** - deployed on monitoring targets - can be deployed on both Linux and Windows **[Binary daemons](/manual/concepts/server)** - written in C, for performance and small memory footprint - easily portable **[Ready for complex environments](/manual/distributed_monitoring)** - remote monitoring made easy by using a Zabbix proxy #### Aperçu Zabbix est une solution de supervision de réseaux hautement intégrée, offrant une multitude de fonctionnalités dans un seul package **[Collecte de données](/manual/config/items)** - disponibilité et contrôles de performance - prise en charge de SNMP (réception et interrogation), IPMI, JMX, et de la surveillance VMware - vérifications personnalisées - collecte des données souhaitées à des intervalles personnalisés - effectuée par le serveur/proxy et par des agents **[Définitions de seuils flexibles](/manual/config/triggers)** - vous pouvez définir des seuils de problèmes très flexibles, appelés déclencheurs, référençant des valeurs à partir de la base de données principale **[Alertes hautement personnalisables](/manual/config/notifications)** - l'envoi de notifications peut être personnalisé selon le calendrier d'escalade, le destinataire ou le type de média - les notifications peuvent être significatives et utiles en utilisant des variables macro - les actions automatiques incluent des commandes à distance **[Graphiques en temps réel](/manual/config/visualization/graphs/simple)** - les éléments supervisés sont immédiatement représentés graphiquement à l'aide de la fonctionnalité graphique intégrée **[Capacités de supervision Web](/manual/web_monitoring)** - Zabbix peut suivre un chemin de clics de souris simulés sur un site Web et ainsi vérifier le bon fonctionnement et le temps de réponse **[Options de visualisation étendues](/manual/config/visualization)** - possibilité de créer des graphiques personnalisés pouvant combiner plusieurs éléments dans une même vue - représentation du réseau sous forme de carte - des diaporamas pour un aperçu dans un tableau de bord - des rapports - vue de haut niveau (métier) des ressources surveillées **[Stockage de données historiques](/manual/installation/requirements#database_size)** - données stockées dans une base de données - historique configurable - procédure de nettoyage intégrée **[Configuration facile](/manual/config/hosts)** - ajouter des équipements surveillés en tant qu'hôtes - les hôtes sont pris en charge pour la surveillance, une fois dans la base de données - appliquer des modèles aux équipements surveillés **[Utilisation de modèles](/manual/config/templates)** - grouper les vérifications dans des modèles - les modèles peuvent hériter d'autres modèles **[Découverte du réseau](/manual/discovery)** - découverte automatique des équipements réseaux - enregistrement automatique de l'agent - découverte de systèmes de fichiers, d'interfaces réseau et d'OID SNMP **[Interface Web rapide](/manual/web_interface)** - une interface web en PHP - accessible de n'importe où - la navigation se fait via des clics - journal d'audit **[API Zabbix](/manual/api)** - L'API Zabbix fournit une interface programmable pour des manipulations de masse sur Zabbix, l'intégration de logiciels tiers et plus encore.. **[Système de permissions](/manual/config/users_and_usergroups)** - authentification utilisateur sécurisée - certains utilisateurs peuvent être limités à certaines vues **[Agent complet et facilement extensible](/manual/concepts/agent)** - déployé sur des cibles de surveillance - peut être déployé sur Linux et Windows **[Démons binaires](/manual/concepts/server)** - écrit en C, pour des performances et une faible empreinte mémoire - facilement portable **[Prêt pour les environnements complexes](/manual/distributed_monitoring)** - supervision à distance facilitée en utilisant un proxy Zabbix #### Overview zabbix\_js is a command line utility that can be used for embedded script testing. This utility will execute a user script with a string parameter and print the result. Scripts are executed using the embedded Zabbix scripting engine. In case of compilation or execution errors zabbix\_js will print the error in stderr and exit with code 1. #### Aperçu zabbix\_js est un utilitaire de ligne de commande qui peut être utilisé pour tester des scripts intégrés. Cet utilitaire exécutera un script utilisateur avec un paramètre de chaîne et écrira le résultat. Les scripts sont exécutés à l'aide du moteur de script Zabbix intégré. En cas d'erreurs de compilation ou d'exécution, zabbix\_js imprimera l'erreur dans stderr et quittera avec le code 1. #### Overview Zabbix Mac OS agent can be installed from PKG installer packages available for [download](https://www.zabbix.com/download_agents#tab:44). Versions with or without encryption are available. #### Aperçu L'agent Zabbix Mac OS peut être installé à partir des packages d'installation PKG disponibles en [téléchargement] (https://www.zabbix.com/download_agents#tab:44). Des versions avec ou sans cryptage sont disponibles. #### Overview Zabbix offers automatic network discovery functionality that is effective and very flexible. With network discovery properly set up you can: - speed up Zabbix deployment - simplify administration - use Zabbix in rapidly changing environments without excessive administration Zabbix network discovery is based on the following information: - IP ranges - Availability of external services (FTP, SSH, WEB, POP3, IMAP, TCP, etc) - Information received from Zabbix agent (only unencrypted mode is supported) - Information received from SNMP agent It does NOT provide: - Discovery of network topology Network discovery basically consists of two phases: discovery and actions. #### Aperçu Zabbix offre une fonctionnalité de découverte automatique du réseau efficace et très flexible. Avec la découverte du réseau correctement configurée, vous pouvez : - accélérer le déploiement de Zabbix - simplifier l'administration - utiliser Zabbix dans des environnements en mutation rapide sans administration excessive La découverte du réseau Zabbix est basée sur les informations suivantes : - Les plages IP - La disponibilité de services externes ( FTP , SSH, WEB, POP3, IMAP, TCP, etc.) - Les informations reçues de l'agent Zabbix (seul le mode non crypté est pris en charge) - Les informations reçues de l'agent SNMP Elle ne fournit PAS : - La découverte de la topologie du réseau La découverte du réseau comprend essentiellement deux phases : la découverte et les actions. #### Overview Zabbix provides an effective and reliable way of monitoring a distributed IT infrastructure using Zabbix [proxies](/manual/distributed_monitoring/proxies). Proxies can be used to collect data locally on behalf of a centralized Zabbix server and then report the data to the server. #### Aperçu Zabbix fournit un moyen efficace et fiable de surveiller une infrastructure informatique distribuée à l'aide de serveurs [proxys](/fr/manual/distributed_monitoring/proxies) Zabbix. Les proxys peuvent être utilisés pour collecter des données localement pour le compte d'un serveur Zabbix centralisé, puis rapporter les données au serveur. #### Overview Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to. Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry. A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators. Zabbix proxy requires a separate database. ::: noteimportant Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle is at your own risk and may contain some limitations as, for example, in [return values](/manual/discovery/low_level_discovery#overview) of low-level discovery rules. ::: See also: [Using proxies in a distributed environment](/manual/distributed_monitoring/proxies) #### Aperçu Le proxy Zabbix est un processus qui peut collecter des données de surveillance à partir d'un ou plusieurs équipements surveillés et envoyer les informations au serveur Zabbix, en travaillant essentiellement pour le compte du serveur. Toutes les données collectées sont bufferisées localement puis transférées au serveur Zabbix auquel appartient le proxy. Le déploiement d'un proxy est facultatif, mais peut s'avérer très utile pour répartir la charge d'un seul serveur Zabbix. Si seuls les proxys collectent des données, le traitement sur le serveur devient moins gourmand en CPU et en E/S disque. Un proxy Zabbix est la solution idéale pour la surveillance centralisée des sites distants, des succursales et des réseaux sans administrateurs locaux. Le proxy Zabbix nécessite une base de données séparée. ::: noteimportant Notez que les bases de données supportées avec le proxy Zabbix sont SQLite, MySQL et PostgreSQL. L'utilisation d'Oracle est à vos propres risques et peut contenir certaines limitations, par exemple, dans les [valeurs de retour](/manual/discovery/low_level_discovery#overview) des règles de découverte de bas niveau. ::: Voir aussi : [Utilisation des proxys dans un environnement distribué](/manual/distributed_monitoring/proxies) #### Overview Zabbix server is the central process of Zabbix software. The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks. The server is the central repository in which all configuration, statistical and operational data is stored, and it is the entity in Zabbix that will actively alert administrators when problems arise in any of the monitored systems. The functioning of a basic Zabbix server is broken into three distinct components; they are: Zabbix server, web frontend and database storage. All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section. #### Aperçu Le serveur Zabbix est le processus central du logiciel Zabbix. Le serveur effectue l'interrogation et la récupération des données, il calcule les déclencheurs, envoie des notifications aux utilisateurs. C'est le composant central auquel les agents et les proxys Zabbix rapportent des données de disponibilité et d'intégrité des systèmes. Le serveur peut lui-même vérifier à distance les services réseaux (tels que les serveurs Web et les serveurs de messagerie) à l'aide de simples vérifications de service. Le serveur est le référentiel central dans lequel toutes les données de configuration, statistiques et opérationnelles sont stockées, et c'est l'entité de Zabbix qui alertera activement les administrateurs lorsque des problèmes surviennent dans l'un des systèmes surveillés. Le fonctionnement d'un serveur Zabbix de base est divisé en trois composants distincts ; ce sont : le serveur Zabbix, l'interface Web et le stockage en base de données. Toutes les informations de configuration de Zabbix sont stockées dans la base de données, avec laquelle le serveur et l'interface Web interagissent. Par exemple, lorsque vous créez un nouvel élément à l'aide de l'interface Web (ou de l'API), il est ajouté à la table des éléments de la base de données. Ensuite, environ une fois par minute, le serveur Zabbix interroge la table des éléments pour obtenir une liste des éléments actifs qui sont ensuite stockés dans un cache sur le serveur Zabbix. C'est pourquoi cela peut prendre jusqu'à deux minutes pour que toute modification apportée à l'interface Zabbix apparaisse dans la dernière section de données. #### Overview Zabbix server uses a JSON- based communication protocol for receiving data from Zabbix sender with the help of [trapper item](/manual/config/items/itemtypes/trapper). Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen). #### Aperçu Le serveur Zabbix utilise un protocole de communication basé sur JSON pour recevoir les données du sender Zabbix à l'aide d'un [élément trapper](/manual/config/items/itemtypes/trapper). Les messages de requêtes et de réponses doivent commencer par [l’en-tête et la longueur des données](/manual/appendix/protocols/header_datalen). #### Overview Zabbix strives to provide a growing list of useful out-of-the-box [templates](/manual/config/templates). Out-of-the-box templates come preconfigured and thus are a useful way for speeding up the deployment of monitoring jobs. The templates are available: - In new installations - in *Configuration* → *Templates*; - If you are upgrading from previous versions, you can find these templates in the `templates` directory of the downloaded latest Zabbix version. While in *Configuration* → *Templates* you can import them manually from this directory. - It is also possible to download the template from [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) directly (make sure the template is compatible with your Zabbix version). Please use the sidebar to access information about specific template types and operation requirements. See also: - [Template import](/manual/xml_export_import/templates#importing) - [Linking a template](/manual/config/templates/linking#linking_a_template) #### Aperçu Zabbix s'efforce de fournir une liste croissante de [modèles](/manual/config/templates) prêts à l'emploi utiles. Les modèles prêts à l'emploi sont préconfigurés et constituent donc un moyen utile d'accélérer le déploiement des tâches de surveillance. Les modèles sont disponibles : - Dans les nouvelles installations - dans *Configuration* → *Modèles* ; - Si vous effectuez une mise à niveau à partir de versions précédentes, vous pouvez trouver ces modèles dans le répertoire `templates` de la dernière version téléchargée de Zabbix. Dans *Configuration* → *Modèles*, vous pouvez les importer manuellement à partir de ce répertoire. - Il est également possible de télécharger le modèle depuis [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) directement (assurez-vous que le modèle est compatible avec votre version de Zabbix) . Veuillez utiliser la barre latérale pour accéder aux informations sur les types de modèles spécifiques et les exigences de fonctionnement. Voir également: - [Importation de modèle](/manual/xml_export_import/templates#importing) - [Lier un modèle](/manual/config/templates/linking#linking_a_template) #### Overview Zabbix supports a number of built-in macros which may be used in various situations. These macros are variables, identified by a specific syntax: {MACRO} Macros resolve to a specific value depending on the context. Effective use of macros allows to save time and make Zabbix configuration more transparent. In one of typical uses, a macro may be used in a template. Thus a trigger on a template may be named "Processor load is too high on {HOST.NAME}". When the template is applied to the host, such as Zabbix server, the name will resolve to "Processor load is too high on Zabbix server" when the trigger is displayed in the Monitoring section. Macros may be used in item key parameters. A macro may be used for only a part of the parameter, for example `item.key[server_{HOST.HOST}_local]`. Double-quoting the parameter is not necessary as Zabbix will take care of any ambiguous special symbols, if present in the resolved macro. There are other types of macros in Zabbix. Zabbix supports the following macros: - `{MACRO}` - built-in macro (see [full list](/manual/appendix/macros/supported_by_location)) - `{<macro>.<func>(<params>)}` - macro [functions](/manual/config/macros/macro_functions) - `{$MACRO}` - [user-defined macro](/manual/config/macros/user_macros), optionally [with context](/manual/config/macros/user_macros_context) - `{#MACRO}` - macro for [low-level discovery](/manual/config/macros/lld_macros) - `{?EXPRESSION}` - [expression macro](/manual/config/macros/expression_macros) #### Aperçu Zabbix prend en charge un certain nombre de macros intégrées qui peuvent être utilisées dans diverses situations. Ces macros sont des variables, identifiées par une syntaxe spécifique : {MACRO} Les macros se résolvent en une valeur spécifique en fonction du contexte. L'utilisation efficace des macros permet de gagner du temps et de rendre la configuration de Zabbix plus transparente. Dans l'une des utilisations typiques, une macro peut être utilisée dans un modèle. Ainsi, un déclencheur sur un modèle peut être nommé "La charge du processeur est trop élevée sur {HOST.NAME}". Lorsque le modèle est appliqué à l'hôte, tel que le serveur Zabbix, le nom se résoudra en "La charge du processeur est trop élevée sur le serveur Zabbix" lorsque le déclencheur s'affiche dans la section Surveillance. Des macros peuvent être utilisées dans les paramètres clés de l'élément. Une macro peut être utilisée pour une partie seulement du paramètre, par exemple `item.key[server_{HOST.HOST}_local]`. Il n'est pas nécessaire de mettre le paramètre entre guillemets doubles car Zabbix prendra soin de tous les symboles spéciaux ambigus, s'ils sont présents dans la macro résolue. Il existe d'autres types de macros dans Zabbix. Zabbix prend en charge les macros suivantes : - `{MACRO}` - macro intégrée (voir [liste complète](/manual/appendix/macros/supported_by_location)) - `{<macro>.<func>(<params>)}` - [fonctions](/manual/config/macros/macro_functions) de macro - `{$MACRO}` - [macro définie par l'utilisateur](/manual/config/macros/user_macros), éventuellement [avec contexte](/manual/config/macros/user_macros_context) - `{#MACRO}` - macro pour [découverte de bas niveau](/manual/config/macros/lld_macros) - `{?EXPRESSION}` - [macro d'expression](/manual/config/macros/expression_macros) #### Overview Zabbix supports the sending of SMS messages using a serial GSM modem connected to Zabbix server's serial port. Make sure that: - The speed of the serial device (normally /dev/ttyS0 under Linux) matches that of the GSM modem. Zabbix does not set the speed of the serial link. It uses default settings. - The 'zabbix' user has read/write access to the serial device. Run the command ls –l /dev/ttyS0 to see current permissions of the serial device. - The GSM modem has PIN entered and it preserves it after power reset. Alternatively you may disable PIN on the SIM card. PIN can be entered by issuing command AT+CPIN="NNNN" (NNNN is your PIN number, the quotes must be present) in a terminal software, such as Unix minicom or Windows HyperTerminal. Zabbix has been tested with these GSM modems: - Siemens MC35 - Teltonika ModemCOM/G10 To configure SMS as the delivery channel for messages, you also need to configure SMS as the media type and enter the respective phone numbers for the users. #### Aperçu Zabbix prend en charge l'envoi de SMS via un modem GSM connecté au port série du serveur Zabbix. Assurez-vous que : - La vitesse du périphérique série (normalement /dev/ttyS0 sous Linux) corresponde à celle du modem GSM. Zabbix ne définit pas la vitesse de la liaison série. Il utilise les paramètres par défaut. - L'utilisateur 'zabbix' dispose d'un accès en lecture/écriture sur le périphérique série. Exécutez la commande ls --l /dev/ttyS0 pour afficher les autorisations en cours du périphérique série. - Le modem GSM a un code PIN entré et qu'il le conserve après la réinitialisation de l'alimentation. Vous pouvez également désactiver le code PIN sur la carte SIM. Vous pouvez entrer un code PIN en émettant la commande AT+CPIN = "NNNN" (NNNN est votre numéro PIN, les guillemets doivent être présents) dans un logiciel de terminal, tel que Unix minicom ou Windows HyperTerminal. Zabbix a été testé avec ces modems GSM : - Siemens MC35 - Teltonika ModemCOM / G10 Pour configurer les SMS en tant que canal de remise des messages, vous devez également configurer les SMS en tant que type de média et entrer les numéros de téléphone respectifs des utilisateurs. #### Overview Zabbix supports TimescaleDB, a PostgreSQL-based database solution of automatically partitioning data into time-based chunks to support faster performance at scale. ::: notewarning Currently TimescaleDB is not supported by Zabbix proxy. ::: Instructions on this page can be used for creating TimescaleDB database or migrating from existing PostgreSQL tables to TimescaleDB. #### Aperçu Zabbix prend en charge TimescaleDB, une solution de base de données basée sur PostgreSQL qui partitionne automatiquement les données en blocs temporels pour prendre en charge des performances plus rapides à grande échelle. ::: notewarning Actuellement, TimescaleDB n'est pas pris en charge par le proxy Zabbix. ::: Les instructions sur cette page peuvent être utilisées pour créer une base de données TimescaleDB ou migrer des tables PostgreSQL existantes vers TimescaleDB. #### Overview Zabbix web frontend can be temporarily disabled in order to prohibit access to it. This can be useful for protecting the Zabbix database from any changes initiated by users, thus protecting the integrity of database. Zabbix database can be stopped and maintenance tasks can be performed while Zabbix frontend is in maintenance mode. Users from defined IP addresses will be able to work with the frontend normally during maintenance mode. #### Aperçu L'interface web de Zabbix peut être temporairement désactivée afin d’en interdire l’accès. Cela peut être utile pour protéger la base de données Zabbix de toute modification initiée par les utilisateurs, protégeant ainsi l'intégrité de la base de données. La base de données Zabbix peut être arrêtée et des tâches de maintenance exécutées lorsque l’interface Zabbix est en mode maintenance. Les utilisateurs ayant les adresses IP définies pourront travailler normalement avec l’interface en mode maintenance. #### Overview Zabbix web service is a process that is used for communication with external web services. This section lists parameters supported in Zabbix web service configuration file (zabbix\_web\_service.conf). Note that: - The default values reflect process defaults, not the values in the shipped configuration files; - Zabbix supports configuration files only in UTF-8 encoding without [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - Comments starting with "\#" are only supported at the beginning of the line. #### Aperçu Le Web service Zabbix est un processus utilisé pour communiquer avec des Web services externes. Cette section répertorie les paramètres pris en charge dans un fichier de configuration du Web service Zabbix (zabbix\_web\_service.conf). Notez que : - Les valeurs par défaut reflètent les valeurs par défaut du processus, et non les valeurs des fichiers de configuration livrés ; - Zabbix prend en charge les fichiers de configuration uniquement en encodage UTF-8 sans [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) ; - Les commentaires commençant par "\#" ne sont pris en charge qu'en début de ligne. #### Overview Zabbix Windows agent can be installed from Windows MSI installer packages (32-bit or 64-bit) available for [download](https://www.zabbix.com/download_agents#tab:44). The minimum requirement for a Zabbix agent 2 MSI installation is Windows 7 x32. The Zabbix get and sender utilities can also be installed, either together with Zabbix agent/agent 2 or separately. A 32-bit package cannot be installed on a 64-bit Windows. All packages come with TLS support, however, configuring TLS is optional. Both UI and command-line based installation is supported. ::: noteimportant Although Zabbix installation from MSI installer packages is fully supported, it is recommended to install at least *Microsoft .NET Framework 2* for proper error handling. See [Microsoft Download .NET Framework](https://dotnet.microsoft.com/en-us/download/dotnet-framework). ::: #### Aperçu L'agent Zabbix Windows peut être installé à partir des packages d'installation Windows MSI (32 bits ou 64 bits) disponibles en [téléchargement] (https://www.zabbix.com/download_agents#tab:44). La configuration minimale requise pour une installation MSI de l'agent Zabbix 2 est Windows 7 x32. Les utilitaires Zabbix get et sender peuvent également être installés, soit avec l'agent/agent Zabbix 2, soit séparément. Un package 32 bits ne peut pas être installé sur un Windows 64 bits. Tous les packages sont livrés avec la prise en charge de TLS, cependant, la configuration de TLS est facultative. L'installation basée sur l'interface utilisateur et la ligne de commande est prise en charge. ::: noteimportant Bien que l'installation de Zabbix à partir des packages d'installation MSI soit entièrement prise en charge, il est recommandé d'installer au moins *Microsoft .NET Framework 2* pour une bonne gestion des erreurs. Voir également [Microsoft Download .NET Framework](https://dotnet.microsoft.com/en-us/download/dotnet-framework). ::: ### Packages SQL scripts have been moved from the `/usr/share/doc` directory to `/usr/share` in Zabbix packages. ### Packages Les scripts SQL ont été déplacés du répertoire `/usr/share/doc` vers `/usr/share` dans les packages Zabbix. #### Page menu The page menu can be opened by clicking on the three dots  next to the page name:  It contains the following options: - *Copy* - copy the page - *Delete* - delete the page (pages can only be deleted in the dashboard editing mode) - *Properties* - customize the page parameters (the name and the page display period in a slideshow) #### Menu Page Le menu de la page peut être ouvert en cliquant sur les trois points  à côté du nom de la page :  Il contient les options suivantes : - *Copier* - copier la page - *Supprimer* - supprimer la page (les pages ne peuvent être supprimées qu'en mode édition du tableau de bord) - *Propriétés* - personnaliser les paramètres de la page (le nom et la période d'affichage de la page dans un diaporama) ### Parameters `(array)` IDs of hosts to delete. ### Paramètres `(array)` ID des hôtes à supprimer. ### Parameters `(array)` IDs of items to clear. ### Paramètres `(array)` ID des éléments à effacer. ### Parameters `(array)` IDs of proxies to delete. ### Paramètres `(array)` ID des proxys à supprimer. ### Parameters `(array)` IDs of the actions to delete. ### Paramètres `(array)` IDs des actions à supprimer. ### Parameters `(array)` IDs of the correlations to delete. ### Paramètres `(array)` ID des corrélations à supprimer. ### Parameters `(array)` IDs of the dashboards to delete. ### Paramètres `(array)` ID des tableaux de bord à supprimer. ### Parameters `(array)` IDs of the discovery rules to delete. ### Paramètres `(array)` ID des règles de découverte à supprimer. ### Parameters `(array)` IDs of the global macros to delete. ### Paramètres `(array)` ID des macros globales à supprimer. ### Parameters `(array)` IDs of the graph prototypes to delete. ### Paramètres `(array)` ID des prototypes de graphique à supprimer. ### Parameters `(array)` IDs of the graphs to delete. ### Paramètres `(array)` ID des graphiques à supprimer. ### Parameters `(array)` IDs of the host groups to delete. ### Paramètres `(array)` ID des groupes d'hôtes à supprimer. ### Parameters `(array)` IDs of the host interfaces to delete. ### Paramètres `(array)` ID des interfaces hôtes à supprimer. ### Parameters `(array)` IDs of the host macros to delete. ### Paramètres `(array)` ID des macros d'hôtes à supprimer. ### Parameters `(array)` IDs of the host prototypes to delete. ### Paramètres `(array)` ID des prototypes d’hôte à supprimer. ### Parameters `(array)` IDs of the icon maps to delete. ### Paramètres `(array)` ID des correspondances d'icônes à supprimer. ### Parameters `(array)` IDs of the images to delete. ### Paramètres `(array)` ID des images à supprimer. ### Parameters `(array)` IDs of the item prototypes to delete. ### Paramètres `(array)` ID des prototypes d'éléments à supprimer. ### Parameters `(array)` IDs of the items to delete. ### Paramètres `(array)` ID des éléments à supprimer. ### Parameters `(array)` IDs of the LLD rules to delete. ### Paramètres `(array)` ID des règles de découverte bas niveau à supprimer. ### Parameters `(array)` IDs of the maintenance periods to delete. ### Paramètres `(array)` ID des périodes de maintenance à supprimer. ### Parameters `(array)` IDs of the maps to delete. ### Paramètres `(array)` ID des cartes à supprimer. ### Parameters `(array)` IDs of the media types to delete. ### Paramètres `(array)` ID des types de média à supprimer. ### Parameters `(array)` IDs of the regular expressions to delete. ### Paramètres `(array)` ID des expressions régulières à supprimer. ### Parameters `(array)` IDs of the roles to delete. ### Paramètres `(array)` ID des rôles à supprimer. ### Parameters `(array)` IDs of the scheduled reports to delete. ### Paramètres `(array)` ID des rapports planifiés à supprimer. ### Parameters `(array)` IDs of the scripts to delete. ### Paramètres `(array)` ID des scripts à supprimer. ### Parameters `(array)` IDs of the services to delete. ### Paramètres `(array)` ID des services à supprimer. ### Parameters `(array)` IDs of the SLAs to delete. ### Paramètres `(array)` ID des SLA à supprimer. ### Parameters `(array)` IDs of the template dashboards to delete. ### Paramètres `(array)` ID des tableaux de bord de modèle à supprimer. ### Parameters `(array)` IDs of the templates to delete. ### Paramètres `(array)` ID des modèles à supprimer. ### Parameters `(array)` IDs of the tokens to generate. ### Paramètres `(array)` ID des jetons à générer. ### Parameters `(array)` IDs of the trigger prototypes to delete. ### Paramètres `(array)` ID des prototypes de déclencheur à supprimer. ### Parameters `(array)` IDs of the triggers to delete. ### Paramètres `(array)` ID des déclencheurs à supprimer. ### Parameters `(array)` IDs of the user groups to delete. ### Paramètres `(array)` ID des groupes d'utilisateurs à supprimer. ### Parameters `(array)` IDs of the value maps to delete. ### Paramètres `(array)` ID des tables de correspondance à supprimer. ### Parameters `(array)` IDs of the web scenarios to delete. ### Paramètres `(array)` ID des scénarios Web à supprimer. ### Parameters `(array)` IDs of users to delete. ### Paramètres `(array)` ID des utilisateurs à supprimer. ### Parameters `(array)` IDs of users to unblock. ### Paramètres `(array)` ID des utilisateurs à débloquer. ### Parameters `(array)` The method accepts an empty array. ### Paramètres `(array)` La méthode accepte un tableau vide. ### Parameters `(array)` The method accepts an empty array. ### Paramètres `(array)` La méthode accepte un tableau vide. #### Parameters Foreach functions support two common parameters - item filter and time period: foreach_function(item filter,time period) for example: avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m) Some functions support additional parameters. #### Paramètres Les fonctions Foreach prennent en charge deux paramètres communs - le filtre d'élément et une période de temps : foreach_function(item filter,time period) par exemple : avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m) Certaines fonctions prennent en charge des paramètres supplémentaires. ### Parameters `(object/array)` Action properties to be updated. The `actionid` property must be defined for each action, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard action properties](object#action), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object to replace the current filter.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to replace existing operations.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to replace existing recovery operations.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to replace existing update operations.| ### Paramètres `(object/array)` Propriété d'action à mettre à jour. La propriété `actionid` doit être définie pour chaque action, toutes les autres propriétés sont optionnelles. Seules les propriétés renseignées seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés d'action standard](object#action), la méthode accepte les paramètres suivants : |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |filter|object|Objet de [filtre](/manual/api/reference/action/object#action_filter) d'action pour remplacer le filtre actuel.| |operations|array|[Opérations](/manual/api/reference/action/object#action_operation) d'action à remplacer dans l'opération existante.| |recovery\_operations|array|[Opérations de récupération](/manual/api/reference/action/object#action_recovery_operation) d'action pour remplacer les opérations de récupération existantes.| |update\_operations|array|[Opérations de mise à jour](/manual/api/reference/action/object#action_update_operation) d'action pour remplacer les opérations de mise à jour existantes.| ### Parameters `(object/array)` Actions to create. Additionally to the [standard action properties](object#action), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object for the action.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to create for the action.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to create for the action.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to create for the action.| ### Paramètres `(object/array)` Actions à créer. En plus des [propriétés d'action standard](object#action), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |filter|object|Objet de [filtre](/manual/api/reference/action/object#action_filter) d'action pour l'action.| |operations|array|[Opérations](/manual/api/reference/action/object#action_operation) d'action à créer pour l'action.| |recovery\_operations|array|[Opérations de récupération](/manual/api/reference/action/object#action_recovery_operation) d'action à créer pour l'action.| |update\_operations|array|[Opérations de mise à jour](/manual/api/reference/action/object#action_update_operation) d'action à créer pour l'action.| ### Parameters `(object/array)` A task to create. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Task type.<br><br>Possible values:<br>1 - Diagnostic information;<br>6 - Check now.| |**request**<br>(required)|object|Task request object according to the task type. Correct format of request object is described in [Task object](/manual/api/reference/task/object) section.| |proxy\_hostid|integer|Proxy about which Diagnostic information task will collect data.<br><br>Ignored for 'Check now' tasks.| *Note* that 'Check now' tasks can be created only for the following types of items/discovery rules: - Zabbix agent - SNMPv1/v2/v3 agent - Simple check - Internal check - External check - Database monitor - HTTP agent - IPMI agent - SSH agent - TELNET agent - Calculated check - JMX agent ### Paramètres `(object/array)` Une tâche à créer. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(obligatoire)|integer|Type de tâche.<br><br>Valeurs possibles :<br>1 - Informations de diagnostic ;<br>6 - Vérifier maintenant.| |**request**<br>(obligatoire)|object|Objet de demande de tâche selon le type de tâche. Le format correct de l'objet de requête est décrit dans la section [Objet de tâche](/manual/api/reference/task/object).| |proxy\_hostid|integer|Proxy pour lequel la tâche d'informations de diagnostic collectera des données.<br><br>Ignoré pour les tâches 'Vérifier maintenant'.| *Notez* que les tâches 'Vérifier maintenant' ne peuvent être créées que pour les types d'objets/règles de découverte suivants : - Agent Zabbix - Agent SNMPv1/v2/v3 - Vérification simple - Contrôle interne - Contrôle externe - Moniteur de base de données - Agent HTTP - Agent IPMI - Agent SSH - Agent TELNET - Vérification calculée - Agent JMX ### Parameters `(object/array)` Correlation properties to be updated. The `correlationid` property must be defined for each correlation, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object to replace the current filter.| |operations|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to replace existing operations.| ### Paramètres `(object/array)` Propriétés de corrélation à mettre à jour. La propriété `correlationid` doit être définie pour chaque corrélation, toutes les autres propriétés sont facultatives. Seules les propriétés passées seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de corrélation standard](object#correlation), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Objet [filtre](/manual/api/reference/correlation/object#correlation_filter) en remplacement du filtre actuel.| |operations|array|[Opérations](/manual/api/reference/correlation/object#correlation_operation) de corrélation en remplacement du opérations existantes.| ### Parameters `(object/array)` Correlations to create. Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operations**<br>(required)|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to create for the correlation.| |**filter**<br>(required)|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object for the correlation.| ### Paramètres `(object/array)` Corrélations à créer En plus des [propriétés de corrélation standard](object#correlation), la méthode accepte les paramètres suivants : |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operations**<br>(obligatoire)|array|[Opérations](/manual/api/reference/correlation/object#correlation_operation) de corrélation à créer pour la corrélation.| |**filter**<br>(obligatoire)|object|Objet de [filtre](/manual/api/reference/correlation/object#correlation_filter) de corrélation pour la corrélation.| ### Parameters `(object/array)` Dashboard properties to be updated. The `dashboardid` property must be specified for each dashboard, all other properties are optional. Only the specified properties will be updated. Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |pages|array|Dashboard [pages](object#dashboard_page) to replace the existing dashboard pages.<br><br>Dashboard pages are updated by the `dashboard_pageid` property. New dashboard pages will be created for objects without `dashboard_pageid` property and the existing dashboard pages will be deleted if not reused. Dashboard pages will be ordered in the same order as specified. Only the specified properties of the dashboard pages will be updated. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to replace the existing elements.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to replace the existing elements.| ### Paramètres `(object/array)` Propriétés du tableau de bord à mettre à jour. La propriété `dashboardid` doit être définie pour chaque tableau de bord, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. Outre les [propriétés standards de tableau de bord](object#dashboard), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |pages|array|[Pages](object#dashboard_page) de tableau de bord en remplacement des pages existantes.<br><br>Les pages de tableau de bord sont mises à jour par la propriété `dashboard_pageid`. Les nouvelles pages de tableau de bord seront créées pour les objets sans propriété `dashboard_pageid` et les pages de tableau de bord existantes seront supprimées si elles ne sont pas réutilisées. Les pages du tableau de bord seront classées dans le même ordre que celui spécifié. Seules les propriétés spécifiées des pages du tableau de bord seront mises à jour. Au moins un objet de page de tableau de bord est requis dans la propriété `pages`.| |users|array|[Utilisateur](object#dashboard_user) de tableau de bord en remplacement de l'existant.| |userGroups|array|[Groupe d'utilisateurs](object#dashboard_user_group) de tableau de bord en remplacement de l'existant.| ### Parameters `(object/array)` Dashboards to create. Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**pages**<br>(required)|array|Dashboard [pages](object#dashboard_page) to be created for the dashboard. Dashboard pages will be ordered in the same order as specified. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to be created on the dashboard.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to be created on the dashboard.| ### Paramètres `(object/array)` Tableaux de bord à créer. Outre les propriétés [standards du tableau de bord](object#dashboard), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**pages**<br>(obligatoire)|array|[Pages](object#dashboard_page) à créer pour le tableau de bord. Les pages du tableau de bord seront classées dans le même ordre que celui spécifié. Au moins un objet de page de tableau de bord est requis pour la propriété `pages`.| |users|array|Partages [utilisateurs](object#dashboard_user) du tableau de bord à créer pour le tableau de bord.| |userGroups|array|Partages [groupes d'utilisateurs](object#dashboard_user_group) du tableau de bord à créer pour le tableau de bord.| ### Parameters `(object/array)` Discovery rule properties to be updated. The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.| ### Paramètres `(object/array)` Propriétés de la règle de découverte à mettre à jour. La propriété `druleid` doit être définie pour chaque règle de découverte, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de l'objet règle de découverte standard](object#discovery_rule), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |dchecks|array|[Tests](/manual/api/reference/dcheck/object) de découverte en remplacement des tests existants.| ### Parameters `(object/array)` Discovery rules to create. Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**dchecks**<br>(required)|array|Discovery [checks](/manual/api/reference/dcheck/object) to create for the discovery rule.| ### Paramètres `(object/array)` Règles de découverte à créer. En plus des [propriétés de l'objet règle de découverte standard](object#discovery_rule), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**dchecks**<br>(obligatoire)|array|[Tests](/manual/api/reference/dcheck/object) de découverte à créer pour la règle de découverte.| ### Parameters `(object/array)` [Global macro properties](object#global_macro) to be updated. The `globalmacroid` property must be defined for each global macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. ### Paramètres `(object/array)` [Propriétés des macros globales](/manual/api/reference/usermacro/object#global_macro)) à mettre à jour. La propriété `globalmacroid` doit être définie pour chaque macro globale. Toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. ### Parameters `(object/array)` Global macros to create. The method accepts global macros with the [standard global macro properties](object#global_macro). ### Paramètres `(object/array)` Macros globales à créer La méthode accepte les macros globales avec les [propriétés de macros globales standard](/manual/api/reference/usermacro/object#global_macro). ### Parameters `(object/array)` Graph properties to be updated. The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard graph properties](object#graph) the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.| ### Paramètres `(object/array)` Propriétés du graphique à mettre à jour. La propriété `graphid` doit être définie pour chaque graphique, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de l'objet graphique standard](object#graphique), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|[Éléments](/manual/api/reference/graphitem/object) de graphique en remplacement des éléments de graphique existants. Si un élément de graphique a la propriété `gitemid` définie, il sera mis à jour, sinon un nouvel élément de graphique sera créé.| ### Parameters `(object/array)` Graph prototype properties to be updated. The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.| ### Paramètres `(object/array)` Propriétés du prototype de graphique à mettre à jour. La propriété `graphid` doit être définie pour chaque prototype de graphique, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de l'objet prototype de graphique standard](object#graph_prototype), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|[Éléments](/manual/api/reference/graphitem/object) de graphique en remplacement des éléments de graphique existants. Si un élément de graphique a la propriété `gitemid` définie, il sera mis à jour, sinon un nouvel élément de graphique sera créé.| ### Parameters `(object/array)` Graph prototypes to create. Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph prototypes. Graph items can reference both items and item prototypes, but at least one item prototype must be present.| ### Paramètres `(object/array)` Prototypes de graphes à créer. En plus des [propriétés standard du prototype de graphe](object#graph_prototype), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**gitems**<br>(obligatoire)|tableau|Graphique [élément] (/manual/api/reference/graphitem/object) à créer pour les prototypes de graphe. Les éléments de graphique peuvent référencer à la fois des éléments et des prototypes d'élément, mais au moins un prototype d'élément doit être présent.| ### Parameters `(object/array)` Graphs to create. Additionally to the [standard graph properties](object#graph), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph.| ### Paramètres `(object/array)` Graphiques à créer. En plus des [propriétés de l'objet graphique standard](object#graph), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |----------|----|-----------| |**gitems**<br>(obligatoire)|array|[Éléments de graphique](/manual/api/reference/graphitem/object) à créer pour le graphique.| ### Parameters `(object/array)` [Host group properties](object#host_group) to be updated. The `groupid` property must be defined for each host group, all other properties are optional. Only the given properties will be updated, all others will remain unchanged. ### Paramètres `(object/array)` [Propriétés des groupes d'hôtes](object#host_group) à mettre à jour. La propriété `groupeid` doit être définie pour chaque groupe d'hôtes. Toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. ### Parameters `(object/array)` Host groups to create. The method accepts host groups with the [standard host group properties](object#host_group). ### Paramètres `(object/array)` Groupes d'hôtes à créer. La méthode accepte les groupes d'hôtes avec les [propriétés standard du groupe d'hôtes](object#host_group). ### Parameters `(object/array)` [Host interface properties](object#host_interface) to be updated. The `interfaceid` property must be defined for each host interface, all other properties are optional. Only the given properties will be updated, all others will remain unchanged. ### Paramètres `(object/array)` [Propriétés de l'interface hôte](/fr/manual/api/reference/hostinterface/object#host_interface) à mettre à jour. La propriété `interfaceid` doit être définie pour chaque interface hôte. Toutes les autres propriétés sont facultatives. Seules les propriétés données seront mises à jour, toutes les autres resteront inchangées. ### Parameters `(object/array)` Host interfaces to create. The method accepts host interfaces with the [standard host interface properties](object#host_interface). ### Paramètres `(object/array)` Interfaces hôtes à créer. La méthode accepte les interfaces hôtes ayant les [propriétés standard de l'objet interface hôte](/fr/manual/api/reference/hostinterface/object#interface_hote). ### Parameters `(object/array)` [Host macro properties](object#host_macro) to be updated. The `hostmacroid` property must be defined for each host macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. ### Paramètres `(object/array)` [Propriétés des macros d'hôte](/manual/api/reference/usermacro/object#host_macro) à mettre à jour. La propriété `hostmacroid` doit être définie pour chaque macro d'hôte. Toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. ### Parameters `(object/array)` Host macros to create. The method accepts host macros with the [standard host macro properties](object#host_macro). ### Paramètres `(object/array)` Macros hôtes à créer. La méthode accepte les macros hôtes avec des [propriétés standard de macro hôte](object#host_macro). ### Parameters `(object/array)` Host prototypes to create. Additionally to the [standard host prototype properties](object#host_prototype), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupLinks**<br>(required)|array|Group [links](/manual/api/reference/hostprototype/object#group_link) to be created for the host prototype.| |**ruleid**<br>(required)|string|ID of the LLD rule that the host prototype belongs to.| |groupPrototypes|array|Group [prototypes](/manual/api/reference/hostprototype/object#group_prototype) to be created for the host prototype.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to be created for the host prototype.| |tags|object/array|Host prototype [tags](/manual/api/reference/hostprototype/object#host_prototype_tag).| |interfaces|object/array|Host prototype [custom interfaces](/manual/api/reference/hostprototype/object#custom_interface).| |templates|object/array|[Templates](/manual/api/reference/template/object) to be linked to the host prototype.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object/array)` Prototypes d'hôte à créer. En plus des [propriétés de l'objet prototype d'hôte standard](object#host_prototype), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupLinks**<br>(obligatoire)|array|[Liens de groupe](/manual/api/reference/hostprototype/object#group_link) à créer pour le prototype d'hôte.| |**ruleid**<br>(obligatoire)|string|ID de la règle de découverte bas niveau à laquelle appartient le prototype d'hôte.| |groupPrototypes|array|[Prototypes de groupe(/manual/api/reference/hostprototype/object#group_prototype) devant être créés pour le prototype d'hôte.| |macros|object/array|[Macros utilisateurs](/manual/api/reference/usermacro/object) à créer pour le prototype d'hôte.| |tags|object/array|[Tags de prototype d'hôte](/manual/api/reference/hostprototype/object#host_prototype_tag).| |interfaces|object/array|[Interfaces personnalisée de prototype d'hôte](/manual/api/reference/hostprototype/object#custom_interface).| |templates|object/array|[Modèles](/manual/api/reference/template/object) à lier au prototype d'hôte.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object/array)` Hosts to create. Additionally to the [standard host properties](object#host), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(required)|object/array|Host [groups](/manual/api/reference/hostgroup/object) to add the host to.<br><br>The host groups must have the `groupid` property defined.| |interfaces|object/array|[Interfaces](/manual/api/reference/hostinterface/object) to be created for the host.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag).| |templates|object/array|[Templates](/manual/api/reference/template/object) to be linked to the host.<br><br>The templates must have the `templateid` property defined.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to be created for the host.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| ### Paramètres `(object/array)` Hôtes à créer. En plus des [propriétés standard de l'hôte](object#host), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(obligatoire)|object/array|[Groupes](/manual/api/reference/hostgroup/object) d'hôtes auquel ajouter l'hôte.<br><br>Les groupes d'hôtes doivent avoir la propriété `groupid` définie.| |interfaces|object/array|[Interfaces](/manual/api/reference/hostinterface/object) à créer pour l'hôte.| |tags|object/array|[Tags](/manual/api/reference/host/object#host_tag) d'hôte.| |templates|object/array|[Templates](/manual/api/reference/template/object) à lier à l'hôte.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |macros|object/array|[Macros utilisateur](/manual/api/reference/usermacro/object) à créer pour l'hôte.| |inventory|objet|Propriétés [inventaire](/manual/api/reference/host/object#host_inventory) de l'hôte.| ### Parameters `(object/array)` Icon map properties to be updated. The `iconmapid` property must be defined for each icon map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard icon map properties](object#icon_map), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |mappings|array|[Icon mappings](/manual/api/reference/iconmap/object#icon_mapping) to replace the existing icon mappings.| ### Paramètres `(object/array)`Correspondance d'icônes à mettre à jour. La propriété `iconmapid` doit être définie pour chaque correspondance d'icônes, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de correspondance d'icônes standard](object#icon_map), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |mappings|array|[Correspondances d'icônes](/manual/api/reference/iconmap/object#icon_mapping) en remplacement des correspondance d'icônes existantes.| ### Parameters `(object/array)` Icon maps to create. Additionally to the [standard icon map properties](object#icon_map), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**mappings**<br>(required)|array|[Icon mappings](/manual/api/reference/iconmap/object#icon_mapping) to be created for the icon map.| ### Paramètres `(object/array)` Table de correspondance des icônes à créer. En plus des [propriétés de table de correspondance des icônes standard](object#icon_map), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**mappings**<br>(obligatoire)|array|[Correspondaces d'icônes](/manual/api/reference/iconmap/object#icon_mapping) à créer pour la table de correspondance des icônes.| ### Parameters `(object/array)` Image properties to be updated. The `imageid` property must be defined for each image, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard image properties](object#image), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |image|string|Base64 encoded image. The maximum size of the encoded image is 1 MB. Maximum size can be adjusted by changing ZBX\_MAX\_IMAGE\_SIZE constant value.<br>Supported image formats are: PNG, JPEG, GIF.| ### Paramètres `(object/array)` Propriétés d'image à mettre à jour. La propriété `imageid` doit être définie pour chaque image, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés d'image standard](object#image), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |image|string|Image encodée en Base64. La taille maximale de l'image encodée est de 1 Mo. La taille maximale peut être ajustée en modifiant la valeur constante ZBX\_MAX\_IMAGE\_SIZE.<br>Les formats d'image pris en charge sont : PNG, JPEG, GIF.| ### Parameters `(object/array)` Images to create. Additionally to the [standard image properties](object#image), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Name of the image.| |**imagetype**<br>(required)|integer|Type of image.<br><br>Possible values:<br>1 - *(default)* icon;<br>2 - background image.| |**image**<br>(required)|string|Base64 encoded image. The maximum size of the encoded image is 1 MB. Maximum size can be adjusted by changing ZBX\_MAX\_IMAGE\_SIZE constant value.<br>Supported image formats are: PNG, JPEG, GIF.| ### Paramètres `(object/array)` Images à créer. En plus des [propriétés d'image standard](object#image), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(obligatoire)|string|Nom de l'image.| |**imagetype**<br>(obligatoire)|integer|Type d'image.<br><br>Valeurs possibles :<br>1 - *(par défaut)* icône;<br>2 - image d'arrière plan.| |**image**<br>(obligatoire)|string|Image encodée en Base64. La taille maximale de l'image encodée est de 1 Mo. La taille maximale peut être ajustée en modifiant la valeur constante ZBX\_MAX\_IMAGE\_SIZE.<br>Les formats d'image pris en charge sont : PNG, JPEG, GIF.| ### Parameters `(object/array)` Item properties to be updated. The `itemid` property must be defined for each item, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard item properties](object#item), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|[Item preprocessing](/manual/api/reference/item/object#item_preprocessing) options to replace the current preprocessing options.| |tags|array|Item [tags.](/manual/api/reference/item/object#item_tag)| ### Paramètres `(object/array)` Propriétés de l'élément à mettre à jour. La propriété `itemid` doit être définie pour chaque élément, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés d'élément standard](object#item), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Options de [prétraitement de l'élément](/manual/api/reference/item/object#item_preprocessing) à remplacer dans les options de prétraitement actuelles.| |tags|array|[Tags](/manual/api/reference/item/object#item_tag) de l'élément.| ### Parameters `(object/array)` Item prototype properties to be updated. The `itemid` property must be defined for each item prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard item prototype properties](object#item_prototype), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Item prototype [preprocessing](/manual/api/reference/itemprototype/object#item_prototype_preprocessing) options to replace the current preprocessing options.| |tags|array|Item prototype [tags](/manual/api/reference/itemprototype/object#item_prototype_tag).| ### Paramètres `(object/array)` Propriétés du prototype d'élément à mettre à jour. La propriété `itemid` doit être définie pour chaque prototype d'élément, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de prototype d'élément standard](object#item_prototype), la méthode accepte les éléments suivantsparameters. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Options de [prétraitement](/manual/api/reference/itemprototype/object#item_prototype_preprocessing) du prototype d'élément pour remplacer les options de prétraitement actuelles.| |tags|array|[Tags](/manual/api/reference/itemprototype/object#item_prototype_tag) de prototype d'élément.| ### Parameters `(object/array)` Item prototype to create. Additionally to the [standard item prototype properties](object#item_prototype), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**ruleid**<br>(required)|string|ID of the LLD rule that the item belongs to.| |preprocessing|array|Item prototype [preprocessing](/manual/api/reference/itemprototype/object#item_prototype_preprocessing) options.| |tags|array|Item prototype [tags](/manual/api/reference/itemprototype/object#item_prototype_tag).| ### Paramètres `(object/array)` Prototype d'élément à créer. En plus des [propriétés de prototype d'élément standard](object#item_prototype), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**ruleid**<br>(obligatoire)|string|ID de la règle LLD à laquelle appartient l'élément.| |preprocessing|array|Options de [prétraitement](/manual/api/reference/itemprototype/object#item_prototype_preprocessing) du prototype d'élément.| |tags|array|[Tags](/manual/api/reference/itemprototype/object#item_prototype_tag) du prototype d'élément.| ### Parameters `(object/array)` Items to create. Additionally to the [standard item properties](object#host), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Item [preprocessing](/manual/api/reference/item/object#item_preprocessing) options.| |tags|array|Item [tags.](/manual/api/reference/item/object#item_tag)| ### Paramètres `(object/array)` Eléments à créer. En plus des [propriétés d'élément standard](object#host), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Options de [prétraitement](/manual/api/reference/item/object#item_preprocessing) d'élément.| |tags|array|[Tags](/manual/api/reference/item/object#item_tag) d'élément.| ### Parameters `(object/array)` Maintenance properties to be updated. The `maintenanceid` property must be defined for each maintenance, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard maintenance properties](object#maintenance), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object) to replace the current groups.<br><br>The host groups must have the `groupid` property defined.| |hosts|object/array|[Hosts](/manual/api/reference/host/object) to replace the current hosts.<br><br>The hosts must have the `hostid` property defined.| |timeperiods|object/array|Maintenance [time periods](/manual/api/reference/maintenance/object#time_period) to replace the current periods.| |tags|object/array|[Problem tags](/manual/api/reference/maintenance/object#problem_tag) to replace the current tags.| |groupids<br>(deprecated)|array|This parameter is deprecated, please use `groups` instead.<br>IDs of the host groups that will undergo maintenance.| |hostids<br>(deprecated)|array|This parameter is deprecated, please use `hosts` instead.<br>IDs of the hosts that will undergo maintenance.| ::: noteimportant At least one host or host group must be defined for each maintenance. ::: ### Paramètres `(object/array)` Propriétés de maintenance à mettre à jour. La propriété `maintenanceid` doit être définie pour chaque maintenance, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de maintenance standard](object#maintenance), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#types-de-données)|Description| |--|--|------| |groups|object/array|[Groupes d'hôtes](/manual/api/reference/hostgroup/object) en remplacement des groupes actuels.<br><br>Les groupes d'hôtes doivent avoir la propriété `groupid` définie.| |hosts|object/array|[Hôtes](/manual/api/reference/host/object) en remplacement de hôtes actuels.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |timeperiods|object/array|[Périodes](/manual/api/reference/maintenance/object#période-de-temps) de maintenance en remplacement des périodes actuelles.| |tags|object/array|[Tags de problème](/manual/api/reference/maintenance/object#tag-de-problème) en remplacement des tags actuels.| |groupids<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser des `groups` à la place. <br> ID des groupes d'hôte qui subiront la maintenance.| |hostids<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser des `hosts` à la place.<br>IDs des hôtes qui subiront la maintenance.| ::: noteimportant Au moins un hôte ou groupe d'hôtes doit être défini pour chaque maintenance. ::: ### Parameters `(object/array)` Maintenances to create. Additionally to the [standard maintenance properties](object#maintenance), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object) that will undergo maintenance.<br><br>The host groups must have the `groupid` property defined.<br><br>At least one object of `groups` or `hosts` must be specified.| |hosts|object/array|[Hosts](/manual/api/reference/host/object) that will undergo maintenance.<br><br>The hosts must have the `hostid` property defined.<br><br>At least one object of `groups` or `hosts` must be specified.| |**timeperiods**<br>(required)|object/array|Maintenance [time periods](/manual/api/reference/maintenance/object#time_period).| |tags|object/array|[Problem tags](/manual/api/reference/maintenance/object#problem_tag).<br><br>Define what problems must be suppressed.<br>If no tags are given, all active maintenance host problems will be suppressed.| |groupids<br>(deprecated)|array|This parameter is deprecated, please use `groups` instead.<br>IDs of the host groups that will undergo maintenance.| |hostids<br>(deprecated)|array|This parameter is deprecated, please use `hosts` instead.<br>IDs of the hosts that will undergo maintenance.| ### Paramètres `(object/array)` Maintenances à créer. En plus des [propriétés de l'objet maintenance standard](object#maintenance), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#types-de-données)|Description| |--|--|------| |groups|object/array|[Groupes d'hôtes](/manual/api/reference/hostgroup/object) qui vont subir une maintenance.<br><br>Les groupes d'hôtes doivent avoir la propriété `groupid` définie.<br><br>Au moins un objet `groups` ou `hosts` doit être spécifié.| |hosts|object/array|[Hôtes](/manual/api/reference/host/object) qui vont subir une maintenance.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.<br><br>Au moins un objet `groups` ou `hosts` doit être spécifié.| |**timeperiods**<br>(obligatoire)|object/array|[Périodes de maintenance](/manual/api/reference/maintenance/object#période-de-temps).| |tags|object/array|[Tags de problème](/manual/api/reference/maintenance/object#tag-de-problème).<br><br>Défini quels problèmes doivent être supprimés.<br>Si aucun tag n’est spécifié, tous les problèmes d’hôte en maintenance actives seront supprimés.| |groupids<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser des `groups` à la place. <br> ID des groupes d'hôte qui subiront la maintenance.| |hostids<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser des `hosts` à la place.<br>IDs des hôtes qui subiront la maintenance.| ### Parameters `(object/array)` Map properties to be updated. The `mapid` property must be defined for each map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard map properties](object#map), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|Map [links](/manual/api/reference/map/object#map_link) to replace the existing links.| |selements|array|Map [elements](/manual/api/reference/map/object#map_element) to replace the existing elements.| |urls|array|Map [URLs](/manual/api/reference/map/object#map_url) to replace the existing URLs.| |users|array|Map [user](/manual/api/reference/map/object#map_user) shares to replace the existing elements.| |userGroups|array|Map [user group](/manual/api/reference/map/object#map_user_group) shares to replace the existing elements.| |shapes|array|Map [shapes](/manual/api/reference/map/object#map_shapes) to replace the existing shapes.| |lines|array|Map [lines](/manual/api/reference/map/object#map_lines) to replace the existing lines.| ::: notetip To create map links between new map elements you'll need to set an element's `selementid` to an arbitrary value and then use this value to reference this element in the links `selementid1` or `selementid2` properties. When the element is created, this value will be replaced with the correct ID generated by Zabbix. [See example for map.create.](create#create_a_host_map) ::: ### Paramètres `(object/array)` Propriétés de carte à mettre à jour. La propriété `mapid` doit être définie pour chaque carte, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de l'objet carte standard](object#map), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|[Liens de carte](/manual/api/reference/map/object#map_link) en remplacement des liens existants.| |selements|array|[Eléments de carte](/manual/api/reference/map/object#map_element) en remplacement des éléments existants.| |urls|array|[URLs de carte](/manual/api/reference/map/object#map_url) en remplacement des URLs existantes.| |users|array|Partages [utilisateurs](/manual/api/reference/map/object#map_user) en remplacement des partages existants.| |userGroups|array|Partages [groupes utilisateurs](/manual/api/reference/map/object#map_user_group) en remplacement des partages existants.| |shapes|array|[Formes](/manual/api/reference/map/object#map_shapes) de carte en remplacement des formes existantes.| |lines|array|[Lignes](/manual/api/reference/map/object#map_lines) de carte en remplacement des lignes existants.| ::: notetip Pour créer des liens de carte, il est nécessaire dedéfinir un élément de carte `selementid` sur une valeur arbitraire, puis d'utiliser cette valeur pour référencer cet élément dans les propriétés des liens `selementid1` ou `selementid2`. Lors de la création de l'élément, cette valeur sera remplacée par l'ID correct généré par Zabbix. [Voir l'exemple](create#create_a_host_map). ::: ### Parameters `(object/array)` Maps to create. Additionally to the [standard map properties](object#map), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|Map [links](/manual/api/reference/map/object#map_link) to be created on the map.| |selements|array|Map [elements](/manual/api/reference/map/object#map_element) to be created on the map.| |urls|array|Map [URLs](/manual/api/reference/map/object#map_url) to be created on the map.| |users|array|Map [user](/manual/api/reference/map/object#map_user) shares to be created on the map.| |userGroups|array|Map [user group](/manual/api/reference/map/object#map_user_group) shares to be created on the map.| |shapes|array|Map [shapes](/manual/api/reference/map/object#map_shapes) to be created on the map.| |lines|array|Map [lines](/manual/api/reference/map/object#map_lines) to be created on the map.| ::: notetip To create map links you'll need to set a map element `selementid` to an arbitrary value and then use this value to reference this element in the links `selementid1` or `selementid2` properties. When the element is created, this value will be replaced with the correct ID generated by Zabbix. [See example.](create#create_a_host_map) ::: ### Paramètres `(object/array)` Cartes à créer. En plus des [propriétés de l'objet carte standard](object#map), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|[Liens de carte](/manual/api/reference/map/object#map_link) à créer sur la carte.| |selements|array|[Éléments de carte](/manual/api/reference/map/object#map_element) à créer sur la carte.| |urls|array|[URLs de carte](/manual/api/reference/map/object#map_url) à créer sur la carte.| |users|array|[Partages d'utilisateur](/manual/api/reference/map/object#map_user) de carte à créer sur la carte.| |userGroups|array|[Partages de groupe d'utilisateurs](/manual/api/reference/map/object#map_user_group) de carte à créer sur la carte.| |shapes|array|[Formes de carte](/manual/api/reference/map/object#map_shapes) à créer sur la carte.| |lines|array|[Lignes de carte](/manual/api/reference/map/object#map_lines) à créer sur la carte.| ::: notetip Pour créer des liens de carte, il est nécessaire de définir un élément de carte `selementid` sur une valeur arbitraire, puis d'utiliser cette valeur pour référencer cet élément dans les propriétés des liens `selementid1` ou `selementid2`. Lors de la création de l'élément, cette valeur sera remplacée par l'ID correct généré par Zabbix. [Voir l'exemple](create#create_a_host_map). ::: ### Parameters `(object/array)` Media type properties to be updated. The `mediatypeid` property must be defined for each media type, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard media type properties](object#media_type), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |parameters|array|[Webhook parameters](object#webhook_parameters) to replace the current webhook parameters.| |message\_templates|array|[Message templates](object#message_template) to replace the current message templates.| ### Paramètres `(object/array)` Propriétés du type de média à mettre à jour. La propriété `mediatypeid` doit être définie pour chaque type de média, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de type de média standard](object#media_type), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |parameters|array|[Paramètres Webhook](object#webhook_parameters) en remplacement de paramètres Webhook actuels.| |message\_templates|array|[Modèles de message](object#message_template) en remplacement des modèles de message actuels.| ### Parameters `(object/array)` Media types to create. Additionally to the [standard media type properties](object#media_type), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |parameters|array|[Webhook parameters](object#webhook_parameters) to be created for the media type.| |message\_templates|array|[Message templates](object#message_template) to be created for the media type.| ### Paramètres `(object/array)` Types de media à créer. En plus des [propriétés de type de média standard](object#media_type), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |parameters|array|[Paramètres Webhook](object#webhook_parameters) à créer pour le type de media.| |message\_templates|array|[Modèle de message](object#message_template) à créer pour le type de media.| ### Parameters `(object/array)` Proxies to create. Additionally to the [standard proxy properties](object#proxy), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hosts|array|[Hosts](/manual/api/reference/host/object) to be monitored by the proxy. If a host is already monitored by a different proxy, it will be reassigned to the current proxy.<br><br>The hosts must have the `hostid` property defined.| |interface|object|Host [interface](/manual/api/reference/hostinterface/object) to be created for the passive proxy.<br><br>Required for passive proxies.| ### Paramètres `(object/array)` Proxys à créer. En plus des [propriétés standard du proxy](object#proxy), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hosts|array|[Hôtes](/manual/api/reference/host/object) à surveiller par le proxy. Si un hôte est déjà surveillé par un proxy différent, il sera réaffecté au proxy actuel.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |interface|object|[Interface](/manual/api/reference/hostinterface/object) d'hôte à créer pour le proxy passif.<br><br>Obligatoire pour les proxys passifs.| ### Parameters `(object/array)` Proxy properties to be updated. The `proxyid` property must be defined for each proxy, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard proxy properties](object#proxy), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hosts|array|[Hosts](/manual/api/reference/host/object) to be monitored by the proxy. If a host is already monitored by a different proxy, it will be reassigned to the current proxy.<br><br>The hosts must have the `hostid` property defined.| |interface|object|Host [interface](/manual/api/reference/hostinterface/object) to replace the existing interface for the passive proxy.| ### Paramètres `(object/array)` Propriétés du proxy à mettre à jour. La propriété `proxyid` doit être définie pour chaque proxy, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés standard du proxy](object#proxy), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hosts|array|[Hôtes](/manual/api/reference/host/object) devant être surveillé par le proxy. Si un hôte est déjà surveillé par un proxy différent, il sera réaffecté au proxy actuel.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |interface|object|[Interface d'hôte](/manual/api/reference/hostinterface/object) en remplacement de l'interface existante pour le proxy passif.| ### Parameters `(object/array)` Roles to create. Additionally to the [standard role properties](object#role), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rules|array|Role [rules](object#role_rules) to be created for the role.| ### Paramètres `(object/array)` Rôles à créer. En plus des [propriétés de rôle standard](object#role), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rules|array|[Règles](object#role_rules) de rôle à créer pour le rôle.| ### Parameters `(object/array)` [Script properties](object#script) to be updated. The `scriptid` property must be defined for each script, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. An exception is `type` property change from 5 (Webhook) to other: the `parameters` property will be cleaned. ### Paramètres `(object/array)` [Propriétés du script](object#script) à mettre à jour. La propriété `scriptid` doit être définie pour chaque script, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. Une exception est le changement de la propriété `type` de 5 (Webhook) à other : la propriété `parameters` sera nettoyée. ### Parameters `(object/array)` Scripts to create. The method accepts scripts with the [standard script properties](/manual/api/reference/script/object#script). ### Paramètres `(object/array)` Scripts à créer. La méthode accepte les scripts avec les [propriétés de script standard](/manual/api/reference/script/object#script). ### Parameters `(object/array)` service properties to be updated. The `serviceid` property must be defined for each service, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard service properties](object#service), the method accepts the following parameters. | Parameter | [Type](/manual/api/reference_commentary#data_types) | Description | |---------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | children | array | Child services to replace the current service children.<br><br>The children must have the `serviceid` property defined. | | parents | array | Parent services to replace the current service parents.<br><br>The parents must have the `serviceid` property defined. | | tags | array | Service [tags](/manual/api/reference/service/object#service_tag) to replace the current service tags. | | problem\_tags | array | [Problem tags](/manual/api/reference/service/object#problem_tag) to replace the current problem tags. | | status\_rules | array | [Status rules](/manual/api/reference/service/object#status_rule) to replace the current status rules. | ### Paramètres Les propriétés du service `(object/array)` doivent être mises à jour. La propriété `serviceid` doit être définie pour chaque service, toutes les autres les propriétés sont facultatives. Seules les propriétés passées seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de service standard](object#service), la méthode accepte les paramètres suivants. | Paramètre | [Type](/manual/api/reference_commentary#data_types) | Descriptif | |---------------|--------------------------------------------- --------------------|-------------------------------------- -------------------------------------------------- ------------------------------------------| | enfants | array | Services enfants pour remplacer les enfants de service actuels.<br><br>Les enfants doivent avoir la propriété `serviceid` définie. | | parents | array | Services parents pour remplacer les services parents actuels.<br><br>Les parents doivent avoir la propriété `serviceid` définie. | | balises | array | [Tags de service](/manual/api/reference/service/object#service_tag) en rempalcement des tags de service actuels. | | problème\_tags | array | [Tags de problème](/manual/api/reference/service/object#problem_tag) en remplacement des tags de problème actuelles. | | statut\_règles | array | [Règles de statut](/manual/api/reference/service/object#status_rule) en remplacement des règles de statut actuelles. | ### Parameters `(object/array)` services to create. Additionally to the [standard service properties](object#service), the method accepts the following parameters. | Parameter | [Type](/manual/api/reference_commentary#data_types) | Description | |---------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | children | array | Child services to be linked to the service.<br><br>The children must have the `serviceid` property defined. | | parents | array | Parent services to be linked to the service.<br><br>The parents must have the `serviceid` property defined. | | tags | array | Service [tags](/manual/api/reference/service/object#service_tag) to be created for the service. | | problem\_tags | array | [Problem tags](/manual/api/reference/service/object#problem_tag) to be created for the service. | | status\_rules | array | [Status rules](/manual/api/reference/service/object#status_rule) to be created for the service. | ### Paramètres `(objet/tableau)` services à créer. En plus des [propriétés de service standard](object#service), la méthode accepte les paramètres suivants. | Paramètre | [Type](/manual/api/reference_commentary#data_types) | Descriptif | |---------------|--------------------------------------------- --------------------|-------------------------------------- -------------------------------------------------- ------------------------------| | enfants | array | Services enfants à lier au service.<br><br>Les enfants doivent avoir la propriété `serviceid` définie. | | parents | array | Services parents à lier au service.<br><br>La propriété `serviceid` doit être définie pour les parents. | | balises | array | [Tags de service](/manual/api/reference/service/object#service_tag) à créer pour le service. | | problème\_tags | tableau | [Tags de problème](/manual/api/reference/service/object#problem_tag) à créer pour le service. | | statut\_règles | array | [Règles de statut](/manual/api/reference/service/object#status_rule) à créer pour le service. | ### Parameters `(object/array)` SLA objects to create. Additionally to the [standard SLA properties](object#sla), the method accepts the following parameters. | Parameter | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| | **service_tags**<br>(required) | array | SLA service tags to be created for the SLA.<br>At least one service tag must be specified. | | schedule | array | SLA schedule to be created for the SLA.<br>Specifying an empty parameter will be interpreted as a 24x7 schedule.<br>Default: 24x7 schedule. | | excluded_downtimes | array | SLA excluded downtimes to be created for the SLA. | ### Paramètres `(object/array)` Objets SLA à créer. En plus des [propriétés SLA standard](object#sla), la méthode accepte les paramètres suivants. | Paramètre | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| | **service_tags**<br>(obligatoire) | array | Tags de service SLA à créer pour le SLA.<br>Au moins un tag de service doit être spécifié. | | schedule | array | Planification SLA à créer pour le SLA.<br>La spécification d'un paramètre vide sera interprétée comme une planification 24x7.<br>Par défaut : planification24x7. | | excluded_downtimes | array | Temps d'arrêt exclus du SLA à créer pour le SLA. | ### Parameters `(object/array)` SLA properties to be updated. The `slaid` property must be defined for each SLA, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard SLA properties](object#sla), the method accepts the following parameters. | Parameter | [Type](/manual/api/reference_commentary#data_types) | Description | |---------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | service\_tags | array | SLA [service tags](/manual/api/reference/sla/object#sla-service-tag) to replace the current SLA service tags.<br><br>At least one service tag must be specified. | | schedule | array | SLA [schedule](/manual/api/reference/sla/object#sla-schedule) to replace the current one.<br><br>Specifying parameter as empty will be interpreted as a 24x7 schedule. | | excluded\_downtimes | array | SLA [excluded downtimes](/manual/api/reference/sla/object#sla-excluded-downtime) to replace the current ones. | ### Paramètres `(object/array)` Propriétés SLA à mettre à jour. La propriété `slaid` doit être définie pour chaque SLA, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés SLA standard](object#sla), la méthode accepte les paramètres suivants. | Paramètre | [Type](/manual/api/reference_commentary#data_types) | Description | |---------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | service\_tags | array | [Tags de service](/manual/api/reference/sla/object#sla-service-tag) de SLA en remplacement des tags actuels.<br><br>Au moins untag de service doit être spécifié. | | schedule | array | [Planification](/manual/api/reference/sla/object#sla-schedule) de SLA en remplacement de la planification actuelle.<br><br>La spécification d'un paramètre vide sera interprétée comme une planification 24h/24 et 7j/7.| | excluded\_downtimes | array | [Temps d'arrêt exclus](/manual/api/reference/sla/object#sla-excluded-downtime) du SLA en remplacement de l'actuel. | ### Parameters `(object/array)` Template dashboard properties to be updated. The `dashboardid` property must be specified for each dashboard, all other properties are optional. Only the specified properties will be updated. Additionally to the [standard template dashboard properties](object#template_dashboard), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |pages|array|Template dashboard [pages](object#template_dashboard_page) to replace the existing dashboard pages.<br><br>Dashboard pages are updated by the `dashboard_pageid` property. New dashboard pages will be created for objects without `dashboard_pageid` property and the existing dashboard pages will be deleted if not reused. Dashboard pages will be ordered in the same order as specified. Only the specified properties of the dashboard pages will be updated. At least one dashboard page object is required for `pages` property.| ### Paramètres `(object/array)` Propriétés du tableau de bord du modèle à mettre à jour. La propriété `dashboardid` doit être spécifiée pour chaque tableau de bord, toutes les autres propriétés sont facultatives. Seules les propriétés spécifiées seront actualisées. En plus des [propriétés standard tableau de bord du modèle](object#template_dashboard), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |pages|array|[Pages du tableau de bord du modèle](object#template_dashboard_page) en remplacement des pages de tableau de bord existantes.<br><br>Les pages de tableau de bord sont mises à jour par la propriété `dashboard_pageid`. De nouvelles pages de tableau de bord seront créées pour les objets sans propriété `dashboard_pageid` et les pages de tableau de bord existantes seront supprimées si elles ne sont pas réutilisées. Les pages du tableau de bord seront classées dans le même ordre que celui spécifié. Seules les propriétés spécifiées des pages du tableau de bord seront mises à jour. Au moins un objet de page de tableau de bord est requis pour la propriété `pages`.| ### Parameters `(object/array)` Template dashboards to create. Additionally to the [standard template dashboard properties](object#template_dashboard), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**pages**<br>(required)|array|Template dashboard [pages](object#dashboard_page) to be created for the dashboard. Dashboard pages will be ordered in the same order as specified. At least one dashboard page object is required for `pages` property.| ### Paramètres `(object/array)` Modèles de tableaux de bord à créer. En plus des [propriétés standard du tableau de bord du modèle](object#template_dashboard), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**pages**<br>(obligatoire)|array|[Pages](object#dashboard_page) de tableau de bord à créer.Les pages du tableau de bord seront classées dans le même ordre que celui spécifié. Au moins un objet de page de tableau de bord est requis pour la propriété `pages`.| ### Parameters `(object/array)` Template properties to be updated. The `templateid` property must be defined for each template, all other properties are optional. Only the given properties will be updated, all others will remain unchanged. Additionally to the [standard template properties](object#template), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object) to replace the current host groups the templates belong to.<br><br>The host groups must have the `groupid` property defined.| |tags|object/array|Template [tags](/manual/api/reference/template/object#template_tag) to replace the current template tags.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros on the given templates.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. Templates that are not passed are only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the given templates.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object/array)` Propriétés du modèle à mettre à jour. La propriété `templateid` doit être définie pour chaque modèle, toutes les autres propriétés sont facultatives. Seules les propriétés données seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de l'objet modèle standard](object#modele), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|[Groupes d'hôtes](/manual/api/reference/hostgroup/object) en remplacement des groupes d'hôtes actuels auxquels appartiennent les modèles.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |tags|object/array|[Tags de modèle](/manual/api/reference/template/object#template_tag) en remplacement de ceux existants.| |macros|object/array|[Macros utilisateur](/manual/api/reference/usermacro/object) en remplacement des macros utilisateur actuelles sur les modèles donnés.| |templates|object/array|[Modèles](/manual/api/reference/template/object) en remplacement des modèles actuellement liés. Les modèles qui ne sont pas transmis sont uniquement déliés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |templates\_clear|object/array|[Modèles(/manual/api/reference/template/object) à délier et à effacer des modèles donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object/array)` Templates to create. Additionally to the [standard template properties](object#template), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(required)|object/array|Host [groups](/manual/api/reference/hostgroup/object) to add the template to.<br><br>The host groups must have the `groupid` property defined.| |tags|object/array|Template [tags](/manual/api/reference/template/object#template_tag).| |templates|object/array|[Templates](/manual/api/reference/template/object) to be linked to the template.<br><br>The templates must have the `templateid` property defined.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to be created for the template.| ### Paramètres `(object/array)` Modèles à créer. En plus des [propriétés de l'objet modèle standard](object#template), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(obligatoire)|object/array|[Groupes d'hôtes](/manual/api/reference/hostgroup/object) auxquels ajouter le modèle.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |tags|object/array|[Tags de modèle](/manual/api/reference/template/object#template_tag).| |templates|object/array|[Modèles](/manual/api/reference/template/object) à associer au modèle.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |macros|object/array|[Macros utilisateur](/manual/api/reference/usermacro/object) à créer pour le modèle.| ### Parameters `(object/array)` Token properties to be updated. The `tokenid` property must be defined for each token, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. The method accepts tokens with the [standard token properties](object). ### Paramètres `(object/array)` Propriétés du jeton à mettre à jour. La propriété `tokenid` doit être définie pour chaque jeton, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. La méthode accepte les jetons avec les [propriétés de jeton standard](object). ### Parameters `(object/array)` Tokens to create. The method accepts tokens with the [standard token properties](object). ### Paramètres `(object/array)` Jetons à créer. La méthode accepte les jetons avec les [propriétés de jeton standard](objet). ### Parameters `(object/array)` Trigger dependencies to create. Each trigger dependency has the following parameters: |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**triggerid**<br>(required)|string|ID of the dependent trigger.| |**dependsOnTriggerid**<br>(required)|string|ID of the trigger that the trigger depends on.| ### Paramètres `(object/array)` Dépendances de déclencheur à créer. Chaque dépendance de déclencheur à les paramètres suivants : |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**triggerid**<br>(obligatoire)|string|ID du déclencheur dépendant.| |**dependsOnTriggerid**<br>(required)|string|ID du déclencheur dont dépend le déclencheur.| ### Parameters `(object/array)` Trigger properties to be updated. The `triggerid` property must be defined for each trigger, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard trigger properties](object#trigger) the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers that the trigger is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger [tags.](/manual/api/reference/trigger/object#trigger_tag)| ::: noteimportant The trigger expression has to be given in its expanded form. ::: ### Paramètres `(object/array)` Propriétés du déclencheur à mettre à jour. La propriété `triggerid` doit être définie pour chaque déclencheur, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés standard du déclencheur](object#trigger), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Déclencheurs dont le déclencheur dépend.<br><br>Les déclencheurs doivent avoir la propriété `triggerid` définie.| |tags|array|[Tags.](/manual/api/reference/trigger/object#trigger_tag) de déclencheur.| ::: noteimportant L'expression du déclencheur doit être donnée sous sa forme développée. ::: ### Parameters `(object/array)` [Trigger prototype properties](object#trigger_prototype) to be updated. The `triggerid` property must be defined for each trigger prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard trigger prototype properties](object#trigger_prototype) the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers and trigger prototypes that the trigger prototype is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger prototype [tags](/manual/api/reference/triggerprototype/object#trigger_prototype_tag).| ::: noteimportant The trigger expression has to be given in its expanded form and must contain at least one item prototype. ::: ### Paramètres `(object/array)` [Propriétés de prototype de déclencheur](object#trigger_prototype) à mettre à jour. La propriété `triggerid` doit être définie pour chaque prototype de déclencheur, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de prototype de déclencheur](object#trigger_prototype) standard, la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Déclencheurs et prototypes de déclencheurs dont dépend le prototype de déclencheur.<br><br>La propriété `triggerid` doit être définie pour les déclencheurs.| |tags|array|[Tags du prototype de déclencheur](/manual/api/reference/triggerprototype/object#trigger_prototype_tag).| ::: noteimportant L'expression de déclenchement doit être donnée dans sa forme développée et doit contenir au moins un prototype d'élément. ::: ### Parameters `(object/array)` Trigger prototypes to create. Additionally to the [standard trigger prototype properties](object#trigger_prototype) the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers and trigger prototypes that the trigger prototype is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger prototype [tags](/manual/api/reference/triggerprototype/object#trigger_prototype_tag).| ::: noteimportant The trigger expression has to be given in its expanded form and must contain at least one item prototype. ::: ### Paramètres `(object/array)` Prototypes de déclencheur à créer. En plus des [propriétés standard du prototype de déclencheur](object#trigger_prototype), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Déclencheurs et prototypes de déclencheurs dont dépend le prototype de déclencheur.<br><br>Les déclencheurs doivent avoir la propriété `triggerid` définie.| |tags|array|[Tags](/manual/api/reference/triggerprototype/object#trigger_prototype_tag) de prototype de déclencheur.| ::: noteimportant L'expression du déclencheur doit être donnée sous sa forme développée et doit contenir au moins un prototype d'élément. ::: ### Parameters `(object/array)` Triggers to create. Additionally to the [standard trigger properties](object#trigger) the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers that the trigger is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger [tags.](/manual/api/reference/trigger/object#trigger_tag)| ::: noteimportant The trigger expression has to be given in its expanded form. ::: ### Paramètres `(object/array)` Déclencheurs à créer. En plus des [propriétés standard du déclencheur](object#trigger), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Déclencheurs dont le déclencheur dépend.<br><br>Les déclencheurs doivent avoir la propriété `triggerid` définie.| |tags|array|[Tags](/manual/api/reference/trigger/object#trigger_tag) de déclencheur.| ::: noteimportant L'expression du déclencheur doit être donnée sous sa forme développée. ::: ### Parameters `(object/array)` User groups to create. Additionally to the [standard user group properties](object#user_group), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rights|object/array|[Permissions](/manual/api/reference/usergroup/object#permission) to assign to the group| |tag\_filters|array|[Tag based permissions](/manual/api/reference/usergroup/object#tag_based_permission) to assign to the group| |users|object/array|[Users](/manual/api/reference/user/create) to add to the user group.<br><br>The user must have the `userid` property defined.| ### Paramètres `(object/array)` Groupes d'utilisateurs à créer. En plus des [propriétés standard du groupe d'utilisateurs](object#user_group), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rights|object/array|[Autorisations ](/manual/api/reference/usergroup/object#permission) à assigner au groupe.| |tag\_filters|array|[Autorisations basées sur les balises](/manual/api/reference/usergroup/object#tag_based_permission) à assigner au groupe.| |users|object/array|[Utilisateurs](/manual/api/reference/user/create) à ajouter au groupe d'hôtes.<br><br>L'utilisateur doit avoir la propriété `userid` définie.| ### Parameters `(object/array)` User properties to be updated. The `userid` property must be defined for each user, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard user properties](object#user), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |passwd|string|User's password.<br><br>Can be empty string if user belongs to or is moved only to groups that have LDAP access.| |usrgrps|array|User [groups](/manual/api/reference/user/create) to replace existing user groups.<br><br>The user groups must have the `usrgrpid` property defined.| |medias|array|[User media](/manual/api/reference/user/object#media) to replace existing media.| |user_medias<br>(deprecated)|array|This parameter is deprecated, please use `medias` instead.<br>User [media](/manual/api/reference/user/object#media) to replace existing media.| ### Paramètres `(object/array)` Propriétés de l'utilisateur à mettre à jour. La propriété `userid` doit être définie pour chaque utilisateur, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés utilisateur standard](object#user), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#types-de-données)|Description| |--|--|------| |passwd|string|Mot de passe de l'utilisateur.<br><br>Peut être une chaîne vide si l'utilisateur appartient ou est déplacé uniquement vers des groupes disposant d'un accès LDAP.| |usrgrps|array|[Groupes d'utilisateurs](/manual/api/reference/user/create) en remplacement des groupes existants.<br><br>Les groupes d'utilisateurs doivent avoir la propriété `usrgrpid` définie.| |medias|array|[Medias utilisateur](/manual/api/reference/user/object#média) des médias existants.| |user_medias<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser `medias` à la place.<br>[Media](/manual/api/reference/user/object#média) utilisateur pour remplacer le média existant.| ### Parameters `(object/array)` Users to create. Additionally to the [standard user properties](object#user), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**passwd**<br>*(required)*|string|User's password.<br><br>Can be omitted if user is added only to groups that have LDAP access.| |**usrgrps**<br>(required)|array|User [groups](/manual/api/reference/user/create) to add the user to.<br><br>The user groups must have the `usrgrpid` property defined.| |medias|array|User [media](/manual/api/reference/user/object#media) to be created.| |user_medias<br>(deprecated)|array|This parameter is deprecated, please use `medias` instead.<br>User [media](/manual/api/reference/user/object#media) to be created.| ### Paramètres `(object/array)` Utilisateurs à créer. En plus des [propriétés utilisateur standard](object#user), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#types-de-données)|Description| |--|--|------| |**passwd**<br>*(obligatoire)*|string|Mot de passe de l'utilisateur.<br><br>Peut être omis si l'utilisateur est ajouté uniquement aux groupes disposant d'un accès LDAP.| |**usrgrps**<br>(obligatoire)|array|[Groupes d'utilisateurs](/manual/api/reference/user/create) auxquels ajoutés l'utilisateur.<br><br>Les groupes d'utilisateurs doivent avoir la propriété `usrgrpid` définie.| |medias|array|[Média](/manual/api/reference/user/object#média) utilisateur à créer.| |user_medias<br>(obsolète)|array|Ce paramètre est obsolète, veuillez utiliser `medias` à la place.<br>[Média](/manual/api/reference/user/object#média) utilisateur à créer.| ### Parameters `(object/array)` [Value map properties](object#value_map) to be updated. The `valuemapid` property must be defined for each value map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. ### Paramètres `(object/array)` [Propriétés de la table de correspondance](object#value_map) à mettre à jour. La propriété `valuemapid` doit être définie pour chaque table de correspondance, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. ### Parameters `(object/array)` Value maps to create. The method accepts value maps with the [standard value map properties](object#value_map). ### Paramètres `(object/array)` Tables de correspondance à créer. La méthode accepte les tables de correspondance avec les [propriétés de table de correspondance standard](object#value_map). ### Parameters `(object/array)` Web scenario properties to be updated. The `httptestid` property must be defined for each web scenario, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. Additionally to the [standard web scenario properties](object#web_scenario), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |steps|array|Scenario [steps](/manual/api/reference/httptest/object#scenario_step) to replace existing steps.| |tags|array|Web scenario [tags.](/manual/api/reference/httptest/object#web_scenario_tag)| ### Paramètres `(object/array)` Propriétés du scénario Web à mettre à jour. La propriété `httptestid` doit être définie pour chaque scénario Web, toutes les autres propriétés sont facultatives. Seules les propriétés transmises seront mises à jour, toutes les autres resteront inchangées. En plus des [propriétés de scénario Web standard](object#web_scenario), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |steps|array|[Etapes](/manual/api/reference/httptest/object#scenario_step) de scenario en remplacement de celles existantes.| |tags|array|[Tags.](/manual/api/reference/httptest/object#web_scenario_tag) de scenario Web| ### Parameters `(object/array)` Web scenarios to create. Additionally to the [standard web scenario properties](object#web_scenario), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**steps**<br>(required)|array|Web scenario [steps](/manual/api/reference/httptest/object#scenario_step).| |tags|array|Web scenario [tags.](/manual/api/reference/httptest/object#web_scenario_tag)| ### Paramètres `(object/array)` Scénarios Web à créer. En plus des [propriétés de scénario Web standard](object#web_scenario), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**steps**<br>(obligatoire)|array|[Etapes](/manual/api/reference/httptest/object#scenario_step) de scénario Web.| |tags|array|[Tags.](/manual/api/reference/httptest/object#web_scenario_tag) de scénario Web..| ### Parameters `(object)` Authentication properties to be updated. ### Paramètres `(object)` Propriétés d'authentification à mettre à jour. ### Parameters `(object)` Autoregistration properties to be updated. ### Paramètres `(object)` Propriétés d'enregistrement automatique à mettre à jour. ### Parameters `(object)` Housekeeping properties to be updated. ### Paramètres `(object)` Propriétés de procédure de nettoyage à mettre à jour. ### Parameters `(object)` Parameters containing the host interfaces to be created on the given hosts. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(required)|object/array|Hosts to be updated.<br><br>The hosts must have the `hostid` property defined.| |**interfaces**<br>(required)|object/array|[Host interfaces](/manual/api/reference/hostinterface/object) to create on the given hosts.| ### Paramètres `(objet)` Paramètres contenant les interfaces hôtes à créer sur les hôtes donnés. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(obligatoire)|object/array|Hôtes à mettre à jour.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |**interfaces**<br>(obligatoire)|object/array|[Host interfaces](/manual/api/reference/hostinterface/object) à créer sur les hôtes donnés.| ### Parameters `(object)` Parameters containing the ID of the host to be updated and the new host interfaces. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hostid**<br>(required)|string|ID of the host to be updated.| |**interfaces**<br>(required)|object/array|[Host interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces with.| ### Paramètres `(object)` Paramètres contenant l'ID de l'hôte à mettre à jour et les nouvelles interfaces hôtes. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hostid**<br>(obligatoire)|chaîne|ID de l'hôte à mettre à jour.| |**interfaces**<br>(obligatoire)|object/array|[Interfaces hôtes](/manual/api/reference/hostinterface/object) pour remplacer les interfaces hôtes actuelles.| ### Parameters `(object)` Parameters containing the ID of the script to run and either the ID of the host or the ID of the event. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**scriptid**<br>(required)|string|ID of the script to run.| |hostid|string|ID of the host to run the script on.| |eventid|string|ID of the event to run the script on.| ### Paramètres `(object)` Paramètres contenant l'ID du script à exécuter et soit l'ID de l'hôte, soit l'ID de l'événement. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**scriptid**<br>(obligatoire)|string|ID du script à exécuter.| |hostid|string|ID de l'hôte sur lequel exécuter le script.| |eventid|string|ID de l'événement sur lequel exécuter le script.| ### Parameters `(object)` Parameters containing the IDs of the host groups to update and the objects that should be removed. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupids**<br>(required)|string/array|IDs of the host groups to be updated.| |hostids|string/array|Hosts to remove from all host groups.| |templateids|string/array|Templates to remove from all host groups.| ### Paramètres `(object)` Paramètres contenant les ID des groupes d'hôtes à mettre à jour et les objets à supprimer. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupids**<br>(obligatoire)|string/array|ID des groupes d'hôtes à mettre à jour.| |hostids|string/array|Hôtes à supprimer de tous les groupes d'hôtes.| |templateids|string/array|Modèles à supprimer de tous les groupes d'hôtes.| ### Parameters `(object)` Parameters containing the IDs of the host groups to update and the objects that should be updated. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(required)|object/array|Host groups to be updated.<br><br>The host groups must have the `groupid` property defined.| |**hosts**<br>(required)|object/array|Hosts to replace the current hosts on the given host groups.<br>All other hosts, except the ones mentioned, will be excluded from host groups.<br>Discovered hosts will not be affected.<br><br>The hosts must have the `hostid` property defined.| |**templates**<br>(required)|object/array|Templates to replace the current templates on the given host groups.<br>All other templates, except the ones mentioned, will be excluded from host groups.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les identifiants des groupes d'hôtes à mettre à jour et les objets à mettre à jour. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(obligatoire)|object/array|Groupes d'hôtes à mettre à jour.<br>Tous les autres hôtes, à l'exception de ceux mentionnés, seront exclus des groupes d'hôtes.<br>Les hôtes découverts ne seront pas affectés.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |hosts|object/array|Hôtes en remplacement des hôtes actuels sur les groupes d'hôtes donnés.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |templates|object/array|Modèles en remplacement des modèles actuels sur les groupes d'hôtes donnés.<br>Tous les autres modèles, à l'exception de ceux mentionnés, seront exclus des groupes d'hôtes.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the IDs of the host groups to update and the objects to add to all the host groups. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(required)|object/array|Host groups to be updated.<br><br>The host groups must have the `groupid` property defined.| |hosts|object/array|Hosts to add to all host groups.<br><br>The hosts must have the `hostid` property defined.| |templates|object/array|Templates to add to all host groups.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les identifiants des groupes d'hôtes à mettre à jour et les objets à ajouter à tous les groupes d'hôtes. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groups**<br>(obligatoire)|object/array|Groupes d'hôtes à mettre à jour.<br><br>Les groupes d'hôtes doivent avoir la propriété `groupid` définie.| |hosts|object/array|Hôtes à ajouter à tous les groupes d'hôtes.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |templates|object/array|Modèles à ajouter à tous les groupes d'hôtes.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the IDs of the hosts to be updated and the interfaces to be removed. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hostids**<br>(required)|string/array|IDs of the hosts to be updated.| |**interfaces**<br>(required)|object/array|Host interfaces to remove from the given hosts.<br><br>The host interface object must have the ip, dns and port properties defined| ### Paramètres `(objet)` Paramètres contenant les ID des hôtes à mettre à jour et les interfaces à supprimer. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hostids**<br>(obligatoire)|string/array|ID des hôtes à mettre à jour.| |**interfaces**<br>(obligatoire)|object/array|Interfaces hôtes à supprimer des hôtes donnés.<br><br>L'objet interface hôte doit avoir les propriétés ip, dns et port définies| ### Parameters `(object)` Parameters containing the IDs of the hosts to update and the objects that should be removed. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hostids**<br>(required)|string/array|IDs of the hosts to be updated.| |groupids|string/array|Host groups to remove the given hosts from.| |interfaces|object/array|Host interfaces to remove from the given hosts.<br><br>The host interface object must have the `ip`, `dns` and `port` properties defined.| |macros|string/array|User macros to delete from the given hosts.| |templateids|string/array|Templates to unlink from the given hosts.| |templateids\_clear|string/array|Templates to unlink and clear from the given hosts.| ### Paramètres `(object)` Paramètres contenant les identifiants des hôtes à mettre à jour et les objets à supprimer. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description|¶ |--|--|------| |**hostids**<br>(obligatoire)|string/array|ID des hôtes à mettre à jour.| |groupids|string/array|Groupes d'hôtes desquels supprimer les hôtes donnés.| |interfaces|object/array|Interfaces hôtes à supprimer des hôtes donnés.<br><br>L'objet d'interface hôte doit avoir les propriétés `ip`, `dns` et `port` définies.| |macros|string/array|Macros utilisateur à supprimer des hôtes donnés.| |templateids|string/array|Modèles à délier des hôtes donnés.| |templateids\_clear|string/array|Modèles à délier et effacer des hôtes donnés.| ### Parameters `(object)` Parameters containing the IDs of the hosts to update and the objects to add to all the hosts. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(required)|object/array|Hosts to be updated.<br><br>The hosts must have the `hostid` property defined.| |groups|object/array|Host groups to add to the given hosts.<br><br>The host groups must have the `groupid` property defined.| |interfaces|object/array|[Host interfaces](/manual/api/reference/hostinterface/object) to be created for the given hosts.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to be created for the given hosts.| |templates|object/array|Templates to link to the given hosts.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les identifiants des hôtes à mettre à jour et les objets à ajouter à tous les hôtes. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(obligatoire)|object/array|Hôtes à mettre à jour.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |groups|object/array|Groupes d'hôtes à ajouter aux hôtes donnés.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |interfaces|object/array|[Interfaces hôtes](/manual/api/reference/hostinterface/object) à créer pour les hôtes donnés.| |macros|object/array|[Macros utilisateur](/manual/api/reference/usermacro/object) à créer pour les hôtes donnés.| |templates|object/array|Modèles à lier aux hôtes donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the IDs of the hosts to update and the properties that should be updated. Additionally to the [standard host properties](object#host), the method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(required)|object/array|[Hosts](/manual/api/reference/host/object) to be updated.<br><br>The hosts must have the `hostid` property defined.| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object) to replace the current host groups the hosts belong to.<br><br>The host groups must have the `groupid` property defined.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces on the given hosts.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.<br><br>Host inventory mode cannot be updated using the `inventory` parameter, use `inventory_mode` instead.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros on the given hosts.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates on the given hosts.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the given hosts.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les ID des hôtes à mettre à jour et les propriétés à mettre à jour. En plus des [propriétés de l'objet hôte standard](object#host), la méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**hosts**<br>(obligatoire)|object/array|[Hôtes](/manual/api/reference/host/object) à mettre à jour.<br><br>Les hôtes doivent avoir la propriété `hostid` définie.| |groups|object/array|[Groupes d'hôtes](/manual/api/reference/hostgroup/object) en remplacement des groupes d'hôtes actuels auxquels appartiennent les hôtes.<br><br>Les hôtes doivent avoir la propriété `groupid` définie.| |interfaces|object/array|[Interfaces hôtes](/manual/api/reference/hostinterface/object) en remplacement des interfaces hôtes actuelles sur les hôtes donnés.| |inventory|object|Propriétés d'[inventaire d'hôte](/manual/api/reference/host/object#host_inventory).<br><br>Le mode d'inventaire de l'hôte ne peut pas être mis à jour à l'aide du paramètre `inventory`, utiliser plutôt `inventory_mode`.| |inventory\_mode|integer|Mode de peuplement de l'inventaire hôte.<br><br>Se référer à la [page de l'objet Inventaire d'hôte](/manual/api/reference/host/object#host_inventory) pour une liste des modes d'inventaire supportés.| |macros|object/array|[Macros utilisateur](/manual/api/reference/usermacro/object) en remplacement des macros utilisateur actuelles sur les hôtes donnés.| |templates|object/array|[Modèles](/manual/api/reference/template/object) en remplacement des modèles actuellement liés sur les hôtes donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |templates\_clear|object/array|[Modèles](/manual/api/reference/template/object) à délier et effacer des hôtes donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the IDs of the templates to update and the objects that should be removed. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templateids**<br>(required)|string/array|IDs of the templates to be updated.| |groupids|string/array|Host groups to remove the given templates from.| |macros|string/array|User macros to delete from the given templates.| |templateids\_clear|string/array|Templates to unlink and clear from the given templates (upstream).| |templateids\_link|string/array|Templates to unlink from the given templates (upstream).| ### Paramètres `(object)` Paramètres contenant les identifiants des modèles à mettre à jour et les objets à supprimer. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templateids**<br>(obligatoire)|string/array|ID des modèles à mettre à jour.| |groupids|string/array|Groupes d'hôte à supprimer des modèles donnés.| |macros|string/array|Macros utilisateur à supprimer des modèles donnés.| |templateids\_clear|string/array|Modèles à délier et à effacer des modèles donnés (en amont).| |templateids\_link|string/array|Modèles à délier des modèles donnés (en amont).| ### Parameters `(object)` Parameters containing the IDs of the templates to update and the objects to add to the templates. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templates**<br>(required)|object/array|Templates to be updated.<br><br>The templates must have the `templateid` property defined.| |groups|object/array|Host groups to add the given templates to.<br><br>The host groups must have the `groupid` property defined.| |macros|object/array|User macros to be created for the given templates.| |templates\_link|object/array|Templates to link to the given templates.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les identifiants des modèles à mettre à jour et les objets à ajouter aux modèles. La méthode prend en charge les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templates**<br>(obligatoire)|object/array|Modèles à mettre à jour.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |groups|object/array|Groupes d'hôtes auxquels ajouter les modèles donnés.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |macros|object/array|Macros utilisateur à créer pour les modèles donnés.| |templates\_link|object/array|Modèles à lier aux modèles donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the IDs of the templates to update and the objects to replace for the templates. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templates**<br>(required)|object/array|Templates to be updated.<br><br>The templates must have the `templateid` property defined.| |groups|object/array|Host groups to replace the current host groups the templates belong to.<br><br>The host groups must have the `groupid` property defined.| |macros|object/array|User macros to replace the current user macros on the given templates.| |templates\_clear|object/array|Templates to unlink and clear from the given templates.<br><br>The templates must have the `templateid` property defined.| |templates\_link|object/array|Templates to replace the currently linked templates.<br><br>The templates must have the `templateid` property defined.| ### Paramètres `(object)` Paramètres contenant les identifiants des modèles à mettre à jour et les propriétés à mettre à jour. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templates**<br>(obligatoire)|object/array|Modèles à mettre à jour.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |groups|object/array|Groupes d'hôtes pour remplacer les groupes d'hôtes actuels auxquels appartiennent les modèles.<br><br>Les groupes hôtes doivent avoir la propriété `groupid` définie.| |macros|object/array|Macros utilisateur en remplacement des macros utilisateur actuelles sur les modèles donnés.| |templates\_clear|object/array|Modèles à délier et à effacer des modèles donnés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| |templates\_link|object/array|Modèles en remplacement des modèles actuellement liés.<br><br>Les modèles doivent avoir la propriété `templateid` définie.| ### Parameters `(object)` Parameters containing the user name and password. The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**password**<br>(required)|string|User password.| |**username**<br>(required)|string|User name.| |userData|flag|Return information about the authenticated user.| |user<br>(deprecated)|string|This parameter is deprecated, please use `username` instead.<br>User name.| ### Paramètres `(object)` Paramètres contenant le nom d'utilisateur et le mot de passe. La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#types-de-données)|Description| |--|--|------| |**password**<br>(obligatoire)|string|Mot de passe de l'utilisateur.| |**username**<br>(obligatoire)|string|Nom d'utilisateur.| |userData|flag|Renvoie des informations sur l'utilisateur authentifié.| |user<br>(obsolète)|string|Ce paramètre est obsolète, veuillez utiliser `username` à la place.<br>Nom d'utilisateur.| ### Parameters `(object)` Parameters defining the LLD rules to copy and the target hosts. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |discoveryids|array|IDs of the LLD rules to be copied.| |hostids|array|IDs of the hosts to copy the LLD rules to.| ### Paramètres `(object)` Paramètres définissant les règles de découverte bas niveau à copier et les hôtes cibles. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |discoveryids|array|ID des règles de découverte bas niveau à copier.| |hostids|array|ID des hôtes sur lesquels copier les règles de découverte bas niveau.| ### Parameters `(object)` Settings properties to be updated. ### Paramètres `(object)` Propriétés des paramètres à mettre à jour. #### Parameters |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |AlertScriptsPath|no| |/usr/local/share/zabbix/alertscripts|Location of custom alert scripts (depends on compile-time installation variable *datadir*).| |AllowRoot|no| |0|Allow the server to run as 'root'. If disabled and the server is started by 'root', the server will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |AllowUnsupportedDBVersions|no| |0|Allow the server to work with unsupported database versions.<br>0 - do not allow<br>1 - allow| |CacheSize|no|128K-64G|32M|Size of configuration cache, in bytes.<br>Shared memory size for storing host, item and trigger data.| |CacheUpdateFrequency|no|1-3600|60|Determines how often Zabbix will perform update of configuration cache in seconds.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |DBHost|no| |localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) empty string results in using the Net Service Name connection method; in this case consider using the TNS\_ADMIN environment variable to specify the directory of the tnsnames.ora file.| |DBName|yes| | |Database name.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO\_TASK environment variable if DBName is set to empty string.| |DBPassword|no| | |Database password.<br>Comment this line if no password is used.| |DBPort|no|1024-65535| |Database port when not using local socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used this parameter will be ignored; the port number from the tnsnames.ora file will be used instead.| |DBSchema|no| | |Schema name. Used for PostgreSQL.| |DBSocket|no| | |Path to MySQL socket file.| |DBUser|no| | |Database user.| |DBTLSConnect|no| | |Setting this option enforces to use TLS connection to database:<br>*required* - connect using TLS<br>*verify\_ca* - connect using TLS and verify certificate<br>*verify\_full* - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate<br><br>On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: "required", "verify\_ca", "verify\_full". On MariaDB starting from version 10.2.6 "required" and "verify\_full" values are supported.<br>By default not set to any option and the behavior depends on database configuration.<br><br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCAFile|no<br>(yes, if DBTLSConnect set to one of: verify\_ca, verify\_full)| | |Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCertFile|no| | |Full pathname of file containing Zabbix server certificate for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSKeyFile|no| | |Full pathname of file containing the private key for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher|no| | |The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2.<br>Supported only for MySQL.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher13|no| | |The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol.<br>Supported only for MySQL, starting from version 8.0.16.<br>This parameter is supported since Zabbix 5.0.0.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)<br>See also [runtime control](/manual/concepts/server#server_process) options.| |ExportDir|no| | |Directory for [real-time export](/manual/appendix/install/real_time_export) of events, history and trends in newline-delimited JSON format. If set, enables real-time export.<br>This parameter is supported since Zabbix 4.0.0.| |ExportFileSize|no|1M-1G|1G|Maximum size per export file in bytes. Only used for rotation if ExportDir is set.<br>This parameter is supported since Zabbix 4.0.0.| |ExportType|no| | |List of comma-delimited entity types (events, history, trends) for [real-time export](/manual/appendix/install/real_time_export) (all types by default). Valid only if ExportDir is set.<br>*Note* that if ExportType is specified, but ExportDir is not, then this is a configuration error and the server will not start.<br>e.g.:<br>ExportType=history,trends - export history and trends only<br>ExportType=events - export events only| |ExternalScripts|no| |/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no| |/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no| |/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HANodeName|no| | |The high availability cluster node name.<br>When empty the server is working in standalone mode and a node with empty name is created.| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |HistoryStorageDateIndex|no| |0|Enable preprocessing of history values in history storage to store values in different indices based on date:<br>0 - disable<br>1 - enable| |HistoryStorageURL|no| | |History storage HTTP\[S\] URL.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HistoryStorageTypes|no| |uint,dbl,str,log,text|Comma separated list of value types to be sent to the history storage.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HousekeepingFrequency|no|0-24|1|Determines how often Zabbix will perform housekeeping procedure in hours.<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no| | |IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no| | |Module to load at server startup. Modules are used to extend functionality of the server.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no| | |Full path to location of server modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| | |Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|Determines how long a database query may take before being logged in milliseconds.<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.| |MaxHousekeeperDelete|no|0-1000000|5000|No more than 'MaxHousekeeperDelete' rows (corresponding to \[tablename\], \[field\], \[value\]) will be deleted per one task in one housekeeping cycle.<br>If set to 0 then no limit is used at all. In this case you must know what you are doing, so as not to [overload the database!](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>This parameter applies only to deleting history and trends of already deleted items.| |NodeAddress|no| |10051|IP or hostname with optional port to override how the frontend should connect to the server.<br>Format: <address>\[:port\]<br>The priority of addresses used by the frontend to specify the server address is: NodeAddress (1); ListenIP (if not 0.0.0.0 or ::) (2); localhost (default) (3)<br>See also: HANodeName parameter| |PidFile|no| |/tmp/zabbix\_server.pid|Name of PID file.| |ProxyConfigFrequency|no|1-604800|3600|Determines how often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |ProblemHousekeepingFrequency|no| 1-3600|60|Determines how often Zabbix will delete problems for deleted triggers in seconds.| |ProxyDataFrequency|no|1-3600|1|Determines how often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |ServiceManagerSyncFrequency|no|1-3600|60| Determines how often Zabbix will synchronize configuration of a service manager in seconds.| |SNMPTrapperFile|no| |/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the server.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.| |SocketDir|no| |/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix proxy and Zabbix agent;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- script item JavaScript HTTP requests;<br>- preprocessing JavaScript HTTP requests;<br>- sending notification emails (connections to SMTP server);<br>- webhook notifications (JavaScript HTTP connections);<br>- connections to the Vault| |SSHKeyLocation|no| | |Location of public and private keys for SSH checks and actions| |SSLCertLocation|no| | |Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only.| |SSLKeyLocation|no| | |Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only.| |SSLCALocation|no| | |Override the location of certificate authority (CA) files for SSL server certificate verification. If not set, system-wide directory will be used.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartAlerters|no|1-100|3|Number of pre-forked instances of [alerters](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.4.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of [history syncers](/manual/concepts/server#server_process_types).<br>*Note*: Be careful when changing this value, increasing it may do more harm than good. Roughly, the default value should be enough to handle up to 4000 NVPS.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of [discoverers](/manual/concepts/server#server_process_types).| |StartEscalators|no|1-100|1|Number of pre-forked instances of [escalators](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.0.0.| |StartHistoryPollers|no|0-1000|5|Number of pre-forked instances of [history pollers](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 5.4.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of [HTTP pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of [IPMI pollers](/manual/concepts/server#server_process_types).| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of [Java pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartLLDProcessors|no|1-100|2|Number of pre-forked instances of low-level discovery (LLD) [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The LLD manager process is automatically started when an LLD worker is started.<br>This parameter is supported since Zabbix 4.2.0.| |StartODBCPollers|no|0-1000|1|Number of pre-forked instances of [ODBC pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPingers|no|0-1000|1|Number of pre-forked instances of [ICMP pingers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of [pollers for unreachable hosts](/manual/concepts/server#server_process_types) (including IPMI and Java)**^[1](zabbix_server#footnotes)^**.<br>At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.| |StartPollers|no|0-1000|5|Number of pre-forked instances of [pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 3.4.0.| |StartProxyPollers|no|0-250|1|Number of pre-forked instances of [pollers for passive proxies](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartReportWriters|no|0-100|0|Number of pre-forked instances of [report writers](/manual/concepts/server#server_process_types).<br>If set to 0, scheduled report generation is disabled.<br>The report manager process is automatically started when a report writer is started.<br>This parameter is supported since Zabbix 5.4.0.| |StartSNMPTrapper|no|0-1|0|If set to 1, [SNMP trapper](/manual/concepts/server#server_process_types) process will be started.| |StartTimers|no|1-1000|1|Number of pre-forked instances of [timers](/manual/concepts/server#server_process_types).<br>Timers process maintenance periods.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of [trappers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>Trappers accept incoming connections from Zabbix sender, active agents and active proxies.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked [VMware collector](/manual/concepts/server#server_process_types) instances.| |StatsAllowedIP|no| | |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.2.0.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check in seconds.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no| |/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |TrendCacheSize|no|128K-2G|4M|Size of trend cache, in bytes.<br>Shared memory size for storing trends data.| |TrendFunctionCacheSize|no|128K-2G|4M|Size of trend function cache, in bytes.<br>Shared memory size for caching calculated trend function data.| |UnavailableDelay|no|1-3600|60|Determines how often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|Determines how often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period in seconds.| |UnreachablePeriod|no|1-3600|45|Determines after how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |User|no| |zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |ValueCacheSize|no|0,128K-64G|8M|Size of history value cache, in bytes.<br>Shared memory size for caching item history data requests.<br>Setting to 0 disables value cache (not recommended).<br>When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.| |VaultDBPath|no| | |Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.<br>Example: secret/zabbix/database<br>This option can only be used if DBUser and DBPassword are not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VaultToken|no| | |Vault authentication token that should have been generated exclusively for Zabbix server with read-only permission to the paths specified in [Vault macros](/manual/config/macros/user_macros#configuration) and read-only permission to the path specified in the optional VaultDBPath configuration parameter.<br>It is an error if VaultToken and VAULT\_TOKEN environment variable are defined at the same time.<br>This parameter is supported since Zabbix 5.2.0.| |VaultURL|no| |https://127.0.0.1:8200|Vault server HTTP\[S\] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).| |WebServiceURL|no| | |HTTP\[S\] URL to Zabbix web service in the format `<host:port>/report`. For example: `http://localhost:10053/report`<br>This parameter is supported since Zabbix 5.4.0.| #### Paramètres |Paramètre|Obligatoire|Plage|Par défaut|Description| |--|--|--|--|----------| |AlertScriptsPath|non| |/usr/local/share/zabbix/alertscripts|Emplacement des scripts d'alerte personnalisés (dépend de la variable d'installation au moment de la compilation *datadir*).| |AllowRoot|non| |0|Autoriser le serveur à s'exécuter en tant que 'root'. S'il est désactivé et que le serveur est démarré par 'root', le serveur essaiera de passer à l'utilisateur 'zabbix' à la place. N'a aucun effet si démarré sous un utilisateur régulier.<br>0 - ne pas autoriser<br>1 - autoriser| |AllowUnsupportedDBVersions|non| |0|Autoriser le serveur à travailler avec des versions de base de données non prises en charge.<br>0 - ne pas autoriser<br>1 - autoriser| |CacheSize|non|128K-64G|32M|Taille du cache de configuration, en octets.<br>Taille de la mémoire partagée pour stocker les données d'hôte, d'élément et de déclencheur.| |CacheUpdateFrequency|non|1-3600|60|Détermine la fréquence à laquelle Zabbix effectuera la mise à jour du cache de configuration en secondes.<br>Voir aussi les options de [contrôle d'exécution](/manual/concepts/server#server_process).| |DBHost|non| |localhost|Nom d'hôte de la base de données.<br>Dans le cas de MySQL, localhost ou une chaîne vide entraîne l'utilisation d'un socket. Dans le cas de PostgreSQL<br>seule une chaîne vide entraîne une tentative d'utilisation de socket.<br>Dans le cas de [Oracle](/manual/appendix/install/oracle#etablissement-de-la-connexion), une chaîne vide entraîne l'utilisation de la méthode de connexion Net Service Name ; dans ce cas, envisagez d'utiliser la variable d'environnement TNS\_ADMIN pour spécifier le répertoire du fichier tnsnames.ora.| |DBName|oui| | |Nom de la base de données.<br>Dans le cas d'[Oracle](/manual/appendix/install/oracle#etablissement-de-la-connexion) si la méthode de connexion Net Service Name est utilisée, spécifiez le nom du service à partir de tnsnames.ora ou définissez une chaîne vide ; définissez la variable d'environnement TWO\_TASK si DBName est défini sur une chaîne vide.| |DBPassword|non| | |Mot de passe de la base de données.<br>Commentez cette ligne si aucun mot de passe n'est utilisé.| |DBPort|non|1024-65535| |Port de la base de données lorsque le socket local n'est pas utilisé.<br>Dans le cas d'[Oracle](/manual/appendix/install/oracle#etablissement-de-la-connexion) si la méthode de connexion Net Service Name est utilisée, ce paramètre sera ignoré ; le numéro de port du fichier tnsnames.ora sera utilisé à la place.| |DBSchema|non| | |Nom du schéma. Utilisé pour PostgreSQL.| |DBSocket|non| | |Chemin d'accès au fichier socket MySQL.| |DBUser|non| | |Utilisateur de la base de données.| |DBTLSConnect|non| | |La définition de cette option force l'utilisation de la connexion TLS à la base de données :<br>*required* - se connecter à l'aide de TLS<br>*verify\_ca* - se connecter à l'aide de TLS et vérifier le certificat<br>*verify\_full* - se connecter à l'aide de TLS, vérifier le certificat et vérifier que l'identité de la base de données spécifiée par DBHost correspond à son certificat<br><br>Sur MySQL à partir de 5.7.11 et PostgreSQL, les valeurs suivantes sont prises en charge : "required", "verify\_ca", "verify\_full". Sur MariaDB à partir de la version 10.2.6, les valeurs "required" et "verify\_full" sont prises en charge.<br>Par défaut, aucune option n'est définie et le comportement dépend de la configuration de la base de données.<br><br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DBTLSCAFile|non<br>(oui, si DBTLSConnect est défini sur l'un des éléments suivants : verify\_ca, verify\_full)| | |Chemin d'accès complet d'un fichier contenant les certificats des autorités de certification de niveau supérieur pour la vérification des certificats de la base de données.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DBTLSCertFile|non| | |Chemin d'accès complet du fichier contenant le certificat du serveur Zabbix pour l'authentification à la base de données.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DBTLSKeyFile|non| | |Chemin d'accès complet du fichier contenant la clé privée pour l'authentification à la base de données.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DBTLSCipher|non| | |La liste des chiffrements de chiffrement que le serveur Zabbix autorise pour les protocoles TLS jusqu'à TLSv1.2.<br>Pris en charge uniquement pour MySQL.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DBTLSCipher13|non| | |La liste des suites de chiffrement autorisées par le serveur Zabbix pour le protocole TLSv1.3.<br>Pris en charge uniquement pour MySQL, à partir de la version 8.0.16.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.| |DebugLevel|non|0-5|3|Spécifie le niveau de débogage :<br>0 - informations de base sur le démarrage et l'arrêt des processus Zabbix<br>1 - informations critiques<br>2 - informations sur les erreurs<br>3 - avertissements< br>4 - pour le débogage (produit beaucoup d'informations)<br>5 - débogage étendu (produit encore plus d'informations)<br>Voir aussi les options de [contrôle d'exécution](/manual/concepts/server#server_process).| |ExportDir|non| | |Répertoire pour [l'exportation en temps réel](/manual/appendix/install/real_time_export) des événements, de l'historique et des tendances au format JSON délimité par une nouvelle ligne. S'il est défini, active l'exportation en temps réel.<br>Ce paramètre est pris en charge depuis Zabbix 4.0.0.| |ExportFileSize|non|1M-1G|1G|Taille maximale par fichier d'exportation en octets. Utilisé uniquement pour la rotation si ExportDir est défini.<br>Ce paramètre est pris en charge depuis Zabbix 4.0.0.| |ExportType|non| | |Liste des types d'entités délimités par des virgules (événements, historique, tendances) pour [l'exportation en temps réel](/manual/appendix/install/real_time_export) (tous les types par défaut). Valide uniquement si ExportDir est défini.<br>*Notez* que si ExportType est spécifié, mais ExportDir ne l'est pas, il s'agit d'une erreur de configuration et le serveur ne démarrera pas.<br>par exemple :<br>ExportType=history,trends - exporter l'historique et les tendances uniquement<br>ExportType=events - exporter les événements uniquement| |ExternalScripts|non| |/usr/local/share/zabbix/externalscripts|Emplacement des scripts externes (dépend de la variable d'installation au moment de la compilation *datadir*).| |Fping6Location|non| |/usr/sbin/fping6|Emplacement de fping6.<br>Assurez-vous que le binaire fping6 a la propriété root et l'indicateur SUID défini.<br>Rendez vide ("Fping6Location=") si votre utilitaire fping est capable de traiter les adresses IPv6. | |FpingLocation|non| |/usr/sbin/fping|Emplacement de fping.<br>Assurez-vous que le binaire fping a la propriété root et l'indicateur SUID défini !| |HANodeName|non| | |Le nom du nœud du cluster haute disponibilité.<br>Lorsqu'il est vide, le serveur fonctionne en mode autonome et un nœud avec un nom vide est créé.| |HistoryCacheSize|non|128K-2G|16M|Taille du cache de l'historique, en octets.<br>Taille de la mémoire partagée pour stocker les données de l'historique.| |HistoryIndexCacheSize|non|128K-2G|4M|Taille du cache d'index d'historique, en octets.<br>Taille de la mémoire partagée pour l'indexation des données d'historique stockées dans le cache d'historique.<br>La taille du cache d'index nécessite environ 100 octets pour mettre en cache un élément.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |HistoryStorageDateIndex|non| |0|Activer le prétraitement des valeurs d'historique dans le stockage d'historique pour stocker les valeurs dans différents index en fonction de la date :<br>0 - désactiver<br>1 - activer| |HistoryStorageURL|non| | |URL HTTP\[S\] de stockage de l'historique.<br>Ce paramètre est utilisé pour la configuration d'[Elasticsearch](/manual/appendix/install/elastic_search_setup).| |HistoryStorageTypes|non| |uint,dbl,str,log,text|Liste séparée par des virgules des types de valeurs à envoyer au stockage de l'historique.<br>Ce paramètre est utilisé pour la configuration de [Elasticsearch](/manual/appendix/install/elastic_search_setup).| |HousekeepingFrequency|non|0-24|1|Détermine la fréquence à laquelle Zabbix effectuera la procédure de nettoyage en heures.<br>Le nettoyage supprime les informations obsolètes de la base de données.<br>*Remarque* : pour éviter que le nettoyage ne soit surchargé (par exemple, lorsque les périodes d'historique et de tendance sont considérablement réduites), pas plus de 4 fois HousekeepingFrequency heures d'informations obsolètes sont supprimées dans un cycle de nettoyage, pour chaque élément. Ainsi, si HousekeepingFrequency est 1, pas plus de 4 heures d'informations obsolètes (à partir de l'entrée la plus ancienne) seront supprimées par cycle.<br>*Remarque* : Pour réduire la charge au démarrage du serveur, le nettoyage est reporté de 30 minutes après le démarrage du serveur. Ainsi, si HousekeepingFrequency est 1, la toute première procédure de nettoyage après le démarrage du serveur s'exécutera après 30 minutes, et se répétera ensuite avec un délai d'une heure.<br>Depuis Zabbix 3.0.0, il est possible de désactiver le nettoyage automatique en définissant HousekeepingFrequency sur 0. Dans ce cas, la procédure de nettoyage ne peut être démarrée que par l'option de contrôle d'exécution *housekeeper\_execute* et la période d'informations obsolètes supprimées dans un cycle de nettoyage est 4 fois la période depuis le dernier cycle de nettoyage, mais pas moins de 4 heures et pas supérieure à 4 jours.<br>Voir aussi les options de [contrôle d'exécution](/manual/concepts/server#server_process).| |Include|non| | |Vous pouvez inclure des fichiers individuels ou tous les fichiers d'un répertoire dans le fichier de configuration.<br>Pour n'inclure que les fichiers pertinents dans le répertoire spécifié, le caractère générique astérisque est pris en charge pour la correspondance de modèle. Par exemple : `/absolute/path/to/config/files/*.conf`.<br>Voir les [notes spéciales](special_notes_include) sur les limitations.| |JavaGateway|non| | |Adresse IP (ou nom d'hôte) de la passerelle Java Zabbix.<br>Requis uniquement si les pollers Java sont démarrés.| |JavaGatewayPort|non|1024-32767|10052|Port sur lequel la passerelle Java Zabbix écoute.| |ListenBacklog|non|0 - INT\_MAX|SOMAXCONN|Le nombre maximal de connexions en attente dans la file d'attente TCP.<br>La valeur par défaut est une constante codée en dur, qui dépend du système.<br>La valeur maximale prise en charge dépend de système, des valeurs trop élevées peuvent être silencieusement tronquées au 'maximum spécifié par l'implémentation'.| |ListenIP|non| |0.0.0.0|Liste des adresses IP délimitées par des virgules sur lesquelles le trappeur doit écouter.<br>Le trappeur écoutera sur toutes les interfaces réseau si ce paramètre est manquant.| |ListenPort|non|1024-32767|10051|Port d'écoute pour le trappeur.| |LoadModule|non| | |Module à charger au démarrage du serveur. Les modules sont utilisés pour étendre les fonctionnalités du serveur.<br>Formats :<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module. so><br>Soit le module doit être situé dans le répertoire spécifié par LoadModulePath, soit le chemin doit précéder le nom du module. Si le chemin précédent est absolu (commence par '/'), alors LoadModulePath est ignoré.<br>Il est permis d'inclure plusieurs paramètres LoadModule.| |LoadModulePath|non| | |Chemin complet vers l'emplacement des modules du serveur.<br>La valeur par défaut dépend des options de compilation.| |LogFile|oui, si LogType est défini sur *file*, sinon<br>non| | |Nom du fichier journal.| |LogFileSize|non|0-1024|1|Taille maximale du fichier journal en Mo.<br>0 - désactiver la rotation automatique des journaux.<br>*Remarque* : si la limite de taille du fichier journal est atteinte et que la rotation des fichiers échoue, par quelle qu'en soit la raison, le fichier journal existant est tronqué et redémarré.| |LogType|non| |file|Type de sortie du journal :<br>*file* - écrit le journal dans le fichier spécifié par le paramètre LogFile,<br>*system* - écrit le journal dans syslog,<br>*console* - écrit le journal dans la sortie standard.<br >Ce paramètre est supporté depuis Zabbix 3.0.0.| |LogSlowQueries|non|0-3600000|0|Détermine le temps qu'une requête de base de données peut prendre avant d'être enregistrée en millisecondes.<br>0 - ne consigne pas les requêtes lentes.<br>Cette option est activée à partir de DebugLevel=3.| |MaxHousekeeperDelete|non|0-1000000|5000|Pas plus de 'MaxHousekeeperDelete' lignes (correspondant à \[tablename\], \[field\], \[value\]) seront supprimées par tâche dans un cycle de nettoyage. <br>Si défini sur 0, aucune limite n'est utilisée. Dans ce cas, vous devez savoir ce que vous faites, afin de ne pas [surcharger la base de données !](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>Ce paramètre s'applique uniquement à la suppression de l'historique et les tendances des éléments déjà supprimés.| |NodeAddress|non| | |IP ou nom d'hôte avec un port facultatif pour remplacer la manière dont l'interface doit se connecter au serveur.<br>Format : \<address\>\[:port\]<br>La priorité des adresses utilisées par l'interface pour spécifier l'adresse du serveur est : NodeAddress (1); ListenIP (si ce n'est pas 0.0.0.0 ou ::) (2); localhost (par défaut) (3)<br>Voir aussi : Paramètre HANodeName| |PidFile|non| |/tmp/zabbix\_server.pid|Nom du fichier PID.| |ProxyConfigFrequency|non|1-604800|3600|Détermine la fréquence à laquelle le serveur Zabbix envoie des données de configuration à un proxy Zabbix en quelques secondes. Utilisé uniquement pour les proxys en mode passif.| |ProblemHousekeepingFrequency|non| 1-3600|60|Détermine la fréquence à laquelle Zabbix supprimera les problèmes des déclencheurs supprimés en secondes.| |ProxyDataFrequency|non|1-3600|1|Détermine la fréquence à laquelle le serveur Zabbix demande des données d'historique à un proxy Zabbix en secondes. Utilisé uniquement pour les proxys en mode passif.| |ServiceManagerSyncFrequency|non|1-3600|60| Détermine la fréquence à laquelle Zabbix synchronisera la configuration d'un gestionnaire de services en secondes.| |SNMPTrapperFile|non| |/tmp/zabbix\_traps.tmp|Fichier temporaire utilisé pour transmettre les données du démon d'interruption SNMP au serveur.<br>Doit être le même que dans zabbix\_trap\_receiver.pl ou le fichier de configuration SNMPTT.| |SocketDir|non| |/tmp|Répertoire pour stocker les sockets IPC utilisés par les services internes de Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.4.0.| |SourceIP|non| | |Adresse IP source pour :<br>- les connexions sortantes au proxy Zabbix et à l'agent Zabbix ;<br>- les connexions sans agent (VMware, SSH, JMX, SNMP, Telnet et vérifications simples) ;<br>- les connexions de l'agent HTTP ;<br >- requêtes JavaScript d'élément de script ;<br>- prétraitement des requêtes HTTP JavaScript ;<br>- envoi d'e-mails de notification (connexions au serveur SMTP );<br>- notifications de webhook (connexions HTTP JavaScript) ;<br>- connexions au Coffre| |SSHKeyLocation|non| | |Emplacement des clés publiques et privées pour les vérifications et actions SSH| |SSLCertLocation|non| | |Emplacement des fichiers de certificat client SSL pour l'authentification client.<br>Ce paramètre est utilisé uniquement dans la surveillance Web.| |SSLKeyLocation|non| | |Emplacement des fichiers de clé privée SSL pour l'authentification du client.<br>Ce paramètre est utilisé uniquement dans la surveillance Web.| |SSLCALocation|non| | |Remplacer l'emplacement des fichiers de l'autorité de certification (CA) pour la vérification du certificat du serveur SSL. S'il n'est pas défini, le répertoire à l'échelle du système sera utilisé.<br>Notez que la valeur de ce paramètre sera définie comme option libcurl CURLOPT\_CAPATH. Pour les versions de libcurl antérieures à 7.42.0, cela n'a d'effet que si libcurl a été compilé pour utiliser OpenSSL. Pour plus d'informations, voir la [page Web cURL](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>Ce paramètre est utilisé dans la surveillance Web depuis Zabbix 2.4.0 et dans l'authentification SMTP depuis Zabbix 3.0.0.| |StartAlerters|non|1-100|3|Nombre d'instances pré-forkées d'[alerteurs](/manual/concepts/server#types_de_processus_serveur).<br>Ce paramètre est pris en charge depuis Zabbix 3.4.0.| |StartDBSyncers|non|1-100|4|Nombre d'instances pré-forkées de [synchroniseurs d'historique](/manual/concepts/server#types_de_processus_serveur).<br>*Remarque* : Soyez prudent lorsque vous modifiez cette valeur, l'augmenter peut faire plus de mal que de bien. En gros, la valeur par défaut devrait être suffisante pour gérer jusqu'à 4000 NVPS.| |StartDiscoverers|non|0-250|1|Nombre d'instances pré-forkées de [discoverers](/manual/concepts/server#types_de_processus_serveur).| |StartEscalators|non|1-100|1|Nombre d'instances pré-forkées de [escalators](/manual/concepts/server#types_de_processus_serveur).<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |StartHistoryPollers|non|0-1000|5|Nombre d'instances pré-forkées d'[interrogateurs d'historique](/manual/concepts/server#types_de_processus_serveur).<br>Ce paramètre est pris en charge depuis Zabbix 5.4.0.| |StartHTTPPollers|non|0-1000|1|Nombre d'instances pré-forkées d'[interrogateurs HTTP](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartIPMIPollers|non|0-1000|0|Nombre d'instances pré-forkées d'[interrogateurs IPMI](/manual/concepts/server#types_de_processus_serveur).| |StartJavaPollers|non|0-1000|0|Nombre d'instances pré-forkées d'[interrogateurs Java](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartLLDProcessors|non|1-100|2|Nombre d'instances pré-forkées de [workers de découverte de bas niveau (LLD)](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.<br>Le processus du gestionnaire LLD est automatiquement lancé lorsqu'un agent LLD est démarré.<br>Ce paramètre est pris en charge depuis Zabbix 4.2.0.| |StartODBCPollers|non|0-1000|1|Nombre d'instances pré-forkées d'[interrogateurs ODBC](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartPingers|non|0-1000|1|Nombre d'instances pré-forkées de [pingers ICMP](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartPollersUnreachable|non|0-1000|1|Nombre d'instances pré-forkées d'[interrogateurs d'hôtes inaccessibles](/manual/concepts/server#types_de_processus_serveur) (y compris IPMI et Java)**^[1](zabbix_server#footnotes)^**.<br>Au moins un interrogateur pour les hôtes inaccessibles doit être en cours d'exécution si les interrogateurs réguliers, IPMI ou Java sont démarrés.| |StartPollers|non|0-1000|5|Nombre d'instances pré-forkées d'[interrogateurs](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartPreprocessors|non|1-1000|3|Nombre d'instances pré-forkées de [workers de prétraitement](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.<br> Le processus du gestionnaire de prétraitement est automatiquement démarré lorsqu'un agent de prétraitement est démarré.<br>Ce paramètre est pris en charge depuis Zabbix 3.4.0.| |StartProxyPollers|non|0-250|1|Nombre d'instances pré-forkées d'[interrogateurs pour les proxys passifs](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.| |StartReportWriters|nov|0-100|0|Nombre d'instances pré-forkées de [rédacteurs de rapports](/manual/concepts/server#types_de_processus_serveur).<br>Si défini sur 0, la génération de rapport planifiée est désactivée.<br> Le processus du gestionnaire de rapports est automatiquement lancé lorsqu'un rédacteur de rapport est lancé.<br>Ce paramètre est pris en charge depuis Zabbix 5.4.0.| |StartSNMPTrapper|non|0-1|0|Si défini sur 1, le processus [Trapper SNMP](/manual/concepts/server#types_de_processus_serveur) sera démarré.| |StartTimers|non|1-1000|1|Nombre d'instances pré-forkées de [timers](/manual/concepts/server#types_de_processus_serveur).<br>Les timers traitent les périodes de maintenance.| |StartTrappers|non|0-1000|5|Nombre d'instances pré-forkées de [trappers](/manual/concepts/server#types_de_processus_serveur)**^[1](zabbix_server#footnotes)^**.<br>Les trappers acceptent les connexions entrantes de l'expéditeur Zabbix, des agents actifs et des proxys actifs.| |StartVMwareCollectors|non|0-250|0|Nombre d'instances [VMware collector](/manual/concepts/server#types_de_processus_serveur) pré-forkées.| |StatsAllowedIP|non| | |Liste des adresses IP délimitées par des virgules, éventuellement en notation CIDR, ou noms DNS des instances Zabbix externes. Les demandes de statistiques ne seront acceptées qu'à partir des adresses indiquées ici. Si ce paramètre n'est pas défini, aucune demande de statistiques ne sera acceptée.<br>Si la prise en charge d'IPv6 est activée, '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' sont traités de la même manière et ' ::/0' autorisera n'importe quelle adresse IPv4 ou IPv6. '0.0.0.0/0' peut être utilisé pour autoriser n'importe quelle adresse IPv4.<br>Exemple : StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com <br>Ce paramètre est pris en charge depuis Zabbix 4.2.0.| |Timeout|non|1-30|3|Spécifie combien de temps les vérifications agent, de périphériques SNMP ou externes seront attendues en secondes.| |TLSCAFile|non| | |Chemin d'accès complet d'un fichier contenant les certificats CA de niveau supérieur pour la vérification des certificats par les pairs, utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCertFile|non| | |Chemin d'accès complet d'un fichier contenant le certificat du serveur ou la chaîne de certificats, utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCipherAll|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplace les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat et PSK.<br>Exemple : TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br> Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherAll13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplace les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat et PSK.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Exemple pour OpenSSL : EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherCert|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Exemple pour OpenSSL : EECDH+aRSA+AES128:RSA+aRSA+AES128<br >Ce paramètre est supporté depuis Zabbix 4.4.7.| |TLSCipherCert13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat.<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherPSK|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur PSK.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Exemple pour OpenSSL : kECDHEPSK+AES128:kPSK+AES128<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7. | |TLSCipherPSK13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur PSK.<br>Exemple : TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCRLFile|non| | |Chemin d'accès complet d'un fichier contenant des certificats révoqués. Ce paramètre est utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSKeyFile|non| | |Chemin d'accès complet d'un fichier contenant la clé privée du serveur, utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TmpDir|non| |/tmp|Répertoire temporaire.| |TrapperTimeout|non|1-300|300|Spécifie le nombre de secondes que le trappeur peut consacrer au traitement de nouvelles données.| |TrendCacheSize|non|128K-2G|4M|Taille du cache de tendances, en octets.<br>Taille de la mémoire partagée pour stocker les données de tendances.| |TrendFunctionCacheSize|non|128K-2G|4M|Taille du cache de la fonction de tendance, en octets.<br>Taille de la mémoire partagée pour la mise en cache des données de la fonction de tendance calculées.| |UnavailableDelay|non|1-3600|60|Détermine la fréquence à laquelle la disponibilité de l'hôte est vérifiée pendant la période d'[indisponibilité](/manual/appendix/items/unreachability#unavailable_host), en secondes.| |UnreachableDelay|non|1-3600|15|Détermine la fréquence à laquelle la disponibilité de l'hôte est vérifiée pendant la période d'[inaccessibilité](/manual/appendix/items/unreachability#unreachable_host) en secondes.| |UnreachablePeriod|non|1-3600|45|Détermine après combien de secondes d'[inaccessibilité](/manual/appendix/items/unreachability#unreachable_host) traiter un hôte comme indisponible.| |User|non| |zabbix|Dépôt des privilèges à un utilisateur spécifique existant sur le système.<br>N'a d'effet que s'il est exécuté en tant que 'root' et que AllowRoot est désactivé.| |ValueCacheSize|non|0,128K-64G|8M|Taille du cache de valeurs d'historique, en octets.<br>Taille de la mémoire partagée pour la mise en cache des demandes de données d'historique d'éléments.<br>Le réglage sur 0 désactive le cache de valeurs (non recommandé).<br >Lorsque le cache de valeurs s'épuise dans la mémoire partagée, un message d'avertissement est écrit dans le journal du serveur toutes les 5 minutes.| |VaultDBPath|non| | |Chemin du coffre-fort à partir duquel les informations d'identification pour la base de données seront récupérées par les clés 'password' et 'username'.<br>Exemple : secret/zabbix/database<br>Cette option ne peut être utilisée que si DBUser et DBPassword ne sont pas spécifiés.<br >Ce paramètre est supporté depuis Zabbix 5.2.0.| |VaultToken|non| | |Jeton d'authentification Vault qui a dû être généré exclusivement pour le serveur Zabbix avec une autorisation en lecture seule sur les chemins spécifiés dans les [Macros Vault](/manual/config/macros/user_macros#configuration) et une autorisation en lecture seule sur le chemin spécifié dans le paramètre de configuration facultatif VaultDBPath.<br>C'est une erreur si VaultToken et la variable d'environnement VAULT\_TOKEN sont définies en même temps.<br>Ce paramètre est pris en charge depuis Zabbix 5.2.0.| |VaultURL|non| |https://127.0.0.1:8200|URL HTTP\[S\] du serveur Vault. Le répertoire des certificats CA à l'échelle du système sera utilisé si SSLCALocation n'est pas spécifié.<br>Ce paramètre est pris en charge depuis Zabbix 5.2.0.| |VMwareCacheSize|non|256K-2G|8M|Taille de la mémoire partagée pour le stockage des données VMware.<br>Une vérification interne VMware zabbix\[vmware,buffer,...\] peut être utilisée pour surveiller l'utilisation du cache VMware (voir les [Vérifications internes](/manual/config/items/itemtypes/internal)).<br>Notez que la mémoire partagée n'est pas allouée s'il n'y a pas d'instances vmware collector configurées pour démarrer.| |VMwareFrequency|non|10-86400|60|Délai en secondes entre la collecte de données à partir d'un seul service VMware.<br>Ce délai doit être défini sur l'intervalle de mise à jour minimal de tout élément de surveillance VMware.| |VMwarePerfFrequency|non|10-86400|60|Délai en secondes entre la récupération des statistiques du compteur de performances à partir d'un seul service VMware.<br>Ce délai doit être défini sur l'intervalle de mise à jour le plus faible de tout [élément](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) de surveillance VMware qui utilise les compteurs de performances VMware.| |VMwareTimeout|non|1-300|10|Le nombre maximal de secondes pendant lesquelles le collecteur vmware attendra une réponse du service VMware (vCenter ou hyperviseur ESX).| |WebServiceURL|non| | |URL HTTP\[S\] du service Web Zabbix au format `<host:port>/report`. Par exemple : `http://localhost:10053/report`<br>Ce paramètre est pris en charge depuis Zabbix 5.4.0.| #### Parameters |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Alias|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* or *PerfCounter* parameters.<br><br>Examples:<br><br>1. Retrieving paging file usage in percents from the server.<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>Now shorthand key **pg\_usage** may be used to retrieve data.<br><br>2. Getting CPU load with default and custom parameters.<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]<br>This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load\[percpu,avg15\]** to get specific data about CPU load.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\].| |HostInterface|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no| | |Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters, performance counters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no| |system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters, performance counters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.<br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `C:\Program Files\Zabbix Agent\zabbix_agentd.d\*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| |C:\\zabbix\_agentd.log|Name of the agent log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log Windows Event Log,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server<br>or proxy processing 'log', 'logrt' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log', 'logrt' or 'eventlog' item keys.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PerfCounter|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You may run "typeperf -qx" to get list of all performance counters available in Windows.| |PerfCounterEn|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>Compared to PerfCounter, perfcounter paths must be in English.<br>Supported only on **Windows Server 2008/Vista** and above.<br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You can find the list of English strings by viewing the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>This parameter is supported since Zabbix 4.0.13 and 4.2.7.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0| | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.| |ServerActive|no|(\*)| |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-63 (\*)|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0-1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts| ::: noteclassic (\*) The number of active servers listed in ServerActive plus the number of pre-forked instances for passive checks specified in StartAgents must be less than 64. ::: #### Paramètres |Paramètre|Obligatoire|Plage|Par défaut|Description| |--|--|--|--|----------| |Alias|non| | |Définit un alias pour une clé d'élément. Il peut être utilisé pour remplacer une clé d'élément longue et complexe par une clé plus petite et plus simple.<br>Plusieurs paramètres *Alias* peuvent être présents. Plusieurs paramètres avec la même clé *Alias* sont autorisés.<br>Différentes clés *Alias* peuvent faire référence à la même clé d'élément.<br>Les alias peuvent être utilisés dans *HostMetadataItem* mais pas dans les paramètres *HostnameItem* ou *PerfCounter*. <br><br>Exemples :<br><br>1. Récupération de l'utilisation du fichier d'échange en pourcentage à partir du serveur.<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>Maintenant la clé abrégée **pg\_usage** peut être utilisé pour récupérer des données.<br><br>2. Obtenir la charge du processeur avec les paramètres par défaut et personnalisés.<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]<br> Cela permet d'utiliser la clé **cpu.load** pour obtenir le pourcentage d'utilisation du processeur avec les paramètres par défaut ainsi que d'utiliser **cpu.load\[percpu,avg15\]** pour obtenir des données spécifiques sur la charge du processeur.<br> <br>3. Exécution de plusieurs règles de [découverte de bas niveau](/manual/discovery/low_level_discovery) traitant les mêmes éléments de découverte.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Maintenant il est possible de configurer plusieurs règles de découverte en utilisant **vfs.fs.discovery** avec des paramètres différents pour chaque règle, par exemple, **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|non| | |Autoriser l'exécution des clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec DenyKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |BufferSend|non|1-3600|5|Ne pas conserver les données plus de N secondes dans le tampon.| |BufferSize|non|2-65535|100|Nombre maximal de valeurs dans une mémoire tampon. L'agent enverra<br>toutes les données collectées au serveur Zabbix ou au proxy si le tampon est plein.| |DebugLevel|non|0-5|3|Spécifie le niveau de débogage :<br>0 - informations de base sur le démarrage et l'arrêt des processus Zabbix<br>1 - informations critiques<br>2 - informations sur les erreurs<br>3 - avertissements<br>4 - pour le débogage (produit beaucoup d'informations)<br>5 - débogage étendu (produit encore plus d'informations)| |DenyKey|non| | |Refuser l'exécution de ces clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec AllowKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |EnableRemoteCommands|non| |0|Indique si les commandes à distance du serveur Zabbix sont autorisées. Ce paramètre est **obsolète**, utilisez plutôt AllowKey=system.run\[\*\] ou DenyKey=system.run\[\*\]<br>Il s'agit d'un alias interne pour les paramètres AllowKey/DenyKey en fonction de la valeur : 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\].| |HostInterface|non|0-255 caractères| |Paramètre facultatif qui définit l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur dépasse la limite de 255 caractères.<br>Si elle n'est pas définie, la valeur sera acquise à partir de HostInterfaceItem.<br>Pris en charge depuis Zabbix 4.4.0.| |HostInterfaceItem|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent consigne un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisée que lorsque HostInterface n'est pas défini.<br>Pris en charge depuis Zabbix 4.4.0.| |HostMetadata|non|0-255 caractères| |Paramètre facultatif qui définit les métadonnées de l'hôte. Les métadonnées de l'hôte sont utilisées uniquement lors du processus d'enregistrement automatique de l'hôte (agent actif).<br> Si elles ne sont pas définies, la valeur sera acquise à partir de HostMetadataItem.<br> Un agent émettra une erreur et ne démarrera pas si la valeur spécifiée dépasse la limite ou une chaîne non-UTF-8.| |HostMetadataItem|non| | |Paramètre facultatif qui définit un élément *agent Zabbix* utilisé pour obtenir les métadonnées de l'hôte. Cette option n'est utilisée que lorsque HostMetadata n'est pas défini.<br> Prend en charge les paramètres utilisateur, les compteurs de performances et les alias. Prend en charge *system.run\[\]* quelle que soit la valeur *EnableRemoteCommands*.<br>La valeur HostMetadataItem est récupérée à chaque tentative d'enregistrement automatique et est utilisée uniquement lors du processus d'enregistrement automatique de l'hôte (agent actif).<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>La valeur renvoyée par l'élément doit être une chaîne UTF-8, sinon elle sera ignorée.| |Hostname|non| |Défini par HostnameItem|Liste des noms d'hôte uniques, délimités par des virgules et sensibles à la casse.<br>Requis pour les vérifications actives et doit correspondre aux noms d'hôte tels qu'ils sont configurés sur le serveur. La valeur est acquise à partir de HostnameItem si elle n'est pas définie.<br>Caractères autorisés : alphanumérique, '.', ' ', '\_' et '-'.<br>Longueur maximale : 128 caractères par nom d'hôte, 2 048 caractères pour toute la ligne. | |HostnameItem|non| |system.hostname|Paramètre facultatif qui définit un élément *agent Zabbix* utilisé pour obtenir le nom d'hôte. Cette option n'est utilisée que lorsque le nom d'hôte n'est pas défini.<br>Ne prend pas en charge les paramètres utilisateur, les compteurs de performances ou les alias, mais prend en charge *system.run\[\]* quelle que soit la valeur *EnableRemoteCommands*.<br>La longueur de sortie est limité à 512 Ko.<br>Voir également une [description plus détaillée](/manual/appendix/install/windows_agent#configuration).| |Include|non| | |Vous pouvez inclure des fichiers individuels ou tous les fichiers d'un répertoire dans le fichier de configuration.<br>Pour n'inclure que les fichiers pertinents dans le répertoire spécifié, le caractère générique astérisque est pris en charge pour la correspondance de modèle. Par exemple : `C:\Program Files\Zabbix Agent\zabbix_agentd.d\*.conf`.<br>Voir les [notes spéciales](special_notes_include) sur les limitations.| |ListenBacklog|non|0 - INT\_MAX|SOMAXCONN|Le nombre maximal de connexions en attente dans la file d'attente TCP.<br>La valeur par défaut est une constante codée en dur, qui dépend du système.<br>La valeur maximale prise en charge dépend de système, des valeurs trop élevées peuvent être silencieusement tronquées au 'maximum spécifié par l'implémentation'.| |ListenIP|non| |0.0.0.0|Liste des adresses IP séparées par des virgules sur lesquelles l'agent doit écouter.| |ListenPort|non|1024-32767|10050|L'agent écoutera sur ce port les connexions du serveur.| |LogFile|oui, si LogType est défini sur *file*, sinon<br>non| |C:\\zabbix\_agentd.log|Nom du fichier journal de l'agent.| |LogFileSize|non|0-1024|1|Taille maximale du fichier journal en Mo.<br>0 - désactiver la rotation automatique des journaux.<br>*Remarque* : si la limite de taille du fichier journal est atteinte et que la rotation des fichiers échoue, par quelle qu'en soit la raison, le fichier journal existant est tronqué et redémarré.| |LogType|non| |file|Type de sortie du journal :<br>*file* - écrit le journal dans le fichier spécifié par le paramètre LogFile,<br>*system* - écrit le journal dans le journal des événements Windows,<br>*console* - écrit le journal dans la sortie standard.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |LogRemoteCommands|non| |0|Activer la journalisation des commandes shell exécutées en tant qu'avertissements.<br>0 - désactivé<br>1 - activé| |MaxLinesPerSecond|non|1-1000|20|Nombre maximal de nouvelles lignes que l'agent enverra par seconde au serveur Zabbix<br>ou au proxy traitant les vérifications actives 'log', 'logrt' et 'eventlog'.<br>Le fourni sera remplacée par le paramètre 'maxlines',<br>fourni dans les clés d'élément 'log', 'logrt' ou 'eventlog'.<br>*Remarque* : Zabbix traitera 10 fois plus de nouvelles lignes que défini dans *MaxLinesPerSecond* pour rechercher la chaîne requise dans les éléments de journal.| |PerfCounter|non| | |Définit un nouveau paramètre \<parameter\_name> qui est une valeur moyenne pour le compteur de performances système \<perf\_counter\_path\> pour la période de temps spécifiée \<period\> (en secondes).<br>Syntaxe : \<parameter\_name\>,"\<perf\_counter\_path\>",\<period\><br>Par exemple, si vous souhaitez recevoir le nombre moyen d'interruptions du processeur par seconde pour la dernière minute, vous pouvez définir un nouveau paramètre "interrupts" comme suit :<br >PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Veuillez noter les guillemets autour du chemin du compteur de performances.<br>Le nom du paramètre (interrupts) doit être utilisé comme clé d'élément lorsque création d'un élément.<br>Des échantillons pour le calcul de la valeur moyenne seront prélevés toutes les secondes.<br>Vous pouvez exécuter "typeperf -qx" pour obtenir la liste de tous les compteurs de performances disponibles dans Windows.| |PerfCounterEn|non| | |Définit un nouveau paramètre \<parameter\_name\> qui est une valeur moyenne pour le compteur de performances système \<perf\_counter\_path\> pour la période de temps spécifiée \<period\> (en secondes).<br>Syntaxe : \<parameter\_name\>,"\<perf\_counter\_path\>",\<period\><br>Par rapport à PerfCounter, les chemins de perfcounter doivent être en anglais.<br>Pris en charge uniquement sur **Windows Server 2008/Vista** et supérieur.<br>Par exemple , si vous souhaitez recevoir le nombre moyen d'interruptions du processeur par seconde pour la dernière minute, vous pouvez définir un nouveau paramètre "interrupts" comme suit :<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Veuillez noter les guillemets autour du chemin du compteur de performances.<br>Le nom du paramètre (interruptions) doit être utilisé comme clé d'élément lors de la création d'un élément.<br>Des échantillons pour le calcul de la valeur moyenne seront prélevés toutes les secondes. <br>Vous pouvez trouver la liste des chaînes anglaises en affichant la clé de registre suivante : `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>Ce paramètre est pris en charge depuis Zabbix 4.0.13 et 4.2.7.| |RefreshActiveChecks|non|60-3600|120|Fréquence d'actualisation de la liste des vérifications actives, en secondes.<br>Notez qu'après l'échec de l'actualisation des vérifications actives, la prochaine actualisation sera tentée après 60 secondes.| |Server|oui, si StartAgents n'est pas explicitement défini sur 0| | |Liste des adresses IP délimitées par des virgules, éventuellement en notation CIDR, ou des noms d'hôte des serveurs Zabbix.<br>Les connexions entrantes ne seront acceptées qu'à partir des hôtes répertoriés ici.<br>Si la prise en charge d'IPv6 est activée, alors '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' sont traités de la même manière et '::/0' autorisera n'importe quelle adresse IPv4 ou IPv6.<br>'0.0.0.0/0' peut être utilisé pour autoriser n'importe quelle Adresse IPv4.<br>Notez que les "adresses IPv6 compatibles IPv4" (préfixe 0000::/96) sont prises en charge mais obsolètes par [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Exemple : Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Les espaces sont autorisés.| |ServerActive|non|(\*)| |Adresse du serveur/proxy Zabbix ou configuration du cluster à partir de laquelle obtenir des vérifications actives.<br>L'adresse du serveur/proxy est l'adresse IP ou le nom DNS et le port facultatif séparés par deux-points.<br>La configuration du cluster est une ou plusieurs adresses de serveur séparées par un point-virgule. <br>Plusieurs serveurs/clusters Zabbix et proxys Zabbix peuvent être spécifiés, séparés par une virgule.<br>Plus d'un proxy Zabbix ne doit pas être spécifié à partir de chaque serveur/cluster Zabbix.<br>Si le proxy Zabbix est spécifié, alors le serveur Zabbix/ cluster pour ce proxy ne doit pas être spécifié.<br>Plusieurs adresses séparées par des virgules peuvent être fournies pour utiliser plusieurs serveurs Zabbix indépendants en parallèle. Les espaces sont autorisés.<br>Si le port n'est pas spécifié, le port par défaut est utilisé.<br>Les adresses IPv6 doivent être entre crochets si le port de cet hôte est spécifié.<br>Si le port n'est pas spécifié, les crochets pour IPv6 les adresses sont facultatives.<br>Si ce paramètre n'est pas spécifié, les vérifications actives sont désactivées.<br>Exemple pour le proxy Zabbix :<br>ServerActive=127.0.0.1:10051<br>Exemple pour plusieurs serveurs :<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Exemple de haute disponibilité :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Exemple de haute disponibilité avec deux clusters et un serveur :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|non| | |Adresse IP source pour :<br>- connexions sortantes au serveur Zabbix ou au proxy Zabbix ;<br>- établissement de connexions lors de l'exécution de certains éléments (web.page.get, net.tcp.port, etc.)| |StartAgents|non|0-63 (\*)|3|Nombre d'instances pré-forkées de zabbix\_agentd qui traitent les vérifications passives.<br>Si défini sur 0, désactive les vérifications passives et l'agent n'écoutera aucun TCP port.| |Timeout|no|1-30|3|Ne pas consacrer plus de secondes de Timeout au traitement| |TLSAccept|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | | Quelles connexions entrantes accepter. Utilisé pour un contrôle passif. Plusieurs valeurs peuvent être spécifiées, séparées par une virgule :<br>*unencrypted* - accepte les connexions sans cryptage (par défaut)<br>*psk* - accepte les connexions avec TLS et une clé pré-partagée (PSK)<br>*cert* - accepter les connexions avec TLS et un certificat<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCAFile|non| | |Chemin d'accès complet d'un fichier contenant les certificats CA de niveau supérieur pour la vérification des certificats par les pairs, utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCertFile|non| | |Chemin d'accès complet d'un fichier contenant le certificat de l'agent ou la chaîne de certificats, utilisé pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSConnect|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Comment l'agent doit se connecter au serveur ou au proxy Zabbix. Utilisé pour les vérifications actives. Une seule valeur peut être spécifiée :<br>*unencrypted* - se connecter sans chiffrement (par défaut)<br>*psk* - se connecter à l'aide de TLS et d'une clé pré-partagée (PSK)<br>*cert* - se connecter à l'aide de TLS et un certificat<br>Ce paramètre est supporté depuis Zabbix 3.0.0.| |TLSCRLFile|non| | |Chemin d'accès complet d'un fichier contenant des certificats révoqués. Ce paramètre est utilisé pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSKeyFile|non| | |Chemin d'accès complet d'un fichier contenant la clé privée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSPSKFile|non| | |Chemin d'accès complet d'un fichier contenant la clé pré-partagée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSPSKIdentity|non| | |Chaîne d'identité de clé pré-partagée, utilisée pour les communications chiffrées avec le serveur Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSServerCertIssuer|non| | |Émetteur de certificat de serveur (proxy) autorisé.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSServerCertSubject|non| | |Sujet de certificat de serveur (proxy) autorisé.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |UnsafeUserParameters|non|0-1|0|Autoriser le passage de tous les caractères dans les arguments des paramètres définis par l'utilisateur.<br>0 - ne pas autoriser<br>1 - autoriser<br>Les caractères suivants ne sont pas autorisés :<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>De plus, les caractères de retour à la ligne ne sont pas autorisés.| |UserParameter|non| | |Paramètre défini par l'utilisateur à surveiller. Il peut y avoir plusieurs paramètres définis par l'utilisateur.<br>Format : UserParameter=\<clé\>,\<commande shell\><br>Notez que la commande shell ne doit pas renvoyer de chaîne vide ou EOL uniquement.<br>Les commandes shell peuvent avoir des chemins relatifs, si le paramètre UserParameterDir est spécifié.<br>Exemples :<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|non| | |Chemin de recherche par défaut pour les commandes UserParameter. S'il est utilisé, l'agent remplacera son répertoire de travail par celui spécifié ici avant d'exécuter une commande. Ainsi, les commandes UserParameter peuvent avoir un préfixe relatif `./` au lieu d'un chemin complet.<br>Une seule entrée est autorisée.<br>Exemple : UserParameterDir=/opt/myscripts| ::: noteclassic (\*) Le nombre de serveurs actifs répertoriés dans ServerActive plus le nombre d'instances pré-forkées pour les contrôles passifs spécifiés dans StartAgents doit être inférieur à 64. ::: #### Parameters |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Alias|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |AllowRoot|no| |0|Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent will try to switch to user 'zabbix' instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\]| |HostInterface|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host [autoregistration](/manual/discovery/auto_registration#using_dns_as_default_interface) process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host [autoregistration](/manual/discovery/auto_registration#using_dns_as_default_interface) process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no| | |Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of AllowKey/DenyKey values.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no| |system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The output length is limited to 512KB.| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma delimited IP addresses that the agent should listen on.<br>Multiple IP addresses are supported in version 1.8.3 and higher.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LoadModule|no| | |Module to load at agent startup. Modules are used to extend functionality of the agent.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no| | |Full path to location of agent modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| | |Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PidFile|no| |/tmp/zabbix\_agentd.pid|Name of PID file.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0| | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.| |ServerActive|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-100|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |User|no| |zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |UserParameter|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts| #### Paramètres |Paramètre|Obligatoire|Plage|Par défaut|Description| |--|--|--|--|----------| |Alias|non| | |Définit un alias pour une clé d'élément. Il peut être utilisé pour remplacer une clé d'élément longue et complexe par une clé plus petite et plus simple.<br>Plusieurs paramètres *Alias* peuvent être présents. Plusieurs paramètres avec la même clé *Alias* sont autorisés.<br>Différentes clés *Alias* peuvent faire référence à la même clé d'élément.<br>Les alias peuvent être utilisés dans *HostMetadataItem* mais pas dans les paramètres *HostnameItem*.<br><br>Exemples :<br><br>1. Récupération de l'ID de l'utilisateur 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Maintenant, la clé abrégée **zabbix.userid** peut être utilisée pour récupérer des données.<br><br>2. Obtenir l'utilisation du processeur avec des paramètres par défaut et personnalisés.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>Cela permet d'utiliser la clé **cpu.util** pour obtenir le pourcentage d'utilisation du processeur avec les paramètres par défaut ainsi que d'utiliser **cpu.util\[all,idle,avg15\]** pour obtenir des données spécifiques sur l'utilisation du processeur.<br><br>3. Exécution de plusieurs règles de [découverte de bas niveau](/manual/discovery/low_level_discovery) traitant les mêmes éléments de découverte.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Maintenant il est possible de configurer plusieurs règles de découverte en utilisant **vfs.fs.discovery** avec des paramètres différents pour chaque règle, par exemple, **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|non| | |Autoriser l'exécution des clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec DenyKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |AllowRoot|non| |0|Autoriser l'agent à s'exécuter en tant que 'root'. S'il est désactivé et que l'agent est démarré par 'root', l'agent essaiera de passer à l'utilisateur 'zabbix' à la place. N'a aucun effet si démarré sous un utilisateur régulier.<br>0 - ne pas autoriser<br>1 - autoriser| |BufferSend|non|1-3600|5|Ne pas conserver les données plus de N secondes dans le tampon.| |BufferSize|non|2-65535|100|Nombre maximal de valeurs dans une mémoire tampon. L'agent enverra<br>toutes les données collectées au serveur Zabbix ou au proxy si le tampon est plein.| |DebugLevel|non|0-5|3|Spécifie le niveau de débogage :<br>0 - informations de base sur le démarrage et l'arrêt des processus Zabbix<br>1 - informations critiques<br>2 - informations sur les erreurs<br>3 - avertissements< br>4 - pour le débogage (produit beaucoup d'informations)<br>5 - débogage étendu (produit encore plus d'informations)| |DenyKey|non| | |Refuser l'exécution de ces clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec AllowKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |EnableRemoteCommands|non| |0|Indique si les commandes à distance du serveur Zabbix sont autorisées. Ce paramètre est **obsolète**, utilisez plutôt AllowKey=system.run\[\*\] ou DenyKey=system.run\[\*\]<br>Il s'agit d'un alias interne pour les paramètres AllowKey/DenyKey en fonction de la valeur : 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\]| |HostInterface|non|0-255 caractères| |Paramètre facultatif qui définit l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'[enregistrement automatique](/manual/discovery/auto_registration#using_dns_as_default_interface) de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur dépasse la limite de 255 caractères.<br>Si elle n'est pas définie, la valeur sera acquise à partir de HostInterfaceItem.<br>Pris en charge depuis Zabbix 4.4.0.| |HostInterfaceItem|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'[enregistrement automatique](/manual/discovery/auto_registration#using_dns_as_default_interface) de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent consigne un avertissement message si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisée que lorsque HostInterface n'est pas défini.<br>Pris en charge depuis Zabbix 4.4.0.| |HostMetadata|non|0-255 caractères| |Paramètre facultatif qui définit les métadonnées de l'hôte. Les métadonnées de l'hôte sont utilisées uniquement lors du processus d'enregistrement automatique de l'hôte (agent actif).<br> Si elles ne sont pas définies, la valeur sera acquise à partir de HostMetadataItem.<br> Un agent émettra une erreur et ne démarrera pas si la valeur spécifiée dépasse la limite ou une chaîne non-UTF-8.| |HostMetadataItem|non| | |Paramètre facultatif qui définit un élément *agent Zabbix* utilisé pour obtenir les métadonnées de l'hôte. Cette option n'est utilisée que lorsque HostMetadata n'est pas défini.<br> Prend en charge les paramètres utilisateur et les alias. Prend en charge *system.run\[\]* quelles que soient les valeurs AllowKey/DenyKey.<br>La valeur HostMetadataItem est récupérée à chaque tentative d'enregistrement automatique et est utilisée uniquement lors du processus d'enregistrement automatique de l'hôte (agent actif).<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>La valeur renvoyée par l'élément doit être une chaîne UTF-8, sinon elle sera ignorée.| |Hostname|non| |Défini par HostnameItem|Liste des noms d'hôte uniques, délimités par des virgules et sensibles à la casse.<br>Requis pour les vérifications actives et doit correspondre aux noms d'hôte tels qu'ils sont configurés sur le serveur. La valeur est acquise à partir de HostnameItem si elle n'est pas définie.<br>Caractères autorisés : alphanumérique, '.', ' ', '\_' et '-'.<br>Longueur maximale : 128 caractères par nom d'hôte, 2 048 caractères pour toute la ligne. | |HostnameItem|non| |system.hostname|Paramètre facultatif qui définit un élément *agent Zabbix* utilisé pour obtenir le nom d'hôte. Cette option n'est utilisée que lorsque le nom d'hôte n'est pas défini.<br>Ne prend pas en charge les paramètres utilisateur ou les alias, mais prend en charge *system.run\[\]* quelles que soient les valeurs AllowKey/DenyKey.<br>La longueur de sortie est limitée à 512 Ko .| |Include|non| | |Vous pouvez inclure des fichiers individuels ou tous les fichiers d'un répertoire dans le fichier de configuration.<br>Pour n'inclure que les fichiers pertinents dans le répertoire spécifié, le caractère générique astérisque est pris en charge pour la correspondance de modèle. Par exemple : `/absolute/path/to/config/files/*.conf`.<br>Voir les [notes spéciales](special_notes_include) sur les limitations.| |ListenBacklog|non|0 - INT\_MAX|SOMAXCONN|Le nombre maximal de connexions en attente dans la file d'attente TCP.<br>La valeur par défaut est une constante codée en dur, qui dépend du système.<br>La valeur maximale prise en charge dépend de système, des valeurs trop élevées peuvent être silencieusement tronquées au 'maximum spécifié par l'implémentation'.| |ListenIP|non| |0.0.0.0|Liste des adresses IP délimitées par des virgules sur lesquelles l'agent doit écouter.<br>Plusieurs adresses IP sont prises en charge dans la version 1.8.3 et supérieure.| |ListenPort|non|1024-32767|10050|L'agent écoutera sur ce port les connexions du serveur.| |LoadModule|non| | |Module à charger au démarrage de l'agent. Les modules sont utilisés pour étendre les fonctionnalités de l'agent.<br>Formats :<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module. so><br>Soit le module doit être situé dans le répertoire spécifié par LoadModulePath, soit le chemin doit précéder le nom du module. Si le chemin précédent est absolu (commence par '/'), alors LoadModulePath est ignoré.<br>Il est permis d'inclure plusieurs paramètres LoadModule.| |LoadModulePath|non| | |Chemin complet vers l'emplacement des modules de l'agent.<br>La valeur par défaut dépend des options de compilation.| |LogFile|oui, si LogType est défini sur *file*, sinon<br>non| | |Nom du fichier journal.| |LogFileSize|non|0-1024|1|Taille maximale du fichier journal en Mo.<br>0 - désactiver la rotation automatique des journaux.<br>*Remarque* : si la limite de taille du fichier journal est atteinte et que la rotation des fichiers échoue, par quelle qu'en soit la raison, le fichier journal existant est tronqué et redémarré.| |LogType|non| |file|Type de sortie du journal :<br>*file* - écrit le journal dans le fichier spécifié par le paramètre LogFile,<br>*system* - écrit le journal dans syslog,<br>*console* - écrit le journal dans la sortie standard.<br >Ce paramètre est supporté depuis Zabbix 3.0.0.| |LogRemoteCommands|non| |0|Activer la journalisation des commandes shell exécutées en tant qu'avertissements.<br>0 - désactivé<br>1 - activé<br>Les commandes seront journalisées uniquement si elles sont exécutées à distance. Les entrées de journal ne seront pas créées si system.run\[\] est lancé localement par les paramètres HostMetadataItem, HostInterfaceItem ou HostnameItem.| |MaxLinesPerSecond|non|1-1000|20|Nombre maximum de nouvelles lignes que l'agent enverra par seconde au serveur Zabbix ou au proxy lors du traitement des vérifications actives 'log' et 'eventlog'.<br>La valeur fournie sera remplacée par le paramètre 'maxlines',<br>fourni dans la clé d'élément 'log' ou 'eventlog'.<br>*Remarque* : Zabbix traitera 10 fois plus de nouvelles lignes que défini dans *MaxLinesPerSecond* pour rechercher la chaîne requise dans les éléments de journal. | |PidFile|non| |/tmp/zabbix\_agentd.pid|Nom du fichier PID.| |RefreshActiveChecks|non|60-3600|120|Fréquence d'actualisation de la liste des vérifications actives, en secondes.<br>Notez qu'après l'échec de l'actualisation des vérifications actives, la prochaine actualisation sera tentée après 60 secondes.| |Server|oui, si StartAgents n'est pas explicitement défini sur 0| | |Liste des adresses IP délimitées par des virgules, éventuellement en notation CIDR, ou des noms d'hôte des serveurs Zabbix et des proxys Zabbix.<br>Les connexions entrantes ne seront acceptées qu'à partir des hôtes répertoriés ici.<br>Si la prise en charge d'IPv6 est activée, alors '127.0.0.1 ', '::127.0.0.1', '::ffff:127.0.0.1' sont traités de la même manière et '::/0' autorisera n'importe quelle adresse IPv4 ou IPv6.<br>'0.0.0.0/0' peut être utilisé pour autoriser n'importe quelle adresse IPv4.<br>Notez que les "adresses IPv6 compatibles IPv4" (préfixe 0000 ::/96) sont prises en charge mais obsolètes par [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Exemple : Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Les espaces sont autorisés.| |ServerActive|non| | |Adresse du serveur/proxy Zabbix ou configuration du cluster à partir de laquelle obtenir des vérifications actives.<br>L'adresse du serveur/proxy est l'adresse IP ou le nom DNS et le port facultatif séparés par deux-points.<br>La configuration du cluster est une ou plusieurs adresses de serveur séparées par un point-virgule. <br>Plusieurs serveurs/clusters Zabbix et proxys Zabbix peuvent être spécifiés, séparés par une virgule.<br>Plus d'un proxy Zabbix ne doit pas être spécifié à partir de chaque serveur/cluster Zabbix.<br>Si le proxy Zabbix est spécifié, alors le serveur Zabbix/ cluster pour ce proxy ne doit pas être spécifié.<br>Plusieurs adresses séparées par des virgules peuvent être fournies pour utiliser plusieurs serveurs Zabbix indépendants en parallèle. Les espaces sont autorisés.<br>Si le port n'est pas spécifié, le port par défaut est utilisé.<br>Les adresses IPv6 doivent être entre crochets si le port de cet hôte est spécifié.<br>Si le port n'est pas spécifié, les crochets pour IPv6 les adresses sont facultatives.<br>Si ce paramètre n'est pas spécifié, les vérifications actives sont désactivées.<br>Exemple pour le proxy Zabbix :<br>ServerActive=127.0.0.1:10051<br>Exemple pour plusieurs serveurs :<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Exemple de haute disponibilité :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Exemple de haute disponibilité avec deux clusters et un serveur :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|non| | |Adresse IP source pour :<br>- connexions sortantes au serveur Zabbix ou au proxy Zabbix ;<br>- établissement de connexions lors de l'exécution de certains éléments (web.page.get, net.tcp.port, etc.)| |StartAgents|non|0-100|3|Nombre d'instances pré-forkées de zabbix\_agentd qui traitent les vérifications passives.<br>Si défini sur 0, désactive les vérifications passives et l'agent n'écoutera sur aucun port TCP.| |Timeout|non|1-30|3|Ne pas consacrer plus de secondes de Timeout au traitement.| |TLSAccept|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | | Quelles connexions entrantes accepter. Utilisé pour un contrôle passif. Plusieurs valeurs peuvent être spécifiées, séparées par une virgule :<br>*unencrypted* - accepte les connexions sans cryptage (par défaut)<br>*psk* - accepte les connexions avec TLS et une clé pré-partagée (PSK)<br>*cert* - accepter les connexions avec TLS et un certificat<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCAFile|non| | |Chemin d'accès complet d'un fichier contenant les certificats CA de niveau supérieur pour la vérification des certificats par les pairs, utilisé pour les communications chiffrées entre les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCertFile|non| | |Chemin d'accès complet d'un fichier contenant le certificat de l'agent ou la chaîne de certificats, utilisé pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSCipherAll|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat et PSK.<br>Exemple : TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br> Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherAll13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat et PSK.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Exemple pour OpenSSL : EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherCert|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Exemple pour OpenSSL : EECDH+aRSA+AES128:RSA+aRSA+AES128<br >Ce paramètre est supporté depuis Zabbix 4.4.7.| |TLSCipherCert13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur certificat.<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSCipherPSK|non| | |Chaîne de priorité GnuTLS ou chaîne de chiffrement OpenSSL (TLS 1.2). Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur PSK.<br>Exemple pour GnuTLS : NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Exemple pour OpenSSL : kECDHEPSK+AES128:kPSK+AES128<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7. | |TLSCipherPSK13|non| | |Chaîne de chiffrement pour OpenSSL 1.1.1 ou plus récent dans TLS 1.3. Remplacez les critères de sélection par défaut de la suite de chiffrement pour le chiffrement basé sur PSK.<br>Exemple : TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>Ce paramètre est pris en charge depuis Zabbix 4.4.7.| |TLSConnect|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Comment l'agent doit se connecter au serveur ou au proxy Zabbix. Utilisé pour les vérifications actives. Une seule valeur peut être spécifiée :<br>*unencrypted* - se connecter sans chiffrement (par défaut)<br>*psk* - se connecter à l'aide de TLS et d'une clé pré-partagée (PSK)<br>*cert* - se connecter à l'aide de TLS et un certificat<br>Ce paramètre est supporté depuis Zabbix 3.0.0.| |TLSCRLFile|non| | |Chemin d'accès complet d'un fichier contenant des certificats révoqués. Ce paramètre est utilisé pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSKeyFile|non| | |Chemin d'accès complet d'un fichier contenant la clé privée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSPSKFile|non| | |Chemin d'accès complet d'un fichier contenant la clé pré-partagée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSPSKIdentity|non| | |Chaîne d'identité de clé pré-partagée, utilisée pour les communications chiffrées avec le serveur Zabbix.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSServerCertIssuer|non| | |Émetteur de certificat de serveur (proxy) autorisé.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |TLSServerCertSubject|non| | |Sujet de certificat de serveur (proxy) autorisé.<br>Ce paramètre est pris en charge depuis Zabbix 3.0.0.| |UnsafeUserParameters|non|0,1|0|Autoriser le passage de tous les caractères dans les arguments des paramètres définis par l'utilisateur.<br>0 - ne pas autoriser<br>1 - autoriser<br>Les caractères suivants ne sont pas autorisés :< br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>De plus, les caractères de retour à la ligne ne sont pas autorisés.| |User|non| |zabbix|Dépôt des privilèges à un utilisateur spécifique existant sur le système.<br>N'a d'effet que s'il est exécuté en tant que 'root' et que AllowRoot est désactivé.| |UserParameter|non| | |Paramètre défini par l'utilisateur à surveiller. Il peut y avoir plusieurs paramètres définis par l'utilisateur.<br>Format : UserParameter/<key/>,/<commande shell/><br>Notez que la commande shell ne doit pas renvoyer de chaîne vide ou EOL uniquement.<br>Les commandes shell peuvent avoir des chemins relatifs, si le paramètre UserParameterDir est spécifié.<br>Exemples :<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|non| | |Chemin de recherche par défaut pour les commandes UserParameter. S'il est utilisé, l'agent remplacera son répertoire de travail par celui spécifié ici avant d'exécuter une commande. Ainsi, les commandes UserParameter peuvent avoir un préfixe relatif `./` au lieu d'un chemin complet.<br>Une seule entrée est autorisée.<br>Exemple : UserParameterDir=/opt/myscripts| #### Parameters |Parameter|<|Mandatory|Range|Default|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|<|no|1-3600|5|The time interval in seconds which determines how often values are sent from the buffer to Zabbix server.<br>Note, that if the buffer is full, the data will be sent sooner.| |BufferSize|<|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send all collected data to Zabbix server or proxy if the buffer is full.<br>This parameter should only be used if persistent buffer is disabled (*EnablePersistentBuffer=0*).| |ControlSocket|<|no| |\\\\.\\pipe\\agent.sock|The control socket, used to send runtime commands with '-R' option.| |DebugLevel|<|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|<|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|Enable usage of local persistent storage for active items.<br>0 - disabled<br>1 - enabled<br>If persistent storage is disabled, the memory buffer will be used.| |ForceActiveChecksOnStart|<|no|0-1|0 |Perform active checks immediately after restart for the first received configuration.<br>0 - disabled<br>1 - enabled<br>Also available as per plugin configuration parameter, for example: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br> Supported since Zabbix 6.0.2. | |HostInterface|<|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|<|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|<|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used at host autoregistration process.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.<br>If not defined, the value will be acquired from HostMetadataItem.| |HostMetadataItem|<|no| | |Optional parameter that defines an item used for getting host metadata. Host metadata item value is retrieved on each autoregistration attempt for host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|<|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|<|no| |system.hostname|Item used for generating Hostname if it is not defined. Ignored if Hostname is defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.| |Include|<|no| | |You may include individual files or all files in a directory in the configuration file.<br>During the installation Zabbix will create the include directory in /usr/local/etc, unless modified during the compile time.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `C:\Program Files\Zabbix Agent\zabbix_agentd.d\*.conf`.<br>Since Zabbix 6.0.0 a path can be relative to *zabbix\_agent2.win.conf* file location.<br>See [special notes](special_notes_include) about limitations.| |ListenIP|<|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.<br>The first IP address is sent to Zabbix server, if connecting to it, to retrieve the list of active checks.| |ListenPort|<|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|<|yes, if LogType is set to *file*, otherwise<br>no| |c:\\zabbix\_agent2.log|Log file name if LogType is 'file'.| |LogFileSize|<|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|<|no| |file|Specifies where log messages are written to:<br>*file* - file specified by LogFile parameter,<br>*console* - standard output.| |PersistentBufferFile|<|no| | |The file, where Zabbix Agent2 should keep SQLite database.<br>Must be a full filename.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PersistentBufferPeriod|<|no|1m-365d|1h|The time period for which data should be stored, when there is no connection to the server or proxy. Older data will be lost. Log data will be preserved.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |Plugins|<|no| | |Since Zabbix 6.0.0 most of the plugins have their own [configuration files](/manual/appendix/config/zabbix_agent2_plugins). The agent configuration file contains plugin parameters listed below.| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.<br>This parameter is supported since 4.4.2 and replaces MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.<br>This parameter is supported since 4.4.2 and replaces LogRemoteCommands.| |PluginSocket|<|no| |\\\\.\pipe\agent.plugin.sock|Path to unix socket for loadable plugin communications.| |PluginTimeout|<|no|1-30 |Global timeout |Timeout for connections with loadable plugins.| |RefreshActiveChecks|<|no|60-3600|120|How often the list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|<|yes| | |List of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Spaces are allowed.| |ServerActive|<|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StatusPort|<|no|1024-32767| |If set, agent will listen on this port for HTTP status requests (http://localhost:<port>/status).| |Timeout|<|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate| |TLSCAFile|<|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.| |TLSCertFile|<|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.| |TLSConnect|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate| |TLSCRLFile|<|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.| |TLSKeyFile|<|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.| |TLSPSKFile|<|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.| |TLSPSKIdentity|<|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.| |TLSServerCertIssuer|<|no| | |Allowed server (proxy) certificate issuer.| |TLSServerCertSubject|<|no| | |Allowed server (proxy) certificate subject.| |UnsafeUserParameters|<|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|<|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts| #### Paramètres |Paramètre|<|Obligatoire|Plage|Défaut|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|non| | |Définit un alias pour une clé d'élément. Il peut être utilisé pour remplacer une clé d'élément longue et complexe par une clé plus petite et plus simple.<br>Plusieurs paramètres *Alias* peuvent être présents. Plusieurs paramètres avec la même clé *Alias* sont autorisés.<br>Différentes clés *Alias* peuvent faire référence à la même clé d'élément.<br>Les alias peuvent être utilisés dans *HostMetadataItem* mais pas dans les paramètres *HostnameItem*.<br><br>Exemples :<br><br>1. Récupération de l'ID de l'utilisateur 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Désormais, la clé abrégée **zabbix.userid** peut être utilisée pour récupérer des données.<br><br>2. Obtenir l'utilisation du processeur avec des paramètres par défaut et personnalisés.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>Cela permet d'utiliser la clé **cpu.util** pour obtenir le pourcentage d'utilisation du processeur avec les paramètres par défaut ainsi que d'utiliser **cpu.util\[all, idle, avg15\]** pour obtenir des données spécifiques sur l'utilisation du processeur.<br><br>3. Exécution de plusieurs règles de [découverte de bas niveau](/manual/discovery/low_level_discovery) traitant les mêmes éléments de découverte.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Il est désormais possible de configurer plusieurs règles de découverte à l'aide de **vfs.fs.discovery** avec des paramètres différents pour chaque règle, par exemple, **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|non| | |Autoriser l'exécution des clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec DenyKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |BufferSend|<|non|1-3600|5|L'intervalle de temps en secondes qui détermine la fréquence à laquelle les valeurs sont envoyées du tampon au serveur Zabbix.<br>Notez que si le tampon est plein, les données seront envoyées plus tôt.| |BufferSize|<|non|2-65535|100|Nombre maximal de valeurs dans une mémoire tampon. L'agent enverra toutes les données collectées au serveur Zabbix ou au proxy si le tampon est plein.<br>Ce paramètre ne doit être utilisé que si le tampon persistant est désactivé (*EnablePersistentBuffer=0*).| |ControlSocket|<|non| |\\\\.\\pipe\\agent.sock|Le socket de contrôle, utilisé pour envoyer des commandes d'exécution avec l'option '-R'.| |DebugLevel|<|non|0-5|3|Spécifie le niveau de débogage :<br>0 - informations de base sur le démarrage et l'arrêt des processus Zabbix<br>1 - informations critiques<br>2 - informations sur les erreurs<br>3 - avertissements<br>4 - pour le débogage (produit beaucoup d'informations)<br>5 - débogage étendu (produit encore plus d'informations)| |DenyKey|<|non| | |Refuser l'exécution de ces clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec AllowKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est supporté depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|non|0-1|0|Activer l'utilisation du stockage persistant local pour les éléments actifs.<br>0 - désactivé<br>1 - activé<br>Si le stockage persistant est désactivé, la mémoire tampon sera utilisée.| |ForceActiveChecksOnStart|<|non|0-1|0 |Effectuer des vérifications actives immédiatement après le redémarrage pour la première configuration reçue.<br>0 - désactivé<br>1 - activé<br>Également disponible selon le paramètre de configuration du plug-in, par exemple : `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br> Pris en charge depuis Zabbix 6.0.2. | |HostInterface|<|non|0-255 characters| |Paramètre facultatif qui définit l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur dépasse la limite de 255 caractères.<br>Si elle n'est pas définie, la valeur sera acquise à partir de HostInterfaceItem.<br>Pris en charge depuis Zabbix 4.4.0.| |HostInterfaceItem|<|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisée que lorsque HostInterface n'est pas défini.<br>Pris en charge depuis Zabbix 4.4.0.| |HostMetadata|<|non|0-255 characters| |Paramètre facultatif qui définit les métadonnées de l'hôte. Les métadonnées de l'hôte sont utilisées lors du processus d'enregistrement automatique de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur spécifiée dépasse la limite ou une chaîne non UTF-8.<br>Si elle n'est pas définie, la valeur sera acquise de HostMetadataItem.| |HostMetadataItem|<|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir les métadonnées de l'hôte. La valeur de l'élément de métadonnées de l'hôte est récupérée à chaque tentative d'enregistrement automatique pour le processus d'enregistrement automatique de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisé que lorsque HostMetadata n'est pas défini.<br>Prend en charge les paramètres utilisateur et les alias. Prend en charge *system.run\[\]* quelle que soit la valeur de *EnableRemoteCommands*.<br>La valeur renvoyée par l'élément doit être une chaîne UTF-8, sinon elle sera ignorée.| |Hostname|<|non| |Défini par HostnameItem|Liste des noms d'hôte uniques, délimités par des virgules et sensibles à la casse.<br>Requis pour les vérifications actives et doit correspondre aux noms d'hôte tels qu'ils sont configurés sur le serveur. La valeur est acquise à partir de HostnameItem si elle n'est pas définie.<br>Caractères autorisés : alphanumérique, '.', ' ', '\_' et '-'.<br>Longueur maximale : 128 caractères par nom d'hôte, 2 048 caractères pour toute la ligne. | |HostnameItem|<|non| |system.hostname|Elément utilisé pour générer le nom d'hôte s'il n'est pas défini. Ignoré si le nom d'hôte est défini.<br>Ne prend pas en charge les paramètres utilisateur ou les alias, mais prend en charge *system.run\[\]* quelle que soit la valeur de *EnableRemoteCommands*.<br>La longueur de sortie est limitée à 512 Ko.| |Include|<|non| | |Vous pouvez inclure des fichiers individuels ou tous les fichiers d'un répertoire dans le fichier de configuration.<br>Pendant l'installation, Zabbix créera le répertoire d'inclusion dans /usr/local/etc, sauf modification pendant la compilation.<br>Pour n'inclure que les fichiers pertinents fichiers dans le répertoire spécifié, le caractère générique astérisque est pris en charge pour la correspondance de modèle. Par exemple : `C:\Program Files\Zabbix Agent\zabbix_agentd.d\*.conf`.<br>Depuis Zabbix 6.0.0, un chemin peut être relatif à l'emplacement du fichier *zabbix\_agent2.win.conf*.<br >Voir les [notes spéciales](special_notes_include) sur les limitations.| |ListenIP|<|non| |0.0.0.0|Liste des adresses IP délimitées par des virgules sur lesquelles l'agent doit écouter.<br>La première adresse IP est envoyée au serveur Zabbix, s'il s'y connecte, pour récupérer la liste des vérifications actives.| |ListenPort|<|non|1024-32767|10050|L'agent écoutera sur ce port les connexions du serveur.| |LogFile|<|oui, si LogType est défini sur *file*, sinon<br>non| |c:\\zabbix\_agent2.log|Nom du fichier journal si LogType est 'file'.| |LogFileSize|<|non|0-1024|1|Taille maximale du fichier journal en Mo.<br>0 - désactive la rotation automatique du journal.<br>*Remarque* : si la limite de taille du fichier journal est atteinte et que la rotation du fichier échoue, pour quelque raison que ce soit, le fichier journal existant est tronqué et démarré nouveau.| |LogType|<|non| |file|Spécifie où les messages du journal sont écrits :<br>*file* - fichier spécifié par le paramètre LogFile,<br>*console* - sortie standard.| |PersistentBufferFile|<|non| | |Le fichier, où Zabbix Agent2 doit conserver la base de données SQLite.<br>Doit être un nom de fichier complet.<br>Ce paramètre n'est utilisé que si le tampon persistant est activé (*EnablePersistentBuffer=1*).| |PersistentBufferPeriod|<|non|1m-365d|1h|La période pendant laquelle les données doivent être stockées, lorsqu'il n'y a pas de connexion au serveur ou au proxy. Les anciennes données seront perdues. Les données du journal seront conservées.<br>Ce paramètre n'est utilisé que si le tampon persistant est activé (*EnablePersistentBuffer=1*).| |Plugins|<|non| | |Depuis Zabbix 6.0.0, la plupart des plugins ont leurs propres [fichiers de configuration](/manual/appendix/config/zabbix_agent2_plugins). Le fichier de configuration de l'agent contient les paramètres de plug-in répertoriés ci-dessous.| | |Plugins.Log.MaxLinesPerSecond|non|1-1000|20|Nombre maximum de nouvelles lignes que l'agent enverra par seconde au serveur Zabbix ou au proxy lors du traitement des vérifications actives 'log' et 'eventlog'.<br>La valeur fournie sera remplacée par le paramètre 'maxlines',<br>fourni dans la clé d'élément 'log' ou 'eventlog'.<br>*Remarque* : Zabbix traitera 10 fois plus de nouvelles lignes que défini dans *MaxLinesPerSecond* pour rechercher la chaîne requise dans les éléments de journal.<br>Ce paramètre est pris en charge depuis la version 4.4.2 et remplace MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|non| |0|Activer la journalisation des commandes shell exécutées en tant qu'avertissements.<br>0 - désactivé<br>1 - activé<br>Les commandes ne seront enregistrées que si elles sont exécutées à distance. Les entrées de journal ne seront pas créées si system.run\[\] est lancé localement par les paramètres HostMetadataItem, HostInterfaceItem ou HostnameItem.<br>Ce paramètre est pris en charge depuis 4.4.2 et remplace LogRemoteCommands.| |PluginSocket|<|non| |\\\\.\pipe\agent.plugin.sock|Chemin d'accès au socket unix pour les communications de plug-in chargeables.| |PluginTimeout|<|non|1-30 |Timeout global |Timeout pour les connexions avec des plugins chargeables.| |RefreshActiveChecks|<|non|60-3600|120|Fréquence d'actualisation de la liste des vérifications actives, en secondes.<br>Notez qu'après l'échec de l'actualisation des vérifications actives, la prochaine actualisation sera tentée après 60 secondes.| |Server|<|oui| | |Liste des adresses IP délimitées par des virgules, éventuellement en notation CIDR, ou noms DNS des serveurs Zabbix et des proxys Zabbix.<br>Les connexions entrantes ne seront acceptées qu'à partir des hôtes répertoriés ici.<br>Si la prise en charge d'IPv6 est activée, alors '127.0. 0.1', '::ffff:127.0.0.1' sont traités de la même manière et '::/0' autorisera n'importe quelle adresse IPv4 ou IPv6.<br>'0.0.0.0/0' peut être utilisé pour autoriser n'importe quelle adresse IPv4.< br>Exemple : Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Les espaces sont autorisés.| |ServerActive|<|non| | |Adresse de serveur/proxy Zabbix ou configuration de cluster à partir de laquelle obtenir des vérifications actives.<br>L'adresse de serveur/proxy est l'adresse IP ou le nom DNS et le port facultatif séparés par deux-points.<br>La configuration de cluster est une ou plusieurs adresses de serveur séparées par un point-virgule.< br>Plusieurs serveurs/clusters Zabbix et proxys Zabbix peuvent être spécifiés, séparés par une virgule.<br>Plus d'un proxy Zabbix ne doit pas être spécifié à partir de chaque serveur/cluster Zabbix.<br>Si le proxy Zabbix est spécifié, alors le serveur/cluster Zabbix pour ce proxy ne doit pas être spécifié.<br>Plusieurs adresses peuvent être fournies pour utiliser plusieurs serveurs Zabbix indépendants en parallèle. Les espaces sont autorisés.<br>Si le port n'est pas spécifié, le port par défaut est utilisé.<br>Les adresses IPv6 doivent être entre crochets si le port de cet hôte est spécifié.<br>Si le port n'est pas spécifié, les crochets pour IPv6 les adresses sont facultatives.<br>Si ce paramètre n'est pas spécifié, les vérifications actives sont désactivées.<br>Exemple pour le proxy Zabbix :<br>ServerActive=127.0.0.1:10051<br>Exemple pour plusieurs serveurs :<br>ServerActive= 127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Exemple de haute disponibilité :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Exemple de haute disponibilité avec deux clusters et un serveur :<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|non| | |Adresse IP source pour :<br>- les connexions sortantes au serveur Zabbix ou au proxy Zabbix ;<br>- l'établissement de connexions lors de l'exécution de certains éléments (web.page.get, net.tcp.port, etc.)| |StatusPort|<|non|1024-32767| |Si défini, l'agent écoutera sur ce port les demandes d'état HTTP (http://localhost:\<port\>/status).| |Timeout|<|non|1-30|3|Ne passer plus de Timeout secondes sur le traitement.| |TLSAccept|<|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Quelles connexions entrantes accepter. Utilisé pour un contrôle passif. Plusieurs valeurs peuvent être spécifiées, séparées par une virgule :<br>*unencrypted* - accepte les connexions sans cryptage (par défaut)<br>*psk* - accepte les connexions avec TLS et une clé pré-partagée (PSK)<br>*cert* - accepter les connexions avec TLS et un certificat | |TLSCAFile|<|non| | |Chemin d'accès complet d'un fichier contenant les certificats des autorités de certification de niveau supérieur pour la vérification des certificats par les pairs, utilisé pour les communications chiffrées entre les composants Zabbix.| |TLSCertFile|<|non| | |Chemin d'accès complet d'un fichier contenant le certificat de l'agent ou la chaîne de certificats, utilisé pour les communications chiffrées avec les composants Zabbix.| |TLSConnect|<|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Comment l'agent doit se connecter au serveur ou au proxy Zabbix. Utilisé pour les vérifications actives. Une seule valeur peut être spécifiée :<br>*unencrypted* - se connecter sans chiffrement (par défaut)<br>*psk* - se connecter à l'aide de TLS et d'une clé pré-partagée (PSK)<br>*cert* - se connecter à l'aide de TLS et un certificat| |TLSCRLFile|<|non| | |Chemin d'accès complet d'un fichier contenant des certificats révoqués. Ce paramètre est utilisé pour les communications chiffrées avec les composants Zabbix.| |TLSKeyFile|<|non| | |Chemin d'accès complet d'un fichier contenant la clé privée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.| |TLSPSKFile|<|non| | |Nom de chemin complet d'un fichier contenant la clé pré-partagée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.| |TLSPSKIdentity|<|non| | |Chaîne d'identité de clé pré-partagée, utilisée pour les communications chiffrées avec le serveur Zabbix.| |TLSServerCertIssuer|<|non| | |Émetteur de certificat de serveur (proxy) autorisé.| |TLSServerCertSubject|<|non| | |Sujet du certificat de serveur (proxy) autorisé.| |UnsafeUserParameters|<|non|0,1|0|Autoriser la transmission de tous les caractères dans les arguments des paramètres définis par l'utilisateur.<br>Les caractères suivants ne sont pas autorisés :<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>De plus, les caractères de retour à la ligne ne sont pas autorisés.| |UserParameter|<|non| | |Paramètre défini par l'utilisateur à surveiller. Il peut y avoir plusieurs paramètres définis par l'utilisateur.<br>Format : UserParameter=\<clé\>,\<commande shell\><br>Notez que la commande shell ne doit pas renvoyer de chaîne vide ou EOL uniquement.<br>Les commandes shell peuvent avoir des chemins relatifs, si le paramètre UserParameterDir est spécifié.<br>Exemples :<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|non| | |Chemin de recherche par défaut pour les commandes UserParameter. S'il est utilisé, l'agent remplacera son répertoire de travail par celui spécifié ici avant d'exécuter une commande. Ainsi, les commandes UserParameter peuvent avoir un préfixe relatif `./` au lieu d'un chemin complet.<br>Une seule entrée est autorisée.<br>Exemple : UserParameterDir=/opt/myscripts| #### Parameters |Parameter|<|Mandatory|Range|Default|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|<|no|1-3600|5|The time interval in seconds which determines how often values are sent from the buffer to Zabbix server.<br>Note, that if the buffer is full, the data will be sent sooner.| |BufferSize|<|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send all collected data to Zabbix server or proxy if the buffer is full.<br>This parameter should only be used if persistent buffer is disabled (*EnablePersistentBuffer=0*).| |ControlSocket| |no| |/tmp/agent.sock|The control socket, used to send runtime commands with '-R' option.| |DebugLevel|<|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|<|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|Enable usage of local persistent storage for active items.<br>0 - disabled<br>1 - enabled<br>If persistent storage is disabled, the memory buffer will be used.| |ForceActiveChecksOnStart|<|no|0-1|0 |Perform active checks immediately after restart for the first received configuration.<br>0 - disabled<br>1 - enabled<br>Also available as per plugin configuration parameter, for example: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br> Supported since Zabbix 6.0.2. | |HostInterface| |no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|<|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|<|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used at host autoregistration process.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.<br>If not defined, the value will be acquired from HostMetadataItem.| |HostMetadataItem|<|no| | |Optional parameter that defines an item used for getting host metadata. Host metadata item value is retrieved on each autoregistration attempt for host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|<|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|<|no| |system.hostname|Item used for generating Hostname if it is not defined. Ignored if Hostname is defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The output length is limited to 512KB.| |Include| |no| | |You may include individual files or all files in a directory in the configuration file.<br>During the installation Zabbix will create the include directory in /usr/local/etc, unless modified during the compile time.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>Since Zabbix 6.0.0 a path can be relative to *zabbix\_agent2.conf* file location.<br>See [special notes](special_notes_include) about limitations.| |ListenIP|<|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.<br>The first IP address is sent to Zabbix server, if connecting to it, to retrieve the list of active checks.| |ListenPort|<|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|<|yes, if LogType is set to *file*, otherwise<br>no| |/tmp/zabbix\_agent2.log|Log file name if LogType is 'file'.| |LogFileSize|<|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|<|no| |file|Specifies where log messages are written to:<br>*system* - syslog,<br>*file* - file specified by LogFile parameter,<br>*console* - standard output.| |PersistentBufferFile|<|no| | |The file, where Zabbix Agent2 should keep SQLite database.<br>Must be a full filename.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PersistentBufferPeriod| |no|1m-365d|1h|The time period for which data should be stored, when there is no connection to the server or proxy. Older data will be lost. Log data will be preserved.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PidFile|<|no| |/tmp/zabbix\_agent2.pid|Name of PID file.| |Plugin|<|no| | |Since Zabbix 6.0.0 most of the plugins have their own [configuration files](/manual/appendix/config/zabbix_agent2_plugins). The agent configuration file contains plugin parameters listed below.| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.<br>This parameter is supported since 4.4.2 and replaces MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.<br>This parameter is supported since 4.4.2 and replaces LogRemoteCommands.| |PluginSocket|<|no| |/tmp/agent.plugin.sock |Path to Unix socket for loadable plugin communications.| |PluginTimeout|<|no|1-30 |Global timeout |Timeout for connections with loadable plugins.| |RefreshActiveChecks|<|no|60-3600|120|How often the list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|<|yes| | |List of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Spaces are allowed.| |ServerActive|<|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StatusPort|<|no|1024-32767| |If set, agent will listen on this port for HTTP status requests (http://localhost:<port>/status).| |Timeout|<|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate| |TLSCAFile|<|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.| |TLSCertFile|<|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.| |TLSConnect|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate| |TLSCRLFile|<|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.| |TLSKeyFile|<|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.| |TLSPSKFile|<|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.| |TLSPSKIdentity|<|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.| |TLSServerCertIssuer|<|no| | |Allowed server (proxy) certificate issuer.| |TLSServerCertSubject|<|no| | |Allowed server (proxy) certificate subject.| |UnsafeUserParameters|<|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|<|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts| #### Paramètres |Paramètre|<|Obligatoire|Plage|Défaut|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|non| | |Définir un alias pour une clé d'élément. Il peut être utilisé pour remplacer une clé d'élément longue et complexe par une clé plus petite et plus simple.<br>Plusieurs paramètres *Alias* peuvent être présents. Plusieurs paramètres avec la même clé *Alias* sont autorisés.<br>Différentes clés *Alias* peuvent faire référence à la même clé d'élément.<br>Les alias peuvent être utilisés dans *HostMetadataItem* mais pas dans les paramètres *HostnameItem*.<br><br>Exemples :<br><br>1. Récupération de l'ID de l'utilisateur 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Désormais, la clé abrégée **zabbix.userid** peut être utilisée pour récupérer des données.<br><br>2. Obtenir l'utilisation du processeur avec des paramètres par défaut et personnalisés.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>Cela permet d'utiliser la clé **cpu.util** pour obtenir le pourcentage d'utilisation du processeur avec les paramètres par défaut ainsi que d'utiliser **cpu.util\[all, idle, avg15\]** pour obtenir des données spécifiques sur l'utilisation du processeur.<br><br>3. Exécution de plusieurs règles de [découverte de bas niveau](/manual/discovery/low_level_discovery) traitant les mêmes éléments de découverte.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Il est désormais possible de configurer plusieurs règles de découverte à l'aide de **vfs.fs.discovery** avec des paramètres différents pour chaque règle, par exemple,**vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|non| | |Autoriser l'exécution des clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec DenyKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |BufferSend|<|non|1-3600|5|L'intervalle de temps en secondes qui détermine la fréquence à laquelle les valeurs sont envoyées du tampon au serveur Zabbix.<br>Notez que si le tampon est plein, les données seront envoyées plus tôt.| |BufferSize|<|non|2-65535|100|Nombre maximal de valeurs dans une mémoire tampon. L'agent enverra toutes les données collectées au serveur Zabbix ou au proxy si le tampon est plein.<br>Ce paramètre ne doit être utilisé que si le tampon persistant est désactivé (*EnablePersistentBuffer=0*).| |ControlSocket| |non| |/tmp/agent.sock|Le socket de contrôle, utilisé pour envoyer des commandes d'exécution avec l'option '-R'.| |DebugLevel|<|non|0-5|3|Spécifier le niveau de débogage :<br>0 - informations de base sur le démarrage et l'arrêt des processus Zabbix<br>1 - informations critiques<br>2 - informations sur les erreurs<br>3 - avertissements<br>4 - pour le débogage (produit beaucoup d'informations)<br>5 - débogage étendu (produit encore plus d'informations)| |DenyKey|<|non| | |Refuser l'exécution de ces clés d'élément qui correspondent à un modèle. Le modèle de clé est une expression générique qui prend en charge le caractère "\*" pour correspondre à n'importe quel nombre de caractères.<br> Plusieurs règles de correspondance de clé peuvent être définies en combinaison avec AllowKey. Les paramètres sont traités un par un selon leur ordre d'apparition.<br>Ce paramètre est pris en charge depuis Zabbix 5.0.0.<br>Voir aussi : [Restriction des vérifications d'agent](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|non|0-1|0|Activer l'utilisation du stockage persistant local pour les éléments actifs.<br>0 - désactivé<br>1 - activé<br>Si le stockage persistant est désactivé, la mémoire tampon sera utilisée.| |ForceActiveChecksOnStart|<|non|0-1|0 |Effectuer des vérifications actives immédiatement après le redémarrage pour la première configuration reçue.<br>0 - désactivé<br>1 - activé<br>Également disponible selon le paramètre de configuration du plug-in, par exemple : `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br>Pris en charge depuis Zabbix 6.0.2. | |HostInterface| |non|0-255 caractères| |Paramètre facultatif qui définit l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur dépasse la limite de 255 caractères.<br>Si elle n'est pas définie, valeur sera acquis à partir de HostInterfaceItem.<br>Pris en charge depuis Zabbix 4.4.0.| |HostInterfaceItem|<|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir l'interface hôte.<br>L'interface hôte est utilisée lors du processus d'enregistrement automatique de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisée que lorsque HostInterface n'est pas défini.<br>Pris en charge depuis Zabbix 4.4.0.| |HostMetadata|<|non|0-255 caractères| |Paramètre facultatif qui définit les métadonnées de l'hôte. Les métadonnées de l'hôte sont utilisées lors du processus d'enregistrement automatique de l'hôte.<br>Un agent émettra une erreur et ne démarrera pas si la valeur spécifiée dépasse la limite ou une chaîne non UTF-8.<br>Si elle n'est pas définie, la valeur sera acquise de HostMetadataItem.| |HostMetadataItem|<|non| | |Paramètre facultatif qui définit un élément utilisé pour obtenir les métadonnées de l'hôte. La valeur de l'élément de métadonnées de l'hôte est récupérée à chaque tentative d'enregistrement automatique pour le processus d'enregistrement automatique de l'hôte.<br>Lors d'une demande d'enregistrement automatique, un agent enregistrera un message d'avertissement si la valeur renvoyée par l'élément spécifié dépasse la limite de 255 caractères.<br>Cette option n'est utilisé que lorsque HostMetadata n'est pas défini.<br> Prend en charge les paramètres utilisateur et les alias. Prend en charge *system.run\[\]* quelles que soient les valeurs AllowKey/DenyKey.<br>La valeur renvoyée par l'élément doit être une chaîne UTF-8, sinon elle sera ignorée.| |Hostname|<|non| |Défini par HostnameItem|Liste des noms d'hôte uniques, délimités par des virgules et sensibles à la casse.<br>Requis pour les vérifications actives et doit correspondre aux noms d'hôte tels qu'ils sont configurés sur le serveur. La valeur est acquise à partir de HostnameItem si elle n'est pas définie.<br>Caractères autorisés : alphanumérique, '.', ' ', '\_' et '-'.<br>Longueur maximale : 128 caractères par nom d'hôte, 2 048 caractères pour toute la ligne. | |HostnameItem|<|non| |system.hostname|Élément utilisé pour générer le nom d'hôte s'il n'est pas défini. Ignoré si le nom d'hôte est défini.<br>Ne prend pas en charge les paramètres utilisateur ou les alias, mais prend en charge *system.run\[\]* quelles que soient les valeurs AllowKey/DenyKey.<br>La longueur de sortie est limitée à 512 Ko.| |Include| |non| | |Vous pouvez inclure des fichiers individuels ou tous les fichiers d'un répertoire dans le fichier de configuration.<br>Pendant l'installation, Zabbix créera le répertoire d'inclusion dans /usr/local/etc, sauf modification pendant la compilation.<br>Pour n'inclure que les fichiers pertinents fichiers dans le répertoire spécifié, le caractère générique astérisque est pris en charge pour la correspondance de modèle. Par exemple: `/absolute/path/to/config/files/*.conf`.<br>Depuis Zabbix 6.0.0, un chemin peut être relatif à l'emplacement du fichier *zabbix\_agent2.conf*.<br>Voir les [notes spéciales](special_notes_include) sur connaitres les limitations.| |ListenIP|<|non| |0.0.0.0|Liste des adresses IP délimitées par des virgules sur lesquelles l'agent doit écouter.<br>La première adresse IP est envoyée au serveur Zabbix, s'il s'y connecte, pour récupérer la liste des vérifications actives.| |ListenPort|<|non|1024-32767|10050|L'agent écoutera sur ce port les connexions du serveur.| |LogFile|<|oui, si LogType est défini sur *file*, sinon<br>non| |/tmp/zabbix\_agent2.log|Nom du fichier journal si LogType est 'file'.| |LogFileSize|<|non|0-1024|1|Taille maximale du fichier journal en Mo.<br>0 - désactive la rotation automatique du journal.<br>*Remarque* : si la limite de taille du fichier journal est atteinte et que la rotation du fichier échoue, pour quelque raison que ce soit, le fichier journal existant est tronqué et démarré nouveau.| |LogType|<|non| |file|Spécifier où les messages du journal sont écrits :<br>*system* - syslog,<br>*file* - fichier spécifié par le paramètre LogFile,<br>*console* - sortie standard.| |PersistentBufferFile|<|non| | |Le fichier, où l'agent Zabbix 2 doit conserver la base de données SQLite.<br>Doit être un nom de fichier complet.<br>Ce paramètre n'est utilisé que si le tampon persistant est activé(*EnablePersistentBuffer=1*).| |PersistentBufferPeriod| |non|1m-365d|1h|La période pendant laquelle les données doivent être stockées, lorsqu'il n'y a pas de connexion au serveur ou au proxy. Les anciennes données seront perdues. Les données du journal seront conservées.<br>Ce paramètre n'est utilisé que si le tampon persistant est activé (*EnablePersistentBuffer=1*).| |PidFile|<|non| |/tmp/zabbix\_agent2.pid|Nom du fichier PID.| |Plugin|<|non| | |Depuis Zabbix 6.0.0, la plupart des plugins ont leurs propres [fichiers de configuration](/manual/appendix/config/zabbix_agent2_plugins). Le fichier de configuration de l'agent contient les paramètres de plug-in répertoriés ci-dessous.| | |Plugins.Log.MaxLinesPerSecond|non|1-1000|20|Nombre maximum de nouvelles lignes que l'agent enverra par seconde au serveur Zabbix ou au proxy lors du traitement des vérifications actives 'log' et 'eventlog'.<br>La valeur fournie sera remplacée par le paramètre 'maxlines',<br>fourni dans la clé d'élément log' ou 'eventlog'.<br>*Remarque* : Zabbix traitera 10 fois plus de nouvelles lignes que défini dans *MaxLinesPerSecond* pour rechercher la chaîne requise dans les éléments de journal.<br>Ce paramètre est pris en charge depuis la version 4.4.2 et remplace MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|non| |0|Activer la journalisation des commandes shell exécutées en tant qu'avertissements.<br>0 - désactivé<br>1 - activé<br>Les commandes ne seront enregistrées que si elles sont exécutées à distance. Les entrées de journal ne seront pas créées si system.run\[\] est lancé localement par les paramètres HostMetadataItem, HostInterfaceItem ou HostnameItem.<br>Ce paramètre est pris en charge depuis 4.4.2 et remplace LogRemoteCommands.| |PluginSocket|<|non| |/tmp/agent.plugin.sock |Chemin d'accès au socket Unix pour les communications de plug-in chargeables.| |PluginTimeout|<|non|1-30 |Délai d'expiration global |Délai d'attente pour les connexions avec des plugins chargeables.| |RefreshActiveChecks|<|non|60-3600|120|Fréquence d'actualisation de la liste des vérifications actives, en secondes.<br>Notez qu'après l'échec de l'actualisation des vérifications actives, la prochaine actualisation sera tentée après 60 secondes.| |Server|<|oui| | |Liste des adresses IP délimitées par des virgules, éventuellement en notation CIDR, ou noms DNS des serveurs Zabbix et des proxys Zabbix.<br>Les connexions entrantes ne seront acceptées qu'à partir des hôtes répertoriés ici.<br>Si la prise en charge d'IPv6 est activée, alors '127.0. 0.1', '::ffff:127.0.0.1' sont traités de la même manière et '::/0' autorisera n'importe quelle adresse IPv4 ou IPv6.<br>'0.0.0.0/0' peut être utilisé pour autoriser n'importe quelle adresse IPv4.< br>Exemple : Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Les espaces sont autorisés.| |ServerActive|<|non| | |Adresse de serveur/proxy Zabbix ou configuration de cluster à partir de laquelle obtenir des vérifications actives.<br>L'adresse de serveur/proxy est l'adresse IP ou le nom DNS et le port facultatif séparés par deux-points.<br>La configuration de cluster est une ou plusieurs adresses de serveur séparées par un point-virgule.< br>Plusieurs serveurs/clusters Zabbix et proxys Zabbix peuvent être spécifiés, séparés par une virgule.<br>Plus d'un proxy Zabbix ne doit pas être spécifié à partir de chaque serveur/cluster Zabbix.<br>Si le proxy Zabbix est spécifié, alors le serveur/cluster Zabbix pour ce proxy ne doit pas être spécifié.<br>Plusieurs adresses délimitées par des virgules peuvent être fournies pour utiliser plusieurs serveurs Zabbix indépendants en parallèle. Les espaces sont autorisés.<br>Si le port n'est pas spécifié, le port par défaut est utilisé.<br>Les adresses IPv6 doivent être entre crochets si le port de cet hôte est spécifié.<br>Si le port n'est pas spécifié, les crochets pour les adresses IPv6 sont facultatifs.<br> Si ce paramètre n'est pas spécifié, les vérifications actives sont désactivées.<br>Exemple pour le proxy Zabbix:<br>ServerActive=127.0.0.1:10051<br>Exemple pour plusieurs serveurs:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Exemple de haute disponibilité:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Exemple de haute disponibilité avec deux clusters et un serveur:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|non| | |Adresse IP source pour :<br>- les connexions sortantes au serveur Zabbix ou au proxy Zabbix ;<br>- l'établissement de connexions lors de l'exécution de certains éléments (web.page.get, net.tcp.port, etc.)| |StatusPort|<|non|1024-32767| |S'il est défini, l'agent écoutera sur ce port les demandes d'état HTTP (http://localhost:<port>/status).| |Timeout|<|non|1-30|3|Ne pas passer plus de Timeout secondes sur le traitement.| |TLSAccept|<|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Quelles connexions entrantes accepter. Utilisé pour un contrôle passif. Plusieurs valeurs peuvent être spécifiées, séparées par une virgule :<br>*unencrypted* - accepte les connexions sans cryptage (par défaut)<br>*psk* - accepte les connexions avec TLS et une clé pré-partagée (PSK)<br>*cert* - accepter les connexions avec TLS et un certificat | |TLSCAFile|<|non| | |Chemin d'accès complet d'un fichier contenant les certificats des autorités de certification de niveau supérieur pour la vérification des certificats par les pairs, utilisé pour les communications chiffrées entre les composants Zabbix.| |TLSCertFile|<|non| | |Chemin d'accès complet d'un fichier contenant le certificat de l'agent ou la chaîne de certificats, utilisé pour les communications chiffrées avec les composants Zabbix.| |TLSConnect|<|oui, si le certificat TLS ou les paramètres PSK sont définis (même pour une connexion *non cryptée*), sinon non| | |Comment l'agent doit se connecter au serveur ou au proxy Zabbix. Utilisé pour les vérifications actives. Une seule valeur peut être spécifiée :<br>*unencrypted* - se connecter sans chiffrement (par défaut)<br>*psk* - se connecter à l'aide de TLS et d'une clé pré-partagée (PSK)<br>*cert* - se connecter à l'aide de TLS et un certificat| |TLSCRLFile|<|non| | |Chemin d'accès complet d'un fichier contenant des certificats révoqués. Ce paramètre est utilisé pour les communications chiffrées avec les composants Zabbix.| |TLSKeyFile|<|non| | |Chemin d'accès complet d'un fichier contenant la clé privée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.| |TLSPSKFile|<|non| | |Chemin d'accès complet d'un fichier contenant la clé pré-partagée de l'agent utilisée pour les communications chiffrées avec les composants Zabbix.| |TLSPSKIdentity|<|non| | |Chaîne d'identité de clé pré-partagée, utilisée pour les communications chiffrées avec le serveur Zabbix.| |TLSServerCertIssuer|<|non| | |Émetteur de certificat de serveur (proxy) autorisé.| |TLSServerCertSubject|<|non| | |Sujet du certificat de serveur (proxy) autorisé.| |UnsafeUserParameters|<|non|0,1|0|Autoriser la transmission de tous les caractères dans les arguments des paramètres définis par l'utilisateur.<br>Les caractères suivants ne sont pas autorisés :<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>De plus, les caractères de retour à la ligne ne sont pas autorisés.| |UserParameter|<|non| | |Paramètre défini par l'utilisateur à surveiller. Il peut y avoir plusieurs paramètres définis par l'utilisateur.<br>Format : UserParameter=<clé>,<commande shell><br>Notez que la commande shell ne doit pas renvoyer de chaîne vide ou EOL uniquement.<br>Les commandes shell peuvent avoir des chemins relatifs, si le paramètre UserParameterDir est spécifié.<br>Exemples :<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|non| | |Chemin de recherche par défaut pour les commandes UserParameter. S'il est utilisé, l'agent remplacera son répertoire de travail par celui spécifié ici avant d'exécuter une commande. Ainsi, les commandes UserParameter peuvent avoir un préfixe relatif `./` au lieu d'un chemin complet.<br>Une seule entrée est autorisée.<br>Exemple : UserParameterDir=/opt/myscripts| #### Parameters Parameters in this file that could be of interest to users: - ZBX\_MIN\_PERIOD Minimum graph period, in seconds. One minute by default. - GRAPH\_YAXIS\_SIDE\_DEFAULT Default location of Y axis in simple graphs and default value for drop down box when adding items to custom graphs. Possible values: 0 - left, 1 - right. Default: 0 - ZBX\_SESSION\_NAME (available since 4.0.0) String used as the name of the Zabbix frontend session cookie. Default: zbx\_sessionid - ZBX\_DATA\_CACHE\_TTL (available since 5.2.0) TTL timeout in seconds used to invalidate data cache of [Vault response](/manual/config/secrets). Set 0 to disable Vault response caching. Default: 60 - SUBFILTER\_VALUES\_PER\_GROUP (available since 6.0.5) Number of subfilter values per group (For example, in the [latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) subfilter). Default: 1000 #### Paramètres Paramètres de ce fichier susceptibles d'intéresser les utilisateurs : - ZBX\_MIN\_PERIOD Période graphique minimale, en secondes. Une minute par défaut. - GRAPH\_YAXIS\_SIDE\_DEFAULT Emplacement par défaut de l'axe Y dans les graphiques simples et valeur par défaut de la liste déroulante lors de l'ajout d'éléments aux graphiques personnalisés. Valeurs possibles : 0 - gauche, 1 - droite. Par défaut : 0 - ZBX\_SESSION\_NAME (available since 4.0.0) Chaîne utilisée comme nom du cookie de session de l'interface Zabbix. Par défaut : zbx\_sessionid - ZBX\_DATA\_CACHE\_TTL (available since 5.2.0) Délai d'attente TTL en secondes utilisé pour invalider le cache de données de [réponse Vault](/manual/config/secrets). Définissez 0 pour désactiver la mise en cache des réponses Vault. Par défaut : 60 - SUBFILTER\_VALUES\_PER\_GROUP (available since 6.0.5) Nombre de valeurs de sous-filtre par groupe (par exemple, dans le sous-filtre [dernières données](/manual/web_interface/frontend_sections/monitoring/latest_data)). Par défaut : 1000 ### Parameters `(string/array)` IDs of hosts to return scripts for. ### Paramètres `(string/array)` ID des hôtes pour lesquels renvoyer les scripts. ### Parameters `(string/array)` Triggers to delete the trigger dependencies from. ### Paramètres `(string/array)` Déclencheurs auxquels supprimer les dépendances de déclencheurs. ### Parameters The method accepts the following parameters. |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |extend|boolean|Default value: "true". Setting it's value to "false" allows to check session without extending it's lifetime. Supported since Zabbix 4.0.| |sessionid|string|User session id.| ### Paramètres La méthode accepte les paramètres suivants. |Paramètre|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |extend|boolean|Valeur par défaut : "true". Définir sa valeur sur "false" permet de vérifier la session sans prolonger sa durée de vie. Pris en charge depuis Zabbix 4.0.| |sessionid|string|Identifiant de session utilisateur.| #### Parameter - unquoted string If the key parameter is an unquoted string, any Unicode character is allowed except comma and right square bracket (\]). Unquoted parameter cannot start with left square bracket (\[).  #### Paramètre - chaîne sans guillemet Si le paramètre clé est une chaîne sans guillemet, tout caractère Unicode est autorisé sauf la virgule et le crochet de droite (\]). Le paramètre sans guillemet ne peut pas commencer avec le crochet gauche (\[).  ##### Passive and active checks Zabbix agents can perform passive and active checks. In a [passive check](/manual/appendix/items/activepassive#passive_checks) the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. [Active checks](/manual/appendix/items/activepassive#active_checks) require more complex processing. The agent must first retrieve a list of items from Zabbix server for independent processing. Then it will periodically send new values to the server. Whether to perform passive or active checks is configured by selecting the respective monitoring [item type](/manual/config/items/itemtypes/zabbix_agent). Zabbix agent processes items of type 'Zabbix agent' or 'Zabbix agent (active)'. ##### Vérifications passives et actives Les agents Zabbix peuvent effectuer des vérifications passives et actives. Dans une [vérification passive](/manual/appendix/items/activepassive#passive_checks), l'agent répond à une demande de données. Le serveur Zabbix (ou le proxy) demande des données, par exemple, la charge du processeur, et l'agent Zabbix renvoie le résultat. Les [vérifications actives](/manual/appendix/items/activepassive#active_checks) nécessitent un traitement plus complexe. L'agent doit d'abord récupérer une liste d'éléments du serveur Zabbix pour un traitement indépendant. Ensuite, il enverra périodiquement de nouvelles valeurs au serveur. Que ce soit pour effectuer des vérifications passives ou actives, cela se configure en sélectionnant un [type d'élément](/manual/config/items/itemtypes/zabbix_agent). L'agent Zabbix traite les éléments de type 'Agent Zabbix' ou 'Agent Zabbix (actif)'. #### Passive checks A passive check is a simple data request. Zabbix server or proxy asks for some data (for example, CPU load) and Zabbix agent sends back the result to the server. **Server request** For definition of header and data length please refer to [protocol details](/manual/appendix/protocols/header_datalen). <item key> **Agent response** <DATA>[\0<ERROR>] Above, the part in square brackets is optional and is only sent for not supported items. For example, for supported items: 1. Server opens a TCP connection 2. Server sends **<HEADER><DATALEN>agent.ping** 3. Agent reads the request and responds with **<HEADER><DATALEN>1** 4. Server processes data to get the value, '1' in our case 5. TCP connection is closed For not supported items: 1. Server opens a TCP connection 2. Server sends **<HEADER><DATALEN>vfs.fs.size\[/nono\]** 3. Agent reads the request and responds with **<HEADER><DATALEN>ZBX\_NOTSUPPORTED\\0Cannot obtain filesystem information: \[2\] No such file or directory** 4. Server processes data, changes item state to not supported with the specified error message 5. TCP connection is closed #### Vérifications passives Une vérification passive est une simple demande de données. Le serveur ou le proxy Zabbix demande des données (par exemple, la charge du processeur) et l'agent Zabbix renvoie le résultat au serveur. \*\*Requête du serveur \*\* Pour la définition de l'en-tête et de la longueur des données, veuillez vous reporter aux [détails du protocole](/manual/appendix/protocols/header_datalen). <item key> **Réponse de l'agent** <DATA>[\0<ERROR>] Ci-dessus, la partie entre crochets est facultative et n'est envoyée que pour les éléments non supportés. Par exemple, pour les éléments supportés : 1. Le serveur ouvre une connexion TCP 2. Le serveur envoie **<HEADER><DATALEN>agent.ping** 3. L'agent lit la requête et répond avec **<HEADER><DATALEN>1** 4. Le serveur traite les données pour obtenir la valeur, '1' dans notre cas 5. La connexion TCP est fermée Pour les éléments non supportés : 1. Le serveur ouvre une connexion TCP 2. Le serveur envoie **<HEADER><DATALEN>vfs.fs.size\[/nono\]** 3. L'agent lit la demande et répond avec **<HEADER><DATALEN>ZBX\_NOTSUPPORTED\\0Cannot obtain filesystem information: \[2\] No such file or directory** 4. Le serveur traite les données et modifie l'état de l'élément à non supporté avec le message d'erreur spécifié. 5. La connexion TCP est fermée #### Passive proxy #### Proxy passif ##### Passphrase authentication SSH checks provide two authentication methods, a user/password pair and key-file based. If you do not intend to use keys, no additional configuration is required, besides linking libssh2/libssh to Zabbix, if you're building from source. ##### Authentification par phrase secrète Les vérifications SSH fournissent deux méthodes d'authentification, un couple utilisateur/mot de passe et un fichier clé. Si vous n'avez pas l'intention d'utiliser des clés, aucune configuration supplémentaire n'est requise en plus de relier libssh2 à Zabbix, si vous installez à partir des sources. ##### Payload data definition ###### Common data These parameters are present in all requests/responses: |Name|Type|Comments| |-----|--------|----------| |id |uint32|For requests - the incrementing identifier used to link requests with responses. Unique within a request direction (i.e. from agent to plugin or from plugin to agent).<br>For responses - ID of the corresponding request.| |type|uint32|The request type.| ##### Définition des données de charge utile ###### Données communes Ces paramètres sont présents dans toutes les requêtes/réponses : |Nom|Type|Commentaires| |-----|--------|----------| |id |uint32|Pour les requêtes - l'identifiant d'incrémentation utilisé pour lier les requêtes aux réponses. Unique dans une direction de requête (c'est-à-dire d'agent à plugin ou de plugin à agent).<br>Pour les réponses - ID de la requête correspondante.| |type|uint32|Le type de requête.| ### Payload data |Type|Size|Comments| |-----|-----|----------| |Byte| Defined by the *Size* field |JSON formatted data.| ### Données de charge utile |Type|Taille|Commentaires| |-----|-----|----------| |Octet| Défini par le champ *Taille* |Données au format JSON.| ##### PCRE2 support Support for PCRE2 has been added. PCRE is still supported, but Zabbix can only be compiled with one of the libraries PCRE or PCRE2, both cannot be used at the same time. The following Zabbix installation packages have been updated and now use PCRE2: - RHEL 7 and newer - SLES (all versions) - Debian 9 and newer - Ubuntu 16.04 and newer Please note that after switching to PCRE2, you may need to update some regular expressions. In particular, the pattern ```^[\w-\.]``` needs to be changed to ```^[-\\w\\.]``` to continue working correctly - see [Known issues](manual/installation/known_issues#invalid_regular_expressions_after_switching_to_pcre2) for a more detailed explanation. ##### Support PCRE2 La prise en charge de PCRE2 a été ajoutée. PCRE est toujours pris en charge, mais Zabbix ne peut être compilé qu'avec l'une des bibliothèques PCRE ou PCRE2, les deux ne peuvent pas être utilisées en même temps. Les packages d'installation Zabbix suivants ont été mis à jour et utilisent désormais PCRE2 : - RHEL 7 et plus récent - SLES (toutes les versions) - Debian 9 et plus récent - Ubuntu 16.04 et plus récent Veuillez noter qu'après être passé à PCRE2, vous devrez peut-être mettre à jour certaines expressions régulières. En particulier, le modèle ```^[\w-\.]``` doit être remplacé par ```^[-\\w\\.]``` pour continuer à fonctionner correctement - voir [Problèmes connus] (manual/installation/known_issues#invalid_regular_expressions_after_switching_to_pcre2) pour une explication plus détaillée. #### Performance counter parameters You can deploy some PerfCounter parameters for the monitoring of Windows performance counters. For example, you can add these to the Zabbix agent configuration file: PerfCounter=UserPerfCounter1,"\Memory\Page Reads/sec",30 or PerfCounter=UserPerfCounter2,"\4\24",30 With such parameters in place, you can then simply use *UserPerfCounter1* or *UserPerfCounter2* as the keys for creating the respective items. Remember to restart Zabbix agent after making changes to the configuration file. #### Paramètres du compteur de performance Vous pouvez déployer certains paramètres PerfCounter pour la surveillance des compteurs de performance Windows . Par exemple, vous pouvez les ajouter au fichier de configuration de l'agent Zabbix : PerfCounter=UserPerfCounter1,"\Memory\Page Reads/sec",30 ou PerfCounter=UserPerfCounter2,"\4\24",30 Avec de tels paramètres en place, vous pouvez alors simplement utiliser *UserPerfCounter1* ou *UserPerfCounter2* comme clés pour créer le éléments respectifs. N'oubliez pas de redémarrer l'agent Zabbix après avoir apporté des modifications au fichier de configuration. #### Performance Using some internal items may negatively affect performance. These items are: - `zabbix[host,,items]` - `zabbix[host,,items_unsupported]` - `zabbix[hosts]` - `zabbix[items]` - `zabbix[items_unsupported]` - `zabbix[queue]` - `zabbix[requiredperformance]` - `zabbix[stats,,,queue]` - `zabbix[triggers]` The [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix) and [Queue](/manual/web_interface/frontend_sections/administration/queue) frontend sections are also affected. #### Performance L'utilisation de certains éléments internes peut nuire à la performance. Ces éléments sont : - `zabbix[host,,items]` - `zabbix[host,,items_unsupported]` - `zabbix[hosts]` - `zabbix[items]` - `zabbix[items_unsupported]` - `zabbix[queue]` - `zabbix[required_performance]` - `zabbix[stats,,,queue]` - `zabbix[triggers]` Les sections [Information système](/manual/web_interface/frontend_sections/reports/status_of_zabbix) et [File d'attente](/manual/web_interface/frontend_sections/administration/queue) de l'interface sont également affectées. ### Performing requests Once you've set up the frontend, you can use remote HTTP requests to call the API. To do that you need to send HTTP POST requests to the `api_jsonrpc.php` file located in the frontend directory. For example, if your Zabbix frontend is installed under *http://example.com/zabbix*, the HTTP request to call the `apiinfo.version` method may look like this: ```yaml POST http://example.com/zabbix/api_jsonrpc.php HTTP/1.1 Content-Type: application/json-rpc { "jsonrpc": "2.0", "method": "apiinfo.version", "id": 1, "auth": null, "params": {} } ``` The request must have the `Content-Type` header set to one of these values: `application/json-rpc`, `application/json` or `application/jsonrequest`. ### Effectuer des requêtes Une fois que vous avez configuré l'interface web, vous pouvez utiliser des requêtes HTTP distantes pour appeler l'API. Pour ce faire, vous devez envoyer des requêtes HTTP POST au fichier `api_jsonrpc.php` situé dans le répertoire frontend. Par exemple, si votre interface Zabbix est installée sous *http://exemple.com/zabbix*, la requête HTTP permettant d'appeler la méthode `apiinfo.version` peut ressembler à ceci: ``` yaml POST http://exemple.com/zabbix/api_jsonrpc.php HTTP/1.1 Content-Type: application/json-rpc { "jsonrpc": "2.0", "method": "apiinfo.version", "id": 1, "auth": null, "params": {} } ``` L'en-tête `Content-Type` de la demande doit être défini sur l'une des valeurs suivantes : `application/json-rpc`, `application/json` ou `application/jsonrequest`. #### Permissions The *Permissions* tab contains information on: - The user role. Users cannot change their own role. - The user type (User, Admin, Super Admin) that is defined in the role configuration. - Host groups the user has access to. Users of type 'User' and 'Admin' do not have access to any host groups and hosts by default. To get the access they need to be included in user groups that have access to respective host groups and hosts. - Access rights to sections and elements of Zabbix frontend, modules, and API methods. Elements to which access is allowed are displayed in green color. Light gray color means that access to the element is denied. - Rights to perform certain actions. Actions that are allowed are displayed in green color. Light gray color means that a user does not have the rights to perform this action. See the [User permissions](permissions) page for details. #### Autorisations L'onglet *Autorisations* contient des informations sur : - Le rôle de l'utilisateur. Les utilisateurs ne peuvent pas modifier leur propre rôle. - Le type d'utilisateur (utilisateur, administrateur, super administrateur) défini dans la configuration du rôle. - Groupes d'hôtes auxquels l'utilisateur a accès. Les utilisateurs de type 'Utilisateur' et 'Administrateur' n'ont accès à aucun groupe d'hôtes ni à aucun hôte par défaut. Pour obtenir l'accès, ils doivent être inclus dans des groupes d'utilisateurs qui ont accès aux groupes d'hôtes et aux hôtes respectifs. - Droits d'accès aux sections et éléments de l'interface Zabbix, des modules et des méthodes API. Les éléments auxquels l'accès est autorisé sont affichés en vert. La couleur gris clair signifie que l'accès à l'élément est refusé. - Droit d'effectuer certaines actions. Les actions autorisées sont affichées en vert. La couleur gris clair signifie qu'un utilisateur n'a pas les droits pour effectuer cette action. Voir la page [Autorisations utilisateur](autorisations) pour plus de détails. #### Permissions to dashboards Permissions to dashboards for regular users and users of 'Admin' type are limited in the following way: - They can see and clone a dashboard if they have at least READ rights to it; - They can edit and delete dashboard only if they have READ/WRITE rights to it; - They cannot change the dashboard owner. #### Autorisation des tableaux de bords es autorisations d'accès aux tableaux de bord pour les utilisateurs réguliers et les utilisateurs de type Admin Zabbix sont limitées de la manière suivante : - Ils peuvent voir et cloner un tableau de bord s'ils disposent au moins des droits LECTURE sur celui-ci ; - Ils ne peuvent modifier et supprimer le tableau de bord que s'ils disposent des droits LECTURE/ÉCRITURE sur celui-ci ; - Ils ne peuvent pas changer le propriétaire du tableau de bord. #### Permissions to host groups Access to any host data in Zabbix is granted to [user groups](/manual/config/users_and_usergroups/usergroup) on the host group level only. That means that an individual user cannot be directly granted access to a host (or host group). It can only be granted access to a host by being part of a user group that is granted access to the host group that contains the host. #### Autorisations sur les groupes d'hôtes L'accès à toutes les données de l'hôte dans Zabbix est accordé aux [groupes d'utilisateurs](/manual/config/users_and_usergroups/usergroup) au niveau du groupe d'hôtes uniquement. Cela signifie qu'un utilisateur individuel ne peut pas se voir accorder directement l'accès à un hôte (ou groupe d'hôtes). Il ne peut obtenir l'accès à un hôte qu'en faisant partie d'un groupe d'utilisateurs qui a accès au groupe d'hôtes qui contient l'hôte. ### Permission The permission object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**id**<br>(required)|string|ID of the host group to add permission to.| |**permission**<br>(required)|integer|Access level to the host group.<br><br>Possible values:<br>0 - access denied;<br>2 - read-only access;<br>3 - read-write access.| ### Autorisation L'objet d'autorisation a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**id**<br>(obligatoire)|string|ID du groupe d'hôtes auquel ajouter une autorisation.| |**permission**<br>(obligatoire)|integer|Niveau d'accès au groupe d'hôtes.<br><br>Valeurs possibles :<br>0 - accès refusé ;<br>2 - accès en lecture seule ;<br>3 - accès en lecture-écriture.| #### PHP 7.2 Zabbix frontend requires PHP version **7.2 or newer**. #### PHP 7.2 L'interface Zabbix nécessite la version PHP **7.2 ou plus récente**. #### PHP 7.2 Zabbix frontend requires PHP version **7.2 or newer**. #### PHP 7.2 L'interface Zabbix nécessite la version PHP **7.2 ou plus récente**. #### PHP 7.2 Zabbix frontend requires PHP version **7.2 or newer** starting with Zabbix 5.0. See [instructions](/manual/installation/frontend/frontend_on_debian) for installing Zabbix frontend on distributions with PHP versions below 7.2. #### PHP 7.2 L'interface Zabbix nécessite la version PHP **7.2 ou plus récente** à partir de Zabbix 5.0. Voir les [instructions](/manual/installation/frontend/frontend_on_debian) pour installer l'interface Zabbix sur les distributions avec des versions PHP inférieures à 7.2. #### PHP 7.3 opcache configuration If "opcache" is enabled in the PHP 7.3 configuration, Zabbix frontend may show a blank screen when loaded for the first time. This is a registered [PHP bug](https://bugs.php.net/bug.php?id=78015). To work around this, please set the "opcache.optimization\_level" parameter to `0x7FFFBFDF` in the PHP configuration (php.ini file). #### Configuration de l'opcache PHP 7.3 Si "opcache" est activé dans la configuration PHP 7.3, l'interface Zabbix peut afficher un écran vide lors du premier chargement. Il s'agit d'un [bogue PHP](https://bugs.php.net/bug.php?id=78015) enregistré. Pour contourner ce problème, veuillez définir le paramètre "opcache.optimization\_level" sur `0x7FFFBFDF` dans la configuration PHP (fichier php.ini). ### PHP 8 support PHP 8.0 and 8.1 is now supported. ### Prise en charge de PHP 8 PHP 8.0 et 8.1 sont désormais pris en charge. ### PHP support The maximum supported version for PHP is now 8.2. ### Prise en charge de PHP La version maximale prise en charge pour PHP est maintenant la 8.2. ### Plugins All metrics supported by Zabbix agent 2 are collected by plugins. ### Plugins Toutes les métriques prises en charge par l'agent Zabbix 2 sont collectées par les plugins. ##### Positional macros no longer supported The support for positional macros in item name ($1, $2...$9), deprecated since Zabbix 4.0, has been fully removed. ##### Les macros positionnelles ne sont plus prises en charge La prise en charge des macros positionnelles dans le nom de l'élément ($1, $2...$9), obsolète depuis Zabbix 4.0, a été entièrement supprimée. #### Possible deadlocks with MySQL/MariaDB When running under high load, and with more than one LLD worker involved, it is possible to run into a deadlock caused by an InnoDB error related to the row-locking strategy (see [upstream bug](https://github.com/mysql/mysql-server/commit/7037a0bdc83196755a3bf3e935cfb3c0127715d5)). The error has been fixed in MySQL since 8.0.29, but not in MariaDB. For more details, see [ZBX-21506](https://support.zabbix.com/browse/ZBX-21506). #### Blocages possibles avec MySQL/MariaDB Lors d'une exécution sous charge élevée et avec plus d'un agent LLD impliqué, il est possible de se retrouver dans un blocage causé par une erreur InnoDB liée à la stratégie de verrouillage de ligne (voir le[bogue en amont](https://github.com/mysql/mysql-server/commit/7037a0bdc83196755a3bf3e935cfb3c0127715d5)). L'erreur a été corrigée dans MySQL depuis 8.0.29, mais pas dans MariaDB. Pour plus de détails, voir [ZBX-21506](https://support.zabbix.com/browse/ZBX-21506). ##### Possible error messages You may encounter a situation when no data is displayed and the following error message appears: {width="600"} Error message in this case is the following: Cannot display item queue. Permission denied This happens when PHP configuration parameters $ZBX\_SERVER\_PORT or $ZBX\_SERVER in zabbix.conf.php point to existing Zabbix server which uses different database. ##### Messages d'erreur possibles Vous pouvez rencontrer une situation où aucune donnée n'est affichée et le message d'erreur suivant apparaît : {width="600"} Le message d'erreur dans ce cas est le suivant : Cannot display item queue. Permission denied Cela se produit lorsque les paramètres de configuration PHP $ZBX\_SERVER\_PORT ou $ZBX\_SERVER dans zabbix.conf.php pointent vers un serveur Zabbix existant qui utilise une base de données différente. ### Possible to build Zabbix agent 2 offline Zabbix agent 2 now can be built offline. The source tarball now includes the `src/go/vendor` directory, which should make sure that golang is not forced to download dependency modules automatically. It is still possible to update to the latest modules manually by using `go mod tidy` or `go get` commands. ### Possibilité de construire l'agent Zabbix 2 hors ligne L'agent Zabbix 2 peut désormais être construit hors ligne. L'archive tar source inclut désormais le répertoire `src/go/vendor`, ce qui devrait assurer que golang n'est pas obligé de télécharger automatiquement les modules de dépendance. Il est toujours possible de mettre à jour manuellement les derniers modules en utilisant les commandes `go mod tidy` ou `go get`. ### PostgreSQL 15 support PostgreSQL 15 is now supported. Note that TimescaleDB **does not** support PostgreSQL 15 yet. ### Prise en charge de PostgreSQL 15 PostgreSQL 15 est désormais pris en charge. Notez que TimescaleDB **ne prend pas encore** en charge PostgreSQL 15. ### PostgreSQL Export and import must be performed in tmux/screen to ensure that the session isn't dropped. For installations with TimescaleDB, skip this section and proceed to [PostgreSQL + TimescaleDB](#postgresql-timescaledb). See also: [Important notes](#important-notes) #### Table upgrade * Rename tables using `history_pk_prepare.sql`: ``` {.bash} sudo -u zabbix psql zabbix < /usr/share/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ``` #### Migration with stopped server * Export current history, import it to the temp table, then insert the data into new tables while ignoring duplicates: ``` {.sql} INSERT INTO history SELECT * FROM history_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_uint SELECT * FROM history_uint_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_str SELECT * FROM history_str_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_log SELECT * FROM history_log_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_text SELECT * FROM history_text_old ON CONFLICT (itemid,clock,ns) DO NOTHING; ``` See tips for improving INSERT performance: [PostgreSQL: Bulk Loading Huge Amounts of Data](https://www.cybertec-postgresql.com/en/postgresql-bulk-loading-huge-amounts-of-data), [Checkpoint Distance and Amount of WAL](https://www.cybertec-postgresql.com/en/checkpoint-distance-and-amount-of-wal). * Follow [post-migration instructions](#post-migration) to drop the old tables. ### PostgreSQL L'exportation et l'importation doivent être effectuées dans tmux/screen pour s'assurer que la session n'est pas abandonnée. Pour les installations avec TimescaleDB, ignorez cette section et passez à [PostgreSQL + TimescaleDB](#postgresql-timescaledb). Voir également : [Notes importantes](#notes-importantes) #### Mise à niveau des tables * Renommer les tables en utilisant `history_pk_prepare.sql` : ``` {.bash} sudo -u zabbix psql zabbix < /usr/share/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ``` #### Migration avec serveur arrêté * Exporter l'historique actuel, importez-le dans la table temporaire, puis insérer les données dans de nouvelles tables en ignorant les doublons : ``` {.sql} INSERT INTO history SELECT * FROM history_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_uint SELECT * FROM history_uint_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_str SELECT * FROM history_str_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_log SELECT * FROM history_log_old ON CONFLICT (itemid,clock,ns) DO NOTHING; INSERT INTO history_text SELECT * FROM history_text_old ON CONFLICT (itemid,clock,ns) DO NOTHING; ``` Consulter les conseils pour améliorer les performances d'INSERT : [PostgreSQL: Bulk Loading Huge Amounts of Data](https://www.cybertec-postgresql.com/en/postgresql-bulk-loading-huge-amounts-of-data), [Checkpoint Distance and Amount of WAL](https://www.cybertec-postgresql.com/en/checkpoint-distance-and-amount-of-wal). * Suivre les [instructions post-migration](#post-migration) pour supprimer les anciennes tables. ### PostgreSQL |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |pgsql.autovacuum.count\[uri,<username>,<password>, <dbName>\]|<|<|<| |The number of autovacuum workers.|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.archive\[uri,<username>,<password>, <dbName>\]|<|<|<| |Information about archived files.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.archive.count\_archived\_files** - the number of WAL files that have been successfully archived.<br>**pgsql.archive.failed\_trying\_to\_archive** - the number of failed attempts for archiving WAL files.<br>**pgsql.archive.count\_files\_to\_archive** - the number of files to archive.<br>**pgsql.archive.size\_files\_to\_archive** -the size of files to archive. | |pgsql.bgwriter\[uri,<username>,<password>, <dbName>\]|<|<|<| |Combined number of checkpoints for the database cluster, broken down by checkpoint type.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.bgwriter.buffers\_alloc** - the number of buffers allocated.<br>**pgsql.bgwriter.buffers\_backend** -the number of buffers written directly by a backend.<br>**pgsql.bgwriter.maxwritten\_clean** - the number of times the background writer stopped a cleaning scan, because it had written too many buffers.<br>**pgsql.bgwriter.buffers\_backend\_fsync** -the number of times a backend had to execute its own fsync call instead of the background writer.<br>**pgsql.bgwriter.buffers\_clean** - the number of buffers written by the background writer.<br>**pgsql.bgwriter.buffers\_checkpoint** - the number of buffers written during checkpoints.<br>**pgsql.bgwriter.checkpoints\_timed** - the number of scheduled checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoints\_req** - the number of requested checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoint\_write\_time** - the total amount of time spent in the portion of checkpoint processing where files are written to disk, in milliseconds.<br>**pgsql.bgwriter.sync\_time** - the total amount of time spent in the portion of checkpoint processing where files are synchronized with disk. | |pgsql.cache.hit\[uri,<username>,<password>, <dbName>\]|<|<|<| |PostgreSQL buffer cache hit rate.|Float |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.connections\[uri,<username>,<password>, <dbName>\]|<|<|<| |Connections by type.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.connections.active** - the backend is executing a query.<br>**pgsql.connections.fastpath\_function\_call** -the backend is executing a fast-path function.<br>**pgsql.connections.idle** - the backend is waiting for a new client command.<br>**pgsql.connections.idle\_in\_transaction** - the backend is in a transaction, but is not currently executing a query.<br>**pgsql.connections.prepared** - the number of prepared connections.<br>**pgsql.connections.total** - the total number of connections.<br>**pgsql.connections.total\_pct** - percantange of total connections in respect to ‘max\_connections’ setting of the PostgreSQL server.<br>**pgsql.connections.waiting** - number of connections in a query.<br>**pgsql.connections.idle\_in\_transaction\_aborted** - the backend is in a transaction, but is not currently executing a query and one of the statements in the transaction caused an error. | |pgsql.custom.query\[uri,<username>,<password>,queryName\[,args...\]\]|<|<|<| |Returns result of a custom query.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**queryName** - name of a custom query, must match SQL file name without an extension. <br> **args**(optional) - arguments to pass to a query. | | |pgsql.dbstat\[uri,<username>,<password>, dbName\]|<|<|<| |Collects statistics per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.dbstat.numbackends\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_read\_time\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time\["{\#DBNAME}"\]** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures\["{\#DBNAME}"\]** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled.(PostgreSQL version 12 only)<br>**pgsql.dbstat.blks\_read.rate\["{\#DBNAME}"\]** - the number of disk blocks read in this database.<br>**pgsql.dbstat.deadlocks.rate\["{\#DBNAME}"\]** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.blks\_hit.rate\["{\#DBNAME}"\]** - the number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL Pro buffer cache, not the operating system's file system cache).<br>**pgsql.dbstat.xact\_rollback.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been rolled back.<br>**pgsql.dbstat.xact\_commit.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.tup\_updated.rate\["{\#DBNAME}"\]** - the number of rows updated by queries in this database.<br>**pgsql.dbstat.tup\_returned.rate\["{\#DBNAME}"\]** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.tup\_inserted.rate\["{\#DBNAME}"\]** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.tup\_fetched.rate\["{\#DBNAME}"\]** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.tup\_deleted.rate\["{\#DBNAME}"\]** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.conflicts.rate\["{\#DBNAME}"\]** - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers).<br>**pgsql.dbstat.temp\_files.rate\["{\#DBNAME}"\]** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.temp\_bytes.rate\["{\#DBNAME}"\]** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing). | |pgsql.dbstat.sum\[uri,<username>,<password>, <dbName>\]|<|<|<| |Summarized data for all databases in a cluster.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by the dependent items:<br>**pgsql.dbstat.numbackends** - the number of backends currently connected to this database.<br>**pgsql.dbstat.sum.blk\_read\_time** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled (PostgreSQL version 12 only).<br>**pgsql.dbstat.sum.xact\_commit** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.sum.conflicts** - database statistics about query cancels due to conflict with recovery on standby servers.<br>**pgsql.dbstat.sum.deadlocks** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.sum.blks\_read** - the number of disk blocks read in this database.<br>**pgsql.dbstat.sum.blks\_hit** - the number of times disk blocks were found already in the buffer cache, so a read was not necessary (only hits in the PostgreSQL Pro buffer cache are included).<br>**pgsql.dbstat.sum.temp\_bytes** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.temp\_files** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.xact\_rollback** - the number of rolled-back transactions in this database.<br>**pgsql.dbstat.sum.tup\_deleted** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.sum.tup\_fetched** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.sum.tup\_inserted** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.sum.tup\_returned** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.sum.tup\_updated** - the number of rows updated by queries in this database. | |pgsql.db.age\[uri,<username>,<password>, dbName\]|<|<|<| |Age of the oldest FrozenXID of the database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.db.bloating\_tables\[uri,<username>,<password>, <dbName>\]|<|<|<| |The number of bloating tables per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.db.discovery\[uri,<username>,<password>, <dbName>\]|<|<|<| |List of the PostgreSQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.db.size\[uri,<username>,<password>, dbName\]|<|<|<| |Database size in bytes. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.locks\[uri,<username>,<password>, <dbName>\]|<|<|<| |Information about granted locks per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.locks.shareupdateexclusive\["{\#DBNAME}"\]** - the number of share update exclusive locks.<br>**pgsql.locks.accessexclusive\["{\#DBNAME}"\]** - the number of access exclusive locks.<br>**pgsql.locks.accessshare\["{\#DBNAME}"\]** - the number of access share locks.<br>**pgsql.locks.exclusive\["{\#DBNAME}"\]** - the number of exclusive locks.<br>**pgsql.locks.rowexclusive\["{\#DBNAME}"\]** - the number of row exclusive locks.<br>**pgsql.locks.rowshare\["{\#DBNAME}"\]** - the number of row share locks.<br>**pgsql.locks.share\["{\#DBNAME}"\]** - the number of shared locks.<br>**pgsql.locks.sharerowexclusive\["{\#DBNAME}"\]** - the number of share row exclusive locks. | |pgsql.oldest.xid\[uri,<username>,<password>, <dbName>\]|<|<|<| |Age of the oldest XID.|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.ping\[uri,<username>,<password>, <dbName>\]|<|<|<| |Tests whether a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.queries\[uri,<username>,<password>, <dbName>,timePeriod\]|<|<|<| |Measures query execution time.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.<br>**timePeriod** - execution time limit for count of slow queries (must be a positive integer).|Returned data are processed by dependent items:<br> **pgsql.queries.mro.time_max\["{\#DBNAME}"]** - max maintenance query time.<br>**pgsql.queries.query.time_max\["{\#DBNAME}"]** - max query time.<br>**pgsql.queries.tx.time_max\["{\#DBNAME}"]** - max transaction query time.<br>**pgsql.queries.mro.slow_count\["{\#DBNAME}"]** - slow maintenance query count.<br>**pgsql.queries.query.slow_count\["{\#DBNAME}"]** - slow query count.<br>**pgsql.queries.tx.slow_count\["{\#DBNAME}"]** - slow transaction query count.<br>**pgsql.queries.mro.time_sum\["{\#DBNAME}"]** - sum maintenance query time.<br>**pgsql.queries.query.time_sum\["{\#DBNAME}"]** - sum query time.<br>**pgsql.queries.tx.time_sum\["{\#DBNAME}"]** - sum transaction query time.<br><br> This item is supported since Zabbix 6.0.3| |pgsql.replication.count\[uri,<username>,<password>\]|<|<|<| |The number of standby servers.|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication.process\[uri,<username>,<password>\]|<|<|<| | Flush lag, write lag and replay lag per each sender process.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication.process.discovery\[uri,<username>,<password>\]|<|<|<| | Replication process name discovery.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication.recovery\_role\[uri,<username>,<password>\]|<|<|<| |Recovery status.|0 - master mode<br>1 - recovery is still in progress (standby mode)|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication.status\[uri,<username>,<password>\]|<|<|<| |The status of replication.|0 - streaming is down<br>1 - streaming is up<br>2 - master mode|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication\_lag.b\[uri,<username>,<password>\]|<|<|<| |Replication lag in bytes.|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.replication\_lag.sec\[uri,<username>,<password>\]|<|<|<| |Replication lag in seconds.|Integer |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.| | |pgsql.uptime\[uri,<username>,<password>, <dbName>\]|<|<|<| |PostgreSQL uptime in milliseconds.|Float |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.| | |pgsql.wal.stat\[uri,<username>,<password>, <dbName>\]|<|<|<| |WAL statistics.|JSON object |**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.wal.count** — the number of WAL files.<br>**pgsql.wal.write** - the WAL lsn used (in bytes). | ### PostgreSQL |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur de retour**|**Paramètres**|**Commentaires**| |pgsql.autovacuum.count\[uri,\<username\>,\<password\>,\<dbName\>\]|<|<|<| |Le nombre de worker de l'autovacuum.|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.archive\[uri,\<username\>,\<password\>,\<dbName\>\]|<|<|<| |Informations sur les fichiers archivés.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par les éléments dépendants :<br>**pgsql.archive.count\_archived\_files** - le nombre de fichiers WAL qui ont été archivés avec succès.<br>**pgsql.archive.failed\_trying\_to\_archive** - le nombre de tentatives infructueuses d'archivage des fichiers WAL.<br>**pgsql.archive.count\_files\_to\_archive** - le nombre de fichiers à archiver.<br>**pgsql.archive.size\_files\_to\_archive** - la taille des fichiers à archiver. | |pgsql.bgwriter\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Nombre combiné de points de contrôle pour le cluster de bases de données, ventilé par type de point de contrôle.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par les éléments dépendants :<br>**pgsql.bgwriter.buffers\_alloc** - le nombre de tampons alloués.<br>**pgsql.bgwriter.buffers\_backend** - le nombre de tampons écrits directement par un backend.<br>**pgsql.bgwriter.maxwritten\_clean** - le nombre de fois que l'enregistreur d'arrière-plan a arrêté une analyse de nettoyage, car il avait écrit trop de tampons.<br>**pgsql.bgwriter.buffers\_backend\_fsync** - le nombre de fois qu'un backend a dû exécuter son propre appel fsync au lieu du writer d'arrière-plan.<br>**pgsql.bgwriter.buffers\_clean** - le nombre de tampons écrits par le writer en arrière-plan.<br>**pgsql.bgwriter.buffers\_checkpoint** - le nombre de tampons écrits lors des points de contrôle.<br>**pgsql.bgwriter.checkpoints\_timed** - le nombre de points de contrôle planifiés qui ont été effectués.<br>**pgsql.bgwriter.checkpoints\_req** - le nombre de points de contrôle demandés qui ont été effectués.<br>**pgsql.bgwriter.checkpoint\_write\_time** - le temps total passé dans la partie du traitement des points de contrôle où les fichiers sont écrits sur le disque, en millisecondes.<br>**pgsql.bgwriter.sync\_time** - le temps total passé dans la partie du traitement des points de contrôle où les fichiers sont synchronisés avec le disque. | |pgsql.cache.hit\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Taux de réussite du cache de tampon PostgreSQL.|Flottant |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.connections\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Connections by type.|JSON object |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par les éléments dépendants :<br>**pgsql.connections.active** - le backend exécute une requête.<br>**pgsql.connections.fastpath\_function\_call** -le backend exécute une fonction de raccourci.<br>**pgsql.connections.idle** - le backend attend une nouvelle commande client.<br>**pgsql.connections.idle\_in\_transaction** - le backend est dans une transaction, mais n'exécute pas actuellement de requête.<br>**pgsql.connections.prepared** - le nombre de connexions préparées.<br>**pgsql.connections.total** - le nombre total de connexions.<br>**pgsql.connections.total\_pct** - pourcentage du nombre total de connexions par rapport au paramètre 'max\_connections' du serveur PostgreSQL.<br>**pgsql.connections.waiting** - nombre de connexions dans une requête.<br>**pgsql.connections.idle\_in\_transaction\_aborted** - le backend est dans une transaction, mais n'exécute pas actuellement de requête et l'une des instructions de la transaction a provoqué une erreur. | |pgsql.custom.query\[uri,\<username\>,\<password\>,queryName\[,args...\]\]|<|<|<| |Renvoie le résultat d'une requête personnalisée.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**queryName** - nom d'une requête personnalisée, doit correspondre au nom de fichier SQL sans extension. <br> **args** (facultatif) - arguments à passer à une requête. | | |pgsql.dbstat\[uri,\<username\>,\<password\>, dbName\]|<|<|<| |Collecte des statistiques par base de données. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|JSON object |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par les éléments dépendants :<br>**pgsql.dbstat.numbackends\["{\#DBNAME}"\]** - temps passé à lire les blocs de fichiers de données par les backends dans cette base de données, en millisecondes.<br>**pgsql.dbstat.sum.blk\_read\_time\["{\#DBNAME}"\]** - temps passé à lire les blocs de fichiers de données par les backends dans cette base de données, en millisecondes.<br>**pgsql.dbstat.sum.blk\_write\_time\["{\#DBNAME}"\]** - temps passé à écrire des blocs de fichiers de données par les backends dans cette base de données, en millisecondes.<br>**pgsql.dbstat.sum.checksum\_failures\["{\#DBNAME}"\]** - le nombre d'échecs de somme de contrôle de page de données détectés (ou sur un objet partagé), ou NULL si les sommes de contrôle de données ne sont pas activées. (PostgreSQL version 12 uniquement)<br>**pgsql.dbstat.blks\_read.rate\["{\#DBNAME}"\]** - le nombre de blocs de disque lus dans cette base de données.<br>**pgsql.dbstat.deadlocks.rate\["{\#DBNAME}"\]** - le nombre d'interblocages détectés dans cette base de données.<br>**pgsql.dbstat.blks\_hit.rate\["{\#DBNAME}"\]** - le nombre de fois où des blocs de disque ont déjà été trouvés dans le cache de tampon, de sorte qu'une lecture n'était pas nécessaire (cela inclut uniquement les hits dans le cache de tampon de PostgreSQL Pro, pas le cache du système de fichiers du système d'exploitation).<br>**pgsql.dbstat.xact\_rollback.rate\["{\#DBNAME}"\]** - le nombre de transactions dans cette base de données qui ont été annulées.<br>**pgsql.dbstat.xact\_commit.rate\["{\#DBNAME}"\]** - le nombre de transactions dans cette base de données qui ont été validées.<br>**pgsql.dbstat.tup\_updated.rate\["{\#DBNAME}"\]** - le nombre de lignes mises à jour par requêtes dans cette base de données.<br>**pgsql.dbstat.tup\_returned.rate\["{\#DBNAME}"\]** - le nombre de lignes renvoyées par les requêtes dans cette base de données.<br>**pgsql.dbstat.tup\_inserted.rate\["{\#DBNAME}"\]** - le nombre de lignes insérées par les requêtes dans cette base de données.<br>**pgsql.dbstat.tup\_fetched.rate\["{\#DBNAME}"\]** - le nombre de lignes récupérées par les requêtes dans cette base de données.<br>**pgsql.dbstat.tup\_deleted.rate\["{\#DBNAME}"\]** - le nombre de lignes supprimées par les requêtes dans cette base de données.<br>**pgsql.dbstat.conflicts.rate\["{\#DBNAME}"\]** - le nombre de requêtes annulées pour cause de conflits avec récupération dans cette base (les conflits ne surviennent que sur les serveurs de secours).<br>**pgsql.dbstat.temp\_files.rate\["{\#DBNAME}"\]** - le nombre de fichiers temporaires créés par requêtes dans cette base de données. Tous les fichiers temporaires sont comptés, quels que soient les paramètres log\_temp\_files et les raisons pour lesquelles le fichier temporaire a été créé (par exemple, tri ou hachage).<br>**pgsql.dbstat.temp\_bytes.rate\["{\#DBNAME}"\]** - la quantité totale de données écrites dans des fichiers temporaires par des requêtes dans cette base de données. Inclut les données de tous les fichiers temporaires, quels que soient les paramètres log\_temp\_files et les raisons pour lesquelles le fichier temporaire a été créé (par exemple, tri ou hachage). | |pgsql.dbstat.sum\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Données résumées pour toutes les bases de données d'un cluster.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par les éléments dépendants :<br>**pgsql.dbstat.numbackends** - le nombre de backends actuellement connectés à cette base de données.<br>**pgsql.dbstat.sum.blk\_read\_time** - temps passé à lire les blocs de fichiers de données par les backends dans cette base de données, en millisecondes.<br>**pgsql.dbstat.sum.blk\_write\_time** - temps passé à écrire des blocs de fichiers de données par les backends dans cette base de données, en millisecondes.<br>**pgsql.dbstat.sum.checksum\_failures** - le nombre d'échecs de somme de contrôle de page de données détectés (ou sur un objet partagé), ou NULL si les sommes de contrôle de données ne sont pas activées (PostgreSQL version 12 uniquement).<br>**pgsql.dbstat.sum.xact\_commit** - le nombre de transactions dans cette base de données qui ont été validées.<br>**pgsql.dbstat.sum.conflicts** - statistiques de la base de données sur les annulations de requêtes en raison d'un conflit avec la récupération sur les serveurs de secours.<br>**pgsql.dbstat.sum.deadlocks** - le nombre d'interblocages détectés dans cette base de données.<br>**pgsql.dbstat.sum.blks\_read** - le nombre de blocs de disque lus dans cette base de données.<br>**pgsql.dbstat.sum.blks\_hit** - le nombre de fois que des blocs de disque ont déjà été trouvés dans le cache de tampon, donc une lecture n'était pas nécessaire (seuls les hits dans le cache de tampon de PostgreSQL Pro sont inclus).<br>**pgsql.dbstat.sum.temp\_bytes** - la quantité totale de données écrites dans des fichiers temporaires par des requêtes dans cette base de données. Inclut les données de tous les fichiers temporaires, quels que soient les paramètres log\_temp\_files et les raisons pour lesquelles le fichier temporaire a été créé (par exemple, tri ou hachage).<br>**pgsql.dbstat.sum.temp\_files** - le nombre de fichiers temporaires créés par requêtes dans cette base de données. Tous les fichiers temporaires sont comptés, quels que soient les paramètres log\_temp\_files et les raisons pour lesquelles le fichier temporaire a été créé (par exemple, tri ou hachage).<br>**pgsql.dbstat.sum.xact\_rollback** - le nombre de transactions annulées dans cette base de données.<br>**pgsql.dbstat.sum.tup\_deleted** - le nombre de lignes supprimées par les requêtes dans cette base de données.<br>**pgsql.dbstat.sum.tup\_fetched** - le nombre de lignes récupérées par les requêtes dans cette base de données.<br>**pgsql.dbstat.sum.tup\_inserted** - le nombre de lignes insérées par les requêtes dans cette base de données.<br>**pgsql.dbstat.sum.tup\_returned** - le nombre de lignes renvoyées par les requêtes dans cette base de données.<br>**pgsql.dbstat.sum.tup\_updated** - le nombre de lignes mises à jour par requêtes dans cette base de données. | |pgsql.db.age\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Âge du plus ancien FrozenXID de la base de données. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Eniter |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.db.bloating\_tables\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Le nombre de tables gonflées par base de données. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.db.discovery\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Liste des bases de données PostgreSQL. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.db.size\[uri,\<username\>,\<password\>, dbName\]|<|<|<| |Taille de la base de données en octets. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.locks\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Informations sur les verrous accordés par base de données. Utilisé pour la [découverte de bas niveau](/manual/discovery/low_level_discovery/examples/systemd).|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.|Les données renvoyées sont traitées par des éléments dépendants :<br>**pgsql.locks.shareupdateexclusive\["{\#DBNAME}"\]** - le nombre de verrous exclusifs de mise à jour de partage.<br>**pgsql.locks.accessexclusive\["{\#DBNAME}"\]** - le nombre de verrous exclusifs d'accès.<br>**pgsql.locks.accessshare\["{\#DBNAME}"\]** - le nombre de verrous de partage d'accès.<br>**pgsql.locks.exclusive\["{\#DBNAME}"\]** - le nombre de verrous exclusifs.<br>**pgsql.locks.rowexclusive\["{\#DBNAME}"\]** - le nombre de verrous exclusifs de ligne.<br>**pgsql.locks.rowshare\["{\#DBNAME}"\]** - le nombre de verrous de partage de lignes.<br>**pgsql.locks.share\["{\#DBNAME}"\]** - le nombre de verrous partagés.<br>**pgsql.locks.sharerowexclusive\["{\#DBNAME}"\]** - le nombre de verrous exclusifs de lignes partagées.| |pgsql.oldest.xid\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Âge du XID le plus ancien.|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.ping\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Teste si une connexion est active ou non.|1 - la connexion est en vie<br><br>0 - la connexion est interrompue (s'il y a une erreur présentée, y compris des problèmes d'authentification et de configuration).|**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.| | |pgsql.queries\[uri,\<username\>,\<password\>, \<dbName\>,timePeriod\]|<|<|<| |Mesure le temps d'exécution de la requête.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.<br>**dbName** - Nom de la base de données.<br>**timePeriod** - limite de temps d'exécution pour le nombre de requêtes lentes (doit être un entier positif).|Les données renvoyées sont traitées par les éléments dépendants :<br> **pgsql.queries.mro.time_max\["{\#DBNAME}"]** - durée maximale de requête de maintenance.<br>**pgsql.queries.query.time_max\["{\#DBNAME}"]** - temps de requête maximum.<br>**pgsql.queries.tx.time_max\["{\#DBNAME}"]** - durée maximale de la requête de transaction.<br>**pgsql.queries.mro.slow_count\["{\#DBNAME}"]** - nombre de requêtes de maintenance lentes.<br>**pgsql.queries.query.slow_count\["{\#DBNAME}"]** - nombre de requêtes lentes.<br>**pgsql.queries.tx.slow_count\["{\#DBNAME}"]** - nombre de requêtes de transaction lentes.<br>**pgsql.queries.mro.time_sum\["{\#DBNAME}"]** - somme temps de requête de maintenance.<br>**pgsql.queries.query.time_sum\["{\#DBNAME}"]** - somme du temps de requête.<br>**pgsql.queries.tx.time_sum\["{\#DBNAME}"]** - somme du temps de requête de la transaction.<br><br> Cet élément est pris en charge depuis Zabbix 6.0.3| |pgsql.replication.count\[uri,\<username\>,\<password\>\]|<|<|<| |Le nombre de serveurs de secours.|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication.process\[uri,\<username\>,\<password\>\]|<|<|<| | Flush lag, write lag et replay lag pour chaque processus expéditeur.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication.process.discovery\[uri,\<username\>,\<password\>\]|<|<|<| | Découverte du nom du processus de réplication.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication.recovery\_role\[uri,\<username\>,\<password\>\]|<|<|<| |Statut de récupération.|0 - mode maître<br>1 - la récupération est toujours en cours (mode veille)|**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication.status\[uri,\<username\>,\<password\>\]|<|<|<| |L'état de la réplication.|0 - le streaming est arrêté<br>1 - le streaming est actif<br>2 - mode maître|**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication\_lag.b\[uri,\<username\>,\<password\>\]|<|<|<| |Retard de réplication en octets.|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.replication\_lag.sec\[uri,\<username\>,\<password\>\]|<|<|<| |Retard de réplication en secondes.|Entier |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.uptime\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Temps de disponibilité de PostgreSQL en millisecondes.|Flottant |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.| | |pgsql.wal.stat\[uri,\<username\>,\<password\>, \<dbName\>\]|<|<|<| |Statistiques WAL.|Objet JSON |**uri** - URI ou nom de session.<br>**username, password** - Informations d'identification PostgreSQL.|Les données renvoyées sont traitées par des éléments dépendants :<br>**pgsql.wal.count** — le nombre de fichiers WAL.<br>**pgsql.wal.write** - le WAL lsn utilisé (en octets). | #### PostgreSQL metrics A new [item](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#postgresql) has been added to PostgreSQL plugin for Zabbix agent 2. The metric **pgsql.queries** is used for monitoring query execution time. #### Métriques PostgreSQL Un nouvel [élément](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#postgresql) a été ajouté au plugin PostgreSQL pour l'agent Zabbix 2. La métrique **pgsql.queries** est utilisée pour surveiller le temps d'exécution des requêtes. ### PostgreSQL plugin moved to loadable plugins The PostgreSQL [plugin](/manual/config/items/plugins#loadable) is no longer built-in in Zabbix agent 2. Instead it is now a loadable plugin in the agent 2. This change may/will break automations with Ansible, Chef, etc, because it is no longer possible to pull the plugin repository directly. See also: [PostgreSQL loadable plugin](https://git.zabbix.com/projects/AP/repos/postgresql/browse) repository ### Plugin PostgreSQL déplacé vers les plugins chargeables Le [plugin](/manual/config/items/plugins#loadable) PostgreSQL n'est plus intégré à l'agent Zabbix 2. Il s'agit désormais d'un plugin chargeable dans l'agent 2. Ce changement peut/cassera les automatisations avec Ansible, Chef, etc., car il n'est plus possible d'extraire directement le référentiel de plugins. Voir aussi : le référentiel [Plug-in chargeable PostgreSQL](https://git.zabbix.com/projects/AP/repos/postgresql/browse) ### PostgreSQL + TimescaleDB Export and import must be performed in tmux/screen to ensure that the session isn't dropped. Zabbix server should be down during the upgrade. See also: [Important notes](#important-notes) * Rename tables using `history_pk_prepare.sql`. ``` {.bash} sudo -u zabbix psql zabbix < /usr/share/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ``` * Run TimescaleDB hypertable migration scripts (compatible with both TSDB v2.x and v1.x version) based on compression settings: * If compression is enabled (on default installation), run scripts from `database/postgresql/tsdb_history_pk_upgrade_with_compression`: ``` {.bash} cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_uint.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_log.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_str.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_text.sql | sudo -u zabbix psql zabbix ``` * If compression is disabled, run scripts from `database/postgresql/tsdb_history_pk_upgrade_no_compression`: ``` {.bash} cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_uint.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_log.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_str.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_text.sql | sudo -u zabbix psql zabbix ``` See also: [Tips](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/) for improving INSERT performance. * Follow [post-migration instructions](#post-migration) to drop the old tables. ### PostgreSQL + TimescaleDB L'exportation et l'importation doivent être effectuées dans tmux/screen pour s'assurer que la session n'est pas abandonnée. Le serveur Zabbix devrait être en panne pendant la mise à niveau. Voir également: [Notes importantes](#notes-importantes) * Renommer les tables en utilisant `history_pk_prepare.sql`. ``` {.bash} sudo -u zabbix psql zabbix < /usr/share/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ``` * Exécuter les scripts de migration d'hypertables TimescaleDB (compatibles avec les versions TSDB v2.x et v1.x) en fonction des paramètres de compression : * Si la compression est activée (sur l'installation par défaut), exécuter les scripts à partir de `database/postgresql/tsdb_history_pk_upgrade_with_compression`: ``` {.bash} cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_uint.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_log.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_str.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_with_compression/history_pk_text.sql | sudo -u zabbix psql zabbix ``` * Si la compression est désactivée exécuter les scripts à partir de `database/postgresql/tsdb_history_pk_upgrade_no_compression`: ``` {.bash} cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_uint.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_log.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_str.sql | sudo -u zabbix psql zabbix cat /usr/share/zabbix-sql-scripts/postgresql/tsdb_history_pk_upgrade_no_compression/history_pk_text.sql | sudo -u zabbix psql zabbix ``` Voir également : [Astuces](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/) pour améliorer les performances d'INSERT. * Suivre les [instructions post-migration](#post-migration) pour supprimer les anciennes tables. #### PostgreSQL You need to have database user with permissions to create database objects. If you are installing from Zabbix **packages**, proceed to the [instructions](https://www.zabbix.com/download) for your platform. If you are installing Zabbix from sources: * Create a database user. The following shell command will create user `zabbix`. Specify a password when prompted and repeat the password (note, you may first be asked for `sudo` password): ```bash sudo -u postgres createuser --pwprompt zabbix ``` * Create a database. The following shell command will create the database `zabbix` (last parameter) with the previously created user as the owner (`-O zabbix`). ```bash sudo -u postgres createdb -O zabbix -E Unicode -T template0 zabbix ``` * Import the initial schema and data (assuming you are in the root directory of Zabbix sources). For a Zabbix proxy database, only `schema.sql` should be imported (no images.sql nor data.sql). ```bash cd database/postgresql cat schema.sql | sudo -u zabbix psql zabbix # stop here if you are creating database for Zabbix proxy cat images.sql | sudo -u zabbix psql zabbix cat data.sql | sudo -u zabbix psql zabbix ``` ::: noteimportant The above commands are provided as an example that will work in most of GNU/Linux installations. You can use different commands depending on how your system/database is configured, for example: <br><br> `psql -U <username>` <br><br> If you have any trouble setting up the database, please consult your Database administrator. ::: #### PostgreSQL Vous devez avoir un utilisateur de base de données avec des autorisations pour créer des objets de base de données. Si vous installez à partir des **paquets** Zabbix, suivez les [instructions](https://www.zabbix.com/download) pour votre plate-forme. Si vous installez Zabbix à partir de sources : * Créez un utilisateur de base de données. La commande shell suivante créera l'utilisateur `zabbix`. Spécifiez un mot de passe lorsque vous y êtes invité et répétez le mot de passe (remarque, il se peut que l'on vous demande d'abord le mot de passe `sudo`) : ```bash sudo -u postgres createuser --pwprompt zabbix ``` * Créez une base de données. La commande shell suivante créera la base de données `zabbix` (dernier paramètre) avec l'utilisateur précédemment créé comme propriétaire (`-O zabbix`). ```bash sudo -u postgres createdb -O zabbix -E Unicode -T template0 zabbix ``` * Importez le schéma et les données initiaux (en supposant que vous êtes dans le répertoire racine des sources Zabbix). Pour une base de données proxy Zabbix, seul `schema.sql` doit être importé (pas d'images.sql ni de data.sql). ```bash cd database/postgresql cat schema.sql | sudo -u zabbix psql zabbix # arrêtez vous ici si vous créez une base de donnée pour le proxy Zabbix cat images.sql | sudo -u zabbix psql zabbix cat data.sql | sudo -u zabbix psql zabbix ``` ::: noteimportant Les commandes ci-dessus sont fournies à titre d'exemple et fonctionneront dans la plupart des installations GNU/Linux. Vous pouvez utiliser différentes commandes selon la configuration de votre système/base de données, par exemple : <br><br> `psql -U <username>` <br><br> Si vous rencontrez des problèmes lors de la configuration de la base de données, veuillez consulter votre administrateur de base de données. ::: ### Post-migration For all databases, once the migration is completed, do the following: * Verify that everything works as expected. * Drop old tables: ``` {.sql} DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ``` ### Post-migration Pour toutes les bases de données, une fois la migration terminée, procéder comme suit : * Vérifier que tout fonctionne comme prévu. * Supprimer les anciennes tables : ``` {.sql} DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ``` #### Predefined scripts All scripts (webhook, script, SSH, Telnet, IPMI) that are available for action operations are defined in [global scripts](/manual/web_interface/frontend_sections/administration/scripts). For example: sudo /etc/init.d/apache restart In this case, Zabbix will try to restart an Apache process. With this command, make sure that the command is executed on Zabbix agent (click the *Zabbix agent* button against *Execute on*). ::: noteimportant Note the use of **sudo** - Zabbix user does not have permissions to restart system services by default. See below for hints on how to configure **sudo**. ::: ::: noteclassic Zabbix agent should run on the remote host and accept incoming connections. Zabbix agent executes commands in background. ::: Remote commands on Zabbix agent are executed without timeout by the system.run\[,nowait\] key and are not checked for execution results. On Zabbix server and Zabbix proxy, remote commands are executed with timeout as set in the TrapperTimeout parameter of zabbix\_server.conf or zabbix\_proxy.conf file and are [checked](/manual/appendix/command_execution#exit_code_checking) for execution results. #### Scripts prédéfinis Tous les scripts (webhook, script, SSH, Telnet, IPMI) disponibles pour les opérations d'action sont définis dans les [scripts globaux](/manual/web_interface/frontend_sections/administration/scripts). Par exemple : sudo /etc/init.d/apache restart Dans ce cas, Zabbix essaiera de redémarrer un processus Apache. Avec cette commande, assurez-vous que la commande est exécutée sur l’agent Zabbix (cliquez sur le bouton *agent Zabbix* à côté de *Exécuter sur*). ::: noteimportant Notez que pour l'utilisation de **sudo** l'utilisateur Zabbix ne dispose pas des autorisations pour redémarrer les services systèmes par défaut. Voir ci-dessous des astuces de configuration de **sudo**. ::: ::: noteclassic L'agent Zabbix doit s'exécuter sur l'hôte distant et accepter les connexions entrantes. L'agent Zabbix exécute les commandes en arrière-plan. ::: Les commandes à distance sur l'agent Zabbix sont exécutées sans délai par la clé system.run\[,nowait\] et les résultats de l'exécution ne sont pas vérifiées. Sur le serveur Zabbix, les commandes à distance sont exécutées avec le délai d'expiration défini dans le paramètre TrapperTimeout du fichier zabbix\_server.conf et leurs résultats sont [vérifiés](/manual/appendix/command_execution#exit_code_checking). #### Prediction functions |FUNCTION|<|<| |--|--|--| |**Description**|**Function-specific parameters**|**Comments**| |**forecast** (/host/key,(sec\|\#num)<:time shift>,time,<fit>,<mode>)|<|<| |Future value, max, min, delta or avg of the item.|See [common parameters](#common-parameters).<br><br>**time** - forecasting horizon in seconds (time suffixes can be used); negative values are supported<br><br>**fit** (optional; must be double-quoted) - function used to fit historical data<br><br>Supported `fits`:<br>*linear* - linear function<br>*polynomialN* - polynomial of degree N (1 <= N <= 6)<br>*exponential* - exponential function<br>*logarithmic* - logarithmic function<br>*power* - power function<br><br>Note that:<br>*linear* is default, *polynomial1* is equivalent to *linear*<br><br>**mode** (optional; must be double-quoted) - demanded output<br><br>Supported `modes`:<br>*value* - value (default)<br>*max* - maximum<br>*min* - minimum<br>*delta* - *max*-*min*<br>*avg* - average<br><br>Note that:<br>*value* estimates item value at the moment `now` + `time`<br>*max*, *min*, *delta* and *avg* investigate item value estimate on the interval between `now` and `now` + `time`|Supported value types: float, int<br><br>If value to return is larger than 1.7976931348623157E+308 or less than -1.7976931348623157E+308, return value is cropped to 1.7976931348623157E+308 or -1.7976931348623157E+308 correspondingly.<br><br>Becomes unsupported only if misused in expression (wrong item type, invalid parameters), otherwise returns -1 in case of errors.<br><br>Examples:<br>=> **forecast**(/host/key,**\#10**,**1h**) → forecast item value in one hour based on the last 10 values<br>=> **forecast**(/host/key,**1h**,**30m**) → forecast item value in 30 minutes based on the last hour data<br>=> **forecast**(/host/key,**1h:now-1d**,**12h**) → forecast item value in 12 hours based on one hour one day ago<br>=> **forecast**(/host/key,**1h**,**10m**,"exponential") → forecast item value in 10 minutes based on the last hour data and exponential function<br>=> **forecast**(/host/key,**1h**,**2h**,"polynomial3","max") → forecast the maximum value the item can reach in the next two hours based on last hour data and cubic (third degree) polynomial<br>=> **forecast**(/host/key,**\#2**,**-20m**) → estimate the item value 20 minutes ago based on the last two values (this can be more precise than using last(), especially if item is updated rarely, say, once an hour)<br><br>See also additional information on [predictive trigger functions](/manual/config/triggers/prediction).| |**timeleft** (/host/key,(sec\|\#num)<:time shift>,threshold,<fit>)|<|<| |Time in seconds needed for an item to reach a specified threshold.|See [common parameters](#common-parameters).<br><br>**threshold** - value to reach ([unit suffixes](/manual/appendix/suffixes) can be used)<br><br>**fit** (optional; must be double-quoted) - see forecast()|Supported value types: float, int<br><br>If value to return is larger than 1.7976931348623157E+308, return value is cropped to 1.7976931348623157E+308.<br><br>Returns 1.7976931348623157E+308 if threshold cannot be reached.<br><br>Becomes unsupported only if misused in the expression (wrong item type, invalid parameters), otherwise returns -1 in case of errors.<br><br>Examples:<br>=> **timeleft**(/host/key,**\#10**,**0**) → time until the item value reaches zero based on the last 10 values<br>=> **timeleft**(/host/key,**1h**,**100**) → time until the item value reaches 100 based on the last hour data<br>=> **timeleft**(/host/key,**1h:now-1d**,**100**) → time until the item value reaches 100 based on one hour one day ago<br>=> **timeleft**(/host/key,**1h**,**200**,"polynomial2") → time until the item value reaches 200 based on the last hour data and assumption that the item behaves like quadratic (second degree) polynomial<br>See also additional information on [predictive trigger functions](/manual/config/triggers/prediction).| #### Fonctions de prédiction |FONCTION|<|<| |--|--|--| |**Description**|**Paramètres spécifiques à la fonction**|**Commentaires**| |**forecast** (/host/key,(sec\|\#num)<:time shift>,time,<fit>,<mode>)|<|<| |Valeur future, max, min, delta ou moyenne de l'élément.|Voir [paramètres communs](#common-parameters).<br><br>**time** - horizon de prévision en secondes (des suffixes de temps peuvent être utilisés ); les valeurs négatives sont prises en charge<br><br>**fit** (facultatif ; doit être entre guillemets doubles) – fonction utilisée pour ajuster les données historiques<br><br>'fits` pris en charge :<br>*linear* - fonction linéaire<br>*polynomialN* - polynôme de degré N (1 <= N <= 6)<br>*exponential* - fonction exponentielle<br>*logarithmic* - fonction logarithmique<br>*power* - fonction puissance<br ><br>Notez que :<br>*linear* est la valeur par défaut, *polynomial1* est équivalent à *linear*<br><br>**mode** (facultatif ; doit être entre guillemets doubles) - sortie demandée<br ><br>`modes` pris en charge :<br>*value* - valeur (par défaut)<br>*max* - maximum<br>*min* - minimum<br>*delta* - *max*-*min* <br>*avg* - moyenne<br><br>Notez que :<br>*value* estime la valeur de l'élément à l'instant `now` + `time`<br>*max*, *min*, *delta* et *avg* étudient l'estimation de la valeur de l'élément sur l'intervalle entre `now` et `now` + `time`|Types de valeurs pris en charge : float, int<br><br>Si la valeur à renvoyer est supérieure à 1,7976931348623157E+308 ou moins supérieur à -1,7976931348623157E+308, la valeur de retour est réduite à 1,79769313486231 57E+308 ou -1.7976931348623157E+308 en conséquence.<br><br>N'est plus pris en charge uniquement s'il est mal utilisé dans l'expression (mauvais type d'élément, paramètres invalides), sinon renvoie -1 en cas d'erreurs.<br><br>Exemples : <br>=> **forecast**(/host/key,**\#10**,**1h**) → valeur de l'élément de prévision dans une heure sur la base des 10 dernières valeurs<br>=> **forecast**(/host/key,**1h**,**30m**) → valeur de l'élément prévue dans 30 minutes sur la base des données de la dernière heure<br>=> **forecast**(/host/key, **1h:now-1d**,**12h**) → valeur de l'élément prévue dans 12 heures sur la base d'une heure il y a un jour<br>=> **forecast**(/host/key,**1h* *,**10m**,"exponential") → valeur de l'élément de prévision dans 10 minutes en fonction des données de la dernière heure et de la fonction exponentielle<br>=> **forecast**(/host/key,**1h**, **2h**,"polynomial3","max") → prévoir la valeur maximale que l'élément peut atteindre au cours des deux prochaines heures sur la base des données de la dernière heure et du polynôme cubique (troisième degré)<br>=> **forecast** (/host/key,**\#2**,**-20m**) → estimer la valeur de l'élément il y a 20 minutes en se basant sur les deux dernières valeurs (cela peut être plus précis que l'utilisation de last(), surtout si l'élément est rarement mis à jour, disons une fois par heure)<br><br>Voir aussi des informations supplémentaires sur les [fonctions de déclenchement prédictives](/manual/config/triggers/prediction) .| |**timeleft** (/host/key,(sec\|\#num)<:time shift>,threshold,<fit>)|<|<| |Temps en secondes nécessaire pour qu'un élément atteigne un seuil spécifié.|Voir [paramètres communs](#common-parameters).<br><br>**threshold** - valeur à atteindre ([suffixes d'unité](/manual /appendix/suffixes) peuvent être utilisés)<br><br>**fit** (facultatif ; doit être entre guillemets doubles) – voir forecast()|Types de valeur pris en charge : float, int<br><br>Si la valeur à renvoyer est supérieur à 1,7976931348623157E+308, la valeur renvoyée est réduite à 1,7976931348623157E+308.<br><br>Renvoie 1,7976931348623157E+308 si le seuil ne peut pas être atteint.<br><br>N'est plus pris en charge uniquement en cas d'utilisation abusive dans le expression (mauvais type d'élément, paramètres invalides), sinon renvoie -1 en cas d'erreur.<br><br>Exemples :<br>=> **timeleft**(/host/key,**\#10** ,**0**) → temps jusqu'à ce que la valeur de l'élément atteigne zéro sur la base des 10 dernières valeurs<br>=> **timeleft**(/host/key,**1h**,**100**) → temps jusqu'à ce que la valeur de l'élément atteigne 100 sur la base des données de la dernière heure<br>=> **timeleft**(/host/key,**1h:now-1d**,**100**) → temps jusqu'à ce que la valeur de l'élément atteigne 100 sur la base d'une heure il y a un jour<br>=> **timeleft**(/host/key,**1h**,**200**,"polynomial2") → temps jusqu'à ce que la valeur de l'élément atteigne 200 sur la base des données de la dernière heure et en supposant que l'élément se comporte comme un polynôme quadratique (deuxième degré)<br>Voir aussi des informations supplémentaires sur les [fonctions de déclenchement prédictives](/manual/config/triggers/prediction).| #### Pre-installation summary Review a summary of settings. {width="550"} #### Résumé de pré-installation Passez en revue un résumé des paramètres. {width="550"} ##### Preparation Zabbix agent is distributed as a zip archive. After you download the archive you need to unpack it. Choose any folder to store Zabbix agent and the configuration file, e. g. C:\zabbix Copy bin\\zabbix\_agentd.exe and conf\\zabbix\_agentd.conf files to c:\\zabbix. Edit the c:\\zabbix\\zabbix\_agentd.conf file to your needs, making sure to specify a correct "Hostname" parameter. ##### Préparation L’agent Zabbix est distribué sous forme d’archive au format zip. Après le téléchargement de l’archive vous devrez la décompresser. Vous pouvez choisir n’importe quel dossier pour stocker l’agent Zabbix et le fichier de configuration. ex : C:\zabbix Copiez les fichiers bin\\zabbix\_agentd.exe et conf\\zabbix\_agentd.conf vers la destination choisie précédemment. Editez le fichier c:\\zabbix\\zabbix\_agentd.conf selon vos besoins en prenant soin de spécifier correctement le paramètre “Hostname”. ##### Preparing frontend Make sure that Zabbix server address:port is **not defined** in the frontend configuration (found in `conf/zabbix.conf.php` of the frontend files directory). {width="600"} Zabbix frontend will autodetect the active node by reading settings from the nodes table in Zabbix database. Node address of the active node will be used as the Zabbix server address. ##### Préparation de l'interface Assurez-vous que address:port du serveur Zabbix n'est **pas défini** dans la configuration de l'interface (situé dans `conf/zabbix.conf.php` du répertoire des fichiers de l'interface). {width="600"} L'interface Zabbix détectera automatiquement le nœud actif en lisant les paramètres de la table des nœuds dans la base de données Zabbix. L'adresse de nœud du nœud actif sera utilisée comme adresse de serveur Zabbix. #### Preprocessing The **Preprocessing** tab allows to define transformation rules to apply to the result of discovery. One or several transformations are possible in this step. Transformations are executed in the order in which they are defined. All preprocessing is done by Zabbix server. See also: - [Preprocessing details](/manual/config/items/preprocessing/preprocessing_details) - [Preprocessing testing](/manual/config/items/preprocessing#testing)  |Type|<|<| |-|----------|----------------------------------------| | |*Transformation*|Description| |Text|<|<| |<|*Regular expression*|Match the received value to the <pattern> regular expression and replace value with the extracted <output>. The regular expression supports extraction of maximum 10 captured groups with the \\N sequence.<br>Parameters:<br>**pattern** - regular expression<br>**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.<br>If you mark the *Custom on fail* checkbox, it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.| |^|*Replace*|Find the search string and replace it with another (or nothing). All occurrences of the search string will be replaced.<br>Parameters:<br>**search string** - the string to find and replace, case-sensitive (required)<br>**replacement** - the string to replace the search string with. The replacement string may also be empty effectively allowing to delete the search string when found.<br>It is possible to use escape sequences to search for or replace line breaks, carriage return, tabs and spaces "\\n \\r \\t \\s"; backslash can be escaped as "\\\\" and escape sequences can be escaped as "\\\\n". Escaping of line breaks, carriage return, tabs is automatically done during low-level discovery.<br>Supported since 5.0.0.| |Structured data|<|<| |<|*JSONPath*|Extract value or fragment from JSON data using [JSONPath functionality](/manual/config/items/preprocessing/jsonpath_functionality).<br>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.| |<|*XML XPath*|Extract value or fragment from XML data using XPath functionality.<br>For this option to work, Zabbix server must be compiled with libxml support.<br>Examples:<br>`number(/document/item/value)` will extract `10` from `<document><item><value>10</value></item></document>`<br>`number(/document/item/@attribute)` will extract `10` from `<document><item attribute="10"></item></document>`<br>`/document/item` will extract `<item><value>10</value></item>` from `<document><item><value>10</value></item></document>`<br>Note that namespaces are not supported.<br>Supported since 4.4.0.<br>If you mark the *Custom on fail* checkbox, it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.| |<|*CSV to JSON*|Convert CSV file data into JSON format.<br>For more information, see: [CSV to JSON preprocessing](/manual/config/items/preprocessing/csv_to_json#csv_header_processing).<br>Supported since 4.4.0.| |^|*XML to JSON*|Convert data in XML format to JSON.<br>For more information, see: [Serialization rules](/manual/config/items/preprocessing/javascript/javascript_objects#serialization_rules).<br>If you mark the *Custom on fail* checkbox, it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.| |Custom scripts|<|<| |<|*JavaScript*|Enter JavaScript code in the block that appears when clicking in the parameter field or on *Open*.<br>Note that available JavaScript length depends on the [database used](/manual/config/items/item#custom_script_limit).<br>For more information, see: [Javascript preprocessing](/manual/config/items/preprocessing/javascript)| |Validation|<|<| |<|*Does not match regular expression*|Specify a regular expression that a value must not match.<br>E.g. `Error:(.*?)\.`<br>If you mark the *Custom on fail* checkbox, 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.<br>E.g. `$.errors`. If a JSON like `{"errors":"e1"}` is received, the next preprocessing step will not be executed.<br>If you mark the *Custom on fail* checkbox, 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.<br>No error will be reported in case of failing to parse invalid XML.<br>Supported since 4.4.0.<br>If you mark the *Custom on fail* checkbox, 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|<|<| |<|*Discard unchanged with heartbeat*|Discard a value if it has not changed within the defined time period (in seconds).<br>Positive integer values are supported to specify the seconds (minimum - 1 second). Time suffixes can be used in this field (e.g. 30s, 1m, 2h, 1d). User macros and low-level discovery macros can be used in this field.<br>Only one throttling option can be specified for a discovery item.<br>E.g. `1m`. If identical text is passed into this rule twice within 60 seconds, it will be discarded.<br>*Note*: Changing item prototypes does not reset throttling. Throttling is reset only when preprocessing steps are changed.| |Prometheus|<|<| |<|*Prometheus to JSON*|Convert required Prometheus metrics to JSON.<br>See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for more details.| Note that if the discovery rule has been applied to the host via template then the content of this tab is read-only. #### Prétraitement L'onglet **Prétraitement** permet de définir des règles de transformation à appliquer au résultat de la découverte. Une ou plusieurs transformations sont possibles dans cette étape. Les transformations sont exécutées dans l'ordre dans lequel elles sont définies. Tout le prétraitement est effectué par le serveur Zabbix. Voir également : - [Détails du prétraitement](/manual/config/items/preprocessing/preprocessing_details) - [Tests de prétraitement](/manual/config/items/preprocessing#testing)  |Type|<|<| |-|----------|----------------------------------------| | |*Transformation*|Description| |Texte|<|<| |<|*Expression régulière*|Faire correspondre la valeur reçue à l'expression régulière <motif> et remplacez la valeur par la <sortie> extraite. L'expression régulière prend en charge l'extraction d'un maximum de 10 groupes capturés avec la séquence \\N.<br>Paramètres :<br>**motif** - expression régulière<br>**sortie** - modèle de formatage de sortie. Une séquence d'échappement \\N (où N=1…9) est remplacée par le Nième groupe correspondant. Une séquence d'échappement \\0 est remplacée par le texte correspondant.<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |^|*Remplacer*|Trouver la chaîne de recherche et la remplacer par une autre (ou rien). Toutes les occurrences de la chaîne de recherche seront remplacées.<br>Paramètres :<br>**chaîne recherchée** - la chaîne à rechercher et à remplacer, sensible à la casse (obligatoire)<br>**remplacement** - la chaîne par laquelle remplacer la chaîne de recherche. La chaîne de remplacement peut également être vide, ce qui permet de supprimer la chaîne de recherche lorsqu'elle est trouvée.<br>Il est possible d'utiliser des séquences d'échappement pour rechercher ou remplacer les sauts de ligne, les retours chariot, les tabulations et les espaces "\\n \\r \\t \\s" ; la barre oblique inverse peut être échappée sous la forme "\\\\" et les séquences d'échappement peuvent être échappées sous la forme "\\\\n". L'échappement des sauts de ligne, des retours chariot et des tabulations est automatiquement effectué lors de la découverte de bas niveau.<br>Pris en charge depuis 5.0.0.| |Données structurées|<|<| |<|*JSONPath*|Extraire une valeur ou un fragment de données JSON à l'aide de la [fonctionnalité JSONPath](/manual/config/items/preprocessing/jsonpath_functionality).<br>Si vous cochez la case *Personnalisé en cas d'échec*, l'élément ne deviendra pas non pris en charge en cas d'échec de l'étape de prétraitement et il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié .| |<|*XPath XML*|Extraire une valeur ou un fragment de données XML à l'aide de la fonctionnalité XPath.<br>Pour que cette option fonctionne, le serveur Zabbix doit être compilé avec le support libxml.<br>Exemples :<br>`number(/document/item/value)` extraira `10` de `<document><item><value>10</value></item></document>`<br>`number(/document/item/@attribute)` extraira `10` de`<document><item attribute="10"></item></document>`<br>`/document/item` extraira `<item><value>10</value></item>` de `<document><item><value>10</value></item></document>`<br>Notez que les espaces de noms ne sont pas pris en charge.<br>Pris en charge depuis la version 4.4.0.<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |<|*CSV vers JSON*|Convertir les données du fichier CSV au format JSON.<br>Pour plus d'informations, voir : [Prétraitement CSV vers JSON](/manual/config/items/preprocessing/csv_to_json#csv_header_processing).<br>Pris en charge depuis 4.4.0.| |^|*XML vers JSON*|Convertir les données au format XML en JSON.<br>Pour plus d'informations, voir : [Règles de sérialisation](/manual/config/items/preprocessing/javascript/javascript_objects#serialization_rules).<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |Custom scripts|<|<| |Scripts personnalisés|<|<| |<|*JavaScript*|Entrer le code JavaScript dans le bloc qui apparaît en cliquant dans le champ paramètre ou sur *Ouvrir*.<br>Notez que la longueur JavaScript disponible dépend de la [base de données utilisée](/manual/config/items/item#custom_script_limit).<br>Pour plus d'informations, voir : [Prétraitement JavaScript](/manual/config/items/preprocessing/javascript)| |Validation|<|<| |<|*Ne correspond pas à l'expression régulière*|Spécifier une expression régulière à laquelle une valeur ne doit pas correspondre.<br>Par exemple `Error:(.*?)\.`<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |^|*Rechercher une erreur dans le JSON*|Rechercher un message d'erreur au niveau de l'application situé dans JSONpath. Arrêtez le traitement en cas de succès et si le message n'est pas vide ; sinon, continuez le traitement avec la valeur qui était avant cette étape de prétraitement. Notez que ces erreurs de service externes sont signalées à l'utilisateur telles quelles, sans ajouter d'informations sur l'étape de prétraitement.<br>Par exemple `$.errors`. Si un JSON comme `{"errors":"e1"}` est reçu, la prochaine étape de prétraitement ne sera pas exécutée.<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |^|*Rechercher une erreur dans le XML*|Rechercher un message d'erreur au niveau de l'application situé dans xpath. Arrêtez le traitement en cas de succès et si le message n'est pas vide ; sinon, continuez le traitement avec la valeur qui était avant cette étape de prétraitement. Notez que ces erreurs de service externe sont signalées à l'utilisateur telles quelles, sans ajouter d'informations sur l'étape de prétraitement.<br>Aucune erreur ne sera signalée en cas d'échec de l'analyse du XML non valide.<br>Pris en charge depuis la version 4.4.0.<br>Si vous cochez la case *Personnalisé en cas d'échec*, il est possible de spécifier des options de gestion des erreurs personnalisées : soit pour ignorer la valeur, soit pour définir une valeur spécifiée, soit pour définir un message d'erreur spécifié.| |Limitation|<|<| |<|*Ecarte les inchangés avec bit de vie*|Ignorer une valeur si elle n'a pas changé au cours de la période définie (en secondes).<br>Les valeurs entières positives sont prises en charge pour spécifier les secondes (minimum - 1 seconde). Des suffixes de temps peuvent être utilisés dans ce champ (par exemple 30s, 1m, 2h, 1d). Des macros utilisateur et des macros de découverte de bas niveau peuvent être utilisées dans ce champ.<br>Une seule option de limitation peut être spécifiée pour un élément de découverte.<br>Par exemple `1m`. Si un texte identique est passé deux fois dans cette règle en 60 secondes, il sera supprimé.<br>*Remarque* : La modification des prototypes d'éléments ne réinitialise pas la limitation. La limitation est réinitialisée uniquement lorsque les étapes de prétraitement sont modifiées.| |Prometheus|<|<| |<|*Prometheus vers JSON*|Convertire les métriques Prometheus requises en JSON.<br>Voir [Vérifications Prometheus](/manual/config/items/itemtypes/prometheus) pour plus de détails.| Notez que si la règle de découverte a été appliquée à l'hôte via un modèle, le contenu de cet onglet est en lecture seule. #### Preprocessing workers Zabbix server configuration file allows users to set count of preprocessing worker processes. StartPreprocessors configuration parameter should be used to set number of pre-forked instances of preprocessing workers. Optimal number of preprocessing workers can be determined by many factors, including the count of "preprocessable" items (items that require to execute any preprocessing steps), count of data gathering processes, average step count for item preprocessing, etc. But assuming that there is no heavy preprocessing operations like parsing of large XML / JSON chunks, number of preprocessing workers can match total number of data gatherers. This way, there will mostly (except for the cases when data from gatherer comes in bulk) be at least one unoccupied preprocessing worker for collected data. ::: notewarning Too many data gathering processes (pollers, unreachable pollers, ODBC pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers) together with IPMI manager, SNMP trapper and preprocessing workers can exhaust the per-process file descriptor limit for the preprocessing manager. This will cause Zabbix server to stop (usually shortly after the start, but sometimes it can take more time). The configuration file should be revised or the limit should be raised to avoid this situation. ::: #### Processus de travail de prétraitement Le fichier de configuration du serveur Zabbix permet aux utilisateurs de définir le nombre de processus de travail de prétraitement. Le paramètre de configuration StartPreprocessors doit être utilisé pour définir le nombre d'instances pré-forkées de processus de travail de prétraitement. Le nombre optimal de processus de travail de prétraitement peut être déterminé par de nombreux facteurs, y compris le nombre d'éléments "prétraitables" (éléments qui nécessitent d'exécuter des étapes de prétraitement), le nombre de processus de collecte de données, le nombre moyen d'étapes pour le prétraitement des éléments, etc. Mais en supposant qu'il n'y a pas d'opérations de prétraitement lourdes comme l'analyse de gros morceaux XML / JSON, le nombre de processus de travail de prétraitement peut correspondre au nombre total de collecteurs de données. De cette façon, il y aura la plupart du temps (sauf dans les cas où les données du collecteur arrivent en masse) au moins un agent de prétraitement inoccupé pour les données collectées. ::: notewarning Trop de processus de collecte de données (pollers, pollers d'inaccessibilité, pollers ODBC, pollers HTTP, pollers Java, pingers, trappeurs, proxypollers) associés au gestionnaire IPMI, au trappeur SNMP et aux agents de prétraitement peuvent épuiser la limite de descripteur de fichier par processus pour le gestionnaire de prétraitement. Cela entraînera l'arrêt du serveur Zabbix (généralement peu de temps après le démarrage, mais parfois cela peut prendre plus de temps). Le fichier de configuration doit être révisé ou la limite doit être augmentée pour éviter cette situation. ::: ### Pre-requisites Install MySQL database from the [official repository](https://dev.mysql.com/downloads/repo/yum/). See [MySQL documentation](https://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en/) for details on how to use MySQL repo. MySQL server is ready to accept secure connections using a self-signed certificate. To see, which users are using an encrypted connection, run the following query (Performance Schema should be turned ON): mysql> SELECT sbt.variable_value AS tls_version, t2.variable_value AS cipher, processlist_user AS user, processlist_host AS host FROM performance_schema.status_by_thread AS sbt JOIN performance_schema.threads AS t ON t.thread_id = sbt.thread_id JOIN performance_schema.status_by_thread AS t2 ON t2.thread_id = t.thread_id WHERE sbt.variable_name = 'Ssl_version' and t2.variable_name = 'Ssl_cipher' ORDER BY tls_version; ### Conditions préalables Installez la base de données MySQL à partir du [référentiel officiel](https://dev.mysql.com/downloads/repo/yum/). Voir la [documentation MySQL](https://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en/) pour plus de détails sur l'utilisation du référentiel MySQL. Le serveur MySQL est prêt à accepter des connexions sécurisées à l'aide d'un certificat auto-signé. Pour voir quels utilisateurs utilisent une connexion chiffrée, exécutez la requête suivante (le schéma de performances doit être activé) : mysql> SELECT sbt.variable_value AS tls_version, t2.variable_value AS cipher, processlist_user AS user, processlist_host AS host FROM performance_schema.status_by_thread AS sbt JOIN performance_schema.threads AS t ON t.thread_id = sbt.thread_id JOIN performance_schema.status_by_thread AS t2 ON t2.thread_id = t.thread_id WHERE sbt.variable_name = 'Ssl_version' and t2.variable_name = 'Ssl_cipher' ORDRE BY tls_version ; ### Pre-requisites Prior to configuring service monitoring, you need to have the hosts configured: - *HA node 1* with at least one trigger and a tag (preferably set on a trigger level) `component:HA node 1` - *HA node 2* with at least one trigger and a tag (preferably set on a trigger level) `component:HA node 2` ### Prérequis Avant de configurer la surveillance des services, vous devez configurer les hôtes : - *HA node 1* avec au moins un déclencheur et un tag (de préférence défini au niveau du déclencheur) `component:HA node 1` - *HA node 2* avec au moins un déclencheur et un tag (de préférence défini au niveau du déclencheur) `component:HA node 2` ##### Primary keys Primary keys are now used for all tables, including history tables, in new installations. There is no automatic upgrade to primary keys for existing installations. Instructions for a **manual upgrade** of history tables to primary keys in pre-existing installations are available for [MySQL/MariaDB](/manual/appendix/install/db_primary_keys#mysql), [PostgreSQL](/manual/appendix/install/db_primary_keys#postgresql), [TimescaleDB v1](/manual/appendix/install/db_primary_keys#timescaledb-v1) and [v2](/manual/appendix/install/db_primary_keys#timescaledb-v2), and [Oracle](/manual/appendix/install/db_primary_keys#oracle). ##### Clés primaires Les clés primaires sont désormais utilisées pour toutes les tables, y compris les tables d'historique, dans les nouvelles installations. Il n'y a pas de mise à niveau automatique vers les clés primaires pour les installations existantes. Des instructions pour une **mise à niveau manuelle** des tables d'historique vers les clés primaires dans les installations préexistantes sont disponibles pour [MySQL/MariaDB](/manual/appendix/install/db_primary_keys#mysql), [PostgreSQL](/manual/appendix/ install/db_primary_keys#postgresql), [TimescaleDB v1](/manual/appendix/install/db_primary_keys#timescaledb-v1) et [v2](/manual/appendix/install/db_primary_keys#timescaledb-v2), et [Oracle](/ manuel/annexe/install/db_primary_keys#oracle). #### Principle of least privilege The principle of least privilege should be used at all times for Zabbix. This principle means that user accounts (in Zabbix frontend) or process user (for Zabbix server/proxy or agent) have only those privileges that are essential to perform intended functions. In other words, user accounts at all times should run with as few privileges as possible. ::: noteimportant Giving extra permissions to 'zabbix' user will allow it to access configuration files and execute operations that can compromise the overall security of the infrastructure. ::: When implementing the least privilege principle for user accounts, Zabbix [frontend user types](/manual/config/users_and_usergroups/permissions) should be taken into account. It is important to understand that while a "Admin" user type has less privileges than "Super Admin" user type, it has administrative permissions that allow managing configuration and execute custom scripts. ::: noteclassic Some information is available even for non-privileged users. For example, while *Administration* → *Scripts* is not available for non-Super Admins, scripts themselves are available for retrieval by using Zabbix API. Limiting script permissions and not adding sensitive information (like access credentials, etc) should be used to avoid exposure of sensitive information available in global scripts. ::: #### Principe du moindre privilège Le principe du moindre privilège doit être utilisé à tout moment dans Zabbix. Ce principe signifie que les comptes d'utilisateurs (dans l'interface Zabbix) ou les utilisateurs de processus (pour le serveur/proxy ou l'agent Zabbix) n'ont que les privilèges essentiels pour exécuter les fonctions prévues. En d'autres termes, les comptes d'utilisateurs doivent à tout moment fonctionner avec le moins de privilèges possible. ::: noteimportant Donner des autorisations supplémentaires à l'utilisateur 'zabbix' lui permettra d'accéder aux fichiers de configuration et d'exécuter des opérations susceptibles de compromettre la sécurité globale de l'infrastructure. ::: Lors de la mise en œuvre du principe du moindre privilège pour les comptes d'utilisateurs, les [types d'utilisateurs frontend](/manual/config/users_and_usergroups/permissions) Zabbix doivent être pris en compte. Il est important de comprendre que même si un type d'utilisateur "Admin" a moins de privilèges qu'un type d'utilisateur "Super Admin", il dispose d'autorisations administratives qui permettent de gérer la configuration et d'exécuter des scripts personnalisés. ::: noteclassic Certaines informations sont disponibles même pour les utilisateurs non privilégiés. Par exemple, alors que *Administration* → *Scripts* n'est pas disponible pour les non-super administrateurs, les scripts eux-mêmes peuvent être récupérés à l'aide de l'API Zabbix. Limiter les autorisations de script et ne pas ajouter d'informations sensibles (comme les informations d'identification d'accès, etc.) doit être utilisé pour éviter l'exposition d'informations sensibles disponibles dans les scripts globaux. ::: #### Problem event popup The problem event popup includes the list of problem events for this trigger and, if defined, the trigger description and a clickable URL. {width="600"} To bring up the problem event popup: - roll a mouse over the problem duration in the *Duration* column of the *Problems* widget. The popup disappears once you remove the mouse from the duration. - click on the duration in the *Duration* column of the *Problems* widget. The popup disappears only if you click on the duration again. #### Fenêtre contextuelle d'événement problème La fenêtre contextuelle d'événement de problème inclut la liste des événements de problème pour ce déclencheur et, s'il est défini, la description du déclencheur et une URL cliquable. {width="600"} Pour afficher la fenêtre contextuelle d'événement de problème : - passez la souris sur la durée du problème dans la colonne *Durée* du widget *Problèmes*. La fenêtre contextuelle disparaît une fois que vous retirez la souris de la durée. - cliquez sur la durée dans la colonne *Durée* du widget *Problèmes*. La popup ne disparaît que si vous cliquez à nouveau sur la durée. #### Problem events A problem event is created: - when a trigger expression evaluates to TRUE if the trigger is in OK state; - each time a trigger expression evaluates to TRUE if multiple problem event generation is enabled for the trigger. #### Événements problèmes Un événement problème est créé : - lorsqu'une expression de déclencheur est évaluée à VRAI si le déclencheur est dans l'état OK ; - chaque fois qu'une expression de déclencheur est évaluée à VRAI si la génération multiples d'événements problèmes est activée pour le déclencheur. # problem.get # problem.get #### Problems Retrieve problems according to the given parameters. [Problem API](/manual/api/reference/problem) #### Problèmes Récupérez les problèmes en fonction de paramètres donnés. [API Problème](/manual/api/reference/problem) ### Problem tag Problem tags allow linking services with problem events. The problem tag object has the following properties. | Property | [Type](/manual/api/reference_commentary#data_types) | Description | |-----------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------| | **tag**<br>(required) | string | Problem tag name. | | operator | integer | Mapping condition operator.<br><br>Possible values:<br>0 - *(default)* equals;<br>2 - like. | | value | string | Problem tag value. | ### Tag de problème Les tags de problème permettent de lier des services à des événements de problème. L'objet de balise de problème a les propriétés suivantes. | Propriété | [Type](/manual/api/reference_commentary#data_types) | Description | |-----------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------| | **tag**<br>(obligatoire) | string | Nom du tag de problème. | | operator | integer | Opérateur de condition de mappage.<br><br>Valeurs possibles :<br>0 - *(par défaut)* equals;<br>2 - like. | | value | string | Valeur du tag de problème. | #### Problem tags Problem tags are used to match problems and services. These tags are specified at the primary service configuration tab. Only child services of the lowest hierarchy level may have problem tags defined and be directly correlated to problems. If problem tags match, the service status will change to the same status as the problem has. In case of several problems, a service will have the status of the most severe one. Status of a parent service is then calculated based on child services statuses according to Status calculation rules. If several tags are specified, *AND* logic is used: a problem must have all tags specified in the service configuration to be mapped to the service. {width=600} :::noteclassic A problem in Zabbix inherits tags from the whole chain of templates, hosts, items, web scenarios, and triggers. Any of these tags can be used for matching problems to services. ::: #### Tags de problème Les tags de problème sont utilisées pour faire correspondre les problèmes et les services. Ces tags sont spécifiés dans l'onglet de configuration du service principal. Seuls les services enfants du niveau hiérarchique le plus bas peuvent avoir des tags de problème définis et être directement corrélés aux problèmes. Si les tags du problème correspondent, l'état du service passera au même état que celui du problème. En cas de plusieurs problèmes, un service aura le statut du plus grave. Le statut d'un service parent est ensuite calculé en fonction des statuts des services enfants conformément aux règles de calcul du statut. Si plusieurs tags sont spécifiés, la logique *ET* est utilisée : un problème doit avoir touts les tags spécifiés dans la configuration du service pour être mappé au service. {width=600} :::noteclassique Un problème dans Zabbix hérite des tags de toute la chaîne de modèles, d'hôtes, d'éléments, de scénarios Web et de déclencheurs. Chacun de ces tags peut être utilisé pour faire correspondre les problèmes aux services. ::: ### Problem tag The problem tag object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Problem tag name.| |value|string|Problem tag value.| ### Tag de problème L'objet de tag de problème a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Nom du tag de problème.| |value|string|Valeur du tag de problème.| ### Problem tag The problem tag object is used to define which problems must be suppressed when the maintenance comes into effect. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Problem tag name.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - Equals;<br>2 - *(default)* Contains.| |value|string|Problem tag value.| Tags can only be specified for maintenance periods with data collection (`"maintenance_type":0`). ### Tag de problème L'objet de tag de problème est utilisé pour définir quels problèmes doivent être supprimés lorsque la maintenance entre en vigueur. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(obligatoire)|string|Nom du tag de problème.| |operator|integer|Opérateur de conditions.<br><br>Valeurs possibles :<br>0 - Egal;<br>2 - *(par défaut)* Contient.| |value|string|Valeur du tag de problème.| Les tags ne peuvent être spécifiées que pour les périodes de maintenance avec collecte de données (`"maintenance_type":0`). ##### Problem update window If a problem arises for a trigger with the *Manual close* flag, you can open the [problem update](/manual/acknowledges#updating_problems) popup window of that problem and close the problem manually. To close the problem, check the *Close problem* option in the form and click on *Update*.  All mandatory input fields are marked with a red asterisk. The request is processed by Zabbix server. Normally it will take a few seconds to close the problem. During that process *CLOSING* is displayed in *Monitoring* → *Problems* as the status of the problem. ##### Fenêtre de mise à jour du problème Si un problème survient pour un déclencheur avec l'indicateur *Fermeture manuelle*, vous pouvez ouvrir la fenêtre contextuelle [mise à jour du problème](/manual/acknowledges#updating_problems) de ce problème et fermer le problème manuellement. Pour fermer le problème, cochez l'option *Fermer le problème* dans le formulaire et cliquez sur *Mettre à jour*.  Tous les champs de saisie obligatoires sont marqués d'un astérisque rouge. La requête est traitée par le serveur Zabbix. Normalement, il faudra quelques secondes pour résoudre le problème. Au cours de ce processus, *CLOSING* s'affiche dans *Monitoring* → *Problems* comme état du problème. ##### Problem with dots So far so good. But what if an attribute name or a hash key contains dot symbol? Here is an example: jmx[com.example:Type=Hello,all.fruits.apple.weight] That's a problem. How to tell Zabbix that attribute name is "all.fruits", not just "all"? How to distinguish a dot that is part of the name from the dot that separates an attribute name and hash keys? Before **2.0.4** Zabbix Java gateway was unable to handle such situations and users were left with UNSUPPORTED items. Since 2.0.4 this is possible, all you need to do is to escape the dots that are part of the name with a backslash: jmx[com.example:Type=Hello,all\.fruits.apple.weight] Same way, if your hash key contains a dot you escape it: jmx[com.example:Type=Hello,all\.fruits.apple.total\.weight] ##### Problème avec les points Jusqu'ici tout va bien. Mais que faire si un nom d'attribut ou une clé de hachage contient un point ? Voici un exemple : jmx[com.example:Type=Hello,all.fruits.apple.weight] C'est un problème. Comment dire à Zabbix que le nom de l'attribut est "all.fruits", et pas seulement "all" ? Comment distinguer un point faisant partie du nom, du point qui sépare un nom d'attribut et des clés de hachage ? Avant la version **2.0.4**, la passerelle Java de Zabbix était incapable de gérer de telles situations et les utilisateurs restaient avec des éléments NON SUPPORTÉ. Depuis 2.0.4 cela est possible, tout ce que vous devez faire est d'échapper les points qui font partie du nom avec un backslash : jmx[com.example:Type=Hello,all\.fruits.apple.weight] De la même façon, si votre clé de hachage contient un point, vous l'échapperez : jmx[com.example:Type=Hello,all\.fruits.apple.total\.weight] ##### Process data |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**proc.cpu.util**\[<name>,<user>,<type>,<cmdline>,<mode>,<zone>\]|<|<|<| |Process CPU utilization percentage.|Float|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**type** - CPU utilization type:<br>*total* (default), *user*, *system*<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**mode** - data gathering mode: *avg1* (default), *avg5*, *avg15*<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.cpu.util\[,root\] → CPU utilization of all processes running under the "root" user<br>=> proc.cpu.util\[zabbix\_server,zabbix\] → CPU utilization of all zabbix\_server processes running under the zabbix user<br><br>The returned value is based on single CPU core utilization percentage. For example CPU utilization of a process fully using two cores is 200%.<br><br>The process CPU utilization data is gathered by a collector which supports the maximum of 1024 unique (by name, user and command line) queries. Queries not accessed during the last 24 hours are removed from the collector.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.<br><br>This key is supported since Zabbix 3.0.0 and is available on several platforms (see [Items supported by platform](/manual/appendix/items/supported_by_platform)).| |**proc.mem**\[<name>,<user>,<mode>,<cmdline>,<memtype>\]|<|<|<| |Memory used by process in bytes.|Integer - with `mode` as *max*, *min*, *sum*<br><br>Float - with `mode` as *avg*|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**mode** - possible values:<br>*avg*, *max*, *min*, *sum* (default)<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**memtype** - [type of memory](/manual/appendix/items/proc_mem_notes) used by process|Examples:<br>=> proc.mem\[,root\] → memory used by all processes running under the "root" user<br>=> proc.mem\[zabbix\_server,zabbix\] → memory used by all zabbix\_server processes running under the zabbix user<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → memory used by the most memory-hungry process running under oracle having oracleZABBIX in its command line<br><br>*Note*: When several processes use shared memory, the sum of memory used by processes may result in large, unrealistic values.<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.mem[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>The `memtype` parameter is supported on several [platforms](/manual/appendix/items/supported_by_platform) since Zabbix 3.0.0.| |**proc.num**\[<name>,<user>,<state>,<cmdline>,<zone>\]|<|<|<| |The number of processes.|Integer|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**state** (*disk* and *trace* options since version 3.4.0) - possible values:<br>*all* (default),<br>*disk* - uninterruptible sleep,<br>*run* - running,<br>*sleep* - interruptible sleep,<br>*trace* - stopped,<br>*zomb* - zombie<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.num\[,mysql\] → number of processes running under the mysql user<br>=> proc.num\[apache2,www-data\] → number of apache2 processes running under the www-data user<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → number of processes in sleep state running under oracle having oracleZABBIX in its command line<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>On Windows, only the `name` and `user` parameters are supported.<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.num[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.| ##### Données de processus |Clé d'élément|<|<|<| |--|--|------|------| |Description|Valeur de retour|Paramètres|Commentaires| |**proc.cpu.util**\[\<name\>,\<user\>,\<type\>,\<cmdline\>,\<mode\>,\<zone\>\]|<|<|<| |Pourcentage d'utilisation du processeur du processus.|Flottant|**name** - nom du processus (la valeur par défaut est *tous les processus*)<br>**user** - nom d'utilisateur (la valeur par défaut est *tous les utilisateurs*)<br>**type** - Type d'utilisation du processeur :<br>*total* (par défaut), *user*, *system*<br>**cmdline** - filtrer par ligne de commande (il s'agit d'une [expression régulière](/manual/regular_expressions#overview))<br>**mode** - mode de collecte de données : *avg1* (par défaut), *avg5*, *avg15*<br>**zone** - zone cible : *current* (par défaut), *all*. Ce paramètre est pris en charge sur Solaris uniquement.|Exemples :<br>=> proc.cpu.util\[,root\] → Utilisation du processeur de tous les processus exécutés sous l'utilisateur "root"<br>=> proc.cpu.util\[zabbix\_server,zabbix\] → Utilisation du processeur de tous les processus zabbix\_server exécutés sous l'utilisateur zabbix<br><br>La valeur renvoyée est basée sur le pourcentage d'utilisation d'un seul cœur de processeur. Par exemple, l'utilisation du processeur d'un processus utilisant entièrement deux cœurs est de 200 %.<br><br>Les données d'utilisation du processeur du processus sont collectées par un collecteur qui prend en charge un maximum de 1 024 requêtes uniques (par nom, utilisateur et ligne de commande). Les requêtes non consultées au cours des dernières 24 heures sont supprimées du collecteur.<br><br>*Notez* que lors de la définition du paramètre `zone` sur *current* (ou par défaut) dans le cas où l'agent a été compilé sur un Solaris sans prise en charge de la zone, mais s'exécutant sur un Solaris plus récent où les zones sont prises en charge, l'agent renverra NOTSUPPORTED (l'agent ne peut pas limiter les résultats à la seule zone actuelle). Cependant, *all* est pris en charge dans ce cas.<br><br>Cette clé est prise en charge depuis Zabbix 3.0.0 et est disponible sur plusieurs plates-formes (voir [Éléments pris en charge par la plate-forme](/manual/appendix/items/supported_by_platform)).| |**proc.mem**\[\<name\>,\<user\>,\<mode\>,\<cmdline\>,\<memtype\>\]|<|<|<| |Mémoire utilisée par le processus en octets.|Entier - avec `mode` sur *max*, *min*, *sum*<br><br>Flottant - avec `mode` sur *avg*|**name** - nom du processus (la valeur par défaut est *tous les processus*)<br>**user** - nom d'utilisateur (la valeur par défaut est *tous les utilisateurs*)<br>**mode** - valeurs possibles :<br>*avg*, *max*, *min*, *sum* (par défaut)<br>**cmdline** - filtrer par ligne de commande (il s'agit d'une [expression régulière](/manual/regular_expressions#overview))<br>**memtype** - [type de mémoire](/manual/appendix/items/proc_mem_notes) utilisé par le process|Exemples :<br>=> proc.mem\[,root\] → mémoire utilisée par tous les processus exécutés sous l'utilisateur "root"<br>=> proc.mem\[zabbix\_server,zabbix\] → mémoire utilisée par tous les processus zabbix\_server exécutés sous l'utilisateur zabbix<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → mémoire utilisée par le processus le plus gourmand en mémoire s'exécutant sous oracle ayant oracleZABBIX dans sa ligne de commande<br><br>*Remarque* : lorsque plusieurs processus utilisent de la mémoire partagée, la somme de la mémoire utilisée par les processus peut entraîner des valeurs importantes et irréalistes. <br><br>Voir les [notes](/manual/appendix/items/proc_mem_num_notes) lors de la sélection de processus avec les paramètres `name` et `cmdline` (spécifiques à Linux).<br><br>Lorsque cet élément est appelé à partir de la ligne de commande et contient un paramètre de ligne de commande (par exemple, en utilisant le mode de test de l'agent : `zabbix_agentd -t proc.mem[,,,apache2]`), un processus supplémentaire sera compté, car l'agent se comptera lui-même.<br><br>Le paramètre `memtype` est pris en charge sur plusieurs [plates-formes](/manual/appendix/items/supported_by_platform) depuis Zabbix 3.0.0.| |**proc.num**\[\<name\>,\<user\>,\<state\>,\<cmdline\>,\<zone\>\]|<|<|<| |Le nombre de processus.|Entier|**name** - nom du processus (la valeur par défaut est *tous les processus*)<br>**user** - nom d'utilisateur (la valeur par défaut est *tous les utilisateurs*)<br>**state** (options *disk* et *trace* depuis la version 3.4.0) - valeurs possibles :<br>*all* (par défaut),<br>*disk* - sommeil ininterruptible,<br>*run* - en fonctionnement,<br>*sleep* - sommeil interruptible,<br>*trace* - stoppé,<br>*zomb* - zombie<br>**cmdline** - filtrer par ligne de commande (il s'agit d'une [expression régulière](/manual/regular_expressions#overview))<br>**zone** - zone cible : *current* (par défaut), *all*. Ce paramètre est pris en charge sur Solaris uniquement.|Exemples :<br>=> proc.num\[,mysql\] → nombre de processus exécutés sous l'utilisateur mysql<br>=> proc.num\[apache2,www-data\] → nombre de processus apache2 exécutés sous l'utilisateur www-data<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → nombre de processus en état de veille s'exécutant sous oracle ayant oracleZABBIX dans sa ligne de commande<br><br>Voir les [notes](/manual/appendix/items/proc_mem_num_notes) lors de la sélection de processus avec les paramètres `name` et `cmdline` (spécifiques à Linux).<br><br>Sous Windows, seuls les paramètres `name` et `user` sont pris en charge.<br><br>Lorsque cet élément est appelé à partir de la ligne de commande et contient un paramètre de ligne de commande (par exemple, en utilisant le mode test de l'agent : `zabbix_agentd -t proc.num[,,,apache2]`), un processus supplémentaire sera compté, car l'agent se comptera lui-même.<br><br>*Notez* que lors de la définition du paramètre `zone` sur *current* (ou par défaut) dans le cas où l'agent a été compilé sur un Solaris sans prise en charge de la zone, mais s'exécutant sur un Solaris plus récent où les zones sont prises en charge, l'agent renverra NOTSUPPORTED (l'agent ne peut pas limiter les résultats à la seule zone actuelle). Cependant, *all* est pris en charge dans ce cas.| #### Process user Zabbix agent on UNIX is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run agent as any non-root user without any issues. If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run agent as 'root' if you modify the 'AllowRoot' parameter in the agent configuration file accordingly. #### Processus utilisateur L'agent Zabbix sous UNIX est conçu pour s'exécuter en tant qu'utilisateur non root. Il fonctionnera comme n'importe quel utilisateur non-root. Vous pouvez donc exécuter l'agent comme n'importe quel utilisateur non root sans aucun problème. Si vous essayez de l'exécuter en tant que 'root', il passera à un utilisateur 'zabbix' codé en dur, qui doit être présent sur votre système. Vous pouvez uniquement exécuter l'agent en tant que 'root' si vous modifiez le paramètre 'AllowRoot' dans le fichier de configuration de l'agent associé. ##### Process user Zabbix proxy is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run proxy as any non-root user without any issues. If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly. ##### Processus utilisateur Le proxy Zabbix est conçu pour s'exécuter en tant qu'utilisateur non root. Il fonctionnera comme n'importe quel utilisateur non-root. Vous pouvez donc exécuter le proxy comme n'importe quel utilisateur non root sans aucun problème. Si vous essayez de l'exécuter en tant que 'root', il passera à un utilisateur 'zabbix' codé en dur, qui doit être présent sur votre système. Vous pouvez uniquement exécuter le proxy en tant que 'root' si vous modifiez le paramètre 'AllowRoot' dans le fichier de configuration du proxy associé. ##### Process user Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run server as any non-root user without any issues. If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be [present](/manual/installation/install) on your system. You can only run server as 'root' if you modify the 'AllowRoot' parameter in the server configuration file accordingly. If Zabbix server and [agent](agent) are run on the same machine it is recommended to use a different user for running the server than for running the agent. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password. ##### Processus utilisateur Le serveur Zabbix est conçu pour fonctionner en tant qu'utilisateur non root. Il fonctionnera avec n’importe quel utilisateur non-root qui lancera les processus. Vous pouvez donc exécuter le serveur en tant qu'utilisateur non root sans aucun problème. Si vous essayez de l'exécuter en tant que 'root', il passera à un utilisateur 'zabbix' codé en dur, qui doit être [présent](/manual/installation/install) sur votre système. Vous pouvez uniquement exécuter le serveur en tant que 'root' si vous modifiez le paramètre 'AllowRoot' dans le fichier de configuration associé du serveur. Si le serveur et l'[agent](agent) Zabbix sont exécutés sur la même machine, il est recommandé d'utiliser un autre utilisateur pour exécuter le serveur que pour exécuter l'agent. Sinon, si les deux sont exécutés sous le même utilisateur, l'agent peut accéder au fichier de configuration du serveur et tout utilisateur de niveau Admin dans Zabbix peut facilement récupérer, par exemple, le mot de passe de la base de données. #### Prometheus to JSON Data from Prometheus can be used for low-level discovery. In this case data in JSON format are needed and the *Prometheus to JSON* preprocessing option will return exactly that. For more details, see [Discovery using Prometheus data](/manual/discovery/low_level_discovery/examples/prometheus). #### Prometheus vers JSON Les données de Prometheus peuvent être utilisées pour la découverte de bas niveau. Dans ce cas, des données au format JSON sont nécessaires et l'option de prétraitement *Prometheus vers JSON* renverra exactement cela. Pour plus de détails, voir [Découverte à l'aide des données Prometheus](/manual/discovery/low_level_discovery/examples/prometheus). ##### Prometheus to JSON In the discovery rule, go to the Preprocessing tab and select the *Prometheus to JSON* preprocessing option. Data in JSON format are needed for discovery and the *Prometheus to JSON* preprocessing option will return exactly that, with the following attributes: - metric name - metric value - help (if present) - type (if present) - labels (if present) - raw line For example, querying `wmi_logical_disk_free_bytes`:  from these Prometheus lines: # HELP wmi_logical_disk_free_bytes Free space in bytes (LogicalDisk.PercentFreeSpace) # TYPE wmi_logical_disk_free_bytes gauge wmi_logical_disk_free_bytes{volume="C:"} 3.5180249088e+11 wmi_logical_disk_free_bytes{volume="D:"} 2.627731456e+09 wmi_logical_disk_free_bytes{volume="HarddiskVolume4"} 4.59276288e+08 will return: ``` {.java} [ { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "C:" }, "value": "3.5180249088e+11", "line_raw": "wmi_logical_disk_free_bytes{volume=\"C:\"} 3.5180249088e+11" }, { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "D:" }, "value": "2.627731456e+09", "line_raw": "wmi_logical_disk_free_bytes{volume=\"D:\"} 2.627731456e+09" }, { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "HarddiskVolume4" }, "value": "4.59276288e+08", "line_raw": "wmi_logical_disk_free_bytes{volume=\"HarddiskVolume4\"} 4.59276288e+08" } ] ``` ##### Prometheus vers JSON Dans la règle de découverte, accédez à l'onglet Prétraitement et sélectionnez l'option de prétraitement *Prometheus vers JSON*. Les données au format JSON sont nécessaires pour la découverte et l'option de prétraitement *Prometheus vers JSON* renverra exactement cela, avec les attributs suivants : - nom de la métrique - valeur métrique - aide (si présente) - type (si présent) - étiquettes (si présentes) - ligne brute Par exemple, en interrogeant `wmi_logical_disk_free_bytes` :  à partir de ces lignes Prometheus : # HELP wmi_logical_disk_free_bytes Free space in bytes (LogicalDisk.PercentFreeSpace) # TYPE wmi_logical_disk_free_bytes gauge wmi_logical_disk_free_bytes{volume="C:"} 3.5180249088e+11 wmi_logical_disk_free_bytes{volume="D:"} 2.627731456e+09 wmi_logical_disk_free_bytes{volume="HarddiskVolume4"} 4.59276288e+08 renverra : ``` {.java} [ { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "C:" }, "value": "3.5180249088e+11", "line_raw": "wmi_logical_disk_free_bytes{volume=\"C:\"} 3.5180249088e+11" }, { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "D:" }, "value": "2.627731456e+09", "line_raw": "wmi_logical_disk_free_bytes{volume=\"D:\"} 2.627731456e+09" }, { "name": "wmi_logical_disk_free_bytes", "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)", "type": "gauge", "labels": { "volume": "HarddiskVolume4" }, "value": "4.59276288e+08", "line_raw": "wmi_logical_disk_free_bytes{volume=\"HarddiskVolume4\"} 4.59276288e+08" } ] ``` #### Property labels Some of the objects properties are marked with short labels to describe their behavior. The following labels are used: - *readonly* - the value of the property is set automatically and cannot be defined or changed by the client; - *constant* - the value of the property can be set when creating an object, but cannot be changed after. #### Étiquettes de propriétés Certaines propriétés des objets sont marquées par de courtes étiquettes décrivant leur comportement. Les étiquettes suivantes sont utilisées : - *readonly* - la valeur de la propriété est définie automatiquement et ne peut pas être définie ou modifiée par le client (lecture seule) ; - *constante* - la valeur de la propriété peut être définie lors de la création d'un objet, mais ne peut pas être modifiée après. | Property | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------| | **name**<br>(required) | string | Name of the excluded downtime. | | **period\_from**<br>(required) | integer | Starting time of the excluded downtime (inclusive).<br><br>Possible values: timestamp. | | **period\_to**<br>(required) | integer | Ending time of the excluded downtime (exclusive).<br><br>Possible values: timestamp. | | Propriété | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------| | **name**<br>(obligatoire) | string | Nom du temps d'arrêt exclu. | | **period\_from**<br>(obligatoire) | integer | Heure de début du temps d'arrêt exclu (inclus).<br><br>Valeurs possibles : timestamp. | | **period\_to**<br>(obligatoire) | integer | Heure de fin du temps d'arrêt exclu (exclus)..<br><br>Valeurs possibles : timestamp. | | Property | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | **period\_from**<br>(required) | integer | Starting time of the recurrent weekly period of time (inclusive).<br><br>Possible values: number of seconds (counting from Sunday). | | **period\_to**<br>(required) | integer | Ending time of the recurrent weekly period of time (exclusive).<br><br>Possible values: number of seconds (counting from Sunday). | | Propriété | [Type](/manual/api/reference_commentary#data_types) | Description | |--------------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | **period\_from**<br>(obligatoire) | integer | Heure de début de la période hebdomadaire récurrente (incluse).<br><br>Valeurs possibles : nombre de secondes (à partir du dimanche). | | **period\_to**<br>(obligatoire) | integer | Heure de fin de la période hebdomadaire récurrente (exclue).<br><br>Valeurs possibles : nombre de secondes (à partir du dimanche). | ##### Protection against brute force attacks In case of five consecutive failed login attempts, Zabbix interface will pause for 30 seconds in order to prevent brute force and dictionary attacks. The IP address of a failed login attempt will be displayed after a successful login. ##### Protection contre les attaques par force brute Dans le cas de cinq tentatives de connexion infructueuses consécutives, l\'interface Zabbix s\'arrêtera pendant 30 secondes afin d\'empêcher les attaques par force brute et par dictionnaire. L\'adresse IP d\'une tentative de connexion échouée sera affichée après une connexion réussie. #### Proxies In a [proxy](/manual/distributed_monitoring/proxies#configuration) configuration, user macros can be used in the following field: |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Interface port (for passive proxy)|<|no| #### Proxys Dans une configuration [proxy](/manual/distributed_monitoring/proxies#configuration), les macros utilisateur peuvent être utilisées dans le champ suivant : |Emplacement|<|Plusieurs macros/mix avec du texte^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Port d'interface (pour un proxy passif)|<|non| #### Proxies Manage the proxies used in your distributed monitoring setup. [Proxy API](/manual/api/reference/proxy) #### Proxys Gérez les proxys utilisés dans votre configuration de surveillance distribuée. [API Proxy](/manual/api/reference/proxy) ##### Proxy config request The `proxy config` request is sent by proxy to obtain proxy configuration data. This request is sent every `ConfigFrequency` (proxy configuration parameter) seconds. |name|<|<|<|value type|description| |-|-|-|----------|----------|----------------------------------------| |proxy→server:|<|<|<|<|<| |**request**|<|<|<|*string*|'proxy config'| |**host**|<|<|<|*string*|Proxy name.| |**version**|<|<|<|*string*|Proxy version (<major>.<minor>.<build>).| |server→proxy:|<|<|<|<|<| |**request**|<|<|<|*string*|'proxy config'| |**<table>**|<|<|<|*object*|One or more objects with <table> data.| | |**fields**|<|<|*array*|Array of field names.| |^| |\-|<|*string*|Field name.| |^|**data**|<|<|*array*|Array of rows.| |^| |\-|<|*array*|Array of columns.| |^|^| |\-|*string*,*number*|Column value with type depending on the column type in database schema.| |proxy→server:|<|<|<|<|<| |**response**|<|<|<|*string*|Request success information ('success' or 'failed').| Example: proxy→server: ``` {.javascript} { "request": "proxy config", "host": "Proxy #12", "version":"5.4.0" } ``` server→proxy: ``` {.javascript} { "globalmacro":{ "fields":[ "globalmacroid", "macro", "value" ], "data":[ [ 2, "{$SNMP_COMMUNITY}", "public" ] ] }, "hosts":{ "fields":[ "hostid", "host", "status", "ipmi_authtype", "ipmi_privilege", "ipmi_username", "ipmi_password", "name", "tls_connect", "tls_accept", "tls_issuer", "tls_subject", "tls_psk_identity", "tls_psk" ], "data":[ [ 10001, "Linux", 3, -1, 2, "", "", "Linux", 1, 1, "", "", "", "" ], [ 10050, "Zabbix Agent", 3, -1, 2, "", "", "Zabbix Agent", 1, 1, "", "", "", "" ], [ 10105, "Logger", 0, -1, 2, "", "", "Logger", 1, 1, "", "", "", "" ] ] }, "interface":{ "fields":[ "interfaceid", "hostid", "main", "type", "useip", "ip", "dns", "port", "bulk" ], "data":[ [ 2, 10105, 1, 1, 1, "127.0.0.1", "", "10050", 1 ] ] }, ... } ``` proxy→server: ``` {.javascript} { "response": "success" } ``` ##### Demande de configuration proxy La requête `proxy config` est envoyée par le proxy pour obtenir les données de configuration du proxy. Cette requête est envoyée à chaque `ConfigFrequency` (paramètre de configuration du proxy) secondes. |nom|<|<|<|type de valeur|description| |-|-|-|----------|----------|--------------------- -------------------| |proxy→server :|<|<|<|<|<| |**request**|<|<|<|*chaîne*|'proxy config'| |**host**|<|<|<|*chaîne*|Nom du proxy.| |**version**|<|<|<|*chaîne*|Version du proxy (<majeur>.<mineur>.<build>).| |server→proxy :|<|<|<|<|<| |**request**|<|<|<|*chaîne*|'proxy config'| |**<table>**|<|<|<|*objet*|Un ou plusieurs objets avec des données <table>.| | |**fields**|<|<|*tableau*|Tableau de noms de champs.| |^| |\-|<|*chaîne*|Nom du champ.| |^|**data**|<|<|*tableau*|Tableau de lignes.| |^| |\-|<|*array*|Tableau de colonnes.| |^|^| |\-|*chaîne*,*nombre*|Valeur de colonne dont le type dépend du type de colonne dans le schéma de la base de données.| |proxy→server :|<|<|<|<|<| |**response**|<|<|<|*chaîne*|Demande d'informations sur le succès ('success' ou 'failed').| Exemple: proxy→server : ``` {.javascript} { "request": "proxy config", "host": "Proxy #12", "version":"5.4.0" } ``` server→proxy : ``` {.javascript} { "globalmacro":{ "fields":[ "globalmacroid", "macro", "value" ], "data":[ [ 2, "{$SNMP_COMMUNITY}", "public" ] ] }, "hosts":{ "fields":[ "hostid", "host", "status", "ipmi_authtype", "ipmi_privilege", "ipmi_username", "ipmi_password", "name", "tls_connect", "tls_accept", "tls_issuer", "tls_subject", "tls_psk_identity", "tls_psk" ], "data":[ [ 10001, "Linux", 3, -1, 2, "", "", "Linux", 1, 1, "", "", "", "" ], [ 10050, "Zabbix Agent", 3, -1, 2, "", "", "Zabbix Agent", 1, 1, "", "", "", "" ], [ 10105, "Logger", 0, -1, 2, "", "", "Logger", 1, 1, "", "", "", "" ] ] }, "interface":{ "fields":[ "interfaceid", "hostid", "main", "type", "useip", "ip", "dns", "port", "bulk" ], "data":[ [ 2, 10105, 1, 1, 1, "127.0.0.1", "", "10050", 1 ] ] }, ... } ``` proxy→server : ``` {.javascript} { "response": "success" } ``` ##### Proxy config request The `proxy config` request is sent by server to provide proxy configuration data. This request is sent every `ProxyConfigFrequency` (server configuration parameter) seconds. |name|<|<|<|value type|description| |-|-|-|----------|----------|----------------------------------------| |server→proxy:|<|<|<|<|<| |**request**|<|<|<|*string*|'proxy config'| |**<table>**|<|<|<|*object*|One or more objects with <table> data.| | |**fields**|<|<|*array*|Array of field names.| |^| |\-|<|*string*|Field name.| |^|**data**|<|<|*array*|Array of rows.| |^| |\-|<|*array*|Array of columns.| |^|^| |\-|*string*,*number*|Column value with type depending on the column type in database schema.| |proxy→server:|<|<|<|<|<| |**response**|<|<|<|*string*|Request success information ('success' or 'failed').| |**version**|<|<|<|*string*|Proxy version (<major>.<minor>.<build>).| Example: server→proxy: ``` {.javascript} { "request": "proxy config", "globalmacro":{ "fields":[ "globalmacroid", "macro", "value" ], "data":[ [ 2, "{$SNMP_COMMUNITY}", "public" ] ] }, "hosts":{ "fields":[ "hostid", "host", "status", "ipmi_authtype", "ipmi_privilege", "ipmi_username", "ipmi_password", "name", "tls_connect", "tls_accept", "tls_issuer", "tls_subject", "tls_psk_identity", "tls_psk" ], "data":[ [ 10001, "Linux", 3, -1, 2, "", "", "Linux", 1, 1, "", "", "", "" ], [ 10050, "Zabbix Agent", 3, -1, 2, "", "", "Zabbix Agent", 1, 1, "", "", "", "" ], [ 10105, "Logger", 0, -1, 2, "", "", "Logger", 1, 1, "", "", "", "" ] ] }, "interface":{ "fields":[ "interfaceid", "hostid", "main", "type", "useip", "ip", "dns", "port", "bulk" ], "data":[ [ 2, 10105, 1, 1, 1, "127.0.0.1", "", "10050", 1 ] ] }, ... } ``` proxy→server: ``` {.javascript} { "response": "success", "version": "6.0.0" } ``` ##### Demande de configuration proxy La requête `proxy config` est envoyée par le serveur pour fournir les données de configuration du proxy. Cette requête est envoyée chaque `ProxyConfigFrequency` (paramètre de configuration du serveur) secondes. |Nom|<|<|<|Type de valeur|Description| |-|-|-|----------|----------|----------------------------------------| |serveur→proxy :|<|<|<|<|<| |**request**|<|<|<|*chaîne*|'proxy config'| |**<table>**|<|<|<|*objet*|Un ou plusieurs objets avec des données \<table\>.| | |**fields**|<|<|*tableau*|Tableau de noms de champs.| |^| |\-|<|*chaîne*|Nom du champ.| |^|**data**|<|<|*tableau*|Tableau de lignes.| |^| |\-|<|*tableau*|Tableau de colonnes.| |^|^| |\-|*chaîne*,*nombre*|Valeur de colonne dont le type dépend du type de colonne dans le schéma de la base de données.| |proxy→serveur :|<|<|<|<|<| |**response**|<|<|<|*chaîne*|Demande d'informations sur le succès ('success' ou 'failed').| |**version**|<|<|<|*chaîne*|Version du proxy (\<majeur\>.\<mineur\>.\<build\>).| Exemple : serveur→proxy : ``` {.javascript} { "request": "proxy config", "globalmacro":{ "fields":[ "globalmacroid", "macro", "value" ], "data":[ [ 2, "{$SNMP_COMMUNITY}", "public" ] ] }, "hosts":{ "fields":[ "hostid", "host", "status", "ipmi_authtype", "ipmi_privilege", "ipmi_username", "ipmi_password", "name", "tls_connect", "tls_accept", "tls_issuer", "tls_subject", "tls_psk_identity", "tls_psk" ], "data":[ [ 10001, "Linux", 3, -1, 2, "", "", "Linux", 1, 1, "", "", "", "" ], [ 10050, "Zabbix Agent", 3, -1, 2, "", "", "Zabbix Agent", 1, 1, "", "", "", "" ], [ 10105, "Logger", 0, -1, 2, "", "", "Logger", 1, 1, "", "", "", "" ] ] }, "interface":{ "fields":[ "interfaceid", "hostid", "main", "type", "useip", "ip", "dns", "port", "bulk" ], "data":[ [ 2, 10105, 1, 1, 1, "127.0.0.1", "", "10050", 1 ] ] }, ... } ``` proxy→serveur : ``` {.javascript} { "response": "success", "version": "6.0.0" } ``` ##### Proxy configuration HA cluster nodes (servers) must be listed in the configuration of either passive or active Zabbix proxy. For a passive proxy, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_proxy) of the proxy, separated by a **comma**. ``` Server=zabbix-node-01,zabbix-node-02 ``` For an active proxy, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_proxy) of the proxy, separated by a **semicolon**. ``` Server=zabbix-node-01;zabbix-node-02 ``` ##### Configuration du proxy Les nœuds de cluster HA (serveurs) doivent être répertoriés dans la configuration du proxy Zabbix passif ou actif. Pour un proxy passif, le nom des nœuds doivent être listés dans le [paramètre](/manual/appendix/config/zabbix_proxy) Server du proxy, séparés par une **virgule**. ``` Server=zabbix-node-01,zabbix-node-02 ``` Pour un proxy actif, le nom des nœud doivent être répertoriés dans le [paramètre](/manual/appendix/config/zabbix_proxy) Server du proxy, séparés par un **point-virgule**. ``` Server=zabbix-node-01;zabbix-node-02 ``` # proxy.create # proxy.create ##### Proxy data request The `proxy data` request is sent by proxy to provide host interface availability, history, discovery and autoregistration data. This request is sent every `DataSenderFrequency` (proxy configuration parameter) seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks (with an empty `proxy data` request). |name|<|value type|description| |-|----------|----------|----------------------------------------| |proxy→server:|<|<|<| |**request**|<|*string*|'proxy data'| |**host**|<|*string*|Proxy name.| |**session**|<|*string*|Data session token.| |**interface availability**|<|*array*|*(optional)* Array of interface availability data objects.| | |**interfaceid**|*number*|Interface identifier.| |^|**available**|*number*|Interface availability:<br><br>**0**, *INTERFACE\_AVAILABLE\_UNKNOWN* - unknown<br>**1**, *INTERFACE\_AVAILABLE\_TRUE* - available<br>**2**, *INTERFACE\_AVAILABLE\_FALSE* - unavailable| |^|**error**|*string*|Interface error message or empty string.| |**history data**|<|*array*|*(optional)* Array of history data objects.| | |**itemid**|*number*|Item identifier.| |^|**clock**|*number*|Item value timestamp (seconds).| |^|**ns**|*number*|Item value timestamp (nanoseconds).| |^|**value**|*string*|*(optional)* Item value.| |^|**id**|*number*|Value identifier (ascending counter, unique within one data session).| |^|**timestamp**|*number*|*(optional)* Timestamp of log type items.| |^|**source**|*string*|*(optional)* Eventlog item source value.| |^|**severity**|*number*|*(optional)* Eventlog item severity value.| |^|**eventid**|*number*|*(optional)* Eventlog item eventid value.| |^|**state**|*string*|*(optional)* Item state:<br>**0**, *ITEM\_STATE\_NORMAL*<br>**1**, *ITEM\_STATE\_NOTSUPPORTED*| |^|**lastlogsize**|*number*|*(optional)* Last log size of log type items.| |^|**mtime**|*number*|*(optional)* Modification time of log type items.| |**discovery data**|<|*array*|*(optional)* Array of discovery data objects.| | |**clock**|*number*|Discovery data timestamp.| |^|**druleid**|*number*|Discovery rule identifier.| |^|**dcheckid**|*number*|Discovery check identifier or null for discovery rule data.| |^|**type**|*number*|Discovery check type:<br><br>**-1** discovery rule data<br>**0**, *SVC\_SSH* - SSH service check<br>**1**, *SVC\_LDAP* - LDAP service check<br>**2**, *SVC\_SMTP* - SMTP service check<br>**3**, *SVC\_FTP* - FTP service check<br>**4**, *SVC\_HTTP* - HTTP service check<br>**5**, *SVC\_POP* - POP service check<br>**6**, *SVC\_NNTP* - NNTP service check<br>**7**, *SVC\_IMAP* - IMAP service check<br>**8**, *SVC\_TCP* - TCP port availability check<br>**9**, *SVC\_AGENT* - Zabbix agent<br>**10**, *SVC\_SNMPv1* - SNMPv1 agent<br>**11**, *SVC\_SNMPv2* - SNMPv2 agent<br>**12**, *SVC\_ICMPPING* - ICMP ping<br>**13**, *SVC\_SNMPv3* - SNMPv3 agent<br>**14**, *SVC\_HTTPS* - HTTPS service check<br>**15**, *SVC\_TELNET* - Telnet availability check| |^|**ip**|*string*|Host IP address.| |^|**dns**|*string*|Host DNS name.| |^|**port**|*number*|*(optional)* Service port number.| |^|**key\_**|*string*|*(optional)* Item key for discovery check of type **9** *SVC\_AGENT*| |^|**value**|*string*|*(optional)* Value received from the service, can be empty for most services.| |^|**status**|*number*|*(optional)* Service status:<br><br>**0**, *DOBJECT\_STATUS\_UP* - Service UP<br>**1**, *DOBJECT\_STATUS\_DOWN* - Service DOWN| |**autoregistration**|<|*array*|*(optional)* Array of autoregistration data objects.| | |**clock**|*number*|Autoregistration data timestamp.| |^|**host**|*string*|Host name.| |^|**ip**|*string*|*(optional)* Host IP address.| |^|**dns**|*string*|*(optional)* Resolved DNS name from IP address.| |^|**port**|*string*|*(optional)* Host port.| |^|**host\_metadata**|*string*|*(optional)* Host metadata sent by the agent (based on HostMetadata or HostMetadataItem agent configuration parameter).| |**tasks**|<|*array*|*(optional)* Array of tasks.| | |**type**|*number*|Task type:<br><br>**0**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND\_RESULT* - remote command result| |^|**status**|*number*|Remote-command execution status:<br><br>**0**, *ZBX\_TM\_REMOTE\_COMMAND\_COMPLETED* - remote command completed successfully<br>**1**, *ZBX\_TM\_REMOTE\_COMMAND\_FAILED* - remote command failed| |^|**error**|*string*|*(optional)* Error message.| |^|**parent\_taskid**|*number*|Parent task ID.| |**more**|<|*number*|*(optional)* 1 - there are more history data to send.| |**clock**|<|*number*|*(optional)* Data transfer timestamp (seconds).| |**ns**|<|*number*|*(optional)* Data transfer timestamp (nanoseconds).| |**version**|<|*string*|Proxy version (<major>.<minor>.<build>).| |server→proxy:|<|<|<| |**response**|<|*string*|Request success information ('success' or 'failed').| |**upload**|<|*string*|Upload control for historical data (history, autoregistration, host availability, network discovery):<br>**enabled** - normal operation<br>**disabled** - server is not accepting data (possibly due to internal cache over limit)| |**tasks**|<|*array*|*(optional)* Array of tasks.| | |**type**|*number*|Task type:<br><br>**1**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND* - remote command| |^|**clock**|*number*|Task creation time.| |^|**ttl**|*number*|Time in seconds after which the task expires.| |^|**commandtype**|*number*|Remote-command type:<br><br>**0**, *ZBX\_SCRIPT\_TYPE\_CUSTOM\_SCRIPT* - use custom script<br>**1**, *ZBX\_SCRIPT\_TYPE\_IPMI* - use IPMI<br>**2**, *ZBX\_SCRIPT\_TYPE\_SSH* - use SSH<br>**3**, *ZBX\_SCRIPT\_TYPE\_TELNET* - use Telnet<br>**4**, *ZBX\_SCRIPT\_TYPE\_GLOBAL\_SCRIPT* - use global script (currently functionally equivalent to custom script)| |^|**command**|*string*|Remote command to execute.| |^|**execute\_on**|*number*|Execution target for custom scripts:<br><br>**0**, *ZBX\_SCRIPT\_EXECUTE\_ON\_AGENT* - execute script on agent<br>**1**, *ZBX\_SCRIPT\_EXECUTE\_ON\_SERVER* - execute script on server<br>**2**, *ZBX\_SCRIPT\_EXECUTE\_ON\_PROXY* - execute script on proxy| |^|**port**|*number*|*(optional)* Port for Telnet and SSH commands.| |^|**authtype**|*number*|*(optional)* Authentication type for SSH commands.| |^|**username**|*string*|*(optional)* User name for Telnet and SSH commands.| |^|**password**|*string*|*(optional)* Password for Telnet and SSH commands.| |^|**publickey**|*string*|*(optional)* Public key for SSH commands.| |^|**privatekey**|*string*|*(optional)* Private key for SSH commands.| |^|**parent\_taskid**|*number*|Parent task ID.| |^|**hostid**|*number*|Target host ID.| Example: proxy→server: ``` {.javascript} { "request": "proxy data", "host": "Proxy #12", "session": "12345678901234567890123456789012", "interface availability": [ { "interfaceid": 1, "available": 1, "error": "" }, { "interfaceid": 2, "available": 2, "error": "Get value from agent failed: cannot connect to [[127.0.0.1]:10049]: [111] Connection refused" }, { "interfaceid": 3, "available": 1, "error": "" }, { "interfaceid": 4, "available": 1, "error": "" } ], "history data":[ { "itemid":"12345", "clock":1478609647, "ns":332510044, "value":"52956612", "id": 1 }, { "itemid":"12346", "clock":1478609647, "ns":330690279, "state":1, "value":"Cannot find information for this network interface in /proc/net/dev.", "id": 2 } ], "discovery data":[ { "clock":1478608764, "drule":2, "dcheck":3, "type":12, "ip":"10.3.0.10", "dns":"vdebian", "status":1 }, { "clock":1478608764, "drule":2, "dcheck":null, "type":-1, "ip":"10.3.0.10", "dns":"vdebian", "status":1 } ], "auto registration":[ { "clock":1478608371, "host":"Logger1", "ip":"10.3.0.1", "dns":"localhost", "port":"10050" }, { "clock":1478608381, "host":"Logger2", "ip":"10.3.0.2", "dns":"localhost", "port":"10050" } ], "tasks":[ { "type": 2, "clock":1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 2, "clock":1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ], "tasks":[ { "type": 0, "status": 0, "parent_taskid": 10 }, { "type": 0, "status": 1, "error": "No permissions to execute task.", "parent_taskid": 20 } ], "version":"5.4.0" } ``` server→proxy: ``` {.javascript} { "response": "success", "upload": "enabled", "tasks":[ { "type": 1, "clock": 1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 1, "clock": 1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ] } ``` ##### Demande de données proxy La demande de `données proxy` est envoyée par proxy pour fournir des données de disponibilité, d'historique, de découverte et d'enregistrement automatique de l'interface hôte. Cette requête est envoyée toutes les `DataSenderFrequency` (paramètre de configuration du proxy) secondes. Notez que le proxy actif interrogera toujours le serveur Zabbix toutes les secondes pour les tâches de commande à distance (avec une requête `proxy data` vide). |nom|<|type de valeur|description| |-|----------|----------|----------------------------------------| |proxy→serveur :|<|<|<| |**request**|<|*chaîne*|'proxy data'| |**host**|<|*chaîne*|Nom du proxy.| |**session**|<|*chaîne*|Jeton de session de données.| |**interface availability**|<|*tableau*|*(optionnel)* Tableau d'objets de données de disponibilité d'interface.| | |**interfaceid**|*nombre*|Identifiant d'interface.| |^|**available**|*nombre*|Disponibilité des interfaces :<br><br>**0**, *INTERFACE\_AVAILABLE\_UNKNOWN* - inconnue<br>**1**, *INTERFACE\_AVAILABLE\_TRUE* - disponible<br>**2**, *INTERFACE\_AVAILABLE\_FALSE* - indisponible| |^|**error**|*chaîne*|Message d'erreur d'interface ou chaîne vide.| |**history data**|<|*tableau*|*(optionnel)* Tableau d'objets de données d'historique.| | |**itemid**|*nombre*|Identifiant de l'élément.| |^|**clock**|*nombre*|Horodatage de la valeur de l'élément (secondes).| |^|**ns**|*nombre*|Horodatage de la valeur de l'élément (nanosecondes).| |^|**value**|*chaîne*|*(optionnel)* Valeur de l'élément.| |^|**id**|*nombre*|Identifiant de valeur (compteur croissant, unique dans une session de données).| |^|**timestamp**|*nombre*|*(optionnel)* Horodatage des éléments de type journal des événements.| |^|**source**|*chaîne*|*(optionnel)* Valeur source de l'élément du journal des événements.| |^|**severity**|*nombre*|*(optionnel)* Valeur de sévérité de l'élément du journal des événements.| |^|**eventid**|*nombre*|*(optionnel)* Valeur de l'ID d'événement de l'élément du journal des événements.| |^|**state**|*chaîne*|*(optionnel)* État de l'élément :<br>**0**, *ITEM\_STATE\_NORMAL*<br>**1**, *ITEM\_STATE\_NOTSUPPORTED*| |^|**lastlogsize**|*nombre*|*(optionnel)* Taille du dernier journal des éléments de type journal.| |^|**mtime**|*nombre*|*(optionnel)* Heure de modification des éléments de type journal.| |**discovery data**|<|*tableau*|*(optionnel)* Tableau d'objets de données de découverte.| | |**clock**|*nombre*|Horodatage des données de découverte.| |^|**druleid**|*nombre*|Identifiant de règle de découverte.| |^|**dcheckid**|*nombre*|Identifiant de vérification de découverte ou null pour les données de règle de découverte.| |^|**type**|*nombre*|Type de contrôle de découverte :<br><br>**-1** données de règle de découverte<br>**0**, *SVC\_SSH* - Vérification du service SSH<br>**1**, *SVC\_LDAP* - Vérification du service LDAP<br>**2**, *SVC\_SMTP* - Vérification du service SMTP<br>**3**, *SVC\_FTP* - Vérification du service FTP<br>**4**, *SVC\_HTTP* - Vérification du service HTTP<br>**5**, *SVC\_POP* - Vérification du service POP<br>**6**, *SVC\_NNTP* - Vérification du service NNTP<br>**7**, *SVC\_IMAP* - Vérification du service IMAP<br>**8**, *SVC\_TCP* - Vérification de la disponibilité du port TCP<br>**9**, *SVC\_AGENT* - Zabbix agent<br>**10**, *SVC\_SNMPv1* - SNMPv1 agent<br>**11**, *SVC\_SNMPv2* - SNMPv2 agent<br>**12**, *SVC\_ICMPPING* - Ping ICMP<br>**13**, *SVC\_SNMPv3* - Agent SNMPv3<br>**14**, *SVC\_HTTPS* - Vérification du service HTTPS<br>**15**, *SVC\_TELNET* - Vérification de la disponibilité Telnet| |^|**ip**|*chaîne*|Adresse IP de l'hôte.| |^|**dns**|*chaîne*|Nom DNS de l'hôte.| |^|**port**|*nombre*|*(optionnel)* Numéro de port de service.| |^|**key\_**|*chaîne*|*(optionnel)* Clé d'élément pour le contrôle de découverte de type **9** *SVC\_AGENT*| |^|**value**|*chaîne*|*(optionnel)* Valeur reçue du service, peut être vide pour la plupart des services.| |^|**status**|*nombre*|*(optionnel)* Statut du service :<br><br>**0**, *DOBJECT\_STATUS\_UP* - Service démarré<br>**1* *, *DOBJECT\_STATUS\_DOWN* - Service arrêté| |**autoregistration**|<|*tableau*|*(optionnel)* Tableau d'objets de données d'auto-enregistrement.| | |**clock**|*nombre*|Horodatage des données d'enregistrement automatique.| |^|**host**|*chaîne*|Nom d'hôte.| |^|**ip**|*chaîne*|*(optionnel)* Adresse IP de l'hôte.| |^|**dns**|*chaîne*|*(optionnel)* Nom DNS résolu à partir de l'adresse IP.| |^|**port**|*chaîne*|*(optionnel)* Port de l'hôte.| |^|**host\_metadata**|*chaîne*|*(optionnel)* Métadonnées de l'hôte envoyées par l'agent (basées sur le paramètre de configuration de l'agent HostMetadata ou HostMetadataItem).| |**tasks**|<|*tableau*|*(optionnel)* Tableau de tâches.| | |**type**|*nombre*|Type de tâche :<br><br>**0**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND\_RESULT* - résultat de la commande à distance| |^|**status**|*nombre*|Statut d'exécution de la commande à distance :<br><br>**0**, *ZBX\_TM\_REMOTE\_COMMAND\_COMPLETED* - commande à distance terminée avec succès<br>**1**, *ZBX\_TM\_REMOTE\_COMMAND\_FAILED* - la commande à distance a échoué| |^|**error**|*chaîne*|*(optionnel)* Message d'erreur.| |^|**parent\_taskid**|*nombre*|ID de la tâche parent.| |**more**|<|*nombre*|*(optionnel)* 1 - il y a plus de données d'historique à envoyer.| |**clock**|<|*nombre*|*(optionnel)* Horodatage du transfert de données (secondes).| |**ns**|<|*nombre*|*(optionnel)* Horodatage du transfert de données (nanosecondes).| |**version**|<|*chaîne*|Version du Proxy(\<major\>.\<minor\>.\<build\>).| |serveur→proxy :|<|<|<| |**response**|<|*chaîne*|Demander des informations sur le succès ('success' ou 'failed').| |**upload**|<|*chaîne*|Contrôle de téléchargement des données historiques (historique, enregistrement automatique, disponibilité de l'hôte, découverte du réseau) :<br>**activé** - fonctionnement normal<br>**désactivé** - le serveur n'accepte pas les données (peut-être en raison d'un dépassement de la limite du cache interne )| |**tasks**|<|*tableau*|*(optionnel)* Tableau de tâches.| | |**type**|*nombre*|Type de tâche :<br><br>**1**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND* - commande à distance| |^|**clock**|*nombre*|Heure de création de la tâche.| |^|**ttl**|*nombre*|Temps en secondes après lequel la tâche expire.| |^|**commandtype**|*nombre*|Type de commande à distance :<br><br>**0**, *ZBX\_SCRIPT\_TYPE\_CUSTOM\_SCRIPT* - utiliser un script personnalisé<br>**1**, *ZBX\_SCRIPT\_TYPE\_IPMI* - use IPMI<br>**2**, *ZBX\_SCRIPT\_TYPE\_SSH* - utiliser SSH<br>**3**, *ZBX\_SCRIPT\_TYPE\_TELNET* - utiliser Telnet<br>**4**, *ZBX\_SCRIPT\_TYPE\_GLOBAL\_SCRIPT* - utiliser le script global (actuellement équivalent fonctionnellement au script personnalisé) | |^|**command**|*chaîne*|Commande distante à exécuter.| |^|**execute\_on**|*nombre*|Cible d'exécution pour les scripts personnalisés :<br><br>**0**, *ZBX\_SCRIPT\_EXECUTE\_ON\_AGENT* - exécuter le script sur l'agent<br>**1**, *ZBX\_SCRIPT\_EXECUTE\_ON\_SERVER* - exécuter le script sur le serveur<br>**2**, *ZBX\_SCRIPT\_EXECUTE\_ON\_PROXY* - exécuter le script sur le proxy| |^|**port**|*nombre*|*(optionnel)* Port for Telnet and SSH commands.| |^|**authtype**|*nombre*|*(optionnel)* Type d'authentification pour les commandes SSH.| |^|**username**|*chaîne*|*(optionnel)* Nom d'utilisateur pour les commandes Telnet et SSH.| |^|**password**|*chaîne*|*(optionnel)* Mot de passe pour les commandes Telnet et SSH.| |^|**publickey**|*chaîne*|*(optionnel)* Clé publique pour les commandes SSH.| |^|**privatekey**|*chaîne*|*(optionnel)* Clé privée pour les commandes SSH.| |^|**parent\_taskid**|*nombre*|ID de la tâche parent.| |^|**hostid**|*nombre*|ID de l'hôte cible.| Exemple : proxy→serveur : ``` {.javascript} { "request": "proxy data", "host": "Proxy #12", "session": "12345678901234567890123456789012", "interface availability": [ { "interfaceid": 1, "available": 1, "error": "" }, { "interfaceid": 2, "available": 2, "error": "Get value from agent failed: cannot connect to [[127.0.0.1]:10049]: [111] Connection refused" }, { "interfaceid": 3, "available": 1, "error": "" }, { "interfaceid": 4, "available": 1, "error": "" } ], "history data":[ { "itemid":"12345", "clock":1478609647, "ns":332510044, "value":"52956612", "id": 1 }, { "itemid":"12346", "clock":1478609647, "ns":330690279, "state":1, "value":"Cannot find information for this network interface in /proc/net/dev.", "id": 2 } ], "discovery data":[ { "clock":1478608764, "drule":2, "dcheck":3, "type":12, "ip":"10.3.0.10", "dns":"vdebian", "status":1 }, { "clock":1478608764, "drule":2, "dcheck":null, "type":-1, "ip":"10.3.0.10", "dns":"vdebian", "status":1 } ], "auto registration":[ { "clock":1478608371, "host":"Logger1", "ip":"10.3.0.1", "dns":"localhost", "port":"10050" }, { "clock":1478608381, "host":"Logger2", "ip":"10.3.0.2", "dns":"localhost", "port":"10050" } ], "tasks":[ { "type": 2, "clock":1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 2, "clock":1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ], "tasks":[ { "type": 0, "status": 0, "parent_taskid": 10 }, { "type": 0, "status": 1, "error": "No permissions to execute task.", "parent_taskid": 20 } ], "version":"5.4.0" } ``` serveur→proxy : ``` {.javascript} { "response": "success", "upload": "enabled", "tasks":[ { "type": 1, "clock": 1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 1, "clock": 1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ] } ``` # proxy.delete # proxy.delete ##### Proxy features When making a choice of using/not using a proxy, several considerations must be taken into account. | |Proxy| |--------|--| |*Lightweight*|**Yes**| |*GUI*|No| |*Works independently*|**Yes**| |*Easy maintenance*|**Yes**| |*Automatic DB creation*|**Yes**^1^| |*Local administration*|No| |*Ready for embedded hardware*|**Yes**| |*One way TCP connections*|**Yes**| |*Centralized configuration*|**Yes**| |*Generates notifications*|No| ^1^ Automatic DB creation feature works only with SQLite. Other databases require [manual setup](/manual/appendix/install/db_scripts). ##### Fonctions du proxy Lorsque vous choisissez d'utiliser ou de ne pas utiliser un proxy, plusieurs considérations doivent être prises en compte. | |Proxy| |--------|--| |*Légèreté*|**Oui**| |*GUI*|Non| |*Fonctionnement indépendant*|**Oui**| |*Facilité de maintenance*|**Oui**| |*Création automatique de la BDD*|**Oui**^1^| |*Administration locale*|Non| |*Prêt pour le matériel embarqué*|**Oui**| |*Connexions TCP à sens unique*|**Oui**| |*Configuration centralisée*|**Oui**| |*Génération de notifications*|Non| ^1^ La fonctionnalité de création automatique de base de données ne fonctionne qu'avec SQLite. Les autres bases de données nécessitent une [configuration manuelle](/fr/manual/appendix/install/db_scripts). # proxy.get # proxy.get ##### Proxy heartbeat request The `proxy heartbeat` request is sent by proxy to report that proxy is running. This request is sent every `HeartbeatFrequency` (proxy configuration parameter) seconds. |name|value type|description| |----------|----------|----------------------------------------| |proxy→server:|<|<| |**request**|*string*|'proxy heartbeat'| |**host**|*string*|Proxy name.| |**version**|*string*|Proxy version (<major>.<minor>.<build>).| |server→proxy:|<|<| |**response**|*string*|Request success information ('success' or 'failed').| proxy→server: ``` {.javascript} { "request": "proxy heartbeat", "host": "Proxy #12", "version": "5.4.0" } ``` server→proxy: ``` {.javascript} { "response": "success" } ``` ##### Demande de heartbeat proxy La requête `proxy heartbeat` est envoyée par proxy pour signaler que le proxy est en cours d'exécution. Cette requête est envoyée toutes les `HeartbeatFrequency` (paramètre de configuration du proxy) secondes. |nom|type de valeur|description| |----------|----------|----------------------------------------| |proxy→serveur:|<|<| |**request**|*string*|'proxy heartbeat'| |**host**|*string*|Nom du proxy.| |**version**|*string*|Version du proxy (<major>.<minor>.<build>).| |serveur→proxy:|<|<| |**response**|*string*|Information sur le succès de la requête ('success' ou 'failed').| proxy→serveur: ``` {.javascript} { "request": "proxy heartbeat", "host": "Proxy #12", "version": "5.4.0" } ``` serveur→proxy: ``` {.javascript} { "response": "success" } ``` ### Proxy installation Once the required repository is added, you can install Zabbix proxy by running: # dnf install zabbix-proxy-mysql zabbix-sql-scripts Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL, or with 'sqlite3' to use SQLite3 (proxy only). The package 'zabbix-sql-scripts' contains database schemas for all supported database management systems for both Zabbix server and Zabbix proxy and will be used for data import. ### Installation du proxy Une fois le référentiel requis ajouté, vous pouvez installer le proxy Zabbix en exécutant : # dnf install zabbix-proxy-mysql zabbix-sql-scripts Remplacez 'mysql' dans la commande par 'pgsql' pour utiliser PostgreSQL, ou par 'sqlite3' pour utiliser SQLite3. Le package 'zabbix-sql-scripts' contient des schémas de base de données pour tous les systèmes de gestion de base de données pris en charge par le serveur Zabbix et le proxy Zabbix et sera utilisé pour l'importation de données. ### Proxy interface The proxy interface object defines the interface used to connect to a passive proxy. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**dns**<br>(required)|string|DNS name to connect to.<br><br>Can be empty if connections are made via IP address.| |**ip**<br>(required)|string|IP address to connect to.<br><br>Can be empty if connections are made via DNS names.| |**port**<br>(required)|string|Port number to connect to.| |**useip**<br>(required)|integer|Whether the connection should be made via IP address.<br><br>Possible values are:<br>0 - connect using DNS name;<br>1 - connect using IP address.| ### Interface de proxy L'objet interface proxy définit l'interface utilisée pour se connecter à un proxy passif. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**dns**<br>(obligatoire)|string|Nom DNS auquel se connecter.<br><br>Peut être vide si les connexions sont établies via une adresse IP.| |**ip**<br>(obligatoire)|string|Adresse IP à laquelle se connecter.<br><br>Peut être vide si les connexions sont établies via des noms DNS.| |**port**<br>(obligatoire)|string|Numéro de port auquel se connecter.| |**useip**<br>(obligatoire)|integer|Si la connexion doit être établie via l'adresse IP.<br><br>Les valeurs possibles sont :<br>0 - se connecter en utilisant le nom DNS ;<br>1 - se connecter en utilisant l'adresse IP.| ##### Proxy request The `proxy data` request is used to obtain host interface availability, historical, discovery and autoregistration data from proxy. This request is sent every `ProxyDataFrequency` (server configuration parameter) seconds. |name|<|value type|description| |-|----------|----------|----------------------------------------| |server→proxy:|<|<|<| |**request**|<|*string*|'proxy data'| |proxy→server:|<|<|<| |**session**|<|*string*|Data session token.| |**interface availability**|<|*array*|*(optional)* Array of interface availability data objects.| | |**interfaceid**|*number*|Interface identifier.| |^|**available**|*number*|Interface availability:<br><br>**0**, *INTERFACE\_AVAILABLE\_UNKNOWN* - unknown<br>**1**, *INTERFACE\_AVAILABLE\_TRUE* - available<br>**2**, *INTERFACE\_AVAILABLE\_FALSE* - unavailable| |^|**error**|*string*|Interface error message or empty string.| |**history data**|<|*array*|*(optional)* Array of history data objects.| | |**itemid**|*number*|Item identifier.| |^|**clock**|*number*|Item value timestamp (seconds).| |^|**ns**|*number*|Item value timestamp (nanoseconds).| |^|**value**|*string*|*(optional)* Item value.| |^|**id**|*number*|Value identifier (ascending counter, unique within one data session).| |^|**timestamp**|*number*|*(optional)* Timestamp of log type items.| |^|**source**|*string*|*(optional)* Eventlog item source value.| |^|**severity**|*number*|*(optional)* Eventlog item severity value.| |^|**eventid**|*number*|*(optional)* Eventlog item eventid value.| |^|**state**|*string*|*(optional)* Item state:<br>**0**, *ITEM\_STATE\_NORMAL*<br>**1**, *ITEM\_STATE\_NOTSUPPORTED*| |^|**lastlogsize**|*number*|*(optional)* Last log size of log type items.| |^|**mtime**|*number*|*(optional)* Modification time of log type items.| |**discovery data**|<|*array*|*(optional)* Array of discovery data objects.| | |**clock**|*number*|Discovery data timestamp.| |^|**druleid**|*number*|Discovery rule identifier.| |^|**dcheckid**|*number*|Discovery check identifier or null for discovery rule data.| |^|**type**|*number*|Discovery check type:<br><br>**-1** discovery rule data<br>**0**, *SVC\_SSH* - SSH service check<br>**1**, *SVC\_LDAP* - LDAP service check<br>**2**, *SVC\_SMTP* - SMTP service check<br>**3**, *SVC\_FTP* - FTP service check<br>**4**, *SVC\_HTTP* - HTTP service check<br>**5**, *SVC\_POP* - POP service check<br>**6**, *SVC\_NNTP* - NNTP service check<br>**7**, *SVC\_IMAP* - IMAP service check<br>**8**, *SVC\_TCP* - TCP port availability check<br>**9**, *SVC\_AGENT* - Zabbix agent<br>**10**, *SVC\_SNMPv1* - SNMPv1 agent<br>**11**, *SVC\_SNMPv2* - SNMPv2 agent<br>**12**, *SVC\_ICMPPING* - ICMP ping<br>**13**, *SVC\_SNMPv3* - SNMPv3 agent<br>**14**, *SVC\_HTTPS* - HTTPS service check<br>**15**, *SVC\_TELNET* - Telnet availability check| |^|**ip**|*string*|Host IP address.| |^|**dns**|*string*|Host DNS name.| |^|**port**|*number*|*(optional)* Service port number.| |^|**key\_**|*string*|*(optional)* Item key for discovery check of type **9** *SVC\_AGENT*| |^|**value**|*string*|*(optional)* Value received from the service, can be empty for most services.| |^|**status**|*number*|*(optional)* Service status:<br><br>**0**, *DOBJECT\_STATUS\_UP* - Service UP<br>**1**, *DOBJECT\_STATUS\_DOWN* - Service DOWN| |**auto registration**|<|*array*|*(optional)* Array of autoregistration data objects.| | |**clock**|*number*|Autoregistration data timestamp.| |^|**host**|*string*|Host name.| |^|**ip**|*string*|*(optional)* Host IP address.| |^|**dns**|*string*|*(optional)* Resolved DNS name from IP address.| |^|**port**|*string*|*(optional)* Host port.| |^|**host\_metadata**|*string*|*(optional)* Host metadata sent by the agent (based on HostMetadata or HostMetadataItem agent configuration parameter).| |**tasks**|<|*array*|*(optional)* Array of tasks.| | |**type**|*number*|Task type:<br><br>**0**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND\_RESULT* - remote command result| |^|**status**|*number*|Remote-command execution status:<br><br>**0**, *ZBX\_TM\_REMOTE\_COMMAND\_COMPLETED* - remote command completed successfully<br>**1**, *ZBX\_TM\_REMOTE\_COMMAND\_FAILED* - remote command failed| |^|**error**|*string*|*(optional)* Error message.| |^|**parent\_taskid**|*number*|Parent task ID.| |**more**|<|*number*|*(optional)* 1 - there are more history data to send.| |**clock**|<|*number*|*(optional)* Data transfer timestamp (seconds).| |**ns**|<|*number*|*(optional)* Data transfer timestamp (nanoseconds).| |**version**|<|*string*|Proxy version (<major>.<minor>.<build>).| |server→proxy:|<|<|<| |**response**|<|*string*|Request success information ('success' or 'failed').| |**tasks**|<|*array*|*(optional)* Array of tasks.| | |**type**|*number*|Task type:<br><br>**1**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND* - remote command| |^|**clock**|*number*|Task creation time.| |^|**ttl**|*number*|Time in seconds after which the task expires.| |^|**commandtype**|*number*|Remote-command type:<br><br>**0**, *ZBX\_SCRIPT\_TYPE\_CUSTOM\_SCRIPT* - use custom script<br>**1**, *ZBX\_SCRIPT\_TYPE\_IPMI* - use IPMI<br>**2**, *ZBX\_SCRIPT\_TYPE\_SSH* - use SSH<br>**3**, *ZBX\_SCRIPT\_TYPE\_TELNET* - use Telnet<br>**4**, *ZBX\_SCRIPT\_TYPE\_GLOBAL\_SCRIPT* - use global script (currently functionally equivalent to custom script)| |^|**command**|*string*|Remote command to execute.| |^|**execute\_on**|*number*|Execution target for custom scripts:<br><br>**0**, *ZBX\_SCRIPT\_EXECUTE\_ON\_AGENT* - execute script on agent<br>**1**, *ZBX\_SCRIPT\_EXECUTE\_ON\_SERVER* - execute script on server<br>**2**, *ZBX\_SCRIPT\_EXECUTE\_ON\_PROXY* - execute script on proxy| |^|**port**|*number*|*(optional)* Port for Telnet and SSH commands.| |^|**authtype**|*number*|*(optional)* Authentication type for SSH commands.| |^|**username**|*string*|*(optional)* User name for Telnet and SSH commands.| |^|**password**|*string*|*(optional)* Password for Telnet and SSH commands.| |^|**publickey**|*string*|*(optional)* Public key for SSH commands.| |^|**privatekey**|*string*|*(optional)* Private key for SSH commands.| |^|**parent\_taskid**|*number*|Parent task ID.| |^|**hostid**|*number*|Target host ID.| Example: server→proxy: ``` {.javascript} { "request": "proxy data" } ``` proxy→server: ``` {.javascript} { "session": "12345678901234567890123456789012" "interface availability": [ { "interfaceid": 1, "available": 1, "error": "" }, { "interfaceid": 2, "available": 2, "error": "Get value from agent failed: cannot connect to [[127.0.0.1]:10049]: [111] Connection refused" }, { "interfaceid": 3, "available": 1, "error": "" }, { "interfaceid": 4, "available": 1, "error": "" } ], "history data":[ { "itemid":"12345", "clock":1478609647, "ns":332510044, "value":"52956612", "id": 1 }, { "itemid":"12346", "clock":1478609647, "ns":330690279, "state":1, "value":"Cannot find information for this network interface in /proc/net/dev.", "id": 2 } ], "discovery data":[ { "clock":1478608764, "drule":2, "dcheck":3, "type":12, "ip":"10.3.0.10", "dns":"vdebian", "status":1 }, { "clock":1478608764, "drule":2, "dcheck":null, "type":-1, "ip":"10.3.0.10", "dns":"vdebian", "status":1 } ], "auto registration":[ { "clock":1478608371, "host":"Logger1", "ip":"10.3.0.1", "dns":"localhost", "port":"10050" }, { "clock":1478608381, "host":"Logger2", "ip":"10.3.0.2", "dns":"localhost", "port":"10050" } ], "tasks":[ { "type": 0, "status": 0, "parent_taskid": 10 }, { "type": 0, "status": 1, "error": "No permissions to execute task.", "parent_taskid": 20 } ], "version":"5.4.0" } ``` server→proxy: ``` {.javascript} { "response": "success", "tasks":[ { "type": 1, "clock": 1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 1, "clock": 1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ] } ``` ##### Requête de proxy La demande de `données prox` est utilisée pour obtenir des données de disponibilité, d'historique, de découverte et d'enregistrement automatique de l'interface hôte à partir du proxy. Cette requête est envoyée toutes les `ProxyDataFrequency` (paramètre de configuration du serveur) secondes. |nom|<|type de valeur|description| |-|----------|----------|----------------------------------------| |serveur→proxy :|<|<|<| |**request**|<|*chaîne*|'proxy data'| |proxy→serveur :|<|<|<| |**session**|<|*chaîne*|Jeton de session de données.| |**interface availability**|<|*tableau*|*(optionnel)* Tableau d'objets de données de disponibilité d'interface.| | |**interfaceid**|*nombre*|Identificateur d'interface.| |^|**available**|*nombre*|Disponibilité des interfaces :<br><br>**0**, *INTERFACE\_AVAILABLE\_UNKNOWN* - inconnue<br>**1**, *INTERFACE\_AVAILABLE\_TRUE* - disponible<br>**2**, *INTERFACE\_AVAILABLE\_FALSE* - indisponible| |^|**error**|*chaîne*|Message d'erreur d'interface ou chaîne vide.| |**history data**|<|*tableau*|*(optionnel)* Tableau d'objets de données d'historique.| | |**itemid**|*nombre*|Identificateur d'élément.| |^|**clock**|*nombre*|Horodatage de la valeur de l'élément (secondes).| |^|**ns**|*nombre*|Horodatage de la valeur de l'élément (nanosecondes).| |^|**value**|*chaîne*|*(optionnel)* Valeur de l'élément.| |^|**id**|*nombre*|Identificateur de valeur (compteur croissant, unique dans une session de données).| |^|**timestamp**|*nombre*|*(optionnel)* Horodatage des éléments de type journal.| |^|**source**|*chaîne*|*(optionnel)* Valeur source de l'élément du journal des événements.| |^|**severity**|*nombre*|*(optionnel)* Valeur de sévérité de l'élément du journal des événements.| |^|**eventid**|*nombre*|*(optionnel)* Valeur de l'ID d'événement de l'élément du journal des événements.| |^|**state**|*chaîne*|*(optionnel)* État de l'élément :<br>**0**, *ITEM\_STATE\_NORMAL*<br>**1**, *ITEM\_STATE\_NOTSUPPORTED*| |^|**lastlogsize**|*nombre*|*(optionnel)* Taille du dernier journal des éléments de type journal.| |^|**mtime**|*nombre*|*(optionnel)* Heure de modification des rubriques de type log.| |**discovery data**|<|*tableau*|*(optionnel)* Tableau d'objets de données de découverte.| | |**clock**|*nombre*|Horodatage des données de découverte.| |^|**druleid**|*nombre*|Identificateur de règle de découverte.| |^|**dcheckid**|*nombre*|Identifiant de vérification de découverte ou nul pour les données de règle de découverte.| |^|**type**|*nombre*|Type de contrôle de découverte :<br><br>**-1** données de règle de découverte<br>**0**, *SVC\_SSH* - Vérification du service SSH<br>**1**, *SVC\_LDAP* - Vérification du service LDAP<br>**2**, *SVC\_SMTP* - Vérification du service SMTP<br>**3**, *SVC\_FTP* - Vérification du service FTP<br>**4**, *SVC\_HTTP* - Vérification du service HTTP<br>**5**, *SVC\_POP* - Vérification du service POP<br>**6**, *SVC\_NNTP* - Vérification du service NNTP<br>**7**, *SVC\_IMAP* - Vérification du service IMAP<br>**8**, *SVC\_TCP* - Vérification de la disponibilité du port TCP<br>**9**, *SVC\_AGENT* - Agent Zabbix<br>**10**, *SVC\_SNMPv1* - Agent SNMPv1<br>**11**, *SVC\_SNMPv2* - Agent SNMPv2<br>**12**, *SVC\_ICMPPING* - Ping ICMP<br>**13**, *SVC\_SNMPv3* - Agent SNMPv3<br>**14**, *SVC\_HTTPS* - Vérification du service HTTPS<br>**15**, *SVC\_TELNET* - Vérification de la disponibilité Telnet| |^|**ip**|*chaîne*|Adresse IP de l'hôte.| |^|**dns**|*chaîne*|Nom DNS de l'hôte.| |^|**port**|*nombre*|*(optionnel)* Numéro de port de service.| |^|**key\_**|*chaîne*|*(optionnel)* Clé d'élément pour le contrôle de découverte de type **9** *SVC\_AGENT*| |^|**value**|*chaîne*|*(optionnel)* Valeur reçue du service, peut être vide pour la plupart des services.| |^|**status**|*nombre*|*(optionnel)* État du service:<br><br>**0**, *DOBJECT\_STATUS\_UP* - Service démarré<br>**1**, *DOBJECT\_STATUS\_DOWN* - Service arrêté| |**auto registration**|<|*tableau*|*(optionnel)* Tableau d'objets de données d'enregistrement automatique.| | |**clock**|*nombre*|Horodatage des données d'enregistrement automatique.| |^|**host**|*chaîne*|Nom d'hôte.| |^|**ip**|*chaîne*|*(optionnel)* Adresse IP de l'hôte.| |^|**dns**|*chaîne*|*(optionnel)* Nom DNS résolu à partir de l'adresse IP.| |^|**port**|*chaîne*|*(optionnel)* Port de l'hôte.| |^|**host\_metadata**|*chaîne*|*(optionnel)* Métadonnées de l'hôte envoyées par l'agent (basées sur le paramètre de configuration de l'agent HostMetadata ou HostMetadataItem).| |**tasks**|<|*tableau*|*(optionnel)* Tableau de tâches.| | |**type**|*nombre*|Type de tâche :<br><br>**0**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND\_RESULT* - résultat de la commande à distance | |^|**status**|*nombre*|Statut d'exécution de la télécommande :<br><br>**0**, *ZBX\_TM\_REMOTE\_COMMAND\_COMPLETED* - commande à distance terminée avec succès<br>**1**, *ZBX\_TM\_REMOTE\_COMMAND\_FAILED* - la commande à distance a échoué| |^|**error**|*chaîne*|*(optionnel)* Message d'erreur.| |^|**parent\_taskid**|*nombre*|ID de tâche parent.| |**more**|<|*nombre*|*(optionnel)* 1 - il y a plus de données d'historique à envoyer.| |**clock**|<|*nombre*|*(optionnel)* Horodatage du transfert de données (secondes).| |**ns**|<|*nombre*|*(optionnel)* Horodatage du transfert de données (nanosecondes).| |**version**|<|*chaîne*|Version proxy (\<major\>.\<minor\>.\<build\>).| |serveur→proxy :|<|<|<| |**response**|<|*chaîne*|Demander des informations sur le succès ('success' ou 'failed').| |**tasks**|<|*tableau*|*(optionnel)* Tableau de tâches.| | |**type**|*nombre*|Type de tâche :<br><br>**1**, *ZBX\_TM\_TASK\_PROCESS\_REMOTE\_COMMAND* - commande à distance| |^|**clock**|*nombre*|Heure de création de la tâche.| |^|**ttl**|*nombre*|Temps en secondes après lequel la tâche expire.| |^|**commandtype**|*nombre*|Type de commande à distance :<br><br>**0**, *ZBX\_SCRIPT\_TYPE\_CUSTOM\_SCRIPT* - utiliser un script personnalisé<br>**1**, *ZBX\_SCRIPT\_TYPE\_IPMI* - utiliser IPMI<br>**2**, *ZBX\_SCRIPT\_TYPE\_SSH* - utiliser SSH<br>**3**, *ZBX\_SCRIPT\_TYPE\_TELNET* - utiliser Telnet<br>**4**, *ZBX\_SCRIPT\_TYPE\_GLOBAL\_SCRIPT* - utiliser le script global (actuellement équivalent fonctionnellement du script personnalisé) | |^|**command**|*chaîne*|Commande distante à exécuter.| |^|**execute\_on**|*nombre*|Cible d'exécution pour les scripts personnalisés :<br><br>**0**, *ZBX\_SCRIPT\_EXECUTE\_ON\_AGENT* - exécuter le script sur l'agent<br>**1**, *ZBX\_SCRIPT\_EXECUTE\_ON\_SERVER* - exécuter le script sur le serveur<br>**2**, *ZBX\_SCRIPT\_EXECUTE\_ON\_PROXY* - exécuter le script sur le proxy| |^|**port**|*nombre*|*(optionnel)* Port pour les commandes Telnet et SSH.| |^|**authtype**|*nombre*|*(optionnel)* Type d'authentification pour les commandes SSH.| |^|**username**|*chaîne*|*(optionnel)* Nom d'utilisateur pour les commandes Telnet et SSH.| |^|**password**|*chaîne*|*(optionnel)* Mot de passe pour les commandes Telnet et SSH.| |^|**publickey**|*chaîne*|*(optionnel)* Clé publique pour les commandes SSH.| |^|**privatekey**|*chaîne*|*(optionnel)* Clé privée pour les commandes SSH.| |^|**parent\_taskid**|*nombre*|ID de tâche parent.| |^|**hostid**|*nombre*|ID de l'hôte cible.| Exemple : serveur→proxy : ``` {.javascript} { "request": "proxy data" } ``` proxy→serveur : ``` {.javascript} { "session": "12345678901234567890123456789012" "interface availability": [ { "interfaceid": 1, "available": 1, "error": "" }, { "interfaceid": 2, "available": 2, "error": "Get value from agent failed: cannot connect to [[127.0.0.1]:10049]: [111] Connection refused" }, { "interfaceid": 3, "available": 1, "error": "" }, { "interfaceid": 4, "available": 1, "error": "" } ], "history data":[ { "itemid":"12345", "clock":1478609647, "ns":332510044, "value":"52956612", "id": 1 }, { "itemid":"12346", "clock":1478609647, "ns":330690279, "state":1, "value":"Cannot find information for this network interface in /proc/net/dev.", "id": 2 } ], "discovery data":[ { "clock":1478608764, "drule":2, "dcheck":3, "type":12, "ip":"10.3.0.10", "dns":"vdebian", "status":1 }, { "clock":1478608764, "drule":2, "dcheck":null, "type":-1, "ip":"10.3.0.10", "dns":"vdebian", "status":1 } ], "auto registration":[ { "clock":1478608371, "host":"Logger1", "ip":"10.3.0.1", "dns":"localhost", "port":"10050" }, { "clock":1478608381, "host":"Logger2", "ip":"10.3.0.2", "dns":"localhost", "port":"10050" } ], "tasks":[ { "type": 0, "status": 0, "parent_taskid": 10 }, { "type": 0, "status": 1, "error": "No permissions to execute task.", "parent_taskid": 20 } ], "version":"5.4.0" } ``` serveur→proxy : ``` {.javascript} { "response": "success", "tasks":[ { "type": 1, "clock": 1478608371, "ttl": 600, "commandtype": 2, "command": "restart_service1.sh", "execute_on": 2, "port": 80, "authtype": 0, "username": "userA", "password": "password1", "publickey": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe", "privatekey": "lsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5QCqGKukO1De7zhd", "parent_taskid": 10, "hostid": 10070 }, { "type": 1, "clock": 1478608381, "ttl": 600, "commandtype": 1, "command": "restart_service2.sh", "execute_on": 0, "authtype": 0, "username": "", "password": "", "publickey": "", "privatekey": "", "parent_taskid": 20, "hostid": 10084 } ] } ``` #### Proxy startup with MySQL 8.0.0-8.0.17 zabbix\_proxy on MySQL versions 8.0.0-8.0.17 fails with the following "access denied" error: [Z3001] connection to database 'zabbix' failed: [1227] Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation That is due to MySQL 8.0.0 starting to enforce special permissions for setting session variables. However, in 8.0.18 this behavior was removed: [As of MySQL 8.0.18, setting the session value of this system variable is no longer a restricted operation.](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html) The workaround is based on granting additional privileges to the `zabbix` user: For MySQL versions 8.0.14 - 8.0.17: grant SESSION_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost'; For MySQL versions 8.0.0 - 8.0.13: grant SYSTEM_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost'; #### Démarrage du proxy avec MySQL 8.0.0-8.0.17 zabbix\_proxy sur MySQL versions 8.0.0-8.0.17 échoue avec l'erreur "accès refusé" suivante : [Z3001] connection to database 'zabbix' failed: [1227] Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation Cela est dû au fait que MySQL 8.0.0 commence à appliquer des autorisations spéciales pour définir les variables de session. Cependant, dans la version 8.0.18, ce comportement a été supprimé : [Depuis MySQL 8.0.18, la définition de la valeur de session de cette variable système n'est plus une opération restreinte.](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html) La solution de contournement est basée sur l'octroi de privilèges supplémentaires à l'utilisateur `zabbix` : Pour les versions 8.0.14 à 8.0.17 de MySQL : grant SESSION_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost'; Pour les versions 8.0.0 à 8.0.13 de MySQL : grant SYSTEM_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost'; # proxy.update # proxy.update #### Proxy upgrade process #### Procédure de mise à jour du Proxy ##### Proxy [Zabbix proxy](/manual/concepts/proxy) can collect performance and availability data on behalf of Zabbix server. A proxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. ##### Proxy Le [Proxy Zabbix](/manual/concepts/proxy) peut collecter des données de performance et de disponibilité au nom du serveur Zabbix. Un proxy est un composant facultatif du déploiement de Zabbix. Cependant, il peut être très bénéfique de distribuer la charge d'un seul serveur Zabbix. #### PSK contains an odd number of hex-digits Proxy or agent does not start, message in the proxy or agent log: invalid PSK in file "/home/zabbix/zabbix_proxy.psk" #### PSK contient un nombre impair de chiffres hexadécimaux Le proxy ou l'agent ne démarre pas, message dans le journal du proxy ou de l'agent : invalid PSK in file "/home/zabbix/zabbix_proxy.psk" #### PSK identity string longer than 128 bytes is passed to GnuTLS In TLS client side log: gnutls_handshake() failed: -110 The TLS connection was non-properly terminated. In TLS server side log. gnutls_handshake() failed: -90 The SRP username supplied is illegal. #### Une chaîne d'identité PSK supérieure à 128 octets est transmise à GnuTLS Dans le journal côté client TLS : gnutls_handshake() failed: -110 The TLS connection was non-properly terminated. Dans le journal côté serveur TLS : gnutls_handshake() failed: -90 The SRP username supplied is illegal. ##### Purpose of persistent files When Zabbix agent is started it receives a list of active checks from Zabbix server or proxy. For log\*\[\] metrics it receives the processed log size and the modification time for finding where to start log file monitoring from. Depending on the actual log file size and modification time reported by file system the agent decides either to continue log file monitoring from the processed log size or re\-analyze the log file from the beginning. A running agent maintains a larger set of attributes for tracking all monitored log files between checks. This in\-memory state is lost when the agent is stopped. The new optional parameter **persistent\_dir** specifies a directory for storing this state of log\[\], log.count\[\], logrt\[\] or logrt.count\[\] item in a file. The state of log item is restored from the persistent file after the Zabbix agent is restarted. The primary use\-case is monitoring of log file located on a mirrored file system. Until some moment in time the log file is written to both mirrors. Then mirrors are split. On the active copy the log file is still growing, getting new records. Zabbix agent analyzes it and sends processed logs size and modification time to server. On the passive copy the log file stays the same, well behind the active copy. Later the operating system and Zabbix agent are rebooted from the passive copy. The processed log size and modification time the Zabbix agent receives from server may not be valid for situation on the passive copy. To continue log file monitoring from the place the agent left off at the moment of file system mirror split the agent restores its state from the persistent file. ##### Objectif des fichiers persistants Lorsque l'agent Zabbix est démarré, il reçoit une liste des vérifications actives du serveur ou du proxy Zabbix. Pour les métriques log\*\[\], il reçoit la taille du journal traité et l'heure de modification pour trouver où commencer la surveillance du fichier journal. En fonction de la taille réelle du fichier journal et de l'heure de modification signalée par le système de fichiers, l'agent décide soit de poursuivre la surveillance du fichier journal à partir de la taille du journal traité, soit de ré\-analyser le fichier journal depuis le début. Un agent en cours d'exécution conserve un plus grand ensemble d'attributs pour le suivi de tous les fichiers journaux surveillés entre les vérifications. Cet état en\-mémoire est perdu lorsque l'agent est arrêté. Le nouveau paramètre facultatif **persistent\_dir** spécifie un répertoire pour stocker cet état de l'élément log\[\], log.count\[\], logrt\[\] ou logrt.count\[\] dans un fichier . L'état de l'élément de journal est restauré à partir du fichier persistant après le redémarrage de l'agent Zabbix. Le principal cas d'usage est la surveillance du fichier journal situé sur un système de fichiers en miroir. Jusqu'à un certain moment, le fichier journal est écrit sur les deux miroirs. Ensuite, les miroirs sont divisés. Sur la copie active, le fichier journal continue de croître, obtenant de nouveaux enregistrements. L'agent Zabbix l'analyse et envoie la taille et l'heure de modification des journaux traités au serveur. Sur la copie passive, le fichier journal reste le même, bien derrière la copie active. Plus tard, le système d'exploitation et l'agent Zabbix sont redémarrés à partir de la copie passive. La taille du journal traité et l'heure de modification que l'agent Zabbix reçoit du serveur peuvent ne pas être valides pour la situation sur la copie passive. Pour continuer la surveillance du fichier journal à partir de l'endroit où l'agent s'est arrêté au moment de la division du miroir du système de fichiers, l'agent restaure son état à partir du fichier persistant. #### Query language comparison The following table lists differences and similarities between PromQL and Zabbix Prometheus preprocessing query language. |[PromQL instant vector selector](https://prometheus.io/docs/prometheus/latest/querying/basics/#instant-vector-selectors)|<|Zabbix Prometheus preprocessing| |----|----|----| |**Differences**|<|<| |Query target|Prometheus server|Plain text in Prometheus exposition format| |Returns|Instant vector|Metric or label value (Prometheus pattern)<br>Array of metrics for single value in JSON (Prometheus to JSON)| |Label matching operators|**=**, **!=**, **=\~**, **!\~**|**=**, **!=**, **=\~**, **!\~**| |Regular expression used in label or metric name matching|RE2|PCRE| |Comparison operators|See [list](https://prometheus.io/docs/prometheus/latest/querying/operators/#comparison-binary-operators)|Only **==** (equal) is supported for value filtering| |**Similarities**|<|<| |Selecting by metric name that equals string|<metric name> or {\_\_name\_\_="<metric name>"}|<metric name> or {\_\_name\_\_="<metric name>"}| |Selecting by metric name that matches regular expression|{\_\_name\_\_=\~"<regex>"}|{\_\_name\_\_=\~"<regex>"}| |Selecting by <label name> value that equals string|{<label name>="<label value>",...}|{<label name>="<label value>",...}| |Selecting by <label name> value that matches regular expression|{<label name>=\~"<regex>",...}|{<label name>=\~"<regex>",...}| |Selecting by value that equals string|{\_\_name\_\_=\~".\*"} == <value>|{\_\_name\_\_=\~".\*"} == <value>| #### Comparaison des langages de requête Le tableau suivant répertorie les différences et les similitudes entre le langage de requête de prétraitement PromQL et Zabbix Prometheus. |[PromQL instant vector selector](https://prometheus.io/docs/prometheus/latest/querying/basics/#instant-vector-selectors)|<|Prétraitement Zabbix Prometheus| |----|----|----| |**Différences**|<|<| |Cible de la requête|Serveur Prometheus|Texte brut au format d'exposition Prometheus| |Renvois|Vecteur instantané|Valeur de métrique ou d'étiquette (modèle Prometheus)<br>Tableau de métriques pour une valeur unique dans JSON (Prometheus vers JSON)| |Opérateurs de correspondance d'étiquettes|**=**, **!=**, **=\~**, **!\~**|**=**, **!=**, **=\~**, **!\~**| |Expression régulière utilisée dans la correspondance de libellé ou de nom de métrique|RE2|PCRE| |Opérateurs de comparaison|Voir la [liste](https://prometheus.io/docs/prometheus/latest/querying/operators/#comparison-binary-operators)|Seulement **==** (égal) est pris en charge pour le filtrage de valeur | |**Similitudes**|<|<| |Sélection par nom de métrique égal à chaîne|<nom de métrique> or {\_\_nom\_\_="<nom de métrique>"}|<nom de métrique> or {\_\_nom\_\_="<nom de métrique>"}| |Sélection par nom de métrique qui correspond à l'expression régulière|{\_\_nom\_\_=\~"\<regex\>"}|{\_\_nom\_\_=\~"\<regex\>"}| |Sélection par <nom d'étiquette> valeur égale à string|{\<nom d'étiquette\>=\"<valeur d'étiquette\>",...}|{\<nom d'étiquette\>="\<valeur d'étiquette\>",...}| |Sélection par la valeur <nom d'étiquette> qui correspond à l'expression régulière |{\<nom d'étiquette\>=\~"\<regex\>",...}|{\<nom d'étiquette\>=\~"\<regex\>",...}| |Sélection par valeur égale à chaîne|{\_\_nom\_\_=\~".\*"} == \<valeur\>|{\_\_nom\_\_=\~".\*"} == \<valeur\>| ### Query separate tablespaces in Oracle databases with Zabbix agent 2 The following [Zabbix agent 2 items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2), supported for the Oracle plugin, now have additional optional parameters: - oracle.diskgroups.stats\[<existingParameters>,**<diskgroup>**\] - oracle.archive.info\[<existingParameters>,**<destination>**\] - oracle.cdb.info\[<existingParameters>,**<database>**\] - oracle.pdb.info\[<existingParameters>,**<database>**\] - oracle.ts.stats\[<existingParameters>,**<tablespace>**,**<type>**\] These parameters allow to query separate instances of data instead of all data, thus improving performance. ### Interroger des tablespaces séparés dans les bases de données Oracle avec l'agent Zabbix 2 Les [éléments Zabbix agent 2](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) suivants, pris en charge pour le plugin Oracle, ont maintenant des paramètres facultatifs supplémentaires : - oracle.diskgroups.stats\[<paramètresExistants>,**<groupeDeDisque>**\] - oracle.archive.info\[<paramètresExistants>,**<destination>**\] - oracle.cdb.info\[<paramètresExistants>,**<baseDeDonnée>**\] - oracle.pdb.info\[<paramètresExistants>,**<baseDeDonnée>**\] - oracle.ts.stats\[<paramètresExistants>,**<tablespace>**,**<type>**\] Ces paramètres permettent d'interroger des instances de données distinctes au lieu de toutes les données, améliorant ainsi les performances. ### Query separate tablespaces in Oracle databases with Zabbix agent 2 The following [Zabbix agent 2 items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2), supported for the Oracle plugin, now have additional optional parameters: - oracle.diskgroups.stats\[<existingParameters>,**<diskgroup>**\] - oracle.archive.info\[<existingParameters>,**<destination>**\] - oracle.cdb.info\[<existingParameters>,**<database>**\] - oracle.pdb.info\[<existingParameters>,**<database>**\] - oracle.ts.stats\[<existingParameters>,**<tablespace>**,**<type>**\] These parameters allow to query separate instances of data instead of all data, thus improving performance. ### Interroger des tablespaces séparés dans les bases de données Oracle avec l'agent Zabbix 2 Les [éléments Zabbix agent 2](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) suivants, pris en charge pour le plugin Oracle, ont maintenant des paramètres facultatifs supplémentaires : - oracle.diskgroups.stats\[<paramètresExistants>,**<groupeDeDisque>**\] - oracle.archive.info\[<paramètresExistants>,**<destination>**\] - oracle.cdb.info\[<paramètresExistants>,**<baseDeDonnée>**\] - oracle.pdb.info\[<paramètresExistants>,**<baseDeDonnée>**\] - oracle.ts.stats\[<paramètresExistants>,**<tablespace>**,**<type>**\] Ces paramètres permettent d'interroger des instances de données distinctes au lieu de toutes les données, améliorant ainsi les performances. #### Queue item A special internal item **zabbix\[queue,<from>,<to>\]** can be used to monitor the health of the queue in Zabbix. It will return the number of items delayed by the set amount of time. For more information see [Internal items](/manual/config/items/itemtypes/internal). #### Élément de file d'attente Un élément interne spécifique à **zabbix\[queue,<from>,<to>\]** peut être utilisé pour superviser l'intégrité de la file d'attente dans Zabbix. Il renverra le nombre d'éléments retardés par rapport à la durée définie. Pour plus d'informations, voir [Éléments internes](/manual/config/items/itemtypes/internal). ##### Readable summary in maps A hidden "aria-label" property is available allowing map information to be read with a screen reader. Both general map description and individual element description is available, in the following format: - for map description: `<Map name>, <* of * items in problem state>, <* problems in total>.` - for describing one element with one problem: `<Element type>, Status <Element status>, <Element name>, <Problem description>.` - for describing one element with multiple problems: `<Element type>, Status <Element status>, <Element name>, <* problems>.` - for describing one element without problems: `<Element type>, Status <Element status>, <Element name>.` For example, this description is available: 'Local network, 1 of 6 elements in problem state, 1 problem in total. Host, Status problem, My host, Free disk space is less than 20% on volume \/. Host group, Status ok, Virtual servers. Host, Status ok, Server 1. Host, Status ok, Server 2. Host, Status ok, Server 3. Host, Status ok, Server 4. ' for the following map: {width="600"} ##### Résumé lisible dans les cartes Une propriété "aria-label" cachée est disponible permettant aux informations de la carte d'être lues avec un lecteur d'écran. La description générale de la carte et une description d'élément individuel est disponible, au format suivant : - pour la description de la carte : `<Nom de la carte>, <* de * éléments en état de problème>, <* problèmes au total>.` - pour décrire un élément avec un problème : `<Type d'élément>, Statut <Statut de l'élément>, <Nom de l'élément>, <Description du problème>.` - pour décrire un élément avec plusieurs problèmes : `<Type d'élément>, Statut <Statut de l'élément>, <Nom de l'élément>, <* problèmes>.` - pour décrire un élément sans problème : `<Type d'élément>, Statut <Statut de l'élément>, <Nom de l'élément>.` Par exemple, cette description est disponible : 'Réseau local, 1 élément sur 6 en état de problème, 1 problème au total. Hôte, Problème d'état, Mon hôte, L'espace disque libre est inférieur à 20 % sur le volume \/. Groupe d'hôtes, Statut ok, Serveurs virtuels. Hôte, état ok, serveur 1. Hôte, état ok, serveur 2. Hôte, état ok, serveur 3. Hôte, état ok, serveur 4. ' pour la carte suivante : {width="600"} #### Reading host availability Host availability icons reflect the current host interface status on Zabbix server. Therefore, in the frontend: - If you disable a host, availability icons will not immediately turn gray (unknown status), because the server has to synchronize the configuration changes first; - If you enable a host, availability icons will not immediately turn green (available), because the server has to synchronize the configuration changes and start polling the host first. #### Lecture de la disponibilité de l'hôte Les icônes de disponibilité de l'hôte reflètent l'état actuel de l'interface hôte sur le serveur Zabbix. Par conséquent, sur l'interface Web : - Si vous désactivez un hôte, les icônes de disponibilité ne deviendront pas immédiatement grises (état inconnu), car le serveur doit d'abord synchroniser les changements de configuration ; - Si vous activez un hôte, les icônes de disponibilité ne deviendront pas immédiatement vertes (disponibles), car le serveur doit d'abord synchroniser les modifications de configuration et commencer à interroger l'hôte. #### Ready-to-use templates The default dataset in Zabbix offers several ready-to-use templates for monitoring VMware vCenter or directly ESX hypervisor. These templates contain pre-configured LLD rules as well as a number of built-in checks for monitoring virtual installations. Templates for VMware vCenter and ESX hypervisor monitoring: - *VMware* - uses UUID data for corresponding macros; - *VMware FQDN* - uses FQDN data for corresponding macros. ::: noteclassic In order for the *VMware FQDN* template to work correctly each monitored VM should have a unique OS name compliant with FQDN rules and VMware Tools must be installed on every machine. If these conditions are met, it is recommended to use *VMware FQDN* template. The creation of *VMware FQDN* template became possible after introducing the ability to create hosts with custom interfaces in Zabbix 5.2.\ \ A classic *VMware* template is still available and can be used if FQDN requirements cannot be met. Please keep in mind, that the *VMware* template has a known issue. Hosts for discovered virtual machines will be created with the names saved in the vCenter (for example, VM1, VM2, etc.). If Zabbix agent active is installed on these hosts later with autoregistration enabled, the autoregistration process will read host names as they have been registered upon launch (for example, vm1.example.com, vm2.example.com, etc.) and create new hosts since no name matches have been found. As a result there will be two duplicate hosts for each machine with different names. ::: Templates used by discovery (normally, these templates should not be manually linked to a host): - *VMware Hypervisor*; - *VMware Guest*.  #### Modèles prêts à l'emploi L'ensemble de données par défaut dans Zabbix propose plusieurs modèles prêts à l'emploi pour surveiller VMware vCenter ou directement l'hyperviseur ESX. Ces modèles contiennent des règles LLD préconfigurées ainsi qu'un certain nombre de contrôles intégrés pour la surveillance des installations virtuelles. Modèles pour la surveillance de l'hyperviseur VMware vCenter et ESX : - *VMware* - utilise les données UUID pour les macros correspondantes ; - *VMware FQDN* - utilise les données FQDN pour les macros correspondantes. ::: noteclassic Pour que le modèle *VMware FQDN* fonctionne correctement, chaque machine virtuelle surveillée doit avoir un nom de système d'exploitation unique conforme aux règles FQDN et VMware Tools doit être installé sur chaque machine. Si ces conditions sont remplies, il est recommandé d'utiliser le modèle *VMware FQDN*. La création du modèle *VMware FQDN* est devenue possible après l'introduction de la possibilité de créer des hôtes avec des interfaces personnalisées dans Zabbix 5.2.\ \ Un modèle *VMware* classique est toujours disponible et peut être utilisé si les exigences FQDN ne peuvent pas être satisfaites. N'oubliez pas que le modèle *VMware* présente un problème connu. Les hôtes des machines virtuelles découvertes seront créés avec les noms enregistrés dans le vCenter (par exemple, VM1, VM2, etc.). Si l'agent Zabbix actif est installé ultérieurement sur ces hôtes avec l'enregistrement automatique activé, le processus d'enregistrement automatique lira les noms d'hôte tels qu'ils ont été enregistrés au lancement (par exemple, vm1.example.com, vm2.example.com, etc.) et créera de nouveaux hôtes car aucune correspondance de nom n'a été trouvée. En conséquence, il y aura deux hôtes en double pour chaque machine avec des noms différents. ::: Modèles utilisés par la découverte (normalement, ces modèles ne doivent pas être liés manuellement à un hôte) : - *VMware Hypervisor*; - *VMware Guest*.  ##### Recent change markers Inward pointing red triangles around an element indicate a recent trigger status change - one that's happened within the last 30 minutes. These triangles are shown if the *Mark elements on trigger status change* check-box is marked in map [configuration](/manual/config/visualization/maps/map#creating_a_map). ##### Marqueurs de changement récent Des triangles rouges pointant vers l'intérieur autour d'un élément indiquent une changement d'état du déclencheur - qui s'est produit au cours des 30 dernières minutes. Ces triangles sont affichés si la case à cocher *Marquer les élément sur changement de l'état du déclencheur* est cochée dans la [configuration](/manual/config/visualization/maps/map#creating_a_map) de la carte. #### Recent data vs longer periods For very recent data a **single** line is drawn connecting each received value. The single line is drawn as long as there is at least one horizontal pixel available for one value. For data that show a longer period **three lines** are drawn - a dark green one shows the average, while a light pink and a light green line shows the maximum and minimum values at that point in time. The space between the highs and the lows is filled with yellow background. Working time (working days) is displayed in graphs as a white background, while non-working time is displayed in gray (with the *Original blue* default frontend theme). {width="550"} Working time is always displayed in simple graphs, whereas displaying it in [custom graphs](custom#configuring_custom_graphs) is a user preference. Working time is not displayed if the graph shows more than 3 months. #### Données récentes vs périodes plus longues Pour les données très récentes, une ligne **simple** est tracée reliant chaque valeur reçue. La ligne unique est tracée tant qu'il y a au moins un pixel horizontal disponible pour une valeur. Pour les données qui affichent une période plus longue, **trois lignes** sont dessinées : une ligne vert foncé indique la moyenne, tandis qu'une ligne rose clair et une ligne vert clair indiquent les valeurs maximale et minimale à ce moment précis. L'espace entre les hauts et les bas est rempli de fond jaune. Le temps de travail (jours ouvrés) est affiché dans les graphiques sur fond blanc, tandis que le temps chômé est affiché en gris (avec le thème frontal par défaut *Original blue*). {width="550"} Le temps de travail est toujours affiché dans des graphiques simples, alors que son affichage dans des [graphiques personnalisés](custom#configuring_custom_graphs) est une préférence de l'utilisateur. Le temps de travail n'est pas affiché si le graphique montre plus de 3 mois. ### Red Hat Enterprise Linux Open the `/etc/yum.repos.d/zabbix.repo` file and set enabled=1 for the `zabbix-unstable` repo. [zabbix-unstable] name=Zabbix Official Repository (unstable) - $basearch baseurl=https://repo.zabbix.com/zabbix/5.5/rhel/8/$basearch/ enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 ### Red Hat Enterprise Linux Ouvrez le fichier `/etc/yum.repos.d/zabbix.repo` et définissez enabled=1 pour le dépôt `zabbix-unstable`. [zabbix-unstable] name=Zabbix Official Repository (unstable) - $basearch baseurl=https://repo.zabbix.com/zabbix/5.5/rhel/8/$basearch/ enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 ### Redis |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |redis.config\[connString,<password>,<pattern>\]|<|<|<| |Gets the configuration parameters of a Redis instance that match the pattern.|JSON - if a glob-style pattern was used<br><br>single value - if a pattern did not contain any wildcard character|**connString** - URI or session name.<br>**password** - Redis password.<br>**pattern** - glob-style pattern (*\** by default).| | |redis.info\[connString,<password>,<section>\]|<|<|<| |Gets the output of the INFO command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**password** - Redis password.<br>**section** - [section](https://redis.io/commands/info) of information (*default* by default).| | |redis.ping\[connString,<password>\]|<|<|<| |Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.<br>**password** - Redis password.| | |redis.slowlog.count\[connString,<password>\]|<|<|<| |The number of slow log entries since Redis was started.|Integer|**connString** - URI or session name.<br>**password** - Redis password.| | ### Redis |Clé|<|<|<| |--|--|------|------| |**Description**|**Valeur retournée**|**Paramètres**|**Commentaires**| |redis.config\[connString,\<password\>,\<pattern\>\]|<|<|<| |Obtient les paramètres de configuration d'une instance Redis qui correspondent au modèle.|JSON - si un modèle de style glob a été utilisé<br><br>valeur unique - si un modèle ne contient aucun caractère générique|**connString** - URI ou nom de session.<br>**password** - Mot de passe Redis.<br>**pattern** - motif de style glob (*\** par défaut).| | |redis.info\[connString,\<password\>,\<section\>\]|<|<|<| |Obtient la sortie de la commande INFO.|JSON - la sortie est sérialisée en JSON|**connString** - URI ou nom de session.<br>**password** - Mot de passe Redis.<br>**section** - [section](https://redis.io/commands/info) de l'information (*default* par défaut).| | |redis.ping\[connString,\<password\>\]|<|<|<| |Teste si une connexion est active ou non.|1 - la connexion est active<br><br>0 - la connexion est interrompue (en cas d'erreur, y compris AUTH et problèmes de configuration)|**connString** - URI ou nom de session.<br>**password** - Mot de passe Redis.| | |redis.slowlog.count\[connString,\<password\>\]|<|<|<| |Le nombre d'entrées de journal lentes depuis le démarrage de Redis.|Entier|**connString** - URI ou nom de session.<br>**password** - Mot de passe Redis.| | ##### Referencing a network map Network maps can be referenced by both `sysmapid` and `mapname` GET parameters. For example, http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network will open the map with that name (Local network). If both `sysmapid` (map ID) and `mapname` (map name) are specified, `mapname` has higher priority. ##### Référencer une carte du réseau Les cartes réseau peuvent être référencées par les paramètres GET `sysmapid` et `mapname`. Par exemple, http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network ouvrira la carte portant ce nom (Local network). Si `sysmapid` (ID de carte) et `mapname` (nom de carte) sont spécifiés, `mapname` a une priorité plus élevée. # regexp.create # regexp.create # regexp.delete # regexp.delete # regexp.get # regexp.get # regexp.update # regexp.update ###### Register request A request sent by the agent during the agent startup phase to obtain provided metrics to register a plugin. | | | |---|---| |direction|agent → plugin| |response|yes| Parameters specific to register requests: |Name|Type|Comments| |---------|--------|----------| |version|string|The protocol version <major>.<minor>| *Example:* {"id":1,"type":2,"version":"1.0"} ###### Requête d'enregistrement Requête envoyée par l'agent lors de la phase de démarrage de l'agent pour obtenir les métriques fournies pour enregistrer un plug-in. | | | |---|---| |direction|agent → plugin| |réponse|oui| Paramètres spécifiques aux requêtes d'enregistrement : |Nom|Type|Commentaires| |---------|--------|----------| |version|string|La version du protocole <major>.<minor>| *Exemple:* {"id":1,"type":2,"version":"1.0"} ###### Register response Plugin's response to the register request. | | | |---|---| |direction|plugin → agent| |response|n/a| Parameters specific to register responses: |Name|Type|Comments| |---------|--------|----------| |name|string|The plugin name.| |metrics|array of strings (optional)|The metrics with descriptions as used in the plugin. Returns RegisterMetrics(). Absent if error is returned.| |interfaces|uint32 (optional)|The bit mask of plugin's supported interfaces. Absent if error is returned.| |error|string (optional)|An error message returned if a plugin cannot be started. Absent, if metrics are returned.| *Examples:* {"id":2,"type":3,"metrics":["external.test", "External exporter Test."], "interfaces": 4} or {"id":2,"type":3,"error":"error message"} ###### Réponse d'enregistrement Réponse du plugin à la requête d'enregistrement. | | | |---|---| |direction|plugin → agent| |réponse|n/a| Paramètres spécifiques aux réponses d'enregistrements : |Nom|Type|Commentaires| |---------|--------|----------| |name|string|Le nom du plug-in.| |metrics|tableau de chaînes (facultatif)|Les métriques avec des descriptions telles qu'elles sont utilisées dans le plugin. Renvoie RegisterMetrics(). Absent si une erreur est renvoyée.| |interfaces|uint32 (facultatif)|Le masque binaire des interfaces prises en charge par le plugin. Absent si une erreur est renvoyée.| |error|string (facultatif)|Un message d'erreur est renvoyé si un plugin ne peut pas être démarré. Absent, si les métriques sont renvoyées.| *Exemples:* {"id":2,"type":3,"metrics":["external.test", "Test de l'exportateur externe."], "interfaces": 4} ou {"id":2,"type":3,"error":"message d'erreur"} #### Regular expressions Manage global regular expressions. [Regular expression API](/manual/api/reference/regexp) #### Expressions régulières Gérez les expressions régulières globales. [API Expressions régulières](/manual/api/reference/regexp) ### Regular expression The global regular expression object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |regexpid|string|*(readonly)* ID of the regular expression.| |**name**<br>(required)|string|Name of the regular expression.| |test\_string|string|Test string.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Expression régulière L'objet d'expression régulière globale a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |regexpid|string|*(lecture seule)* ID de l'expression régulière.| |**name**<br>(obligatoire)|string|Nom de l'expression régulière.| |test\_string|string|Chaîne de caractère de test.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. #### Remote commands with multiple interfaces If the target system has multiple interfaces of the selected type (Zabbix agent or IPMI), remote commands will be executed on the default interface. It is possible to execute remote commands via SSH and Telnet using another interface than the Zabbix agent one. The available interface to use is selected in the following order: * Zabbix agent default interface * SNMP default interface * JMX default interface * IPMI default interface #### Commandes à distance avec plusieurs interfaces Si le système cible possède plusieurs interfaces du type sélectionné (agent Zabbix ou IPMI), les commandes à distance seront exécutées sur l'interface par défaut. Il est possible d'exécuter des commandes à distance via SSH et Telnet en utilisant une autre interface que celle de l'agent Zabbix. L'interface disponible à utiliser est sélectionnée dans l'ordre suivant : - Interface par défaut de l'agent Zabbix - Interface par défaut SNMP - Interface par défaut JMX - Interface par défaut IPMI #### Remove token expiry Remove expiry date from token. Request: ```json { "jsonrpc": "2.0", "method": "token.update", "params": { "tokenid": "2", "expires_at": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "2" ] }, "id": 1 } ``` #### Renommer le token Supprimer la date d'expiration du token. Requête : ```json { "jsonrpc": "2.0", "method": "token.update", "params": { "tokenid": "2", "expires_at": "0" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "tokenids": [ "2" ] }, "id": 1 } ``` #### Removing hosts from host groups Remove two hosts from the given host groups. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.massremove", "params": { "groupids": [ "5", "6" ], "hostids": [ "30050", "30001" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "5", "6" ] }, "id": 1 } ``` #### Suppression d'hôtes de groupes d'hôtes Supprimez deux hôtes des groupes d'hôtes donnés. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostgroup.massremove", "params": { "groupids": [ "5", "6" ], "hostids": [ "30050", "30001" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "groupids": [ "5", "6" ] }, "id": 1 } ``` #### Removing interfaces Remove the "127.0.0.1" SNMP interface from two hosts. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.massremove", "params": { "hostids": [ "30050", "30052" ], "interfaces": { "dns": "", "ip": "127.0.0.1", "port": "161" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30069", "30070" ] }, "id": 1 } ``` #### Suppression d'interfaces Supprimez l'interface SNMP "127.0.0.1" de deux hôtes. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.massremove", "params": { "hostids": [ "30050", "30052" ], "interfaces": { "dns": "", "ip": "127.0.0.1", "port": "161" } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30069", "30070" ] }, "id": 1 } ``` #### Removing templates from a group Remove two templates from group "2". Request: ```json { "jsonrpc": "2.0", "method": "template.massremove", "params": { "templateids": [ "10085", "10086" ], "groupids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Suppression de modèles d'un groupe Supprimez deux modèles du groupe "2". Requête : ```json { "jsonrpc": "2.0", "method": "template.massremove", "params": { "templateids": [ "10085", "10086" ], "groupids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Removing web server test page It is recommended to remove the web server test page to avoid information exposure. By default, web server webroot contains a test page called index.html (Apache2 on Ubuntu is used as an example):  The test page should be removed or should be made unavailable as part of the web server hardening process. #### Suppression de la page de test du serveur Web Il est recommandé de supprimer la page de test du serveur Web pour éviter l'exposition d'informations. Par défaut, la racine du serveur Web contient une page de test appelée index.html (Apache2 sur Ubuntu est utilisé comme exemple) :  La page de test doit être supprimée ou rendue indisponible dans le cadre du processus de renforcement du serveur Web. #### Rename icon map Rename an icon map to "OS icons". Request: ```json { "jsonrpc": "2.0", "method": "iconmap.update", "params": { "iconmapid": "1", "name": "OS icons" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "iconmapids": [ "1" ] }, "id": 1 } ``` #### Renommer la carte d'icônes Renommez une carte d'icônes en "OS icons". Requête : ```json { "jsonrpc": "2.0", "method": "iconmap.update", "params": { "iconmapid": "1", "name": "OS icons" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "iconmapids": [ "1" ] }, "id": 1 } ``` #### Rename image Rename image to "Cloud icon". Request: ```json { "jsonrpc": "2.0", "method": "image.update", "params": { "imageid": "2", "name": "Cloud icon" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "imageids": [ "2" ] }, "id": 1 } ``` #### Renommer l'image Renommez l'image en "Cloud icon". Requête : ```json { "jsonrpc": "2.0", "method": "image.update", "params": { "imageid": "2", "name": "Cloud icon" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "imageids": [ "2" ] }, "id": 1 } ``` #### Renaming a dashboard Rename a dashboard to "SQL server status". Request: ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.update", "params": { "dashboardid": "2", "name": "SQL server status" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 1 } ``` #### Renommage d'un tableau de bord Renomme un tableau de bord en "Etat du serveur SQL". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "dashboard.update", "params": { "dashboardid": "2", "name": "SQL server status" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "dashboardids": [ "2" ] }, "id": 1 } ``` #### Renaming a template dashboard Rename a template dashboard to "Performance graphs". Request: ```json { "jsonrpc": "2.0", "method": "templatedashboard.update", "params": { "dashboardid": "23", "name": "Performance graphs" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "dashboardids": [ "23" ] }, "id": 1 } ``` #### Renommer un modèle de tableau de bord Renommez un modèle de tableau de bord en "Performance graphs". Requête : ```json { "jsonrpc": "2.0", "method": "templatedashboard.update", "params": { "dashboardid": "23", "name": "Performance graphs" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "dashboardids": [ "23" ] }, "id": 1 } ``` #### Renaming a template Rename the template to "Template OS Linux". Request: ```json { "jsonrpc": "2.0", "method": "template.update", "params": { "templateid": "10086", "name": "Template OS Linux" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10086" ] }, "id": 1 } ``` #### Renommer un modèle Renommez le modèle en "Template OS Linux". Requête : ```json { "jsonrpc": "2.0", "method": "template.update", "params": { "templateid": "10086", "name": "Template OS Linux" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10086" ] }, "id": 1 } ``` #### Renaming a user Rename a user to John Doe. Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.update", "params": { "userid": "1", "name": "John", "surname": "Doe" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "1" ] }, "id": 1 } ``` #### Renommer un utilisateur Renommez un utilisateur en John Doe. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.update", "params": { "userid": "1", "name": "John", "surname": "Doe" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "userids": [ "1" ] }, "id": 1 } ``` #### Replace conditions, but keep the evaluation method Request: ``` {.java} { "jsonrpc": "2.0", "method": "correlation.update", "params": { "correlationid": "1", "filter": { "conditions": [ { "type": 3, "oldtag": "error", "newtag": "ok" } ] } }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Remplacement de conditions, en conservant la méthode d'évaluation Requête : ``` {.java} { "jsonrpc": "2.0", "method": "correlation.update", "params": { "correlationid": "1", "filter": { "conditions": [ { "type": 3, "oldtag": "error", "newtag": "ok" } ] } }, "auth": "343baad4f88b4106b9b5961e77437688", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "correlationids": [ "1" ] }, "id": 1 } ``` #### Replacing host groups Unlink and clear template "10091" from the given templates. Request: ```json { "jsonrpc": "2.0", "method": "template.massupdate", "params": { "templates": [ { "templateid": "10085" }, { "templateid": "10086" } ], "templates_clear": [ { "templateid": "10091" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Remplacement des groupes d'hôtes Dissociez et effacez le modèle "10091" des modèles donnés. Requête : ```json { "jsonrpc": "2.0", "method": "template.massupdate", "params": { "templates": [ { "templateid": "10085" }, { "templateid": "10086" } ], "templates_clear": [ { "templateid": "10091" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "templateids": [ "10085", "10086" ] }, "id": 1 } ``` #### Replacing host interfaces Replace all host interfaces with a single agent interface. Request: ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.replacehostinterfaces", "params": { "hostid": "30052", "interfaces": { "dns": "", "ip": "127.0.0.1", "main": 1, "port": "10050", "type": 1, "useip": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30081" ] }, "id": 1 } ``` #### Remplacement des interfaces hôtes Remplacez toutes les interfaces hôtes par une seule interface agent. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "hostinterface.replacehostinterfaces", "params": { "hostid": "30052", "interfaces": { "dns": "", "ip": "127.0.0.1", "main": 1, "port": "10050", "type": 1, "useip": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "interfaceids": [ "30081" ] }, "id": 1 } ``` #### Replacing hosts and templates in a host group Replace all hosts in a host group to ones mentioned host and unlink all templates from host group. Request: ```json { "jsonrpc": "2.0", "method": "hostgroup.massupdate", "params": { "groups": [ { "groupid": "6" } ], "hosts": [ { "hostid": "30050" } ], "templates": [] }, "auth": "f223adf833b2bf2ff38574a67bba6372", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "groupids": [ "6", ] }, "id": 1 } ``` #### Remplacement d'hôtes et de modèles dans un groupe d'hôtes Remplacez tous les hôtes d'un groupe d'hôtes par ceux mentionnés et dissociez tous les modèles du groupe d'hôtes. Requête : ```json { "jsonrpc": "2.0", "method": "hostgroup.massupdate", "params": { "groups": [ { "groupid": "6" } ], "hosts": [ { "hostid": "30050" } ], "templates": [] }, "auth": "f223adf833b2bf2ff38574a67bba6372", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "groupids": [ "6", ] }, "id": 1 } ``` #### Replacing trigger prototype tags Replace tags for one trigger prototype. Request: ```json { "jsonrpc": "2.0", "method": "triggerprototype.update", "params": { "triggerid": "17373", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17373" ] }, "id": 1 } ``` #### Remplacement des tags de prototype de déclencheur Remplacement des tags d'un prototype de déclencheur. Requête : ```json { "jsonrpc": "2.0", "method": "triggerprototype.update", "params": { "triggerid": "17373", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "17373" ] }, "id": 1 } ``` #### Replacing triggers tags Replace tags for trigger. Request: ```json { "jsonrpc": "2.0", "method": "trigger.update", "params": { "triggerid": "13938", "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` #### Remplacement des tags des déclencheurs Remplacement des tags des déclencheurs. Requête : ```json { "jsonrpc": "2.0", "method": "trigger.update", "params": { "triggerid": "13938", "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "triggerids": [ "13938" ] }, "id": 1 } ``` # report.create # report.create # report.delete # report.delete # report.get # report.get ### Reporting file systems with zero inodes `vfs.fs.get` agent items are now capable of reporting file systems with the inode count equal to zero, which can be the case for file systems with dynamic inodes (e.g. btrfs). Additionally `vfs.fs.inode` items now will not become unsupported in such cases with mode set to 'pfree' or 'pused'. Instead the pfree/pused values for such file systems will be reported as "100" and "0" respectively. ### Signaler des systèmes de fichiers sans inode Les éléments d'agent `vfs.fs.get` sont désormais capables de signaler les systèmes de fichiers avec un nombre d'inode égal à zéro, ce qui peut être le cas pour les systèmes de fichiers avec des inodes dynamiques (par exemple, btrfs). De plus, les éléments `vfs.fs.inode` ne deviendront plus non pris en charge dans de tels cas avec le mode défini sur 'pfree' ou 'pused'. Au lieu de cela, les valeurs pfree/pused pour de tels systèmes de fichiers seront transmises comme "100" et "0" respectivement. ### Report The filter allows to select the report based on the SLA name as well as the service name. It is also possible to limit the displayed period. {width="600"} Each column (period) displays the SLI for that period. SLIs that are in breach of the set SLO are highlighted in red. 20 periods are displayed in the report. A maximum of 100 periods can be displayed, if both the *From* date and *To* date are specified. ### Rapport Le filtre permet de sélectionner le rapport en fonction du nom du SLA ainsi que du nom du service. Il est également possible de limiter la période affichée. {width="600"} Chaque colonne (période) affiche le SLI pour cette période. Les SLI qui ne respectent pas le SLO défini sont surlignés en rouge. 20 périodes sont affichées dans le rapport. Un maximum de 100 périodes peuvent être affichées, si la date *De* et la date *À* sont spécifiées. # report.update # report.update Request: ```json { "jsonrpc": "2.0", "method": "sla.create", "params": [ { "name": "Database Uptime", "slo": "99.9995", "period": "1", "timezone": "America/Toronto", "description": "Provide excellent uptime for main database engines.", "effective_date": 1672444800, "status": 1, "schedule": [ { "period_from": 0, "period_to": 601200 } ], "service_tags": [ { "tag": "Database", "operator": "0", "value": "MySQL" }, { "tag": "Database", "operator": "0", "value": "PostgreSQL" } ], "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" } ] } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` Requête : ```json { "jsonrpc": "2.0", "method": "sla.create", "params": [ { "name": "Database Uptime", "slo": "99.9995", "period": "1", "timezone": "America/Toronto", "description": "Provide excellent uptime for main database engines.", "effective_date": 1672444800, "status": 1, "schedule": [ { "period_from": 0, "period_to": 601200 } ], "service_tags": [ { "tag": "Database", "operator": "0", "value": "MySQL" }, { "tag": "Database", "operator": "0", "value": "PostgreSQL" } ], "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" } ] } ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "slaids": [ "5" ] }, "id": 1 } ``` #### Required software Zabbix is built around modern web servers, leading database engines, and PHP scripting language. #### Logiciels requis Zabbix est construit autour de serveurs Web modernes, de moteurs de base de données de pointe et du langage de script PHP. ### Reserved ID value "0" Reserved ID value "0" can be used to filter elements and to remove referenced objects. For example, to remove a referenced proxy from a host, proxy\_hostid should be set to 0 ("proxy\_hostid": "0") or to filter hosts monitored by server option proxyids should be set to 0 ("proxyids": "0"). ### Valeur d'ID réservée "0" La valeur d'ID réservée "0" peut être utilisée pour filtrer des éléments et pour supprimer des objets référencés. Par exemple, pour supprimer un proxy référencé d'un hôte, proxy\_hostid doit être défini sur 0 ("proxy\_hostid": "0") ou pour filtrer les hôtes surveillés par le serveur, l'option proxyids doit être définie sur 0 ("proxyids": "0"). #### Resize a map Change the size of the map to 1200x1200 pixels. Request: ```json { "jsonrpc": "2.0", "method": "map.update", "params": { "sysmapid": "8", "width": 1200, "height": 1200 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "8" ] }, "id": 1 } ``` #### Redimensionnement d'une carte Changer la taille de la carte en 1200x1200 pixels. Requête : ```json { "jsonrpc": "2.0", "method": "map.update", "params": { "sysmapid": "8", "width": 1200, "height": 1200 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "sysmapids": [ "8" ] }, "id": 1 } ``` #### Retrieve all discovery rules Retrieve all configured discovery rules and the discovery checks they use. Request: ```json { "jsonrpc": "2.0", "method": "drule.get", "params": { "output": "extend", "selectDChecks": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "druleid": "2", "proxy_hostid": "0", "name": "Local network", "iprange": "192.168.3.1-255", "delay": "5s", "nextcheck": "1348754327", "status": "0", "dchecks": [ { "dcheckid": "7", "druleid": "2", "type": "3", "key_": "", "snmp_community": "", "ports": "21", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" }, { "dcheckid": "8", "druleid": "2", "type": "4", "key_": "", "snmp_community": "", "ports": "80", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" } ] }, { "druleid": "6", "proxy_hostid": "0", "name": "Zabbix agent discovery", "iprange": "192.168.1.1-255", "delay": "1h", "nextcheck": "0", "status": "0", "dchecks": [ { "dcheckid": "10", "druleid": "6", "type": "9", "key_": "system.uname", "snmp_community": "", "ports": "10050", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "2", "name_source": "3" } ] } ], "id": 1 } ``` #### Récupération de toutes les règles de découverte Récupérer toutes les règles de découverte configurées et les vérifications de découverte qu'elles utilisent. Requête : ```json { "jsonrpc": "2.0", "method": "drule.get", "params": { "output": "extend", "selectDChecks": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "druleid": "2", "proxy_hostid": "0", "name": "Local network", "iprange": "192.168.3.1-255", "delay": "5s", "nextcheck": "1348754327", "status": "0", "dchecks": [ { "dcheckid": "7", "druleid": "2", "type": "3", "key_": "", "snmp_community": "", "ports": "21", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" }, { "dcheckid": "8", "druleid": "2", "type": "4", "key_": "", "snmp_community": "", "ports": "80", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" } ] }, { "druleid": "6", "proxy_hostid": "0", "name": "Zabbix agent discovery", "iprange": "192.168.1.1-255", "delay": "1h", "nextcheck": "0", "status": "0", "dchecks": [ { "dcheckid": "10", "druleid": "6", "type": "9", "key_": "system.uname", "snmp_community": "", "ports": "10050", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "2", "name_source": "3" } ] } ], "id": 1 } ``` #### Retrieve all proxies Retrieve all configured proxies and their interfaces. Request: ```json { "jsonrpc": "2.0", "method": "proxy.get", "params": { "output": "extend", "selectInterface": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "host": "Active proxy", "status": "5", "lastaccess": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "proxy_address": "", "auto_compress": "0", "proxyid": "30091", "interface": [] }, { "host": "Passive proxy", "status": "6", "lastaccess": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "proxy_address": "", "auto_compress": "0", "proxyid": "30092", "interface": { "interfaceid": "30109", "hostid": "30092", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "10051" ] } ], "id": 1 } ``` #### Récupérer tous les proxys Récupérez tous les proxys configurés et leurs interfaces. Requête : ```json { "jsonrpc": "2.0", "method": "proxy.get", "params": { "output": "extend", "selectInterface": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "host": "Active proxy", "status": "5", "lastaccess": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "proxy_address": "", "auto_compress": "0", "proxyid": "30091", "interface": [] }, { "host": "Passive proxy", "status": "6", "lastaccess": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "proxy_address": "", "auto_compress": "0", "proxyid": "30092", "interface": { "interfaceid": "30109", "hostid": "30092", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "10051" ] } ], "id": 1 } ``` #### Retrieve all scripts Retrieve all configured scripts. Request: ```json { "jsonrpc": "2.0", "method": "script.get", "params": { "output": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "4", "name": "Webhook", "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "5", "execute_on": "1", "timeout": "30s", "parameters": [ { "name": "token", "value": "{$WEBHOOK.TOKEN}" }, { "name": "host", "value": "{HOST.HOST}" }, { "name": "v", "value": "2.2" } ] } ], "id": 1 } ``` #### Récupération de tous les scripts Récupérez tous les scripts configurés. Requête : ```json { "jsonrpc": "2.0", "method": "script.get", "params": { "output": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "timeout": "30s", "parameters": [] }, { "scriptid": "4", "name": "Webhook", "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "5", "execute_on": "1", "timeout": "30s", "parameters": [ { "name": "token", "value": "{$WEBHOOK.TOKEN}" }, { "name": "host", "value": "{HOST.HOST}" }, { "name": "v", "value": "2.2" } ] } ], "id": 1 } ``` #### Retrieve a map Retrieve all data about map "3". Request: ```json { "jsonrpc": "2.0", "method": "map.get", "params": { "output": "extend", "selectSelements": "extend", "selectLinks": "extend", "selectUsers": "extend", "selectUserGroups": "extend", "selectShapes": "extend", "selectLines": "extend", "sysmapids": "3" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "selements": [ { "selementid": "10", "sysmapid": "3", "elementtype": "4", "evaltype": "0", "iconid_off": "1", "iconid_on": "0", "label": "Zabbix server", "label_location": "3", "x": "11", "y": "141", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "tags": [ { "tag": "service", "value": "mysqld", "operator": "0" } ], "viewtype": "0", "use_iconmap": "1", "urls": [], "elements": [] }, { "selementid": "11", "sysmapid": "3", "elementtype": "4", "evaltype": "0", "iconid_off": "1", "iconid_on": "0", "label": "Web server", "label_location": "3", "x": "211", "y": "191", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "viewtype": "0", "use_iconmap": "1", "tags": [], "urls": [], "elements": [] }, { "selementid": "12", "sysmapid": "3", "elementtype": "0", "evaltype": "0", "iconid_off": "185", "iconid_on": "0", "label": "{HOST.NAME}\r\n{HOST.CONN}", "label_location": "0", "x": "111", "y": "61", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "viewtype": "0", "use_iconmap": "0", "tags": [], "urls": [], "elements": [ { "hostid": "10084" } ] } ], "links": [ { "linkid": "23", "sysmapid": "3", "selementid1": "10", "selementid2": "11", "drawtype": "0", "color": "00CC00", "label": "", "linktriggers": [] } ], "users": [ { "sysmapuserid": "1", "userid": "2", "permission": "2" } ], "userGroups": [ { "sysmapusrgrpid": "1", "usrgrpid": "7", "permission": "2" } ], "shapes":[ { "sysmap_shapeid":"1", "type":"0", "x":"0", "y":"0", "width":"680", "height":"15", "text":"{MAP.NAME}", "font":"9", "font_size":"11", "font_color":"000000", "text_halign":"0", "text_valign":"0", "border_type":"0", "border_width":"0", "border_color":"000000", "background_color":"", "zindex":"0" } ], "lines":[ { "sysmap_shapeid":"2", "x1": 30, "y1": 10, "x2": 100, "y2": 50, "line_type": 1, "line_width": 10, "line_color": "009900", "zindex":"1" } ], "sysmapid": "3", "name": "Local network", "width": "400", "height": "400", "backgroundid": "0", "label_type": "2", "label_location": "3", "highlight": "1", "expandproblem": "1", "markelements": "0", "show_unack": "0", "grid_size": "50", "grid_show": "1", "grid_align": "1", "label_format": "0", "label_type_host": "2", "label_type_hostgroup": "2", "label_type_trigger": "2", "label_type_map": "2", "label_type_image": "2", "label_string_host": "", "label_string_hostgroup": "", "label_string_trigger": "", "label_string_map": "", "label_string_image": "", "iconmapid": "0", "expand_macros": "0", "severity_min": "0", "userid": "1", "private": "1", "show_suppressed": "1" } ], "id": 1 } ``` #### Récupération d'une carte Récupérer toutes les données concernant la carte "3". Requête : ```json { "jsonrpc": "2.0", "method": "map.get", "params": { "output": "extend", "selectSelements": "extend", "selectLinks": "extend", "selectUsers": "extend", "selectUserGroups": "extend", "selectShapes": "extend", "selectLines": "extend", "sysmapids": "3" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "selements": [ { "selementid": "10", "sysmapid": "3", "elementtype": "4", "evaltype": "0", "iconid_off": "1", "iconid_on": "0", "label": "Zabbix server", "label_location": "3", "x": "11", "y": "141", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "tags": [ { "tag": "service", "value": "mysqld", "operator": "0" } ], "viewtype": "0", "use_iconmap": "1", "urls": [], "elements": [] }, { "selementid": "11", "sysmapid": "3", "elementtype": "4", "evaltype": "0", "iconid_off": "1", "iconid_on": "0", "label": "Web server", "label_location": "3", "x": "211", "y": "191", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "viewtype": "0", "use_iconmap": "1", "tags": [], "urls": [], "elements": [] }, { "selementid": "12", "sysmapid": "3", "elementtype": "0", "evaltype": "0", "iconid_off": "185", "iconid_on": "0", "label": "{HOST.NAME}\r\n{HOST.CONN}", "label_location": "0", "x": "111", "y": "61", "iconid_disabled": "0", "iconid_maintenance": "0", "elementsubtype": "0", "areatype": "0", "width": "200", "height": "200", "viewtype": "0", "use_iconmap": "0", "tags": [], "urls": [], "elements": [ { "hostid": "10084" } ] } ], "links": [ { "linkid": "23", "sysmapid": "3", "selementid1": "10", "selementid2": "11", "drawtype": "0", "color": "00CC00", "label": "", "linktriggers": [] } ], "users": [ { "sysmapuserid": "1", "userid": "2", "permission": "2" } ], "userGroups": [ { "sysmapusrgrpid": "1", "usrgrpid": "7", "permission": "2" } ], "shapes":[ { "sysmap_shapeid":"1", "type":"0", "x":"0", "y":"0", "width":"680", "height":"15", "text":"{MAP.NAME}", "font":"9", "font_size":"11", "font_color":"000000", "text_halign":"0", "text_valign":"0", "border_type":"0", "border_width":"0", "border_color":"000000", "background_color":"", "zindex":"0" } ], "lines":[ { "sysmap_shapeid":"2", "x1": 30, "y1": 10, "x2": 100, "y2": 50, "line_type": 1, "line_width": 10, "line_color": "009900", "zindex":"1" } ], "sysmapid": "3", "name": "Local network", "width": "400", "height": "400", "backgroundid": "0", "label_type": "2", "label_location": "3", "highlight": "1", "expandproblem": "1", "markelements": "0", "show_unack": "0", "grid_size": "50", "grid_show": "1", "grid_align": "1", "label_format": "0", "label_type_host": "2", "label_type_hostgroup": "2", "label_type_trigger": "2", "label_type_map": "2", "label_type_image": "2", "label_string_host": "", "label_string_hostgroup": "", "label_string_trigger": "", "label_string_map": "", "label_string_image": "", "iconmapid": "0", "expand_macros": "0", "severity_min": "0", "userid": "1", "private": "1", "show_suppressed": "1" } ], "id": 1 } ``` #### Retrieve an icon map Retrieve all data about icon map "3". Request: ```json { "jsonrpc": "2.0", "method": "iconmap.get", "params": { "iconmapids": "3", "output": "extend", "selectMappings": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "mappings": [ { "iconmappingid": "3", "iconmapid": "3", "iconid": "6", "inventory_link": "1", "expression": "server", "sortorder": "0" }, { "iconmappingid": "4", "iconmapid": "3", "iconid": "10", "inventory_link": "1", "expression": "switch", "sortorder": "1" } ], "iconmapid": "3", "name": "Host type icons", "default_iconid": "2" } ], "id": 1 } ``` #### Récupération d'une carte d'icônes Récupérez toutes les données sur la carte d'icônes "3". Requête : ```json { "jsonrpc": "2.0", "method": "iconmap.get", "params": { "iconmapids": "3", "output": "extend", "selectMappings": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "mappings": [ { "iconmappingid": "3", "iconmapid": "3", "iconid": "6", "inventory_link": "1", "expression": "server", "sortorder": "0" }, { "iconmappingid": "4", "iconmapid": "3", "iconid": "10", "inventory_link": "1", "expression": "switch", "sortorder": "1" } ], "iconmapid": "3", "name": "Host type icons", "default_iconid": "2" } ], "id": 1 } ``` #### Retrieve an image Retrieve all data for image with ID "2". Request: ```json { "jsonrpc": "2.0", "method": "image.get", "params": { "output": "extend", "select_image": true, "imageids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "imageid": "2", "imagetype": "1", "name": "Cloud_(24)", "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII=" } ], "id": 1 } ``` #### Récupérer une image Récupérez toutes les données de l'image avec l'ID "2". Requête : ```json { "jsonrpc": "2.0", "method": "image.get", "params": { "output": "extend", "select_image": true, "imageids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "imageid": "2", "imagetype": "1", "name": "Cloud_(24)", "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII=" } ], "id": 1 } ``` #### Retrieve a token Retrieve all data for the token with ID "2". Request: ```json { "jsonrpc": "2.0", "method": "token.get", "params": { "output": "extend", "tokenids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "tokenid": "1", "name": "The Token", "description": "", "userid": "1", "lastaccess": "0", "status": "0", "expires_at": "1609406220", "created_at": "1611239454", "creator_userid": "1" } ], "id": 1 } ``` #### Récupération d'un token Récupérez toutes les données du token avec l'ID "2". Requête : ```json { "jsonrpc": "2.0", "method": "token.get", "params": { "output": "extend", "tokenids": "2" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "tokenid": "1", "name": "The Token", "description": "", "userid": "1", "lastaccess": "0", "status": "0", "expires_at": "1609406220", "created_at": "1611239454", "creator_userid": "1" } ], "id": 1 } ``` #### Retrieve discovered hosts by discovery rule Retrieve all hosts and the discovered services they are running that have been detected by discovery rule "4". Request: ```json { "jsonrpc": "2.0", "method": "dhost.get", "params": { "output": "extend", "selectDServices": "extend", "druleids": "4" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "dservices": [ { "dserviceid": "1", "dhostid": "1", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697227", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.1", "dns": "station.company.lan" } ], "dhostid": "1", "druleid": "4", "status": "0", "lastup": "1337697227", "lastdown": "0" }, { "dservices": [ { "dserviceid": "2", "dhostid": "2", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.4", "dns": "john.company.lan" } ], "dhostid": "2", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" }, { "dservices": [ { "dserviceid": "3", "dhostid": "3", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.26", "dns": "printer.company.lan" } ], "dhostid": "3", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" }, { "dservices": [ { "dserviceid": "4", "dhostid": "4", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.7", "dns": "mail.company.lan" } ], "dhostid": "4", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" } ], "id": 1 } ``` #### Récupération des hôtes découverts par règle de découverte Récupérer tous les hôtes et les services découverts qu'ils exécutent, détectés par la règle de découverte "4". Requête : ```json { "jsonrpc": "2.0", "method": "dhost.get", "params": { "output": "extend", "selectDServices": "extend", "druleids": "4" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "dservices": [ { "dserviceid": "1", "dhostid": "1", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697227", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.1", "dns": "station.company.lan" } ], "dhostid": "1", "druleid": "4", "status": "0", "lastup": "1337697227", "lastdown": "0" }, { "dservices": [ { "dserviceid": "2", "dhostid": "2", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.4", "dns": "john.company.lan" } ], "dhostid": "2", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" }, { "dservices": [ { "dserviceid": "3", "dhostid": "3", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.26", "dns": "printer.company.lan" } ], "dhostid": "3", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" }, { "dservices": [ { "dserviceid": "4", "dhostid": "4", "type": "4", "key_": "", "value": "", "port": "80", "status": "0", "lastup": "1337697234", "lastdown": "0", "dcheckid": "5", "ip": "192.168.1.7", "dns": "mail.company.lan" } ], "dhostid": "4", "druleid": "4", "status": "0", "lastup": "1337697234", "lastdown": "0" } ], "id": 1 } ``` #### Retrieve discovery actions Retrieve all configured discovery actions together with action conditions and operations. The filter uses the "and" evaluation type, so the `formula` property is empty and `eval_formula` is generated automatically. Request: ```json { "jsonrpc": "2.0", "method": "action.get", "params": { "output": "extend", "selectOperations": "extend", "selectFilter": "extend", "filter": { "eventsource": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "actionid": "2", "name": "Auto discovery. Linux servers.", "eventsource": "1", "status": "1", "esc_period": "0s", "pause_suppressed": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [ { "conditiontype": "10", "operator": "0", "value": "0", "value2": "", "formulaid": "B" }, { "conditiontype": "8", "operator": "0", "value": "9", "value2": "", "formulaid": "C" }, { "conditiontype": "12", "operator": "2", "value": "Linux", "value2": "", "formulaid": "A" } ], "eval_formula": "A and B and C" }, "operations": [ { "operationid": "1", "actionid": "2", "operationtype": "6", "esc_period": "0s", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "optemplate": [ { "templateid": "10001" } ] }, { "operationid": "2", "actionid": "2", "operationtype": "4", "esc_period": "0s", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "opgroup": [ { "groupid": "2" } ] } ] } ], "id": 1 } ``` #### Récupération des actions de découverte Récupérer toutes les actions de découverte configurées avec les conditions d'action et les opérations. Le filtre utilise le type d'évaluation "and", la propriété `formula` est donc vide et la propriété `eval_formula` est générée automatiquement. Requête : ```json { "jsonrpc": "2.0", "method": "action.get", "params": { "output": "extend", "selectOperations": "extend", "selectFilter": "extend", "filter": { "eventsource": 1 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "actionid": "2", "name": "Auto discovery. Linux servers.", "eventsource": "1", "status": "1", "esc_period": "0s", "pause_suppressed": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [ { "conditiontype": "10", "operator": "0", "value": "0", "value2": "", "formulaid": "B" }, { "conditiontype": "8", "operator": "0", "value": "9", "value2": "", "formulaid": "C" }, { "conditiontype": "12", "operator": "2", "value": "Linux", "value2": "", "formulaid": "A" } ], "eval_formula": "A and B and C" }, "operations": [ { "operationid": "1", "actionid": "2", "operationtype": "6", "esc_period": "0s", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "optemplate": [ { "templateid": "10001" } ] }, { "operationid": "2", "actionid": "2", "operationtype": "4", "esc_period": "0s", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "opgroup": [ { "groupid": "2" } ] } ] } ], "id": 1 } ``` #### Retrieve discovery checks for a discovery rule Retrieve all discovery checks used by discovery rule "6". Request: ```json { "jsonrpc": "2.0", "method": "dcheck.get", "params": { "output": "extend", "dcheckids": "6" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "dcheckid": "6", "druleid": "4", "type": "3", "key_": "", "snmp_community": "", "ports": "21", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" } ], "id": 1 } ``` #### Récupération de tests de découverte d'une règle de découverte Récupérer toutes les vérifications de découverte utilisés par la règle de découverte "6". Requête : ```json { "jsonrpc": "2.0", "method": "dcheck.get", "params": { "output": "extend", "dcheckids": "6" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "dcheckid": "6", "druleid": "4", "type": "3", "key_": "", "snmp_community": "", "ports": "21", "snmpv3_securityname": "", "snmpv3_securitylevel": "0", "snmpv3_authpassphrase": "", "snmpv3_privpassphrase": "", "uniq": "0", "snmpv3_authprotocol": "0", "snmpv3_privprotocol": "0", "host_source": "1", "name_source": "0" } ], "id": 1 } ``` #### Retrieve LLD rule by URL Retrieve LLD rule for host by rule URL field value. Only exact match of URL string defined for LLD rule is supported. Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "hostids": "10257", "filter": { "type": "19", "url": "http://127.0.0.1/discoverer.php" } }, "id": 39, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "itemid": "28336", "type": "19", "snmp_oid": "", "hostid": "10257", "name": "API HTTP agent", "key_": "api_discovery_rule", "delay": "5s", "history": "90d", "trends": "0", "status": "0", "value_type": "4", "trapper_hosts": "", "units": "", "error": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "1", "interfaceid": "5", "description": "", "inventory_link": "0", "lifetime": "30d", "state": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "http://127.0.0.1/discoverer.php", "query_fields": [ { "mode": "json" }, { "elements": "2" } ], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": { "X-Type": "api", "Authorization": "Bearer mF_A.B5f-2.1JcM" }, "retrieve_mode": "0", "request_method": "1", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] } ], "id": 39 } ``` #### Récupération d'une règle par URL Récupérer la règle pour l'hôte par la valeur du champ URL de la règle. Seule la correspondance exacte de la chaîne d'URL définie pour la règle est prise en charge. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "hostids": "10257", "filter": { "type": "19", "url": "http://127.0.0.1/discoverer.php" } }, "id": 39, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "itemid": "28336", "type": "19", "snmp_oid": "", "hostid": "10257", "name": "API HTTP agent", "key_": "api_discovery_rule", "delay": "5s", "history": "90d", "trends": "0", "status": "0", "value_type": "4", "trapper_hosts": "", "units": "", "error": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "flags": "1", "interfaceid": "5", "description": "", "inventory_link": "0", "lifetime": "30d", "state": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "http://127.0.0.1/discoverer.php", "query_fields": [ { "mode": "json" }, { "elements": "2" } ], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": { "X-Type": "api", "Authorization": "Bearer mF_A.B5f-2.1JcM" }, "retrieve_mode": "0", "request_method": "1", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] } ], "id": 39 } ``` #### Retrieve LLD rule with overrides Retrieve one LLD rule that has various override settings. Request: ```json { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": ["name"], "itemids": "30980", "selectOverrides": ["name", "step", "stop", "filter", "operations"] }, "id": 39, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "name": "Discover database host", "overrides": [ { "name": "Discover MySQL host", "step": "1", "stop": "1", "filter": { "evaltype": "2", "formula": "", "conditions": [ { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^mysqld\\.service$", "formulaid": "A" }, { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^mariadb\\.service$", "formulaid": "B" } ], "eval_formula": "A or B" }, "operations": [ { "operationobject": "3", "operator": "2", "value": "Database host", "opstatus": { "status": "0" }, "optag": [ { "tag": "Database", "value": "MySQL" } ], "optemplate": [ { "templateid": "10170" } ] } ] }, { "name": "Discover PostgreSQL host", "step": "2", "stop": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [ { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^postgresql\\.service$", "formulaid": "A" } ], "eval_formula": "A" }, "operations": [ { "operationobject": "3", "operator": "2", "value": "Database host", "opstatus": { "status": "0" }, "optag": [ { "tag": "Database", "value": "PostgreSQL" } ], "optemplate": [ { "templateid": "10263" } ] } ] } ] } ], "id": 39 } ``` #### Récupération d'une règle LLD avec remplacements Récupérer une règle LLD qui possède divers paramètres de remplacement. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": ["name"], "itemids": "30980", "selectOverrides": ["name", "step", "stop", "filter", "operations"] }, "id": 39, "auth": "d678e0b85688ce578ff061bd29a20d3b" } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "name": "Discover database host" "overrides": [ { "name": "Discover MySQL host", "step": "1", "stop": "1", "filter": { "evaltype": "2", "formula": "", "conditions": [ { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^mysqld\\.service$" "formulaid": "A" }, { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^mariadb\\.service$" "formulaid": "B" } ], "eval_formula": "A or B" }, "operations": [ { "operationobject": "3", "operator": "2", "value": "Database host", "opstatus": { "status": "0" }, "optag": [ { "tag": "Database", "value": "MySQL" } ], "optemplate": [ { "templateid": "10170" } ] } ] }, { "name": "Discover PostgreSQL host", "step": "2", "stop": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [ { "macro": "{#UNIT.NAME}", "operator": "8", "value": "^postgresql\\.service$" "formulaid": "A" } ], "eval_formula": "A" }, "operations": [ { "operationobject": "3", "operator": "2", "value": "Database host", "opstatus": { "status": "0" }, "optag": [ { "tag": "Database", "value": "PostgreSQL" } ], "optemplate": [ { "templateid": "10263" } ] } ] } ] } ], "id": 39 } ``` #### Retrieve scripts by host IDs Retrieve all scripts available on hosts "30079" and "30073". Request: ``` {.java} { "jsonrpc": "2.0", "method": "script.getscriptsbyhosts", "params": [ "30079", "30073" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "30079": [ { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" } ], "30073": [ { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" } ] }, "id": 1 } ``` #### Récupération des scripts par ID d'hôte Récupérer tous les scripts disponibles sur les hôtes "30079" et "30073". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "script.getscriptsbyhosts", "params": [ "30079", "30073" ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": { "30079": [ { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" } ], "30073": [ { "scriptid": "3", "name": "Detect operating system", "command": "sudo /usr/bin/nmap -O {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "7", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "1", "name": "Ping", "command": "/bin/ping -c 3 {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" }, { "scriptid": "2", "name": "Traceroute", "command": "/usr/bin/traceroute {HOST.CONN} 2>&1", "host_access": "2", "usrgrpid": "0", "groupid": "0", "description": "", "confirmation": "", "type": "0", "execute_on": "1", "hostid": "10001" } ] }, "id": 1 } ``` #### Retrieve services discovered on a host Retrieve all discovered services detected on discovered host "11". Request: ```json { "jsonrpc": "2.0", "method": "dservice.get", "params": { "output": "extend", "dhostids": "11" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "dserviceid": "12", "dhostid": "11", "value": "", "port": "80", "status": "1", "lastup": "0", "lastdown": "1348650607", "dcheckid": "5", "ip": "192.168.1.134", "dns": "john.local" }, { "dserviceid": "13", "dhostid": "11", "value": "", "port": "21", "status": "1", "lastup": "0", "lastdown": "1348650610", "dcheckid": "6", "ip": "192.168.1.134", "dns": "john.local" } ], "id": 1 } ``` #### Récupération des services découverts sur un hôte Récupérer tous les services découverts détectés sur l'hôte découvert "11". Requête : ```json { "jsonrpc": "2.0", "method": "dservice.get", "params": { "output": "extend", "dhostids": "11" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "dserviceid": "12", "dhostid": "11", "value": "", "port": "80", "status": "1", "lastup": "0", "lastdown": "1348650607", "dcheckid": "5", "ip": "192.168.1.134", "dns": "john.local" }, { "dserviceid": "13", "dhostid": "11", "value": "", "port": "21", "status": "1", "lastup": "0", "lastdown": "1348650610", "dcheckid": "6", "ip": "192.168.1.134", "dns": "john.local" } ], "id": 1 } ``` #### Retrieve task by ID Retrieve all the data about the task with the ID "1". Request: ```json { "jsonrpc": "2.0", "method": "task.get", "params": { "output": "extend", "taskids": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "taskid": "1", "type": "7", "status": "3", "clock": "1601039076", "ttl": "3600", "proxy_hostid": null, "request": { "alerting": { "stats": [ "alerts" ], "top": { "media.alerts": 10 } }, "lld": { "stats": "extend", "top": { "values": 5 } } }, "result": { "data": { "alerting": { "alerts": 0, "top": { "media.alerts": [] }, "time": 0.000663 }, "lld": { "rules": 0, "values": 0, "top": { "values": [] }, "time": 0.000442 } }, "status": "0" } } ], "id": 1 } ``` #### Récupérer d'une tâche par ID Récupérez toutes les données sur la tâche avec l'ID "1". Requête : ```json { "jsonrpc": "2.0", "method": "task.get", "params": { "output": "extend", "taskids": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "taskid": "1", "type": "7", "status": "3", "clock": "1601039076", "ttl": "3600", "proxy_hostid": null, "request": { "alerting": { "stats": [ "alerts" ], "top": { "media.alerts": 10 } }, "lld": { "stats": "extend", "top": { "values": 5 } } }, "result": { "data": { "alerting": { "alerts": 0, "top": { "media.alerts": [] }, "time": 0.000663 }, "lld": { "rules": 0, "values": 0, "top": { "values": [] }, "time": 0.000442 } }, "status": "0" } } ], "id": 1 } ``` #### Retrieve trigger actions Retrieve all configured trigger actions together with action conditions and operations. Request: ```json { "jsonrpc": "2.0", "method": "action.get", "params": { "output": "extend", "selectOperations": "extend", "selectRecoveryOperations": "extend", "selectUpdateOperations": "extend", "selectFilter": "extend", "filter": { "eventsource": 0 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "actionid": "3", "name": "Report problems to Zabbix administrators", "eventsource": "0", "status": "1", "esc_period": "1h", "pause_suppressed": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [], "eval_formula": "" }, "operations": [ { "operationid": "3", "actionid": "3", "operationtype": "0", "esc_period": "0", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "opmessage": [ { "default_msg": "1", "subject": "", "message": "", "mediatypeid" => "0" } ], "opmessage_grp": [ { "usrgrpid": "7" } ] } ], "recovery_operations": [ { "operationid": "7", "actionid": "3", "operationtype": "11", "evaltype": "0", "opconditions": [], "opmessage": { "default_msg": "0", "subject": "{TRIGGER.STATUS}: {TRIGGER.NAME}", "message": "Trigger: {TRIGGER.NAME}\r\nTrigger status: {TRIGGER.STATUS}\r\nTrigger severity: {TRIGGER.SEVERITY}\r\nTrigger URL: {TRIGGER.URL}\r\n\r\nItem values:\r\n\r\n1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}\r\n2. {ITEM.NAME2} ({HOST.NAME2}:{ITEM.KEY2}): {ITEM.VALUE2}\r\n3. {ITEM.NAME3} ({HOST.NAME3}:{ITEM.KEY3}): {ITEM.VALUE3}\r\n\r\nOriginal event ID: {EVENT.ID}", "mediatypeid": "0" } } ], "update_operations": [ { "operationid": "31", "operationtype": "12", "evaltype": "0", "opmessage": { "default_msg": "1", "subject": "", "message": "", "mediatypeid": "0" } }, { "operationid": "32", "operationtype": "0", "evaltype": "0", "opmessage": { "default_msg": "0", "subject": "Updated: {TRIGGER.NAME}", "message": "{USER.FULLNAME} updated problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME} with the following message:\r\n{EVENT.UPDATE.MESSAGE}\r\n\r\nCurrent problem status is {EVENT.STATUS}", "mediatypeid": "1" }, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage_usr": [] }, { "operationid": "33", "operationtype": "1", "evaltype": "0", "opcommand": { "scriptid": "3" }, "opcommand_hst": [ { "hostid": "10084" } ], "opcommand_grp": [] } ] } ], "id": 1 } ``` #### Récupération des actions sur déclencheurs Récupérer toutes les actions sur déclencheurs configurées avec les conditions d'action et les opérations. Requête : ```json { "jsonrpc": "2.0", "method": "action.get", "params": { "output": "extend", "selectOperations": "extend", "selectRecoveryOperations": "extend", "selectUpdateOperations": "extend", "selectFilter": "extend", "filter": { "eventsource": 0 } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "actionid": "3", "name": "Report problems to Zabbix administrators", "eventsource": "0", "status": "1", "esc_period": "1h", "pause_suppressed": "1", "filter": { "evaltype": "0", "formula": "", "conditions": [], "eval_formula": "" }, "operations": [ { "operationid": "3", "actionid": "3", "operationtype": "0", "esc_period": "0", "esc_step_from": "1", "esc_step_to": "1", "evaltype": "0", "opconditions": [], "opmessage": [ { "default_msg": "1", "subject": "", "message": "", "mediatypeid" => "0" } ], "opmessage_grp": [ { "usrgrpid": "7" } ] } ], "recovery_operations": [ { "operationid": "7", "actionid": "3", "operationtype": "11", "evaltype": "0", "opconditions": [], "opmessage": { "default_msg": "0", "subject": "{TRIGGER.STATUS}: {TRIGGER.NAME}", "message": "Trigger: {TRIGGER.NAME}\r\nTrigger status: {TRIGGER.STATUS}\r\nTrigger severity: {TRIGGER.SEVERITY}\r\nTrigger URL: {TRIGGER.URL}\r\n\r\nItem values:\r\n\r\n1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}\r\n2. {ITEM.NAME2} ({HOST.NAME2}:{ITEM.KEY2}): {ITEM.VALUE2}\r\n3. {ITEM.NAME3} ({HOST.NAME3}:{ITEM.KEY3}): {ITEM.VALUE3}\r\n\r\nOriginal event ID: {EVENT.ID}", "mediatypeid": "0" } } ], "update_operations": [ { "operationid": "31", "operationtype": "12", "evaltype": "0", "opmessage": { "default_msg": "1", "subject": "", "message": "", "mediatypeid": "0" } }, { "operationid": "32", "operationtype": "0", "evaltype": "0", "opmessage": { "default_msg": "0", "subject": "Updated: {TRIGGER.NAME}", "message": "{USER.FULLNAME} updated problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME} with the following message:\r\n{EVENT.UPDATE.MESSAGE}\r\n\r\nCurrent problem status is {EVENT.STATUS}", "mediatypeid": "1" }, "opmessage_grp": [ { "usrgrpid": "7" } ], "opmessage_usr": [] }, { "operationid": "33", "operationtype": "1", "evaltype": "0", "opcommand": { "scriptid": "3" }, "opcommand_hst": [ { "hostid": "10084" } ], "opcommand_grp": [] } ] } ], "id": 1 } ``` ### Retrieving additional information with docker.container_info[] The `docker.container_info[]` [Zabbix agent 2 item](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) now supports the option to retrieve either partial (short) or full low-level information about a Docker container. ### Récupérer des informations supplémentaires avec docker.container_info[] Le `docker.container_info[]` [élément Zabbix agent 2](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) prend désormais en charge la possibilité de récupérer des informations partielles (courtes) ou complètes de bas niveau sur un conteneur Docker. #### Retrieving all SLAs Retrieve all data about all SLAs and their properties. Request: ```json { "jsonrpc": "2.0", "method": "sla.get", "params": { "output": "extend", "selectSchedule": ["period_from", "period_to"], "selectExcludedDowntimes": ["name", "period_from", "period_to"], "selectServiceTags": ["tag", "operator", "value"], "preservekeys": true }, "auth": "85dd04b94cbfad794616eb923be13c71", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "1": { "slaid": "1", "name": "Database Uptime", "period": "1", "slo": "99.9995", "effective_date": "1672444800", "timezone": "America/Toronto", "status": "1", "description": "Provide excellent uptime for main SQL database engines.", "service_tags": [ { "tag": "Database", "operator": "0", "value": "MySQL" }, { "tag": "Database", "operator": "0", "value": "PostgreSQL" } ], "schedule": [ { "period_from": "0", "period_to": "601200" } ], "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" } ] } }, "id": 1 } ``` #### Récupération de tous les SLA Récupérez toutes les données sur tous les SLA et leurs propriétés. Requête : ```json { "jsonrpc": "2.0", "method": "sla.get", "params": { "output": "extend", "selectSchedule": ["period_from", "period_to"], "selectExcludedDowntimes": ["name", "period_from", "period_to"], "selectServiceTags": ["tag", "operator", "value"], "preservekeys": true }, "auth": "85dd04b94cbfad794616eb923be13c71", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "1": { "slaid": "1", "name": "Database Uptime", "period": "1", "slo": "99.9995", "effective_date": "1672444800", "timezone": "America/Toronto", "status": "1", "description": "Provide excellent uptime for main SQL database engines.", "service_tags": [ { "tag": "Database", "operator": "0", "value": "MySQL" }, { "tag": "Database", "operator": "0", "value": "PostgreSQL" } ], "schedule": [ { "period_from": "0", "period_to": "601200" } ], "excluded_downtimes": [ { "name": "Software version upgrade rollout", "period_from": "1648760400", "period_to": "1648764900" } ] } }, "id": 1 } ``` #### Retrieving a specific trigger prototype with tags Request: ```json { "jsonrpc": "2.0", "method": "triggerprototype.get", "params": { "output": [ "triggerid", "description" ] "selectTags": "extend", "triggerids": [ "17373" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "17373", "description": "Free disk space is less than 20% on volume {#FSNAME}", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] } ], "id": 1 } ``` #### Récupération d'un prototype de déclencheur spécifique avec des tags Requête : ```json { "jsonrpc": "2.0", "method": "triggerprototype.get", "params": { "output": [ "triggerid", "description" ] "selectTags": "extend", "triggerids": [ "17373" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "17373", "description": "Free disk space is less than 20% on volume {#FSNAME}", "tags": [ { "tag": "volume", "value": "{#FSNAME}" }, { "tag": "type", "value": "{#FSTYPE}" } ] } ], "id": 1 } ``` #### Retrieving a specific trigger with tags Retrieve a specific trigger with tags. Request: ```json { "jsonrpc": "2.0", "method": "trigger.get", "params": { "output": [ "triggerid", "description" ], "selectTags": "extend", "triggerids": [ "17578" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "17370", "description": "Service status", "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] } ], "id": 1 } ``` #### Récupération d'un déclencheur spécifique avec des tags Récupération d'un déclencheur spécifique avec des tags. Requête : ```json { "jsonrpc": "2.0", "method": "trigger.get", "params": { "output": [ "triggerid", "description" ], "selectTags": "extend", "triggerids": [ "17578" ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "17370", "description": "Service status", "tags": [ { "tag": "service", "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}" }, { "tag": "error", "value": "" } ] } ], "id": 1 } ``` #### Retrieving a web scenario Retrieve all data about web scenario "4". Request: ```json { "jsonrpc": "2.0", "method": "httptest.get", "params": { "output": "extend", "selectSteps": "extend", "httptestids": "9" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "httptestid": "9", "name": "Homepage check", "nextcheck": "0", "delay": "1m", "status": "0", "variables": [], "agent": "Zabbix", "authentication": "0", "http_user": "", "http_password": "", "hostid": "10084", "templateid": "0", "http_proxy": "", "retries": "1", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "headers": [], "steps": [ { "httpstepid": "36", "httptestid": "9", "name": "Homepage", "no": "1", "url": "http://example.com", "timeout": "15s", "posts": "", "required": "", "status_codes": "200", "variables": [ { "name":"{var}", "value":"12" } ], "follow_redirects": "1", "retrieve_mode": "0", "headers": [], "query_fields": [] }, { "httpstepid": "37", "httptestid": "9", "name": "Homepage / About", "no": "2", "url": "http://example.com/about", "timeout": "15s", "posts": "", "required": "", "status_codes": "200", "variables": [], "follow_redirects": "1", "retrieve_mode": "0", "headers": [], "query_fields": [] } ] } ], "id": 1 } ``` #### Récupération d'un scénario Web Récupérez toutes les données sur le scénario Web "4". Requête : ```json { "jsonrpc": "2.0", "method": "httptest.get", "params": { "output": "extend", "selectSteps": "extend", "httptestids": "9" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "httptestid": "9", "name": "Homepage check", "nextcheck": "0", "delay": "1m", "status": "0", "variables": [], "agent": "Zabbix", "authentication": "0", "http_user": "", "http_password": "", "hostid": "10084", "templateid": "0", "http_proxy": "", "retries": "1", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "headers": [], "steps": [ { "httpstepid": "36", "httptestid": "9", "name": "Homepage", "no": "1", "url": "http://example.com", "timeout": "15s", "posts": "", "required": "", "status_codes": "200", "variables": [ { "name":"{var}", "value":"12" } ], "follow_redirects": "1", "retrieve_mode": "0", "headers": [], "query_fields": [] }, { "httpstepid": "37", "httptestid": "9", "name": "Homepage / About", "no": "2", "url": "http://example.com/about", "timeout": "15s", "posts": "", "required": "", "status_codes": "200", "variables": [], "follow_redirects": "1", "retrieve_mode": "0", "headers": [], "query_fields": [] } ] } ], "id": 1 } ``` #### Retrieving data by name Retrieve all data about two host groups named "Zabbix servers" and "Linux servers". Request: ```json { "jsonrpc": "2.0", "method": "hostgroup.get", "params": { "output": "extend", "filter": { "name": [ "Zabbix servers", "Linux servers" ] } }, "auth": "6f38cddc44cfbb6c1bd186f9a220b5a0", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "groupid": "2", "name": "Linux servers", "internal": "0" }, { "groupid": "4", "name": "Zabbix servers", "internal": "0" } ], "id": 1 } ``` #### Récupération des données par nom Récupérez toutes les données sur deux groupes d'hôtes nommés "Zabbix servers" et "Linux servers". Requête : ```json { "jsonrpc": "2.0", "method": "hostgroup.get", "params": { "output": "extend", "filter": { "name": [ "Zabbix servers", "Linux servers" ] } }, "auth": "6f38cddc44cfbb6c1bd186f9a220b5a0", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "groupid": "2", "name": "Linux servers", "internal": "0" }, { "groupid": "4", "name": "Zabbix servers", "internal": "0" } ], "id": 1 } ``` #### Retrieving data by name Retrieve all data about two hosts named "Zabbix server" and "Linux server". Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "filter": { "host": [ "Zabbix server", "Linux server" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10160", "proxy_hostid": "0", "host": "Zabbix server", "status": "0", "lastaccess": "0", "ipmi_authtype": "-1", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "name": "Zabbix server", "flags": "0", "description": "The Zabbix monitoring server.", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "inventory_mode": "1" }, { "hostid": "10167", "proxy_hostid": "0", "host": "Linux server", "status": "0", "lastaccess": "0", "ipmi_authtype": "-1", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "name": "Linux server", "flags": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "inventory_mode": "1" } ], "id": 1 } ``` #### Récupération des données par nom Récupérez toutes les données sur deux hôtes nommés "Zabbix server" et "Linux server". Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "filter": { "host": [ "Zabbix server", "Linux server" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10160", "proxy_hostid": "0", "host": "Zabbix server", "status": "0", "lastaccess": "0", "ipmi_authtype": "-1", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "name": "Zabbix server", "flags": "0", "description": "The Zabbix monitoring server.", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "inventory_mode": "1" }, { "hostid": "10167", "proxy_hostid": "0", "host": "Linux server", "status": "0", "lastaccess": "0", "ipmi_authtype": "-1", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "name": "Linux server", "flags": "0", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "inventory_mode": "1" } ], "id": 1 } ``` #### Retrieving discovery rules from a host Retrieve all discovery rules from host "10202". Request: ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": "extend", "hostids": "10202" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "itemid": "27425", "type": "0", "snmp_oid": "", "hostid": "10202", "name": "Network interface discovery", "key_": "net.if.discovery", "delay": "1h", "state": "0", "status": "0", "trapper_hosts": "", "error": "", "templateid": "22444", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "119", "description": "Discovery of network interfaces as defined in global regular expression \"Network interfaces for discovery\".", "lifetime": "30d", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] }, { "itemid": "27426", "type": "0", "snmp_oid": "", "hostid": "10202", "name": "Mounted filesystem discovery", "key_": "vfs.fs.discovery", "delay": "1h", "state": "0", "status": "0", "trapper_hosts": "", "error": "", "templateid": "22450", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "119", "description": "Discovery of file systems of different types as defined in global regular expression \"File systems for discovery\".", "lifetime": "30d", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] } ], "id": 1 } ``` #### Récupération des règles de découverte bas niveau d'un hôte Récupérer toutes les règles de découverte de l'hôte "10202". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": "extend", "hostids": "10202" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "itemid": "27425", "type": "0", "snmp_oid": "", "hostid": "10202", "name": "Network interface discovery", "key_": "net.if.discovery", "delay": "1h", "state": "0", "status": "0", "trapper_hosts": "", "error": "", "templateid": "22444", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "119", "description": "Discovery of network interfaces as defined in global regular expression \"Network interfaces for discovery\".", "lifetime": "30d", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] }, { "itemid": "27426", "type": "0", "snmp_oid": "", "hostid": "10202", "name": "Mounted filesystem discovery", "key_": "vfs.fs.discovery", "delay": "1h", "state": "0", "status": "0", "trapper_hosts": "", "error": "", "templateid": "22450", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "119", "description": "Discovery of file systems of different types as defined in global regular expression \"File systems for discovery\".", "lifetime": "30d", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "parameters": [] } ], "id": 1 } ``` #### Retrieving enabled user groups Retrieve all enabled user groups. Request: ```json { "jsonrpc": "2.0", "method": "usergroup.get", "params": { "output": "extend", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "usrgrpid": "7", "name": "Zabbix administrators", "gui_access": "0", "users_status": "0", "debug_mode": "1" }, { "usrgrpid": "8", "name": "Guests", "gui_access": "0", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "11", "name": "Enabled debug mode", "gui_access": "0", "users_status": "0", "debug_mode": "1" }, { "usrgrpid": "12", "name": "No access to the frontend", "gui_access": "2", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "14", "name": "Read only", "gui_access": "0", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "18", "name": "Deny", "gui_access": "0", "users_status": "0", "debug_mode": "0" } ], "id": 1 } ``` #### Récupération des groupes d'utilisateurs activés Récupérer tous les groupes d'utilisateurs activés. Requête : ```json { "jsonrpc": "2.0", "method": "usergroup.get", "params": { "output": "extend", "status": 0 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "usrgrpid": "7", "name": "Zabbix administrators", "gui_access": "0", "users_status": "0", "debug_mode": "1" }, { "usrgrpid": "8", "name": "Guests", "gui_access": "0", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "11", "name": "Enabled debug mode", "gui_access": "0", "users_status": "0", "debug_mode": "1" }, { "usrgrpid": "12", "name": "No access to the frontend", "gui_access": "2", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "14", "name": "Read only", "gui_access": "0", "users_status": "0", "debug_mode": "0" }, { "usrgrpid": "18", "name": "Deny", "gui_access": "0", "users_status": "0", "debug_mode": "0" } ], "id": 1 } ``` #### Retrieving filter conditions Retrieve the name of the LLD rule "24681" and its filter conditions. The filter uses the "and" evaluation type, so the `formula` property is empty and `eval_formula` is generated automatically. Request: ```json { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": ["name"], "selectFilter": "extend", "itemids": ["24681"] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "24681", "name": "Filtered LLD rule", "filter": { "evaltype": "1", "formula": "", "conditions": [ { "macro": "{#MACRO1}", "value": "@regex1", "operator": "8", "formulaid": "A" }, { "macro": "{#MACRO2}", "value": "@regex2", "operator": "9", "formulaid": "B" }, { "macro": "{#MACRO3}", "value": "", "operator": "12", "formulaid": "C" }, { "macro": "{#MACRO4}", "value": "", "operator": "13", "formulaid": "D" } ], "eval_formula": "A and B and C and D" } } ], "id": 1 } ``` #### Récupération des conditions de filtre Récupérez le nom de la règle "24681" et ses conditions de filtrage. Le filtre utilise le type d'évaluation "et". La propriété `formula` est donc vide et la propriété `eval_formula` est générée automatiquement. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "discoveryrule.get", "params": { "output": [ "name" ], "selectFilter": "extend", "itemids": ["24681"] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "itemid": "24681", "name": "Filtered LLD rule", "filter": { "evaltype": "1", "formula": "", "conditions": [ { "macro": "{#MACRO1}", "value": "@regex1", "operator": "8", "formulaid": "A" }, { "macro": "{#MACRO2}", "value": "@regex2", "operator": "9", "formulaid": "B" }, { "macro": "{#MACRO3}", "value": "", "operator": "12", "formulaid": "C" }, { "macro": "{#MACRO4}", "value": "", "operator": "13", "formulaid": "D" } ], "eval_formula": "A and B and C and D" } } ], "id": 1 } ``` #### Retrieving global macros Retrieve all global macros. Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.get", "params": { "output": "extend", "globalmacro": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "globalmacroid": "6", "macro": "{$SNMP_COMMUNITY}", "value": "public", "description": "", "type": "0" } ], "id": 1 } ``` #### Récupération des macros globales Récupérez toutes les macros globales. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.get", "params": { "output": "extend", "globalmacro": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "globalmacroid": "6", "macro": "{$SNMP_COMMUNITY}", "value": "public", "description": "", "type": "0" } ], "id": 1 } ``` #### Retrieving global regular expressions. Request: ```json { "jsonrpc": "2.0", "method": "regexp.get", "params": { "output": ["regexpid", "name"], "selectExpressions": ["expression", "expression_type"], "regexpids": [1, 2], "preservekeys": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": { "1": { "regexpid": "1", "name": "File systems for discovery", "expressions": [ { "expression": "^(btrfs|ext2|ext3|ext4|reiser|xfs|ffs|ufs|jfs|jfs2|vxfs|hfs|apfs|refs|ntfs|fat32|zfs)$", "expression_type": "3" } ] }, "2": { "regexpid": "2", "name": "Network interfaces for discovery", "expressions": [ { "expression": "^Software Loopback Interface", "expression_type": "4" }, { "expression": "^(In)?[Ll]oop[Bb]ack[0-9._]*$", "expression_type": "4" }, { "expression": "^NULL[0-9.]*$", "expression_type": "4" }, { "expression": "^[Ll]o[0-9.]*$", "expression_type": "4" }, { "expression": "^[Ss]ystem$", "expression_type": "4" }, { "expression": "^Nu[0-9.]*$", "expression_type": "4" } ] } }, "id": 1 } ``` #### Récupération des expressions régulières globales. Requête : ```json { "jsonrpc": "2.0", "method": "regexp.get", "params": { "output": ["regexpid", "name"], "selectExpressions": ["expression", "expression_type"], "regexpids": [1, 2], "preservekeys": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "1": { "regexpid": "1", "name": "File systems for discovery", "expressions": [ { "expression": "^(btrfs|ext2|ext3|ext4|reiser|xfs|ffs|ufs|jfs|jfs2|vxfs|hfs|apfs|refs|ntfs|fat32|zfs)$", "expression_type": "3" } ] }, "2": { "regexpid": "2", "name": "Network interfaces for discovery", "expressions": [ { "expression": "^Software Loopback Interface", "expression_type": "4" }, { "expression": "^(In)?[Ll]oop[Bb]ack[0-9._]*$", "expression_type": "4" }, { "expression": "^NULL[0-9.]*$", "expression_type": "4" }, { "expression": "^[Ll]o[0-9.]*$", "expression_type": "4" }, { "expression": "^[Ss]ystem$", "expression_type": "4" }, { "expression": "^Nu[0-9.]*$", "expression_type": "4" } ] } }, "id": 1 } ``` #### Retrieving graphs from hosts Retrieve all graphs from host "10107" and sort them by name. Request: ```json { "jsonrpc": "2.0", "method": "graph.get", "params": { "output": "extend", "hostids": 10107, "sortfield": "name" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "graphid": "612", "name": "CPU jumps", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "439", "show_work_period": "1", "show_triggers": "1", "graphtype": "0", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "0", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "613", "name": "CPU load", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "433", "show_work_period": "1", "show_triggers": "1", "graphtype": "0", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "1", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "614", "name": "CPU utilization", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "387", "show_work_period": "1", "show_triggers": "0", "graphtype": "1", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "1", "ymax_type": "1", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "645", "name": "Disk space usage /", "width": "600", "height": "340", "yaxismin": "0", "yaxismax": "0", "templateid": "0", "show_work_period": "0", "show_triggers": "0", "graphtype": "2", "show_legend": "1", "show_3d": "1", "percent_left": "0", "percent_right": "0", "ymin_type": "0", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "4" } ], "id": 1 } ``` #### Récupération des graphiques des hôtes Récupérez tous les graphiques de l'hôte "10107" et triez-les par nom. Requête : ```json { "jsonrpc": "2.0", "method": "graph.get", "params": { "output": "extend", "hostids": 10107, "sortfield": "name" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "graphid": "612", "name": "CPU jumps", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "439", "show_work_period": "1", "show_triggers": "1", "graphtype": "0", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "0", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "613", "name": "CPU load", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "433", "show_work_period": "1", "show_triggers": "1", "graphtype": "0", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "1", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "614", "name": "CPU utilization", "width": "900", "height": "200", "yaxismin": "0", "yaxismax": "100", "templateid": "387", "show_work_period": "1", "show_triggers": "0", "graphtype": "1", "show_legend": "1", "show_3d": "0", "percent_left": "0", "percent_right": "0", "ymin_type": "1", "ymax_type": "1", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "0" }, { "graphid": "645", "name": "Disk space usage /", "width": "600", "height": "340", "yaxismin": "0", "yaxismax": "0", "templateid": "0", "show_work_period": "0", "show_triggers": "0", "graphtype": "2", "show_legend": "1", "show_3d": "1", "percent_left": "0", "percent_right": "0", "ymin_type": "0", "ymax_type": "0", "ymin_itemid": "0", "ymax_itemid": "0", "flags": "4" } ], "id": 1 } ``` #### Retrieving host groups Retrieve names of the groups host "Zabbix server" is member of, but no host details themselves. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectGroups": "extend", "filter": { "host": [ "Zabbix server" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10085", "groups": [ { "groupid": "2", "name": "Linux servers", "internal": "0", "flags": "0" }, { "groupid": "4", "name": "Zabbix servers", "internal": "0", "flags": "0" } ] } ], "id": 2 } ``` #### Récupération des groupes d'hôtes Récupérer les noms des groupes dont l'hôte "Zabbix server" est membre, mais pas les détails des hôtes eux-mêmes. Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectGroups": "extend", "filter": { "host": [ "Zabbix server" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 2 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10085", "groups": [ { "groupid": "2", "name": "Linux servers", "internal": "0", "flags": "0" }, { "groupid": "4", "name": "Zabbix servers", "internal": "0", "flags": "0" } ] } ], "id": 2 } ``` #### Retrieving host macros for a host Retrieve all host macros defined for host "10198". Request: ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.get", "params": { "output": "extend", "hostids": "10198" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "hostmacroid": "9", "hostid": "10198", "macro": "{$INTERFACE}", "value": "eth0", "description": "", "type": "0" }, { "hostmacroid": "11", "hostid": "10198", "macro": "{$SNMP_COMMUNITY}", "value": "public", "description": "", "type": "0" } ], "id": 1 } ``` #### Récupération des macros d'hôte pour un hôte Récupérez toutes les macros d'hôte définies pour l'hôte "10198". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "usermacro.get", "params": { "output": "extend", "hostids": "10198" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "hostmacroid": "9", "hostid": "10198", "macro": "{$INTERFACE}", "value": "eth0", "description": "", "type": "0" }, { "hostmacroid": "11", "hostid": "10198", "macro": "{$SNMP_COMMUNITY}", "value": "public", "description": "", "type": "0" } ], "id": 1 } ``` #### Retrieving host prototypes from an LLD rule Retrieve all host prototypes, their group links, group prototypes and tags from an LLD rule. Request: ```json { "jsonrpc": "2.0", "method": "hostprototype.get", "params": { "output": "extend", "selectInterfaces": "extend", "selectGroupLinks": "extend", "selectGroupPrototypes": "extend", "selectTags": "extend", "discoveryids": "23554" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10092", "host": "{#HV.UUID}", "name": "{#HV.UUID}", "status": "0", "templateid": "0", "discover": "0", "custom_interfaces": "1", "inventory_mode": "-1", "groupLinks": [ { "group_prototypeid": "4", "hostid": "10092", "groupid": "7", "templateid": "0" } ], "groupPrototypes": [ { "group_prototypeid": "7", "hostid": "10092", "name": "{#CLUSTER.NAME}", "templateid": "0" } ], "tags": [ { "tag": "Datacenter", "value": "{#DATACENTER.NAME}" }, { "tag": "Instance type", "value": "{#INSTANCE_TYPE}" } ], "interfaces": [ { "main": "1", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } } ] } ], "id": 1 } ``` #### Récupération de prototypes d'hôtes à partir d'une règle LLD Récupérez tous les prototypes d'hôtes, leurs liens de groupe, prototypes de groupe et tags à partir d'une règle LLD. Requête : ```json { "jsonrpc": "2.0", "method": "hostprototype.get", "params": { "output": "extend", "selectInterfaces": "extend", "selectGroupLinks": "extend", "selectGroupPrototypes": "extend", "selectTags": "extend", "discoveryids": "23554" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10092", "host": "{#HV.UUID}", "name": "{#HV.UUID}", "status": "0", "templateid": "0", "discover": "0", "custom_interfaces": "1", "inventory_mode": "-1", "groupLinks": [ { "group_prototypeid": "4", "hostid": "10092", "groupid": "7", "templateid": "0" } ], "groupPrototypes": [ { "group_prototypeid": "7", "hostid": "10092", "name": "{#CLUSTER.NAME}", "templateid": "0" } ], "tags": [ { "tag": "Datacenter", "value": "{#DATACENTER.NAME}" }, { "tag": "Instance type", "value": "{#INSTANCE_TYPE}" } ], "interfaces": [ { "main": "1", "type": "2", "useip": "1", "ip": "127.0.0.1", "dns": "", "port": "161", "details": { "version": "2", "bulk": "1", "community": "{$SNMP_COMMUNITY}" } } ] } ], "id": 1 } ``` #### Retrieving hosts We now have a valid user authentication token that can be used to access the data in Zabbix. For example, let's use the [host.get](/manual/api/reference/host/get) method to retrieve the IDs, host names and interfaces of all configured [hosts](/manual/api/reference/host/object): ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": [ "hostid", "host" ], "selectInterfaces": [ "interfaceid", "ip" ] }, "id": 2, "auth": "0424bd59b807674191e7d77572075f33" } ``` ::: noteimportant Note that the `auth` property is now set to the authentication token we've obtained by calling `user.login`. ::: The response object will contain the requested data about the hosts: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "host": "Zabbix server", "interfaces": [ { "interfaceid": "1", "ip": "127.0.0.1" } ] } ], "id": 2 } ``` ::: notetip For performance reasons we recommend to always list the object properties you want to retrieve and avoid retrieving everything. ::: #### Récupération des hôtes Nous avons maintenant un jeton d'authentification utilisateur valide qui peut être utilisé pour accéder aux données dans Zabbix. Par exemple, utilisons la méthode [host.get](/manual/api/reference/host/get) pour récupérer les ID, les noms d'hôtes et les interfaces de tous les [hôtes](/manual/api/reference/host/object) : ``` json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": [ "hostid", "host" ], "selectInterfaces": [ "interfaceid", "ip" ] }, "id": 2, "auth": "0424bd59b807674191e7d77572075f33" } ``` ::: noteimportant Notez que la propriété `auth` est maintenant définie sur le jeton d'authentification que nous avons obtenu en appelant `user.login`. ::: L'objet de réponse contiendra les données demandées au sujet des hôtes : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "host": "Zabbix server", "interfaces": [ { "interfaceid": "1", "ip": "127.0.0.1" } ] } ], "id": 2 } ``` ::: notetip Pour des raisons de performances, nous vous recommandons de toujours lister les propriétés d'objet que vous souhaitez récupérer et d'éviter de tout récupérer. ::: #### Retrieving item history data Return 10 latest values received from a numeric(float) item. Request: ```json { "jsonrpc": "2.0", "method": "history.get", "params": { "output": "extend", "history": 0, "itemids": "23296", "sortfield": "clock", "sortorder": "DESC", "limit": 10 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23296", "clock": "1351090996", "value": "0.085", "ns": "563157632" }, { "itemid": "23296", "clock": "1351090936", "value": "0.16", "ns": "549216402" }, { "itemid": "23296", "clock": "1351090876", "value": "0.18", "ns": "537418114" }, { "itemid": "23296", "clock": "1351090816", "value": "0.21", "ns": "522659528" }, { "itemid": "23296", "clock": "1351090756", "value": "0.215", "ns": "507809457" }, { "itemid": "23296", "clock": "1351090696", "value": "0.255", "ns": "495509699" }, { "itemid": "23296", "clock": "1351090636", "value": "0.36", "ns": "477708209" }, { "itemid": "23296", "clock": "1351090576", "value": "0.375", "ns": "463251343" }, { "itemid": "23296", "clock": "1351090516", "value": "0.315", "ns": "447947017" }, { "itemid": "23296", "clock": "1351090456", "value": "0.275", "ns": "435307141" } ], "id": 1 } ``` #### Récupération des données d'historique des éléments Renvoie les 10 dernières valeurs reçues d'un élément numérique (flottant). Requête : ```json { "jsonrpc": "2.0", "method": "history.get", "params": { "output": "extend", "history": 0, "itemids": "23296", "sortfield": "clock", "sortorder": "DESC", "limit": 10 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23296", "clock": "1351090996", "value": "0.085", "ns": "563157632" }, { "itemid": "23296", "clock": "1351090936", "value": "0.16", "ns": "549216402" }, { "itemid": "23296", "clock": "1351090876", "value": "0.18", "ns": "537418114" }, { "itemid": "23296", "clock": "1351090816", "value": "0.21", "ns": "522659528" }, { "itemid": "23296", "clock": "1351090756", "value": "0.215", "ns": "507809457" }, { "itemid": "23296", "clock": "1351090696", "value": "0.255", "ns": "495509699" }, { "itemid": "23296", "clock": "1351090636", "value": "0.36", "ns": "477708209" }, { "itemid": "23296", "clock": "1351090576", "value": "0.375", "ns": "463251343" }, { "itemid": "23296", "clock": "1351090516", "value": "0.315", "ns": "447947017" }, { "itemid": "23296", "clock": "1351090456", "value": "0.275", "ns": "435307141" } ], "id": 1 } ``` #### Retrieving item prototypes from an LLD rule Retrieve all item prototypes for specific LLD rule ID. Request: ```json { "jsonrpc": "2.0", "method": "itemprototype.get", "params": { "output": "extend", "discoveryids": "27426" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23077", "type": "0", "snmp_oid": "", "hostid": "10079", "name": "Incoming network traffic on en0", "key_": "net.if.in[en0]", "delay": "1m", "history": "1w", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "bps", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] }, { "itemid": "10010", "type": "0", "snmp_oid": "", "hostid": "10001", "name": "Processor load (1 min average per core)", "key_": "system.cpu.load[percpu,avg1]", "delay": "1m", "history": "1w", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "The processor load is calculated as system CPU load divided by number of CPU cores.", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 1 } ``` #### Récupération des prototypes d'éléments à partir d'une règle LLD Récupérez tous les prototypes d'éléments pour un ID de règle LLD spécifique. Requête : ```json { "jsonrpc": "2.0", "method": "itemprototype.get", "params": { "output": "extend", "discoveryids": "27426" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23077", "type": "0", "snmp_oid": "", "hostid": "10079", "name": "Incoming network traffic on en0", "key_": "net.if.in[en0]", "delay": "1m", "history": "1w", "trends": "365d", "status": "0", "value_type": "3", "trapper_hosts": "", "units": "bps", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "discover": "0", "uuid": "", "parameters": [] }, { "itemid": "10010", "type": "0", "snmp_oid": "", "hostid": "10001", "name": "Processor load (1 min average per core)", "key_": "system.cpu.load[percpu,avg1]", "delay": "1m", "history": "1w", "trends": "365d", "status": "0", "value_type": "0", "trapper_hosts": "", "units": "", "logtimefmt": "", "templateid": "0", "valuemapid": "0", "params": "", "ipmi_sensor": "", "authtype": "0", "username": "", "password": "", "publickey": "", "privatekey": "", "interfaceid": "0", "description": "The processor load is calculated as system CPU load divided by number of CPU cores.", "evaltype": "0", "jmx_endpoint": "", "master_itemid": "0", "timeout": "3s", "url": "", "query_fields": [], "posts": "", "status_codes": "200", "follow_redirects": "1", "post_type": "0", "http_proxy": "", "headers": [], "retrieve_mode": "0", "request_method": "0", "output_format": "0", "ssl_cert_file": "", "ssl_key_file": "", "ssl_key_password": "", "verify_peer": "0", "verify_host": "0", "allow_traps": "0", "lastclock": "0", "lastns": "0", "lastvalue": "0", "prevvalue": "0", "discover": "0", "uuid": "", "parameters": [] } ], "id": 1 } ``` #### Retrieving items with preprocessing rules Retrieve all items and their preprocessing rules for specific host ID. Request: ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": ["itemid", "name", "key_"], "selectPreprocessing": "extend", "hostids": "10254" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "itemid": "23865", "name": "HTTP agent example JSON", "key_": "json", "preprocessing": [ { "type": "12", "params": "$.random", "error_handler": "1", "error_handler_params": "" } ] }, "id": 1 } ``` #### Récupérer des éléments avec des règles de prétraitement Récupérez tous les éléments et leurs règles de prétraitement pour un ID d'hôte spécifique. Requête : ```json { "jsonrpc": "2.0", "method": "item.get", "params": { "output": ["itemid", "name", "key_"], "selectPreprocessing": "extend", "hostids": "10254" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "itemid": "23865", "name": "HTTP agent example JSON", "key_": "json", "preprocessing": [ { "type": "12", "params": "$.random", "error_handler": "1", "error_handler_params": "" } ] }, "id": 1 } ``` #### Retrieving item trend data Request: ```json { "jsonrpc": "2.0", "method": "trend.get", "params": { "output": [ "itemid", "clock", "num", "value_min", "value_avg", "value_max", ], "itemids": [ "23715" ], "limit": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23715", "clock": "1446199200", "num": "60", "value_min": "0.165", "value_avg": "0.2168", "value_max": "0.35", } ], "id": 1 } ``` #### Récupération des données de tendance d'un élément Requête : ```json { "jsonrpc": "2.0", "method": "trend.get", "params": { "output": [ "itemid", "clock", "num", "value_min", "value_avg", "value_max", ], "itemids": [ "23715" ], "limit": "1" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "itemid": "23715", "clock": "1446199200", "num": "60", "value_min": "0.165", "value_avg": "0.2168", "value_max": "0.35", } ], "id": 1 } ``` #### Retrieving linked templates Retrieve the IDs and names of templates linked to host "10084". Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectParentTemplates": [ "templateid", "name" ], "hostids": "10084" }, "id": 1, "auth": "70785d2b494a7302309b48afcdb3a401" } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "parentTemplates": [ { "name": "Linux", "templateid": "10001" }, { "name": "Zabbix Server", "templateid": "10047" } ] } ], "id": 1 } ``` #### Récupération des modèles liés Récupérez les identifiants et les noms des modèles liés à l'hôte "10084". Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectParentTemplates": [ "templateid", "name" ], "hostids": "10084" }, "id": 1, "auth": "70785d2b494a7302309b48afcdb3a401" } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "parentTemplates": [ { "name": "Linux", "templateid": "10001" }, { "name": "Zabbix Server", "templateid": "10047" } ] } ], "id": 1 } ``` #### Retrieving maintenances Retrieve all configured maintenances, and the data about the assigned host groups, defined time periods and problem tags. Request: ```json { "jsonrpc": "2.0", "method": "maintenance.get", "params": { "output": "extend", "selectGroups": "extend", "selectTimeperiods": "extend", "selectTags": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "maintenanceid": "3", "name": "Sunday maintenance", "maintenance_type": "0", "description": "", "active_since": "1358844540", "active_till": "1390466940", "tags_evaltype": "0", "groups": [ { "groupid": "4", "name": "Zabbix servers", "internal": "0" } ], "timeperiods": [ { "timeperiod_type": "3", "every": "1", "month": "0", "dayofweek": "1", "day": "0", "start_time": "64800", "period": "3600", "start_date": "2147483647" } ], "tags": [ { "tag": "service", "operator": "0", "value": "mysqld", }, { "tag": "error", "operator": "2", "value": "" } ] } ], "id": 1 } ``` #### Récupération des maintenances Récupérez toutes les maintenances configurées et les données sur les groupes d'hôtes affectés, les périodes définies et les tags de problème. Requête : ```json { "jsonrpc": "2.0", "method": "maintenance.get", "params": { "output": "extend", "selectGroups": "extend", "selectTimeperiods": "extend", "selectTags": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "maintenanceid": "3", "name": "Sunday maintenance", "maintenance_type": "0", "description": "", "active_since": "1358844540", "active_till": "1390466940", "tags_evaltype": "0", "groups": [ { "groupid": "4", "name": "Zabbix servers", "internal": "0" } ], "timeperiods": [ { "timeperiod_type": "3", "every": "1", "month": "0", "dayofweek": "1", "day": "0", "start_time": "64800", "period": "3600", "start_date": "2147483647" } ], "tags": [ { "tag": "service", "operator": "0", "value": "mysqld", }, { "tag": "error", "operator": "2", "value": "" } ] } ], "id": 1 } ``` #### Retrieving media types Retrieve all configured media types. Request: ```json { "jsonrpc": "2.0", "method": "mediatype.get", "params": { "output": "extend", "selectMessageTemplates": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "mediatypeid": "1", "type": "0", "name": "Email", "smtp_server": "mail.example.com", "smtp_helo": "example.com", "smtp_email": "zabbix@example.com", "exec_path": "", "gsm_modem": "", "username": "", "passwd": "", "status": "0", "smtp_port": "25", "smtp_security": "0", "smtp_verify_peer": "0", "smtp_verify_host": "0", "smtp_authentication": "0", "exec_params": "", "maxsessions": "1", "maxattempts": "3", "attempt_interval": "10s", "content_type": "0", "script": "", "timeout": "30s", "process_tags": "0", "show_event_menu": "1", "event_menu_url": "", "event_menu_name": "", "description": "", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "Problem: {EVENT.NAME}", "message": "Problem started at {EVENT.TIME} on {EVENT.DATE}\r\nProblem name: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\nSeverity: {EVENT.SEVERITY}\r\nOperational data: {EVENT.OPDATA}\r\nOriginal problem ID: {EVENT.ID}\r\n{TRIGGER.URL}" }, { "eventsource": "0", "recovery": "1", "subject": "Resolved: {EVENT.NAME}", "message": "Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}\r\nProblem name: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\nSeverity: {EVENT.SEVERITY}\r\n\r\nOriginal problem ID: {EVENT.ID}\r\n{TRIGGER.URL}" }, { "eventsource": "0", "recovery": "2", "subject": "Updated problem: {EVENT.NAME}", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}.\r\n{EVENT.UPDATE.MESSAGE}\r\n\r\nCurrent problem status is {EVENT.STATUS}, acknowledged: {EVENT.ACK.STATUS}." }, { "eventsource": "1", "recovery": "0", "subject": "Discovery: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}", "message": "Discovery rule: {DISCOVERY.RULE.NAME}\r\n\r\nDevice IP: {DISCOVERY.DEVICE.IPADDRESS}\r\nDevice DNS: {DISCOVERY.DEVICE.DNS}\r\nDevice status: {DISCOVERY.DEVICE.STATUS}\r\nDevice uptime: {DISCOVERY.DEVICE.UPTIME}\r\n\r\nDevice service name: {DISCOVERY.SERVICE.NAME}\r\nDevice service port: {DISCOVERY.SERVICE.PORT}\r\nDevice service status: {DISCOVERY.SERVICE.STATUS}\r\nDevice service uptime: {DISCOVERY.SERVICE.UPTIME}" }, { "eventsource": "2", "recovery": "0", "subject": "Autoregistration: {HOST.HOST}", "message": "Host name: {HOST.HOST}\r\nHost IP: {HOST.IP}\r\nAgent port: {HOST.PORT}" } ], "parameters": [] }, { "mediatypeid": "3", "type": "2", "name": "SMS", "smtp_server": "", "smtp_helo": "", "smtp_email": "", "exec_path": "", "gsm_modem": "/dev/ttyS0", "username": "", "passwd": "", "status": "0", "smtp_port": "25", "smtp_security": "0", "smtp_verify_peer": "0", "smtp_verify_host": "0", "smtp_authentication": "0", "exec_params": "", "maxsessions": "1", "maxattempts": "3", "attempt_interval": "10s", "content_type": "1", "script": "", "timeout": "30s", "process_tags": "0", "show_event_menu": "1", "event_menu_url": "", "event_menu_name": "", "description": "", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "", "message": "{EVENT.SEVERITY}: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\n{EVENT.DATE} {EVENT.TIME}" }, { "eventsource": "0", "recovery": "1", "subject": "", "message": "RESOLVED: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\n{EVENT.DATE} {EVENT.TIME}" }, { "eventsource": "0", "recovery": "2", "subject": "", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}" }, { "eventsource": "1", "recovery": "0", "subject": "", "message": "Discovery: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}" }, { "eventsource": "2", "recovery": "0", "subject": "", "message": "Autoregistration: {HOST.HOST}\r\nHost IP: {HOST.IP}\r\nAgent port: {HOST.PORT}" } ], "parameters": [] } ], "id": 1 } ``` #### Récupération des types de médias Récupérez tous les types de médias configurés. Requête : ```json { "jsonrpc": "2.0", "method": "mediatype.get", "params": { "output": "extend", "selectMessageTemplates": "extend" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "mediatypeid": "1", "type": "0", "name": "Email", "smtp_server": "mail.example.com", "smtp_helo": "example.com", "smtp_email": "zabbix@example.com", "exec_path": "", "gsm_modem": "", "username": "", "passwd": "", "status": "0", "smtp_port": "25", "smtp_security": "0", "smtp_verify_peer": "0", "smtp_verify_host": "0", "smtp_authentication": "0", "exec_params": "", "maxsessions": "1", "maxattempts": "3", "attempt_interval": "10s", "content_type": "0", "script": "", "timeout": "30s", "process_tags": "0", "show_event_menu": "1", "event_menu_url": "", "event_menu_name": "", "description": "", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "Problem: {EVENT.NAME}", "message": "Problem started at {EVENT.TIME} on {EVENT.DATE}\r\nProblem name: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\nSeverity: {EVENT.SEVERITY}\r\nOperational data: {EVENT.OPDATA}\r\nOriginal problem ID: {EVENT.ID}\r\n{TRIGGER.URL}" }, { "eventsource": "0", "recovery": "1", "subject": "Resolved: {EVENT.NAME}", "message": "Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}\r\nProblem name: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\nSeverity: {EVENT.SEVERITY}\r\n\r\nOriginal problem ID: {EVENT.ID}\r\n{TRIGGER.URL}" }, { "eventsource": "0", "recovery": "2", "subject": "Updated problem: {EVENT.NAME}", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}.\r\n{EVENT.UPDATE.MESSAGE}\r\n\r\nCurrent problem status is {EVENT.STATUS}, acknowledged: {EVENT.ACK.STATUS}." }, { "eventsource": "1", "recovery": "0", "subject": "Discovery: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}", "message": "Discovery rule: {DISCOVERY.RULE.NAME}\r\n\r\nDevice IP: {DISCOVERY.DEVICE.IPADDRESS}\r\nDevice DNS: {DISCOVERY.DEVICE.DNS}\r\nDevice status: {DISCOVERY.DEVICE.STATUS}\r\nDevice uptime: {DISCOVERY.DEVICE.UPTIME}\r\n\r\nDevice service name: {DISCOVERY.SERVICE.NAME}\r\nDevice service port: {DISCOVERY.SERVICE.PORT}\r\nDevice service status: {DISCOVERY.SERVICE.STATUS}\r\nDevice service uptime: {DISCOVERY.SERVICE.UPTIME}" }, { "eventsource": "2", "recovery": "0", "subject": "Autoregistration: {HOST.HOST}", "message": "Host name: {HOST.HOST}\r\nHost IP: {HOST.IP}\r\nAgent port: {HOST.PORT}" } ], "parameters": [] }, { "mediatypeid": "3", "type": "2", "name": "SMS", "smtp_server": "", "smtp_helo": "", "smtp_email": "", "exec_path": "", "gsm_modem": "/dev/ttyS0", "username": "", "passwd": "", "status": "0", "smtp_port": "25", "smtp_security": "0", "smtp_verify_peer": "0", "smtp_verify_host": "0", "smtp_authentication": "0", "exec_params": "", "maxsessions": "1", "maxattempts": "3", "attempt_interval": "10s", "content_type": "1", "script": "", "timeout": "30s", "process_tags": "0", "show_event_menu": "1", "event_menu_url": "", "event_menu_name": "", "description": "", "message_templates": [ { "eventsource": "0", "recovery": "0", "subject": "", "message": "{EVENT.SEVERITY}: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\n{EVENT.DATE} {EVENT.TIME}" }, { "eventsource": "0", "recovery": "1", "subject": "", "message": "RESOLVED: {EVENT.NAME}\r\nHost: {HOST.NAME}\r\n{EVENT.DATE} {EVENT.TIME}" }, { "eventsource": "0", "recovery": "2", "subject": "", "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}" }, { "eventsource": "1", "recovery": "0", "subject": "", "message": "Discovery: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}" }, { "eventsource": "2", "recovery": "0", "subject": "", "message": "Autoregistration: {HOST.HOST}\r\nHost IP: {HOST.IP}\r\nAgent port: {HOST.PORT}" } ], "parameters": [] } ], "id": 1 } ``` #### Retrieving report data Request: ```json { "jsonrpc": "2.0", "method": "report.get", "params": [ "output": "extend", "selectUsers": "extend", "selectUserGroups": "extend", "reportids": ["1", "2"] ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "reportid": "1", "userid": "1", "name": "Weekly report", "dashboardid": "1", "period": "1", "cycle": "1", "start_time": "43200", "weekdays": "31", "active_since": "2021-04-01", "active_till": "2021-08-31", "subject": "Weekly report", "message": "Report accompanying text", "status": "1", "description": "Report description", "state": "1", "lastsent": "1613563219", "info": "", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" }, { "userid": "2", "access_userid": "0", "exclude": "1" } ], "user_groups": [ { "usrgrpid": "7", "access_userid": "0" } ] }, { "reportid": "2", "userid": "1", "name": "Monthly report", "dashboardid": "2", "period": "2", "cycle": "2", "start_time": "0", "weekdays": "0", "active_since": "2021-05-01", "active_till": "", "subject": "Monthly report", "message": "Report accompanying text", "status": "1", "description": "", "state": "0", "lastsent": "0", "info": "", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" } ], "user_groups": [] } ], "id": 1 } ``` #### Récupération des données du rapport Requête : ```json { "jsonrpc": "2.0", "method": "report.get", "params": [ "output": "extend", "selectUsers": "extend", "selectUserGroups": "extend", "reportids": ["1", "2"] ], "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "reportid": "1", "userid": "1", "name": "Weekly report", "dashboardid": "1", "period": "1", "cycle": "1", "start_time": "43200", "weekdays": "31", "active_since": "2021-04-01", "active_till": "2021-08-31", "subject": "Weekly report", "message": "Report accompanying text", "status": "1", "description": "Report description", "state": "1", "lastsent": "1613563219", "info": "", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" }, { "userid": "2", "access_userid": "0", "exclude": "1" } ], "user_groups": [ { "usrgrpid": "7", "access_userid": "0" } ] }, { "reportid": "2", "userid": "1", "name": "Monthly report", "dashboardid": "2", "period": "2", "cycle": "2", "start_time": "0", "weekdays": "0", "active_since": "2021-05-01", "active_till": "", "subject": "Monthly report", "message": "Report accompanying text", "status": "1", "description": "", "state": "0", "lastsent": "0", "info": "", "users": [ { "userid": "1", "access_userid": "1", "exclude": "0" } ], "user_groups": [] } ], "id": 1 } ``` #### Retrieving role data Retrieve "Super admin role" role data and its access rules. Request: ```json { "jsonrpc": "2.0", "method": "role.get", "params": { "output": "extend", "selectRules": "extend", "roleids": "3" }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "roleid": "3", "name": "Super admin role", "type": "3", "readonly": "1", "rules": { "ui": [ { "name": "inventory.hosts", "status": "1" }, { "name": "inventory.overview", "status": "1" }, { "name": "monitoring.dashboard", "status": "1" }, { "name": "monitoring.hosts", "status": "1" }, { "name": "monitoring.latest_data", "status": "1" }, { "name": "monitoring.maps", "status": "1" }, { "name": "monitoring.problems", "status": "1" }, { "name": "reports.availability_report", "status": "1" }, { "name": "reports.top_triggers", "status": "1" }, { "name": "services.services", "status": "1" }, { "name": "services.sla_report", "status": "1" }, { "name": "configuration.actions", "status": "1" }, { "name": "configuration.discovery", "status": "1" }, { "name": "configuration.host_groups", "status": "1" }, { "name": "configuration.hosts", "status": "1" }, { "name": "configuration.maintenance", "status": "1" }, { "name": "configuration.templates", "status": "1" }, { "name": "monitoring.discovery", "status": "1" }, { "name": "reports.notifications", "status": "1" }, { "name": "reports.scheduled_reports", "status": "1" }, { "name": "services.actions", "status": "1" }, { "name": "services.sla", "status": "1" }, { "name": "administration.authentication", "status": "1" }, { "name": "administration.general", "status": "1" }, { "name": "administration.media_types", "status": "1" }, { "name": "administration.proxies", "status": "1" }, { "name": "administration.queue", "status": "1" }, { "name": "administration.scripts", "status": "1" }, { "name": "administration.user_groups", "status": "1" }, { "name": "administration.user_roles", "status": "1" }, { "name": "administration.users", "status": "1" }, { "name": "configuration.event_correlation", "status": "1" }, { "name": "reports.action_log", "status": "1" }, { "name": "reports.audit", "status": "1" }, { "name": "reports.system_info", "status": "1" } ], "ui.default_access": "1", "services.read.mode": "1", "services.read.list": [], "services.read.tag": { "tag": "", "value": "" }, "services.write.mode": "1", "services.write.list": [], "services.write.tag": { "tag": "", "value": "" }, "modules": [], "modules.default_access": "1", "api.access": "1", "api.mode": "0", "api": [], "actions": [ { "name": "edit_dashboards", "status": "1" }, { "name": "edit_maps", "status": "1" }, { "name": "acknowledge_problems", "status": "1" }, { "name": "close_problems", "status": "1" }, { "name": "change_severity", "status": "1" }, { "name": "add_problem_comments", "status": "1" }, { "name": "execute_scripts", "status": "1" }, { "name": "manage_api_tokens", "status": "1" }, { "name": "edit_maintenance", "status": "1" }, { "name": "manage_scheduled_reports", "status": "1" }, { "name": "manage_sla", "status": "1" } ], "actions.default_access": "1" } } ], "id": 1 } ``` #### Récupération des données de rôle Récupérer les données du rôle "Super admin" et ses règles d'accès. Requête : ```json { "jsonrpc": "2.0", "method": "role.get", "params": { "output": "extend", "selectRules": "extend", "roleids": "3" }, "auth": "3a57200802b24cda67c4e4010b50c065", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "roleid": "3", "name": "Super admin role", "type": "3", "readonly": "1", "rules": { "ui": [ { "name": "inventory.hosts", "status": "1" }, { "name": "inventory.overview", "status": "1" }, { "name": "monitoring.dashboard", "status": "1" }, { "name": "monitoring.hosts", "status": "1" }, { "name": "monitoring.latest_data", "status": "1" }, { "name": "monitoring.maps", "status": "1" }, { "name": "monitoring.problems", "status": "1" }, { "name": "reports.availability_report", "status": "1" }, { "name": "reports.top_triggers", "status": "1" }, { "name": "services.services", "status": "1" }, { "name": "services.sla_report", "status": "1" }, { "name": "configuration.actions", "status": "1" }, { "name": "configuration.discovery", "status": "1" }, { "name": "configuration.host_groups", "status": "1" }, { "name": "configuration.hosts", "status": "1" }, { "name": "configuration.maintenance", "status": "1" }, { "name": "configuration.templates", "status": "1" }, { "name": "monitoring.discovery", "status": "1" }, { "name": "reports.notifications", "status": "1" }, { "name": "reports.scheduled_reports", "status": "1" }, { "name": "services.actions", "status": "1" }, { "name": "services.sla", "status": "1" }, { "name": "administration.authentication", "status": "1" }, { "name": "administration.general", "status": "1" }, { "name": "administration.media_types", "status": "1" }, { "name": "administration.proxies", "status": "1" }, { "name": "administration.queue", "status": "1" }, { "name": "administration.scripts", "status": "1" }, { "name": "administration.user_groups", "status": "1" }, { "name": "administration.user_roles", "status": "1" }, { "name": "administration.users", "status": "1" }, { "name": "configuration.event_correlation", "status": "1" }, { "name": "reports.action_log", "status": "1" }, { "name": "reports.audit", "status": "1" }, { "name": "reports.system_info", "status": "1" } ], "ui.default_access": "1", "services.read.mode": "1", "services.read.list": [], "services.read.tag": { "tag": "", "value": "" }, "services.write.mode": "1", "services.write.list": [], "services.write.tag": { "tag": "", "value": "" }, "modules": [], "modules.default_access": "1", "api.access": "1", "api.mode": "0", "api": [], "actions": [ { "name": "edit_dashboards", "status": "1" }, { "name": "edit_maps", "status": "1" }, { "name": "acknowledge_problems", "status": "1" }, { "name": "close_problems", "status": "1" }, { "name": "change_severity", "status": "1" }, { "name": "add_problem_comments", "status": "1" }, { "name": "execute_scripts", "status": "1" }, { "name": "manage_api_tokens", "status": "1" }, { "name": "edit_maintenance", "status": "1" }, { "name": "manage_scheduled_reports", "status": "1" }, { "name": "manage_sla", "status": "1" } ], "actions.default_access": "1" } } ], "id": 1 } ``` #### Retrieving template dashboards Retrieve all template dashboards with widgets for a specified template. Request: ```json { "jsonrpc": "2.0", "method": "templatedashboard.get", "params": { "output": "extend", "selectPages": "extend", "templateids": "10001" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "dashboardid": "23", "name": "Docker overview", "templateid": "10001", "display_period": "30", "auto_start": "1", "uuid": "6dfcbe0bc5ad400ea9c1c2dd7649282f", "pages": [ { "dashboard_pageid": "1", "name": "", "display_period": "0", "widgets": [ { "widgetid": "220", "type": "graph", "name": "", "x": "0", "y": "0", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1125" } ] }, { "widgetid": "221", "type": "graph", "name": "", "x": "12", "y": "0", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1129" } ] }, { "widgetid": "222", "type": "graph", "name": "", "x": "0", "y": "5", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1128" } ] }, { "widgetid": "223", "type": "graph", "name": "", "x": "12", "y": "5", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1126" } ] }, { "widgetid": "224", "type": "graph", "name": "", "x": "0", "y": "10", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1127" } ] } ] } ] } ], "id": 1 } ``` #### Récupération des modèles de tableaux de bord Récupérez tous les modèles de tableaux de bord avec des widgets pour un modèle spécifié. Requête : ```json { "jsonrpc": "2.0", "method": "templatedashboard.get", "params": { "output": "extend", "selectPages": "extend", "templateids": "10001" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "dashboardid": "23", "name": "Docker overview", "templateid": "10001", "display_period": "30", "auto_start": "1", "uuid": "6dfcbe0bc5ad400ea9c1c2dd7649282f", "pages": [ { "dashboard_pageid": "1", "name": "", "display_period": "0", "widgets": [ { "widgetid": "220", "type": "graph", "name": "", "x": "0", "y": "0", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1125" } ] }, { "widgetid": "221", "type": "graph", "name": "", "x": "12", "y": "0", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1129" } ] }, { "widgetid": "222", "type": "graph", "name": "", "x": "0", "y": "5", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1128" } ] }, { "widgetid": "223", "type": "graph", "name": "", "x": "12", "y": "5", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1126" } ] }, { "widgetid": "224", "type": "graph", "name": "", "x": "0", "y": "10", "width": "12", "height": "5", "view_mode": "0", "fields": [ { "type": "6", "name": "graphid", "value": "1127" } ] } ] } ] } ], "id": 1 } ``` #### Retrieving templates by name Retrieve all data about two templates named "Linux" and "Windows". Request: ```json { "jsonrpc": "2.0", "method": "template.get", "params": { "output": "extend", "filter": { "host": [ "Linux", "Windows" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "proxy_hostid": "0", "host": "Linux", "status": "3", "disable_until": "0", "error": "", "available": "0", "errors_from": "0", "lastaccess": "0", "ipmi_authtype": "0", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "ipmi_disable_until": "0", "ipmi_available": "0", "snmp_disable_until": "0", "snmp_available": "0", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "ipmi_errors_from": "0", "snmp_errors_from": "0", "ipmi_error": "", "snmp_error": "", "jmx_disable_until": "0", "jmx_available": "0", "jmx_errors_from": "0", "jmx_error": "", "name": "Linux", "flags": "0", "templateid": "10001", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "tls_psk_identity": "", "tls_psk": "", "uuid": "282ffe33afc74cccaf1524d9aa9dc502" }, { "proxy_hostid": "0", "host": "Windows", "status": "3", "disable_until": "0", "error": "", "available": "0", "errors_from": "0", "lastaccess": "0", "ipmi_authtype": "0", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "ipmi_disable_until": "0", "ipmi_available": "0", "snmp_disable_until": "0", "snmp_available": "0", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "ipmi_errors_from": "0", "snmp_errors_from": "0", "ipmi_error": "", "snmp_error": "", "jmx_disable_until": "0", "jmx_available": "0", "jmx_errors_from": "0", "jmx_error": "", "name": "Windows", "flags": "0", "templateid": "10081", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "tls_psk_identity": "", "tls_psk": "", "uuid": "522d17e1834049be879287b7c0518e5d" } ], "id": 1 } ``` #### Récupération des modèles par nom Récupérez toutes les données sur deux modèles nommés "Linux" et "Windows". Requête : ```json { "jsonrpc": "2.0", "method": "template.get", "params": { "output": "extend", "filter": { "host": [ "Linux", "Windows" ] } }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "proxy_hostid": "0", "host": "Linux", "status": "3", "disable_until": "0", "error": "", "available": "0", "errors_from": "0", "lastaccess": "0", "ipmi_authtype": "0", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "ipmi_disable_until": "0", "ipmi_available": "0", "snmp_disable_until": "0", "snmp_available": "0", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "ipmi_errors_from": "0", "snmp_errors_from": "0", "ipmi_error": "", "snmp_error": "", "jmx_disable_until": "0", "jmx_available": "0", "jmx_errors_from": "0", "jmx_error": "", "name": "Linux", "flags": "0", "templateid": "10001", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "tls_psk_identity": "", "tls_psk": "", "uuid": "282ffe33afc74cccaf1524d9aa9dc502" }, { "proxy_hostid": "0", "host": "Windows", "status": "3", "disable_until": "0", "error": "", "available": "0", "errors_from": "0", "lastaccess": "0", "ipmi_authtype": "0", "ipmi_privilege": "2", "ipmi_username": "", "ipmi_password": "", "ipmi_disable_until": "0", "ipmi_available": "0", "snmp_disable_until": "0", "snmp_available": "0", "maintenanceid": "0", "maintenance_status": "0", "maintenance_type": "0", "maintenance_from": "0", "ipmi_errors_from": "0", "snmp_errors_from": "0", "ipmi_error": "", "snmp_error": "", "jmx_disable_until": "0", "jmx_available": "0", "jmx_errors_from": "0", "jmx_error": "", "name": "Windows", "flags": "0", "templateid": "10081", "description": "", "tls_connect": "1", "tls_accept": "1", "tls_issuer": "", "tls_subject": "", "tls_psk_identity": "", "tls_psk": "", "uuid": "522d17e1834049be879287b7c0518e5d" } ], "id": 1 } ``` #### Retrieving the version of the API Retrieve the version of the Zabbix API. Request: ``` {.java} { "jsonrpc": "2.0", "method": "apiinfo.version", "params": [], "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": "4.0.0", "id": 1 } ``` #### Récupération de la version de l'API Récupère la version de l'API Zabbix. Requête : ``` {.java} { · "jsonrpc": "2.0", · "method": "apiinfo.version", · "params": [], · "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": "4.0.0", "id": 1 } ``` #### Retrieving triggers in problem state Retrieve the ID, name and severity of all triggers in problem state and sort them by severity in descending order. Request: ```json { "jsonrpc": "2.0", "method": "trigger.get", "params": { "output": [ "triggerid", "description", "priority" ], "filter": { "value": 1 }, "sortfield": "priority", "sortorder": "DESC" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "13907", "description": "Zabbix self-monitoring processes < 100% busy", "priority": "4" }, { "triggerid": "13824", "description": "Zabbix discoverer processes more than 75% busy", "priority": "3" } ], "id": 1 } ``` #### Récupération des déclencheurs en état problématique Récupérer l'ID, le nom et la sévérité de tous les déclencheurs en état problématique et les trier par sévérité en ordre décroissant. Requête : ```json { "jsonrpc": "2.0", "method": "trigger.get", "params": { "output": [ "triggerid", "description", "priority" ], "filter": { "value": 1 }, "sortfield": "priority", "sortorder": "DESC" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "triggerid": "13907", "description": "Zabbix self-monitoring processes < 100% busy", "priority": "4" }, { "triggerid": "13824", "description": "Zabbix discoverer processes more than 75% busy", "priority": "3" } ], "id": 1 } ``` #### Retrieving user data Retrieve data of a user with ID "12". Request: ``` {.java} { "jsonrpc": "2.0", "method": "user.get", "params": { "output": ["userid", "username"], "selectRole": "extend", "userids": "12" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "userid": "12", "username": "John", "role": { "roleid": "5", "name": "Operator", "type": "1", "readonly": "0" } } ], "id": 1 } ``` #### Récupération des données utilisateur Récupérer les données d'un utilisateur avec l'ID "12". Requête : ``` {.java} { "jsonrpc": "2.0", "method": "user.get", "params": { "output": ["userid", "username"], "selectRole": "extend", "userids": "12" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "userid": "12", "username": "John", "role": { "roleid": "5", "name": "Operator", "type": "1", "readonly": "0" } } ], "id": 1 } ``` #### Retrieving value maps Retrieve all configured value maps. Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.get", "params": { "output": "extend" }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "valuemapid": "4", "name": "APC Battery Replacement Status" }, { "valuemapid": "5", "name": "APC Battery Status" }, { "valuemapid": "7", "name": "Dell Open Manage System Status" } ], "id": 1 } ``` Retrieve one value map with its mappings. Request: ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.get", "params": { "output": "extend", "selectMappings": "extend", "valuemapids": ["4"] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Response: ``` {.java} { "jsonrpc": "2.0", "result": [ { "valuemapid": "4", "name": "APC Battery Replacement Status", "mappings": [ { "type": "0", "value": "1", "newvalue": "unknown" }, { "type": "0", "value": "2", "newvalue": "notInstalled" }, { "type": "0", "value": "3", "newvalue": "ok" }, { "type": "0", "value": "4", "newvalue": "failed" }, { "type": "0", "value": "5", "newvalue": "highTemperature" }, { "type": "0", "value": "6", "newvalue": "replaceImmediately" }, { "type": "0", "value": "7", "newvalue": "lowCapacity" } ] } ], "id": 1 } ``` #### Récupération des cartes de valeurs Récupérez toutes les cartes de valeurs configurées. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.get", "params": { "output": "extend" }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "valuemapid": "4", "name": "APC Battery Replacement Status" }, { "valuemapid": "5", "name": "APC Battery Status" }, { "valuemapid": "7", "name": "Dell Open Manage System Status" } ], "id": 1 } ``` Récupérez une carte de valeurs avec ses correspondances. Requête : ``` {.java} { "jsonrpc": "2.0", "method": "valuemap.get", "params": { "output": "extend", "selectMappings": "extend", "valuemapids": ["4"] }, "auth": "57562fd409b3b3b9a4d916d45207bbcb", "id": 1 } ``` Réponse : ``` {.java} { "jsonrpc": "2.0", "result": [ { "valuemapid": "4", "name": "APC Battery Replacement Status", "mappings": [ { "type": "0", "value": "1", "newvalue": "unknown" }, { "type": "0", "value": "2", "newvalue": "notInstalled" }, { "type": "0", "value": "3", "newvalue": "ok" }, { "type": "0", "value": "4", "newvalue": "failed" }, { "type": "0", "value": "5", "newvalue": "highTemperature" }, { "type": "0", "value": "6", "newvalue": "replaceImmediately" }, { "type": "0", "value": "7", "newvalue": "lowCapacity" } ] } ], "id": 1 } ``` ### Return values `(array)` Returns an array of objects containing the ID of the generated token under the `tokenid` property and generated authorization string under `token` property. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tokenid|string|ID of the token.| |token|string|The generated authorization string for this token.| ### Valeurs retournées `(array)` Renvoie un tableau d'objets contenant l'ID du jeton généré sous la propriété `tokenid` et la chaîne d'autorisation générée sous la propriété `token`. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tokenid|string|ID du jeton.| |token|string|La chaîne d'autorisation générée pour ce jeton.| ### Return values `(array)` Returns an array with changes in configuration, that will be made. ### Valeurs retournées `(array)` Renvoie un tableau avec les changements de configuration qui seront effectués. ### Return values `(array)` Returns array with the names of updated parameters. ### Valeurs retournées `(array)` Retourne un tableau des noms des paramètres mis à jour. ### Return values `(array)` Returns array with the names of updated parameters. ### Valeurs retournées `(array)` Retourne un tableau des noms des paramètres mis à jour. ### Return values `(array)` Returns array with the names of updated parameters. ### Valeurs retournées `(array)` Retourne un tableau des noms des paramètres mis à jour. ### Return values `(boolean )` Returns boolean true as result on successful update. ### Valeurs retournées `(boolean )` Renvoie un booléen positionné à VRAI comme résultat si la mise à jour est réussie. ### Return values `(boolean)` Returns `true` if importing has been successful. ### Valeurs retournées `(boolean)` Retourne `true` si l'import est réussi. ### Return values `(boolean)` Returns `true` if the copying was successful. ### Valeurs retournées `(boolean)` Retourne `true` si la copie a réussi. ### Return values `(boolean)` Returns `true` if the user has been logged out successfully. ### Valeurs retournées `(boolean)` Retourne `true` si l'utilisateur a été déconnecté avec succès. ### Return values `(integer/array)` Returns an array of objects. ### Valeurs retournées `(integer/array)` Retourne un tableau d'objets. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit: - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit: - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(entier/tableau)` Renvoie soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Renvoie soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Renvoie soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(entier/tableau)` Renvoie soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(integer/array)` Returns either: - an array of objects; - the count of retrieved objects, if the `countOutput` parameter has been used. ### Valeurs retournées `(integer/array)` Retourne soit : - un tableau d'objets ; - le nombre d'objets récupérés, si le paramètre `countOutput` a été utilisé. ### Return values `(object)` Returns an object containing information about user. ### Valeurs retournées `(object)` Renvoie un objet contenant des informations sur l'utilisateur. ### Return values `(object)` Returns an object containing the IDs of the affected triggers under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs affectés sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des éléments effacés sous la propriété `itemids`. ### Return values `(object)` Returns an object containing the IDs of the created actions under the `actionids` property. The order of the returned IDs matches the order of the passed actions. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des actions créées sous la propriété `actionids`. L'ordre des ID retournés correspond à l'ordre des actions transmises. ### Return values `(object)` Returns an object containing the IDs of the created correlations under the `correlationids` property. The order of the returned IDs matches the order of the passed correlations. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des corrélations créées sous la propriété `correlationids`. L'ordre des ID renvoyés correspond à l'ordre des corrélations transmises. ### Return values `(object)` Returns an object containing the IDs of the created dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed dashboards. ### Valeurs retournées `(object)` Retourne un objet contenant les ID des tableaux de bord créés dans la propriété `dashboardids`. L'ordre des ID retournés correspond à l'ordre des tableaux de bord transmis. ### Return values `(object)` Returns an object containing the IDs of the created discovery rules under the `druleids` property. The order of the returned IDs matches the order of the passed discovery rules. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des règles de découverte créées sous la propriété `druleids`. L'ordre des ID retournés correspond à l'ordre des règles de découverte passées. ### Return values `(object)` Returns an object containing the IDs of the created global macros under the `globalmacroids` property. The order of the returned IDs matches the order of the passed global macros. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des macros globales créées sous la propriété `globalmacroids`. L'ordre des ID retournés correspond à l'ordre des macros globales transmises. ### Return values `(object)` Returns an object containing the IDs of the created graph prototypes under the `graphids` property. The order of the returned IDs matches the order of the passed graph prototypes. ### Valeurs retournées `(object)` Renvoie un objet contenant les IDs des prototypes de graphe créés sous la propriété `graphids`. L'ordre des ID renvoyés correspond à l'ordre des prototypes de graphe transmis. ### Return values `(object)` Returns an object containing the IDs of the created graphs under the `graphids` property. The order of the returned IDs matches the order of the passed graphs. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des graphiques créés sous la propriété `graphids`. L'ordre des ID retournés correspond à l'ordre des graphiques transmis. ### Return values `(object)` Returns an object containing the IDs of the created host groups under the `groupids` property. The order of the returned IDs matches the order of the passed host groups. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes créés sous la propriété `groupids`. L'ordre des identifiants retournés correspond à l'ordre des groupes d'hôtes transmis. ### Return values `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes créées sous la propriété `interfaceids`. ### Return values `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes créées sous la propriété `interfaceids`. ### Return values `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. The order of the returned IDs matches the order of the passed host interfaces. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes créées sous la propriété `interfaceids`. L'ordre des ID retournés correspond à l'ordre des interfaces hôtes transmises. ### Return values `(object)` Returns an object containing the IDs of the created host macros under the `hostmacroids` property. The order of the returned IDs matches the order of the passed host macros. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des macros hôtes créées sous la propriété `hostmacroids`. L'ordre des ID renvoyés correspond à l'ordre des macros hôtes transmises. ### Return values `(object)` Returns an object containing the IDs of the created host prototypes under the `hostids` property. The order of the returned IDs matches the order of the passed host prototypes. ### Valeurs retournées `(object)` Renvoie un objet contenant les IDs des prototypes d'hôtes créés sous la propriété `hostids`. L'ordre des ID renvoyés correspond à l'ordre des prototypes d'hôtes transmis. ### Return values `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes créés sous la propriété `hostids`. L'ordre des ID retournés correspond à l'ordre des hôtes transmis. ### Return values `(object)` Returns an object containing the IDs of the created icon maps under the `iconmapids` property. The order of the returned IDs matches the order of the passed icon maps. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des tables de correspondance d'icônes créées sous la propriété `iconmapids`. L'ordre des ID renvoyés correspond à l'ordre des tables de correspondance d'icônes transmises. ### Return values `(object)` Returns an object containing the IDs of the created images under the `imageids` property. The order of the returned IDs matches the order of the passed images. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des images créées sous la propriété `imageids`. L'ordre des ID retournés correspond à l'ordre des images transmises. ### Return values `(object)` Returns an object containing the IDs of the created item prototypes under the `itemids` property. The order of the returned IDs matches the order of the passed item prototypes. ### Valeurs retournées `(object)` Renvoie un objet contenant les IDs des prototypes d'éléments créés sous la propriété `itemids`. L'ordre des ID renvoyés correspond à l'ordre des prototypes d'éléments transmis. ### Return values `(object)` Returns an object containing the IDs of the created items under the `itemids` property. The order of the returned IDs matches the order of the passed items. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des éléments créés sous la propriété `itemids`. L'ordre des ID retournés correspond à l'ordre des éléments transmis. ### Return values `(object)` Returns an object containing the IDs of the created LLD rules under the `itemids` property. The order of the returned IDs matches the order of the passed LLD rules. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des règles de découverte bas niveau créées sous la propriété `itemids`. L'ordre des ID retournés correspond à l'ordre des règles de découverte bas niveau transmises. ### Return values `(object)` Returns an object containing the IDs of the created maintenances under the `maintenanceids` property. The order of the returned IDs matches the order of the passed maintenances. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des maintenance créées sous la propriété `maintenanceids`. L'ordre des ID retournés correspond à l'ordre des maintenances transmises. ### Return values `(object)` Returns an object containing the IDs of the created maps under the `sysmapids` property. The order of the returned IDs matches the order of the passed maps. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des cartes créées sous la propriété `sysmapids`. L'ordre des ID retournés correspond à l'ordre des cartes transmises. ### Return values `(object)` Returns an object containing the IDs of the created media types under the `mediatypeids` property. The order of the returned IDs matches the order of the passed media types. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des types de média créées sous la propriété `mediatypeids`. L'ordre des ID retournés correspond à l'ordre des types de média transmis. ### Return values `(object)` Returns an object containing the IDs of the created proxies under the `proxyids` property. The order of the returned IDs matches the order of the passed proxies. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs créés sous la propriété `proxyids`. L'ordre des ID retournés correspond à l'ordre des proxys transmis. ### Return values `(object)` Returns an object containing the IDs of the created regular expressions under the `regexpids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des expressions régulières créées sous la propriété `regexpids`. ### Return values `(object)` Returns an object containing the IDs of the created roles under the `roleids` property. The order of the returned IDs matches the order of the passed roles. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des rôles créés sous la propriété `roleids`. L'ordre des ID retournés correspond à l'ordre des rôles transmis. ### Return values `(object)` Returns an object containing the IDs of the created scheduled reports under the `reportids` property. The order of the returned IDs matches the order of the passed scheduled reports. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des rapports planifiés créés sous la propriété `reportids`. L'ordre des ID renvoyés correspond à l'ordre des rapports planifiés transmis. ### Return values `(object)` Returns an object containing the IDs of the created scripts under the `scriptids` property. The order of the returned IDs matches the order of the passed scripts. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scripts créés sous la propriété `scriptids`. L'ordre des ID retournés correspond à l'ordre des scripts transmis. ### Return values `(object)` Returns an object containing the IDs of the created services under the `serviceids` property. The order of the returned IDs matches the order of the passed services. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des services créés sous la propriété `servicesids`. L'ordre des ID retournés correspond à l'ordre des services transmis. ### Return values `(object)` Returns an object containing the IDs of the created SLAs under the `slaids` property. The order of the returned IDs matches the order of the passed SLAs. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des SLAs sous la propriété `slaids`. L'ordre des ID retournés correspond à l'ordre des SLA transmis. ### Return values `(object)` Returns an object containing the IDs of the created tasks under the `taskids` property. One task is created for each item and low-level discovery rule. The order of the returned IDs matches the order of the passed `itemids`. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des tâches créés sous la propriété `taskids`. L'ordre des ID retournés correspond à l'ordre des tâches transmises. ### Return values `(object)` Returns an object containing the IDs of the created template dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed template dashboards. ### Valeurs retournées `(object)` Retourne un objet contenant les ID des modèles de tableaux de bord créés dans la propriété `dashboardids`. L'ordre des ID retournés correspond à l'ordre des modèles de tableaux de bord transmis. ### Return values `(object)` Returns an object containing the IDs of the created templates under the `templateids` property. The order of the returned IDs matches the order of the passed templates. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles créés sous la propriété `templateids`. L'ordre des ID retournés correspond à l'ordre des modèles transmis. ### Return values `(object)` Returns an object containing the IDs of the created tokens under the `tokenids` property. The order of the returned IDs matches the order of the passed tokens. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des jetons créés sous la propriété `tokenids`. L'ordre des ID renvoyés correspond à l'ordre des jetons passés. ### Return values `(object)` Returns an object containing the IDs of the created trigger prototypes under the `triggerids` property. The order of the returned IDs matches the order of the passed trigger prototypes. ### Valeurs retournées `(object)` Renvoie un objet contenant les IDs des prototypes de déclencheurs créés sous la propriété `itemids`. L'ordre des ID renvoyés correspond à l'ordre des prototypes de déclencheurs transmis. ### Return values `(object)` Returns an object containing the IDs of the created triggers under the `triggerids` property. The order of the returned IDs matches the order of the passed triggers. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs créés sous la propriété `triggerids`. L'ordre des ID retournés correspond à l'ordre des déclencheurs transmis. ### Return values `(object)` Returns an object containing the IDs of the created user groups under the `usrgrpids` property. The order of the returned IDs matches the order of the passed user groups. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des groupes d'utilisateurs créés sous la propriété `usrgrpids`. L'ordre des ID renvoyés correspond à l'ordre des groupes d'utilisateurs passés. ### Return values `(object)` Returns an object containing the IDs of the created users under the `userids` property. The order of the returned IDs matches the order of the passed users. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des utilisateurs créés sous la propriété `userids`. L'ordre des ID renvoyés correspond à l'ordre des utilisateurs passés. ### Return values `(object)` Returns an object containing the IDs of the created value maps the `valuemapids` property. The order of the returned IDs matches the order of the passed value maps. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des tables de correspondance créées dans la propriété `valuemapids`. L'ordre des ID retournés correspond à l'ordre des tables de correspondance transmises. ### Return values `(object)` Returns an object containing the IDs of the created web scenarios under the `httptestids` property. The order of the returned IDs matches the order of the passed web scenarios. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scénarios Web créés sous la propriété `httptestids`. L'ordre des ID retournés correspond à l'ordre des scénarios Web transmis. ### Return values `(object)` Returns an object containing the IDs of the deleted actions under the `actionids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des actions supprimées sous la propriété `actionids`. ### Return values `(object)` Returns an object containing the IDs of the deleted correlations under the `correlationids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des corrélations supprimées dans la variable `correlationids`. ### Return values `(object)` Returns an object containing the IDs of the deleted dashboards under the `dashboardids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les ID des tableaux de bord supprimés dans la propriété `dashboardids`. ### Return values `(object)` Returns an object containing the IDs of the deleted discovery rules under the `druleids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des règles de découverte supprimées sous la propriété `druleids`. ### Return values `(object)` Returns an object containing the IDs of the deleted global macros under the `globalmacroids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des macros globales supprimées sous la propriété `globalmacroids`. ### Return values `(object)` Returns an object containing the IDs of the deleted graph prototypes under the `graphids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes de graphique supprimés sous la propriété `graphids`. ### Return values `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des graphiques supprimés sous la propriété `graphids`. ### Return values `(object)` Returns an object containing the IDs of the deleted host groups under the `groupids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes supprimés sous la propriété `groupids`. ### Return values `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes supprimées sous la propriété `interfaceids`. ### Return values `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes supprimées sous la propriété `interfaceids`. ### Return values `(object)` Returns an object containing the IDs of the deleted host macros under the `hostmacroids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des macros d'hôtes supprimées sous la propriété `hostmacroids`. ### Return values `(object)` Returns an object containing the IDs of the deleted host prototypes under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes hôte supprimés sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the deleted hosts under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes supprimés sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the deleted icon maps under the `iconmapids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des correspondances d'icônes supprimées sous la propriété `iconmapids`. ### Return values `(object)` Returns an object containing the IDs of the deleted images under the `imageids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des images supprimées sous la propriété `imageids`. ### Return values `(object)` Returns an object containing the IDs of the deleted item prototypes under the `prototypeids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des prototypes d'éléments supprimés sous la propriété `prototypeids`. ### Return values `(object)` Returns an object containing the IDs of the deleted items under the `itemids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des éléments supprimés sous la propriété `itemids`. ### Return values `(object)` Returns an object containing the IDs of the deleted maintenance periods under the `maintenanceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des maintenances supprimées sous la propriété `maintenanceids`. ### Return values `(object)` Returns an object containing the IDs of the deleted maps under the `sysmapids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des cartes supprimées sous la propriété `sysmapids`. ### Return values `(object)` Returns an object containing the IDs of the deleted media types under the `mediatypeids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des types de média supprimés sous la propriété `mediatypeids`. ### Return values `(object)` Returns an object containing the IDs of the deleted proxies under the `proxyids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des proxys supprimés sous la propriété `proxyids`. ### Return values `(object)` Returns an object containing the IDs of the deleted regular expressions under the `regexpids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des expressions régulières supprimées sous la propriété `regexpids`. ### Return values `(object)` Returns an object containing the IDs of the deleted roles under the `roleids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des rôles supprimés sous la propriété `roleids`. ### Return values `(object)` Returns an object containing the IDs of the deleted scheduled reports under the `reportids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des rapports planifiés supprimés sous la propriété `reportids`. ### Return values `(object)` Returns an object containing the IDs of the deleted scripts under the `scriptids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scripts supprimés sous la propriété `scriptids`. ### Return values `(object)` Returns an object containing the IDs of the deleted services under the `serviceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des services supprimés sous la propriété `serviceids`. ### Return values `(object)` Returns an object containing the IDs of the deleted SLAs under the `slaids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des SLA supprimés sous la propriété `slaids`. ### Return values `(object)` Returns an object containing the IDs of the deleted template dashboards under the `dashboardids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les ID des tableaux de bord de modèle supprimés sous la propriété `dashboardids`. ### Return values `(object)` Returns an object containing the IDs of the deleted templates under the `templateids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles supprimés sous la propriété `templateids`. ### Return values `(object)` Returns an object containing the IDs of the deleted trigger prototypes under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes de déclencheur supprimés sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the deleted triggers under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs supprimés sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the deleted user groups under the `usrgrpids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des groupes d'utilisateurs supprimés sous la propriété `usrgrpids`. ### Return values `(object)` Returns an object containing the IDs of the deleted users under the `userids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des utilisateurs supprimés sous la propriété `userids`. ### Return values `(object)` Returns an object containing the IDs of the deleted value maps under the `valuemapids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des tables de correspondance supprimées sous la propriété `valuemapids`. ### Return values `(object)` Returns an object containing the IDs of the deleted web scenarios under the `httptestids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scénarios Web supprimés sous la propriété `httptestids`. ### Return values `(object)` Returns an object containing the IDs of the dependent triggers under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs dépendants sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the unblocked users under the `userids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des utilisateurs débloqués sous la propriété `userids`. ### Return values `(object)` Returns an object containing the IDs of the updated actions under the `actionids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des actions mises à jour sous la propriété `actionids`. ### Return values `(object)` Returns an object containing the IDs of the updated correlations under the `correlationids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des corrélations mises à jour dans la propriété `correlationids`. ### Return values `(object)` Returns an object containing the IDs of the updated dashboards under the `dashboardids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des tableaux de bord mis à jour dans la propriété `dashboardids`. ### Return values `(object)` Returns an object containing the IDs of the updated discovery rules under the `druleids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des règles de découverte mises à jour sous la propriété `druleids`. ### Return values `(object)` Returns an object containing the IDs of the updated events under the `eventids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des événements mis à jour sous la propriété `eventids`. ### Return values `(object)` Returns an object containing the IDs of the updated global macros under the `globalmacroids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des macros globales mises à jour sous la propriété `globalmacroids`. ### Return values `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes de graphique mis à jour sous la propriété `graphids`. ### Return values `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des graphiques mis à jour sous la propriété `graphids`. ### Return values `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes mis à jour sous la propriété `groupids`. ### Return values `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes mis à jour sous la propriété `groupids`. ### Return values `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes mis à jour sous la propriété `groupids`. ### Return values `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les identifiants des groupes d'hôtes mis à jour sous la propriété `groupids`. ### Return values `(object)` Returns an object containing the IDs of the updated host interfaces under the `interfaceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des interfaces hôtes mises à jour sous la propriété `interfaceids`. ### Return values `(object)` Returns an object containing the IDs of the updated host macros under the `hostmacroids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des macros d'hôtes mises à jour sous la propriété `hostmacroids`. ### Return values `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes hôte mis à jour sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes mis à jour sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes mis à jour sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes mis à jour sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des hôtes mis à jour sous la propriété `hostids`. ### Return values `(object)` Returns an object containing the IDs of the updated icon maps under the `iconmapids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des tables de correspondance d'icônes mises à jour sous la propriété `iconmapids`. ### Return values `(object)` Returns an object containing the IDs of the updated images under the `imageids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des images mises à jours sous la propriété `imageids`. ### Return values `(object)` Returns an object containing the IDs of the updated item prototypes under the `itemids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes d'élément mis à jour sous la propriété `itemids`. ### Return values `(object)` Returns an object containing the IDs of the updated items under the `itemids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des éléments mis à jour sous la propriété `itemids`. ### Return values `(object)` Returns an object containing the IDs of the updated LLD rules under the `itemids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des règles mises à jour sous la propriété `itemids`. ### Return values `(object)` Returns an object containing the IDs of the updated maintenances under the `maintenanceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des maintenances mises à jour sous la propriété `maintenanceids`. ### Return values `(object)` Returns an object containing the IDs of the updated maps under the `sysmapids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des cartes mises à jour sous la propriété `sysmapids`. ### Return values `(object)` Returns an object containing the IDs of the updated media types under the `mediatypeids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des types de média mis à jour sous la propriété `mediatypeids`. ### Return values `(object)` Returns an object containing the IDs of the updated proxies under the `proxyids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des proxys mis à jour sous la propriété `proxyids`. ### Return values `(object)` Returns an object containing the IDs of the updated regular expressions under the `regexpids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des expressions régulières mis à jour sous la propriété `regexpids`. ### Return values `(object)` Returns an object containing the IDs of the updated roles under the `roleids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des rôles mis à jour sous la propriété `roleids`. ### Return values `(object)` Returns an object containing the IDs of the updated scheduled reports under the `reportids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des rapports planifiés mis à jour sous la propriété `reportids`. ### Return values `(object)` Returns an object containing the IDs of the updated scripts under the `scriptids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scripts mis à jour sous la propriété `scriptids`. ### Return values `(object)` Returns an object containing the IDs of the updated services under the `serviceids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des services mis à jour sous la propriété `serviceids`. ### Return values `(object)` Returns an object containing the IDs of the updated SLAs under the `slaids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des SLA mis à jour sous la propriété `slaids`. ### Return values `(object)` Returns an object containing the IDs of the updated template dashboards under the `dashboardids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles de tableaux de bord mis à jour dans la propriété `dashboardids`. ### Return values `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles mis à jour sous la propriété `templateids`. ### Return values `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles mis à jour sous la propriété `templateids`. ### Return values `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles mis à jour sous la propriété `templateids`. ### Return values `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des modèles mis à jour sous la propriété `templateids`. ### Return values `(object)` Returns an object containing the IDs of the updated tokens under the `tokenids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des jetons mis à jour sous la propriété `tokenids`. ### Return values `(object)` Returns an object containing the IDs of the updated trigger prototypes under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des prototypes de déclencheur mis à jour sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the updated triggers under the `triggerids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des déclencheurs mis à jour sous la propriété `triggerids`. ### Return values `(object)` Returns an object containing the IDs of the updated user groups under the `usrgrpids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des groupes d'utilisateurs mis à jour sous la propriété `usrgrpids`. ### Return values `(object)` Returns an object containing the IDs of the updated users under the `userids` property. ### Valeurs retournées `(object)` Renvoie un objet contenant les ID des utilisateurs mis à jour sous la propriété `userids`. ### Return values `(object)` Returns an object containing the IDs of the updated value maps under the `valuemapids` property. ### Valeurs retournées `(object)` Retourne un objet contenant les ID des tables de correspondance mises à jour sous la propriété `valuemapids`. ### Return values `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property. ### Valeurs retournées `(object)` Retourne un objet contenant les identifiants des scénarios Web mis à jour sous la propriété `httptestids`. ### Return values `(object)` Returns an object with host IDs as properties and arrays of available scripts as values. ::: notetip The method will automatically expand macros in the `confirmation` text. ::: ### Valeurs retournées `(object)` Renvoie un objet avec des ID d'hôte en tant que propriétés et des tableaux de scripts disponibles en tant que valeurs. ::: notetip La méthode développera automatiquement les macros dans le texte de `confirmation`. ::: ### Return values `(object)` Returns authentication object. ### Valeurs retournées `(object)` Renvoie l'objet d'authentification. ### Return values `(object)` Returns autoregistration object. ### Valeurs retournées `(object)` Retourne l'objet enregistrement automatique ### Return values `(object)` Returns housekeeping object. ### Valeurs retournées `(object)` Renvoie l'objet de procédure de nettoyage. ### Return values `(object)` Returns settings object. ### Valeurs retournées `(object)` Renvoie l'objet paramètres. ### Return values `(object)` Returns the result of script execution. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |response|string|Whether the script was run successfully.<br><br>Possible value - `success`.| |value|string|Script output.| |debug|object|Contains a [debug object](/manual/api/reference/script/object#Debug) if a webhook script is executed. For other script types, it contains empty object.| ### Valeurs retournées `(object)` Renvoie le résultat de l'exécution du script. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |response|string|Indique si le script a été exécuté avec succès.<br><br>Valeur possible - `success`.| |value|string|Sortie du script.| |debug|object|Contient un [objet de débogage](/manual/api/reference/script/object#Debug) si un script webhook est exécuté. Pour les autres types de script, il contient un objet vide.| ### Return values `(string)` Returns a serialized string containing the requested configuration data. ### Valeurs retournées `(string)` Renvoie une chaîne sérialisée contenant les données de configuration demandées. ### Return values `(string)` Returns the version of the Zabbix API. ::: notetip Starting from Zabbix 2.0.4 the version of the API matches the version of Zabbix. ::: ### Valeurs retournées `(string)` Renvoie la version de l\'API Zabbix. ::: notetip A partir de Zabbix 2.0.4, la version de l\'API correspond à la version de Zabbix. ::: ### RHEL packages renamed RHEL packages have been renamed by adding a "release" word in the name: |Naming|Package name| |--|--------| |Old|`zabbix-agent-6.0.7-1.el9.x86_64.rpm`| |New|`zabbix-agent-6.0.8-release1.el9.x86_64.rpm`| There is no functional change associated with this change. This is necessary as preparation for providing packages of minor version (i.e. 6.0.x) release candidates, expected to start with 6.0.9. The naming change will ensure that for someone who has both stable and unstable repositories enabled on their system, repository updates will be received in the correct order. This naming change is for RHEL packages only. ### Packages RHEL renommés Les packages RHEL ont été renommés en ajoutant le mot "release" dans le nom : |Nommage|Nom du package| |--|--------| |Ancien|`zabbix-agent-6.0.7-1.el9.x86_64.rpm`| |Nouveau|`zabbix-agent-6.0.8-release1.el9.x86_64.rpm`| Il n'y a pas de changement fonctionnel associé à ce changement. Ceci est nécessaire pour préparer la fourniture de packages de versions mineures (c'est-à-dire 6.0.x), qui devraient commencer avec la version 6.0.9. Le changement de nom garantira que pour quelqu'un qui a des référentiels stables et instables activés sur son système, les mises à jour du référentiel seront reçues dans le bon ordre. Ce changement de nom concerne uniquement les packages RHEL. # role.create # role.create # role.delete # role.delete # role.get # role.get ### Role rules The role rules object has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |ui|array|Array of the [UI element](object#ui_element) objects.| |ui.default\_access|integer|Whether access to new UI elements is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |services.read.mode|integer|Read-only access to services.<br><br>Possible values:<br><br>0 - Read-only access to the services, specified by the `services.read.list` or matched by the `services.read.tag` properties.<br>1 - *(default)* Read-only access to all services.| |services.read.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.read.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.write.mode|integer|Read-write access to services.<br><br>Possible values:<br><br>0 - (default) Read-write access to the services, specified by the `services.write.list` or matched by the `services.write.tag` properties.<br>1 - Read-write access to all services.| |services.write.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |services.write.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |modules|array|Array of the [module](object#module) objects.| |modules.default\_access|integer|Whether access to new modules is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.access|integer|Whether access to API is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.mode|integer|Mode for treating API methods listed in the `api` property.<br><br>Possible values:<br>0 - *(default)* Deny list;<br>1 - Allow list.| |api|array|Array of API methods.| |actions|array|Array of the [action](object#action) objects.| |actions.default\_access|integer|Whether access to new actions is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| ### Règles de rôle L'objet de règles de rôle a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |ui|array|Tableau d\'objets [élément UI](object#ui_element).| |ui.default\_access|integer|Indique si l'accès aux nouveaux éléments de l'interface utilisateur est activé.<br><br>Valeurs possibles :<br>0 - Désactivé ;<br>1 - *(par défaut)* Activé.| |services.read.mode|integer|Accès en lecture seule aux services.<br><br>Valeurs possibles :<br><br>0 - Accès en lecture seule aux services, spécifié par la propriété `services.read.list` ou correspondant à la propriété `services.read.tag`.<br>1 - *(par défaut)* Accès en lecture seule à tous les services.| |services.read.list|array|Tableau d'objets [Service](object#service).<br><br>Les services spécifiés, y compris les services enfants, se verront accorder un accès en lecture seule au rôle d'utilisateur. L'accès en lecture seule ne remplacera pas l'accès en lecture-écriture aux services.<br><br>Utilisé uniquement si `services.read.mode` est défini sur 0.| |services.read.tag|object|Tableau d'objets [tag de service](object#service_tag).<br><br>Les services correspondant au(x) tag(s), y compris les services enfants, se verront accorder un accès en lecture seule au rôle d'utilisateur. L'accès en lecture seule ne remplacera pas l'accès en lecture-écriture aux services.<br><br>Utilisé uniquement si `services.read.mode` est défini sur 0.| |services.write.mode|integer|Accès en lecture-écriture aux services.<br><br>Valeurs possibles :<br><br>0 - (par défaut) Accès en lecture-écriture aux services, spécifié par la propriété `services.write.list` ou correspondant à la propriété `services.write.tag`.<br>1 - Accès en lecture-écriture à tous les services.| |services.write.list|array|Tableau d'objets [Service](object#service).<br><br>Les services spécifiés, y compris les services enfants, se verront accorder un accès en lecture-écriture au rôle d'utilisateur. L'accès en lecture-écriture remplacera l'accès en lecture seule aux services.<br><br>Utilisé uniquement si `services.write.mode` est défini sur 0.| |services.write.tag|object|Tableau d'objets [tag de service](object#service_tag).<br><br>Les services correspondant au(x) tag(s), y compris les services enfants, se verront accorder un accès en lecture-écriture au rôle d'utilisateur. L'accès en lecture-écriture remplacera l'accès en lecture seule aux services.<br><br>Utilisé uniquement si `services.write.mode` est défini sur 0.| |modules|array|Tableau d'objets [module](object#module).| |modules.default\_access|integer|Indique si l'accès aux nouveaux modules est activé.<br><br>Valeurs possibles :<br>0 - Désactivé ;<br>1 - *(par défaut)* Activé.| |api.access|integer|Indique si l'accès à l'API est activé.<br><br>Valeurs possibles :<br>0 - Désactivé ;<br>1 - *(par défaut)* Activé.| |api.mode|integer|Mode de traitement les méthodes API répertoriées dans la propriété `api`.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Liste de refus ;<br>1 - Liste d'autorisation.| |api|array|Tableau de méthodes API.| |actions|array|Tableau d'objets [action](objet#action).| |actions.default\_access|integer|Indique si l'accès aux nouvelles actions est activé.<br><br>Valeurs possibles :<br>0 - Désactivé ;<br>1 - *(par défaut)* Activé.| ### Role The role object has the following properties: |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |roleid|string|*(readonly)* ID of the role.| |**name**<br>(required)|string|Name of the role.| |**type**<br>(required)|integer|User type.<br><br>Possible values:<br>1 - *(default)* User;<br>2 - Admin;<br>3 - Super admin.| |readonly|integer|*(readonly)* Whether the role is readonly.<br><br>Possible values:<br>0 - *(default)* No;<br>1 - Yes.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Rôle L'objet rôle a les propriétés suivantes : |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |roleid|string|*(lecture seule)* ID du rôle.| |**name**<br>(obligatoire)|string|Nom du rôle.| |**type**<br>(obligatoire)|integer|Type d'utilisateur.<br><br>Valeurs possibles :<br>1 - *(par défaut)* Utilisateur;<br>2 - Administrateur;<br>3 - Super administrateur.| |readonly|integer|*(lecture seule)* Indique si le rôle est en lecture seule.<br><br>Valeurs possibles :<br>0 - *(par défaut)* Non;<br>1 - Oui.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. # role.update # role.update #### Run a custom script Run a "ping" script on a host. Request: ```json { "jsonrpc": "2.0", "method": "script.execute", "params": { "scriptid": "1", "hostid": "30079" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "response": "success", "value": "PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.\n64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.074 ms\n64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.030 ms\n64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.030 ms\n\n--- 127.0.0.1 ping statistics ---\n3 packets transmitted, 3 received, 0% packet loss, time 1998ms\nrtt min/avg/max/mdev = 0.030/0.044/0.074/0.022 ms\n", "debug": [] }, "id": 1 } ``` #### Exécution d'un script personnalisé Exécutez un script "ping" sur un hôte. Requête : ```json { "jsonrpc": "2.0", "method": "script.execute", "params": { "scriptid": "1", "hostid": "30079" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "response": "success", "value": "PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.\n64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.074 ms\n64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.030 ms\n64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.030 ms\n\n--- 127.0.0.1 ping statistics ---\n3 packets transmitted, 3 received, 0% packet loss, time 1998ms\nrtt min/avg/max/mdev = 0.030/0.044/0.074/0.022 ms\n", "debug": [] }, "id": 1 } ``` #### Run a webhook script Run a webhook script that sends HTTP request to external service. Request: ```json { "jsonrpc": "2.0", "method": "script.execute", "params": { "scriptid": "4", "hostid": "30079" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": { "response": "success", "value": "{\"status\":\"sent\",\"timestamp\":\"1611235391\"}", "debug": { "logs": [ { "level": 3, "ms": 480, "message": "[Webhook Script] HTTP status: 200." } ], "ms": 495 } }, "id": 1 } ``` #### Exécuter un script de webhook Exécutez un script webhook qui envoie une requête HTTP à un service externe. Requête : ```json { "jsonrpc": "2.0", "method": "script.execute", "params": { "scriptid": "4", "hostid": "30079" }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": { "response": "success", "value": "{\"status\":\"sent\",\"timestamp\":\"1611235391\"}", "debug": { "logs": [ { "level": 3, "ms": 480, "message": "[Webhook Script] HTTP status: 200." } ], "ms": 495 } }, "id": 1 } ``` #### Running agent The agent will start automatically after installation or restart. You may edit the configuration file at `/usr/local/etc/zabbix/zabbix_agentd.conf` if necessary. To start the agent manually, you may run: sudo launchctl start com.zabbix.zabbix_agentd To stop the agent manually: sudo launchctl stop com.zabbix.zabbix_agentd During upgrade, the existing configuration file is not overwritten. Instead a new `zabbix_agentd.conf.NEW` file is created to be used for reviewing and updating the existing configuration file, if necessary. Remember to restart the agent after manual changes to the configuration file. #### Exécution de l'agent L'agent démarrera automatiquement après l'installation ou le redémarrage. Vous pouvez modifier le fichier de configuration dans `/usr/local/etc/zabbix/zabbix_agentd.conf` si nécessaire. Pour démarrer l'agent manuellement, vous pouvez exécuter : sudo launchctl start com.zabbix.zabbix_agentd Pour arrêter l'agent manuellement : sudo launchctl stop com.zabbix.zabbix_agentd Lors de la mise à niveau, le fichier de configuration existant n'est pas écrasé. Au lieu de cela, un nouveau fichier `zabbix_agentd.conf.NEW` est créé pour être utilisé pour réviser et mettre à jour le fichier de configuration existant, si nécessaire. N'oubliez pas de redémarrer l'agent après des modifications manuelles du fichier de configuration. #### Running proxy #### Exécution du Proxy #### Running server #### Serveur en cours d'exécution ### Runtime commands for profiling Runtime commands for profiling have been added to Zabbix server and Zabbix proxy. - `prof_enable` - enable profiling - `prof_disable` - disable profiling Profiling can be enabled per server/proxy process. Enabled profiling provides details of all rwlocks/mutexes by function name. See also: - [Zabbix server runtime commands](/manual/concepts/server#runtime-control) - [Zabbix proxy runtime commands](/manual/concepts/proxy#runtime-control) ### Commandes d'exécution pour le profilage Des commandes d'exécution pour le profilage ont été ajoutées au serveur Zabbix et au proxy Zabbix. - `prof_enable` - activer le profilage - `prof_disable` - désactiver le profilage Le profilage peut être activé par processus serveur/proxy. Le profilage activé fournit des détails sur tous les rwlocks/mutexes par nom de fonction. Voir également : - [Commandes d'exécution du serveur Zabbix](/manual/concepts/server#runtime-control) - [Commandes d'exécution du proxy Zabbix](/manual/concepts/proxy#runtime-control) ### Runtime command transfer Zabbix server and proxy runtime commands are now sent via socket instead of Unix signals. This change allowed to improve user experience working with runtime control options: - Results of the command execution are now printed to the console. - It is possible to send longer input parameters, such as HA node name instead of node number. ### Transfert de commande d'exécution Les commandes d'exécution du serveur et du proxy Zabbix sont désormais envoyées via socket au lieu de signaux Unix. Cette modification a permis d'améliorer l'expérience utilisateur en travaillant avec les options de contrôle d'exécution : - Les résultats de l'exécution de la commande sont maintenant affichés sur la console. - Il est possible d'envoyer des paramètres d'entrée plus longs, tels que le nom du nœud HA au lieu du numéro de nœud. ##### Runtime command transfer Zabbix server and proxy runtime commands are now sent via socket instead of Unix signals. This change allows to improve user experience working with runtime control options: - Results of the command execution are now printed to the console. - It is possible to send longer input parameters, such as HA node name instead of node number. ##### Transfert de commande d'exécution Les commandes d'exécution du serveur et du proxy Zabbix sont désormais envoyées via socket au lieu de signaux Unix. Cette modification permet d'améliorer l'expérience utilisateur en travaillant avec les options de contrôle d'exécution : - Les résultats de l'exécution de la commande sont maintenant affichés sur la console. - Il est possible d'envoyer des paramètres d'entrée plus longs, tels que le nom du nœud HA au lieu du numéro de nœud. ### Runtime control options **userparameter\_reload** Reload user parameters from the configuration file **log\_level\_increase**\[=*target*\] Increase log level, affects all processes if target is not specified **log\_level\_decrease**\[=*target*\] Decrease log level, affects all processes if target is not specified [ ]{#lbAG} ### Options de contrôle d'exécution : **userparameter\_reload** Recharger les paramètres utilisateur à partir du fichier de configuration **log\_level\_increase**\[=*target*\] Augmenter le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée **log\_level\_decrease**\[=*target*\] Diminue le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée [ ]{#lbAG} ##### Runtime control Runtime control options: |Option|Description|Target| |--|------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.<br>Active Zabbix proxy will connect to the Zabbix server and request configuration data.| | |diaginfo\[=<**target**>\]|Gather diagnostic information in the proxy log file.|**historycache** - history cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**locks** - list of mutexes (is empty on **BSD* systems)| |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.| | |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified. <br>Not supported on **BSD* systems.|**process type** - All processes of specified type (e.g., poller)<br>See all [proxy process types](#proxy_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.<br>Not supported on **BSD* systems.|^| |prof\_enable\[=<**target**>\]|Enable profiling.<br>Affects all processes if target is not specified.<br>Enabled profiling provides details of all rwlocks/mutexes by function name.<br>Supported since Zabbix 6.0.13.|**process type** - All processes of specified type (e.g., history syncer)<br>See all [proxy process types](#proxy_process_types).<br>**process type,N** - Process type and number (e.g., history syncer,1)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.<br><br>**scope** - `rwlock`, `mutex`, `processing` can be used with the process type and number (e.g., history syncer,1,processing)| |prof\_disable\[=<**target**>\]|Disable profiling.<br>Affects all processes if target is not specified.<br>Supported since Zabbix 6.0.13.|**process type** - All processes of specified type (e.g., history syncer)<br>See all [proxy process types](#proxy_process_types).<br>**process type,N** - Process type and number (e.g., history syncer,1)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| Example of using runtime control to reload the proxy configuration cache: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R config_cache_reload Examples of using runtime control to gather diagnostic information: Gather all available diagnostic information in the proxy log file: shell> zabbix_proxy -R diaginfo Gather history cache statistics in the proxy log file: shell> zabbix_proxy -R diaginfo=historycache Example of using runtime control to reload the SNMP cache: shell> zabbix_proxy -R snmp_cache_reload Example of using runtime control to trigger execution of housekeeper shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R housekeeper_execute Examples of using runtime control to change log level: Increase log level of all processes: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase Increase log level of second poller process: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=poller,2 Increase log level of process with PID 1234: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=1234 Decrease log level of all http poller processes: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_decrease="http poller" ##### Runtime control Options du runtime control : |Option|Description|Cible| |--|------|------| |config\_cache\_reload|Recharge le cache de configuration. Ignoré si le cache est en cours de chargement.<br>Le proxy actif Zabbix se connectera au serveur Zabbix pour demande les données de configuration.| | |diaginfo\[=<**target**>\]|Rassemble les informations de diagnostic dans le fichier journal du proxy.|**historycache** - statistiques du cache de l'historique<br>**preprocessing** - statistiques du gestionnaire de prétraitement<br>**locks** - liste des mutex (vide sur les systèmes **BSD*)| |snmp\_cache\_reload|Recharge le cache SNMP, efface les propriétés SNMP (heure du moteur, démarrages du moteur, ID du moteur, informations d'identification) pour tous les hôtes.| | |housekeeper\_execute|Démarre la procédure de nettoyage. Ignoré si la procédure de nettoyage est en cours d'exécution.| | |log\_level\_increase\[=<**target**>\]|Augmente le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée. <br>Non supporté sur les systèmes **BSD*.|**process type** - Tous les processus du type spécifié (ex : poller)<br>Voir tous les [types de processus du proxy](#proxy_process_types).<br>**process type,N** - Type de processus et leur numéro (ex : poller,3)<br>**pid** - Identifiant du processus (1 à 65535). Pour les valeurs plus grandes spécifiez la cible telle que 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Diminue le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée. <br>Non supporté sur les systèmes **BSD*.| | |prof\_enable\[=\<**target**\>\]|Active le profilage.<br>Affecte tous les processus si la cible n'est pas spécifiée.<br>Le profilage activé fournit des détails sur tous les rwlocks/mutexes par nom de fonction.<br>Pris en charge depuis Zabbix 6.0.13.|**process type** - Tous les processus du type spécifié (par exemple, history syncer)<br>Voir tous les [types de processus de proxy](#proxy_process_types).<br>**process type,N** - Type et nombre de processus (par exemple, history syncer,1)<br>**pid** - Identifiant du processus (1 à 65535). Pour des valeurs supérieures, spécifiez la cible comme 'process type,N'.<br><br>**scope** - `rwlock`, `mutex`, `processing` peut être utilisé avec le type et le numéro de processus (par exemple, history syncer,1,processing)| |prof\_disable\[=\<**target**\>\]|Désactiver le profilage.<br>Affecte tous les processus si la cible n'est pas spécifiée.<br>Pris en charge depuis Zabbix 6.0.13.|**process type** - Tous les processus du type spécifié (par exemple, history syncer)<br>Voir tous les [types de processus de proxy](#proxy_process_types).<br>**process type,N** - Type et nombre de processus (par exemple, history syncer,1)<br>**pid** - Identifiant du processus (1 à 65535). Pour des valeurs supérieures, spécifiez la cible comme 'process type,N'.| Exemple d’utilisation du runtime control pour recharger le cache de configuration du proxy : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R config_cache_reload Exemples d'utilisation du contrôle d'exécution pour collecter des informations de diagnostic : Rassembler toutes les informations de diagnostic disponibles dans le fichier journal du proxy : shell> zabbix_proxy -R diaginfo Rassembler les statistiques du cache de l'historique dans le fichier journal du proxy : shell> zabbix_proxy -R diaginfo=historycache Exemple d'utilisation du contrôle d'exécution pour recharger le cache SNMP : shell> zabbix_proxy -R snmp_cache_reload Exemple d’utilisation du runtime control pour déclencher l’exécution du nettoyage : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R housekeeper_execute Exemples d’utilisation du runtime control pour changer le niveau de journalisation : Augmenter le niveau de journalisation de tous les processus : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase Augmenter le niveau de journalisation du second processus poller : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=poller,2 Augmenter le niveau de journalisation du processus ayant le PID 1234 : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=1234 Diminuer le niveau de journalisation de tous les processus http poller : shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_decrease="http poller" ##### Runtime control Runtime control options: |Option|Description|Target| |------|-----------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.| | |diaginfo\[=<**target**>\]|Gather diagnostic information in the server log file.|**historycache** - history cache statistics<br>**valuecache** - value cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**alerting** - alert manager statistics<br>**lld** - LLD manager statistics<br>**locks** - list of mutexes| |ha\_status|Log high availability (HA) cluster status.| | |ha\_remove\_node=target|Remove the high availability (HA) node specified by its listed number.<br>Note that active/standby nodes cannot be removed.|**target** - number of the node in the list (can be obtained by running ha\_status)| |ha\_set\_failover\_delay=delay|Set high availability (HA) failover delay.<br>Time suffixes are supported, e.g. 10s, 1m.| | |secrets\_reload|Reload secrets from Vault.| | |service\_cache\_reload|Reload the service manager cache.| | |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.| | |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)<br>See all [server process types](#server_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.|^| Example of using runtime control to reload the server configuration cache: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Examples of using runtime control to gather diagnostic information: Gather all available diagnostic information in the server log file: shell> zabbix_server -R diaginfo Gather history cache statistics in the server log file: shell> zabbix_server -R diaginfo=historycache Example of using runtime control to reload the SNMP cache: shell> zabbix_server -R snmp_cache_reload Example of using runtime control to trigger execution of housekeeper: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute Examples of using runtime control to change log level: Increase log level of all processes: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase Increase log level of second poller process: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2 Increase log level of process with PID 1234: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234 Decrease log level of all http poller processes: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller" Example of setting the HA failover delay to the minimum of 10 seconds: shell> zabbix_server -R ha_set_failover_delay=10s ##### Contrôle d'exécution Options contrôle d'exécution : |Option|Description|Cible| |------|-----------|------| |config\_cache\_reload|Recharger le cache de configuration. Ignoré si le cache est en cours de chargement| | |diaginfo\[=<**target**>\]|Recueillir des informations de diagnostic dans le fichier journal du serveur.|**historycache** - statistiques du cache d'historique<br>**valuecache** - statistiques du cache de valeurs<br>**preprocessing** - statistiques du gestionnaire de prétraitement<br>**alerting** - statistiques du gestionnaire d'alertes<br>**lld** - statistiques du gestionnaire LLD<br>**locks** - liste des mutex| |ha\_status|Journaliser l'état du cluster haute disponibilité (HA).| | |ha\_remove\_node=target|Supprimer le nœud haute disponibilité (HA) spécifié par son numéro.<br>Notez que les nœuds actifs/en veille ne peuvent pas être supprimés.|**target** - numéro du nœud dans la liste (peut être obtenu en exécutant ha\_status)| |ha\_set\_failover\_delay=delay|Définir le délai de basculement de la haute disponibilité (HA).<br>Les suffixes temporels sont pris en charge, par ex. 10s, 1m.| | |secrets\_reload|Reload Recharger les informations d'identification depuis Vault.| | |service\_cache\_reload|Recharger le cache du gestionnaire de services.| | |snmp\_cache\_reload|Recharger le cache SNMP, effacer les propriétés SNMP (engine time, engine boots, engine id, informations d'identification) pour tous les hôtes.| | |housekeeper\_execute|Démarrer la procédure de nettoyage. Ignoré si la procédure de nettoyage est actuellement en cours d'exécution.| | |log\_level\_increase\[=<**target**>\]|Augmenter le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée.|**process type** -Tous les processus du type spécifié (ex : poller)<br>Voir tous les [types de processus serveur](#server_process_types).<br>**process type,N** - Type de processus et numéro (ex : poller,3)<br>**pid** - Identifiant du processus (1 to 65535). Pour des valeurs plus grandes, spécifiez la cible ainsi : 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Diminuer le niveau de journalisation, affecte tous les processus si la cible n'est pas spécifiée.|^| Exemple d'utilisation du contrôle d'exécution pour recharger le cache de configuration du serveur : shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Exemple d'utilisation du contrôle d'exécution pour recueillir des informations de diagnostic : Rassembler toutes les informations de diagnostic disponibles dans le fichier journal du serveur : shell> zabbix_server -R diaginfo Rassembler les statistiques du cache d'historique dans le fichier journal du serveur : shell> zabbix_server -R diaginfo=historycache Exemple d'utilisation du contrôle d'exécution pour recharger le cache SNMP : shell> zabbix_server -R snmp_cache_reload Exemple d'utilisation du contrôle d'exécution pour déclencher l'exécution du nettoyage : shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute Exemple d'utilisation du contrôle d'exécution pour modifier le niveau de journalisation : Augmenter le niveau de journalisation de tous les processus : shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase Augmenter le niveau de journalisation du deuxième processus de type poller: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2 Augmenter le niveau de journalisation du processus avec le PID 1234 : shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234 Diminuer le niveau de journalisation de tous les processus de type http poller : shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller" Exemple de réglage du délai de basculement HA sur un minimum de 10 secondes : shell> zabbix_server -R ha_set_failover_delay=10s ### Runtime controls on BSD-based OS Previously, Zabbix server and Zabbix proxy runtime control options were not supported on BSD-based systems. Changing the runtime command transfer method has allowed to withdraw this limitation. Now the majority of the commands are supported on *FreeBSD*, *NetBSD*, *OpenBSD*, and other operating systems from the **BSD* family. For the exact list, see *Runtime control* for Zabbix [server](/manual/concepts/server#runtime_control) or [proxy](/manual/concepts/proxy#runtime_control). ### Contrôles d'exécution sur un système d'exploitation basé sur BSD Auparavant, les options de contrôle d'exécution du serveur Zabbix et du proxy Zabbix n'étaient pas prises en charge sur les systèmes basés sur BSD. La modification de la méthode de transfert des commandes d'exécution a permis de supprimer cette limitation. Désormais, la majorité des commandes sont prises en charge sur *FreeBSD*, *NetBSD*, *OpenBSD* et d'autres systèmes d'exploitation de la famille **BSD*. Pour la liste exacte, voir *Contrôles d'exécution* pour le [serveur](/manual/concepts/server#runtime_control) ou le [proxy](/manual/concepts/proxy#runtime_control) Zabbix. ### SAML authentication SAML 2.0 authentication can be used to sign in to Zabbix. Note that a user must exist in Zabbix, however, its Zabbix password will not be used. If authentication is successful, then Zabbix will match a local username with the username attribute returned by SAML. ::: noteclassic If SAML authentication is enabled, users will be able to choose between logging in locally or via SAML Single Sign-On. ::: ### Authentification SAML L'authentification SAML 2.0 peut être utilisée pour se connecter à Zabbix. Notez qu'un utilisateur doit exister dans Zabbix, cependant, son mot de passe Zabbix ne sera pas utilisé. Si l'authentification réussit, Zabbix associera un nom d'utilisateur local à l'attribut de nom d'utilisateur renvoyé par SAML. ::: noteclassic Si l'authentification SAML est activée, les utilisateurs pourront choisir entre se connecter localement ou via l'authentification unique SAML. ::: #### Scenario #### Scénario #### Scenario items As soon as a scenario is created, Zabbix automatically adds the following items for monitoring. |Item|Description| |----|-----------| |*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.<br>Item key: web.test.in\[Scenario,,bps\]<br>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.<br>Item key: web.test.fail\[Scenario\]<br>Type: *Numeric(unsigned)*| |*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.<br>Item key: web.test.error\[Scenario\]<br>Type: *Character*| The actual scenario name will be used instead of "Scenario". ::: noteclassic Web monitoring items are added with a 30 day history and a 90 day trend retention period. ::: ::: noteclassic If scenario name starts with a doublequote or contains comma or square bracket, it will be properly quoted in item keys. In other cases no additional quoting will be performed. ::: These items can be used to create triggers and define notification conditions. #### Éléments de scenario Dès qu'un scénario est créé, Zabbix ajoute automatiquement les éléments suivants à superviser. | Élément|Description| |----|-----------| |*Vitesse de téléchargement du scénario <Scenario>*|Cet élément collectera des informations sur la vitesse de téléchargement (octets par seconde) de l’ensemble du scénario, c’est-à-dire la moyenne pour toutes les étapes.<br>Clé de l'élément : web.test.in\[Scenario,,bps\]<br>Type: *Numeric(float)*| |*Etape en échec du scénario <Scenario>*|Cet élément affichera le numéro de l'étape ayant échouée dans le scénario. Si toutes les étapes sont exécutées avec succès, 0 est renvoyé.<br>Clé de l'élément : web.test.fail\[Scenario\]<br>Type: *Numeric(unsigned)*| |*Dernier message d'erreur du scénario <Scenario>*|Cet élément renvoie le dernier texte du message d'erreur du scénario. Une nouvelle valeur est stockée uniquement si le scénario a échoué. Si toutes les étapes sont correctes, aucune nouvelle valeur n'est collectée.<br>Clé de l'élément : web.test.error\[Scenario\]<br>Type: *Character*| Le nom du scénario actuel sera utilisé à la place de "Scenario". ::: noteclassic Les éléments de supervision Web sont ajoutés avec un historique de 30 jours et une période de conservation des tendances de 90 jours. ::: ::: noteclassic Si le nom du scénario commence par des guillemets doubles ou contient une virgule ou un crochet, il sera correctement déspécialisé dans les clés d’élément. Dans les autres cas, aucune déspécialisation supplémentaire ne sera effectuée. ::: Ces éléments peuvent être utilisés pour créer des déclencheurs et définir des conditions de notification. #### Scenario step items As soon as a step is created, Zabbix automatically adds the following items for monitoring. |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.<br>Item key: web.test.in\[Scenario,Step,bps\]<br>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.<br>Item key: web.test.time\[Scenario,Step,resp\]<br>Type: *Numeric(float)*| |*Response code for step <Step> of scenario <Scenario>*|This item will collect response codes of the step.<br>Item key: web.test.rspcode\[Scenario,Step\]<br>Type: *Numeric(unsigned)*| Actual scenario and step names will be used instead of "Scenario" and "Step" respectively. ::: noteclassic Web monitoring items are added with a 30 day history and a 90 day trend retention period. ::: ::: noteclassic If scenario name starts with a doublequote or contains comma or square bracket, it will be properly quoted in item keys. In other cases no additional quoting will be performed. ::: 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: last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3 #### Éléments d'étape de scénario Dès qu'une étape est créée, Zabbix ajoute automatiquement les éléments suivants à superviser. | Élément|Description| |----|-----------| |*Vitesse de téléchargement de l'étape <Etape> du scénario <Scenario>*|Cet élément collectera des informations sur la vitesse de téléchargement (octets par seconde) de l'étape.<br>Clé de l'élément :web.test.in\[Scenario,Step,bps\]<br>Type : *Numeric(float)*| |*Temps de réponse de l'étape <Etape> du scénario <Scenario>*|et élément collectera des informations sur le temps de réponse de l'étape en secondes. Le temps de réponse est compté à partir du début de la demande jusqu'à ce que toutes les informations aient été transférées.<br>Clé de l'élément : web.test.time\[Scenario,Step,resp\]<br>Type : *Numeric(float)*| |* Code de réponse pour l'étape <Etape> du scénario <Scenario>*|Cet élément va collecter les codes de réponse de l'étape.<br>Clé de l'élément : web.test.rspcode\[Scenario,Step\]<br>Type : *Numeric(unsigned)*| Les noms de scénario et d'étape seront utilisés à la place de "Scenario" et "Step" respectivement. ::: noteclassic Les éléments de supervision Web sont ajoutés avec un historique de 30 jour et une période de conservation des tendances de 90 jours ::: ::: noteclassic Si le nom du scénario commence par des guillemets doubles ou contient une virgule ou un crochet, il sera correctement déspécialisé dans les clés d’élément. Dans les autres cas, aucune déspécialisation supplémentaire ne sera effectuée. ::: Ces éléments peuvent être utilisés pour créer des déclencheurs et définir des conditions de notification. Par exemple, pour créer un déclencheur "La connexion à l'interface graphique de Zabbix est trop lente", vous pouvez définir une expression de déclencheur : last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3 ### Scenario step The scenario step object defines a specific web scenario check. It has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |httpstepid|string|*(readonly)* ID of the scenario step.| |**name**<br>(required)|string|Name of the scenario step.| |**no**<br>(required)|integer|Sequence number of the step in a web scenario.| |**url**<br>(required)|string|URL to be checked.| |follow\_redirects|integer|Whether to follow HTTP redirects.<br><br>Possible values are:<br>0 - don't follow redirects;<br>1 - *(default)* follow redirects.| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP headers that will be sent when performing a request. Scenario step headers will overwrite headers specified for the web scenario.| |httptestid|string|*(readonly)* ID of the web scenario that the step belongs to.| |posts|string<br>array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP POST variables as a string (raw post data) or as an array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) (form field data).| |required|string|Text that must be present in the response.| |retrieve\_mode|integer|Part of the HTTP response that the scenario step must retrieve.<br><br>Possible values are:<br>0 - *(default)* only body;<br>1 - only headers;<br>2 - headers and body.| |status\_codes|string|Ranges of required HTTP status codes separated by commas.| |timeout|string|Request timeout in seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Default: 15s. Maximum: 1h. Minimum: 1s.| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Scenario step variables.| |query\_fields|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Query fields - array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) that will be added to URL when performing a request| ### Étape du scénario L'objet d'étape de scénario définit une vérification de scénario Web spécifique. Il a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |httpstepid|string|*(lecture seule)* ID de l'étape du scénario.| |**name**<br>(obligatoire)|string|Nom de l'étape du scénario.| |**no**<br>(obligatoire)|integer|Numéro de séquence de l'étape dans un scénario Web.| |**url**<br>(obligatoire)|string|URL à vérifier.| |follow\_redirects|integer|Suivre ou non les redirections HTTP.<br><br>Les valeurs possibles sont :<br>0 - ne pas suivre les redirections ;<br>1 - *(par défaut)* suivre les redirections.| |headers|tableau de [champs HTTP](/manual/api/reference/httptest/object#HTTP field)|En-têtes HTTP qui seront envoyés lors de l'exécution d'une requête. Les en-têtes d'étape de scénario remplaceront les en-têtes spécifiés pour le scénario Web.| |httptestid|string|*(lecture seule)* ID du scénario Web auquel appartient l'étape.| |posts|string<br>tableau de [champs HTTP](/manual/api/reference/httptest/object#HTTP field)|Variables HTTP POST sous forme de chaîne (données de publication brutes) ou sous forme de tableau de [champs HTTP]( /manual/api/reference/httptest/object#HTTP field) (données du champ de formulaire).| |required|string|Texte qui doit être présent dans la réponse.| |retrieve\_mode|integer|Partie de la réponse HTTP que l'étape du scénario doit récupérer.<br><br>Les valeurs possibles sont :<br>0 - *(par défaut)* uniquement le corps ;<br>1 - uniquement les en-têtes ; <br>2 - en-têtes et corps.| |status\_codes|string|Plages de codes d'état HTTP requis séparés par des virgules.| |timeout|string|Délai d'expiration de la demande en secondes. Accepte les secondes, l'unité de temps avec suffixe et la macro utilisateur.<br><br>Par défaut : 15 s. Maximum : 1h. Minimum : 1s.| |variables|tableau de [champs HTTP](/manual/api/reference/httptest/object#HTTP field)|Variables d'étape de scénario.| |query\_fields|tableau de [champs HTTP](/manual/api/reference/httptest/object#HTTP field)|Champs de requête - tableau de [champs HTTP](/manual/api/reference/httptest/object#HTTP field) qui sera ajouté à l'URL lors de l'exécution d'une requête | #### Scheduling intervals Scheduling intervals are used to check items at specific times. While flexible intervals are designed to redefine the default item update interval, the scheduling intervals are used to specify an independent checking schedule, which is executed in parallel. A scheduling interval is defined as: `md<filter>wd<filter>h<filter>m<filter>s<filter>` where: - **md** - month days - **wd** - week days - **h** - hours - **m** - minutes - **s** – seconds `<filter>` is used to specify values for its prefix (days, hours, minutes, seconds) and is defined as: `[<from>[-<to>]][/<step>][,<filter>]` where: - `<from>` and `<to>` define the range of matching values (included). If `<to>` is omitted then the filter matches a `<from> - <from>` range. If `<from>` is also omitted then the filter matches all possible values. - `<step>` defines the skips of the number value through the range. By default `<step>` has the value of 1, which means that all values of the defined range are matched. While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the *<step>* value defined. An empty filter matches either '0' if no lower-level filter is defined or all possible values otherwise. For example, if the hour filter is omitted then only '0' hour will match, provided minute and seconds filters are omitted too, otherwise an empty hour filter will match all hour values. Valid `<from>` and `<to>` values for their respective filter prefix are: |Prefix|Description|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59| The `<from>` value must be less or equal to `<to>` value. The `<step>` value must be greater or equal to 1 and less or equal to `<to>` - `<from>`. Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example `md01-31` and `h/02` are valid intervals, but `md01-031` and `wd01-07` are not. In Zabbix frontend, multiple scheduling intervals are entered in separate rows. In Zabbix API, they are concatenated into a single string with a semicolon `;` as a separator. If a time is matched by several intervals it is executed only once. For example, `wd1h9;h9` will be executed only once on Monday at 9am. Examples: |Interval|Will be executed| |--------|----------------| |m0-59|every minute| |h9-17/2|every 2 hours starting with 9:00 (9:00, 11:00 ...)| |m0,30 or m/30|hourly at hh:00 and hh:30| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|every five minutes| |wd1-5h9|every Monday till Friday at 9:00| |wd1-5h9-18|every Monday till Friday at 9:00,10:00,...,18:00| |h9,10,11 or h9-11|every day at 9:00, 10:00 and 11:00| |md1h9m30|every 1st day of each month at 9:30| |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday| |h9m/30|every day at 9:00, 9:30| |h9m0-59/30|every day at 9:00, 9:30| |h9,10m/30|every day at 9:00, 9:30, 10:00, 10:30| |h9-10m30|every day at 9:30, 10:30| |h9m10-40/30|every day at 9:10, 9:40| |h9,10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9-10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9m10-40|every day at 9:10, 9:11, 9:12, ... 9:40| |h9m10-40/1|every day at 9:10, 9:11, 9:12, ... 9:40| |h9-12,15|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0s30|every day at 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30| |h9-12s30|every day at 9:00:30, 9:01:30, 9:02:30 ... 12:58:30, 12:59:30| |h9m/30;h10 (*API-specific syntax*)|every day at 9:00, 9:30, 10:00| |h9m/30<br>h10 (*add this as another row in frontend*)|every day at 9:00, 9:30, 10:00| #### Intervalles de planification Les intervalles de planification sont utilisés pour vérifier les éléments à des moments précis. Alors que les intervalles flexibles sont conçus pour redéfinir l'intervalle d’actualisation par défaut des éléments, les intervalles de planification sont utilisés pour spécifier un calendrier de contrôle indépendant, qui est exécuté en parallèle. Un intervalle de planification est défini comme suit : `md<filter>wd<filter>h<filter>m<filter>s<filter>` où : - **md** - jours du mois - **wd** - jours de la semaine - **h** - heures - **m** - minutes - **s** – secondes `<filter>` est utilisé pour spécifier les valeurs du préfixe (jours, heures, minutes, secondes) et est défini comme : `[<from>[-<to>]][/<step>][,<filter>]` où : - `<from>` et `<to>` définissent la plage de valeurs correspondantes (incluses). Si `<to>` est omis alors le filtre correspond à une plage `<from> - <from>`. Si `<from>` est également omis, le filtre correspond à toutes les valeurs possibles. - `<step>` définit les sauts de la valeur numérique dans la plage. Par défaut, `<step>` a la valeur 1, ce qui signifie que toutes les valeurs de la plage définie correspondent. Alors que les définitions de filtre sont facultatives, au moins un filtre doit être utilisé. Un filtre doit avoir une plage ou la valeur *<step>* définie. Un filtre vide correspond à '0' si aucun filtre de niveau inférieur n'est défini ou à toutes les valeurs possibles dans le cas contraire. Par exemple, si le filtre d'heure est omis, seule l'heure '0' correspondra, à condition que les filtres minutes et secondes soient également omis, sinon un filtre d'heures vide correspondra à toutes les valeurs d'heure. Les valeurs `<from>` et `<to>` valides pour leur préfixe de filtre respectif sont : |Préfixe|Description|*<from>*|*<to>*| |--|--|------| |md|Jour du mois|1-31|1-31| |wd|Jour de la semaine|1-7|1-7| |h|Heures|0-23|0-23| |m|Minutes|0-59|0-59| |s|Secondes|0-59|0-59| La valeur `<from>` doit être inférieure ou égale à la valeur `<to>`. La valeur `<step>` doit être supérieure ou égale à 1 et inférieure ou égale à `<to>` - `<from>`. La valeur des jours, des heures, des minutes et des secondes à un seul chiffre peuvent être préfixées avec 0. Par exemple, `md01-31` et `h/02` sont des intervalles valides, mais `md01-031` et `wd01-07` ne le sont pas. Dans l'interface Zabbix, plusieurs intervalles de planification sont entrés dans des lignes séparées. Dans l'API Zabbix, ils sont concaténés en une seule chaîne avec un point-virgule ; en tant que séparateur. Si un instant correspond à plusieurs intervalles, il n'est exécuté qu'une seule fois. Par exemple, `wd1h9;h9` ne sera exécuté qu'une seule fois le lundi à 9h. Exemples : |Intervalle|Description| |----------|-----------| |m0-59|exécuté chaque minute| |h9-17/2|exécuté toutes les 2 heures en commençant à 9:00 (9:00, 11:00 ...)| |m0,30 or m/30|exécuté toutes les heures à hh:00 et hh:30| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|toutes les 5 minutes| |wd1-5h9|du lundi au vendredi à 9:00| |wd1-5h9-18|du lundi au vendredi à 9:00,10:00,...,18:00| |h9,10,11 or h9-11|chaque jour à 9:00, 10:00 et 11:00| |md1h9m30|chaque premier jour de chaque mois à 9:30| |md1wd1h9m30|chaque premier jour de chaque mois à 9:30 si c'est un lundi| |h9m/30|exécuté à 9:00, 9:30| |h9m0-59/30|exécuté à 9:00, 9:30| |h9,10m/30|exécuté à 9:00, 9:30, 10:00, 10:30| |h9-10m30|exécuté à 9:30, 10:30| |h9m10-40/30|exécuté à 9:10, 9:40| |h9,10m10-40/30|exécuté à 9:10, 9:40, 10:10, 10:40| |h9-10m10-40/30|exécuté à 9:10, 9:40, 10:10, 10:40| |h9m10-40|exécuté à 9:10, 9:11, 9:12, ... 9:40| |h9m10-40/1|exécuté à 9:10, 9:11, 9:12, ... 9:40| |h9-12,15|exécuté à 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0|exécuté à 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0s30|exécuté à 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30| |h9-12s30|exécuté à 9:00:30, 9:01:30, 9:02:30 ... 12:58:30, 12:59:30| |h9m/30;h10|exécuté à 9:00, 9:30, 10:00| # script.create # script.create # script.delete # script.delete # script.execute # script.execute # script.get # script.get # script.getscriptsbyhosts # script.getscriptsbyhosts #### Scripts Configure and execute scripts to help you with your daily tasks. [Script API](/manual/api/reference/script) #### Scripts Configurez et exécutez pour vous aider dans vos tâches quotidiennes. [API Script](/manual/api/reference/script) ### Script The script object has the following properties. |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |scriptid|string|*(readonly)* ID of the script.| |**name**<br>(required)|string|Name of the script.| |**type**<br>(required)|integer|Script type.<br><br>Possible values:<br>0 - Script;<br>1 - IPMI;<br>2 - SSH;<br>3 - Telnet;<br>5 - *(default)* Webhook.| |**command**<br>(required)|string|Command to run.| |scope|integer|Script scope.<br><br>Possible values:<br>1 - *default* action operation;<br>2 - manual host action;<br>4 - manual event action.| |execute\_on|integer|Where to run the script.<br>Used if `type` is `0` (script).<br><br>Possible values:<br>0 - run on Zabbix agent;<br>1 - run on Zabbix server;<br>2 - *(default)* run on Zabbix server (proxy).| |menu\_path|string|Folders separated by slash that form a menu like navigation in frontend when clicked on host or event.<br>Used if `scope` is `2` or `4`.| |authtype|integer|Authentication method used for SSH script type.<br>Used if `type` is `2`.<br><br>Possible values:<br>0 - password;<br>1 - public key.| |username|string|User name used for authentication.<br>Required if `type` is `2` or `3`.| |password|string|Password used for SSH scripts with password authentication and Telnet scripts.<br>Used if `type` is `2` and `authtype` is `0` or `type` is `3`.| |publickey|string|Name of the public key file used for SSH scripts with public key authentication.<br>Required if type is `2` and `authtype` is `1`.| |privatekey|string|Name of the private key file used for SSH scripts with public key authentication.<br>Required if type is `2` and `authtype` is `1`.| |port|string|Port number used for SSH and Telnet scripts.<br>Used if type is `2` or `3`.| |groupid|string|ID of the host group that the script can be run on. If set to 0, the script will be available on all host groups.<br><br>Default: 0.| |usrgrpid|string|ID of the user group that will be allowed to run the script. If set to 0, the script will be available for all user groups.<br>Used if `scope` is `2` or `4`.<br><br>Default: 0.| |host\_access|integer|Host permissions needed to run the script.<br>Used if `scope` is `2` or `4`.<br><br>Possible values:<br>2 - *(default)* read;<br>3 - write.| |confirmation|string|Confirmation pop up text. The pop up will appear when trying to run the script from the Zabbix frontend.<br>Used if `scope` is `2` or `4`.| |timeout|string|Webhook script execution timeout in seconds. Time suffixes are supported, e.g. 30s, 1m.<br>Required if `type` is `5`.<br><br>Possible values:<br>1-60s<br><br>Default value:<br>30s| |parameters|array|Array of [webhook input parameters](/manual/api/reference/script/object#Webhook parameters).<br>Used if `type` is `5`.| |description|string|Description of the script.| Note that for some methods (update, delete) the required/optional parameter combination is different. ### Script L'objet script a les propriétés suivantes. |Propriété|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |scriptid|string|*(lecture seule)* ID du script.| |**name**<br>(obligatoire)|string|Nom du script.| |**type**<br>(obligatoire)|integer|Type de script.<br><br>Valeurs possibles :<br>0 - Script ;<br>1 - IPMI ;<br>2 - SSH ;<br>3 - Telnet ;<br>5 - *(par défaut)* Webhook.| |**command**<br>(obligatoire)|string|Commande à exécuter.| |scope|integer|Portée du script.<br><br>Valeurs possibles :<br>1 - *par défaut* opération d'action ;<br>2 - action manuelle sur hôte ;<br>4 - action manuelle sur évènement.| |execute\_on|integer|Où exécuter le script.<br>Utilisé si `type` est à `0` (script).<br><br>Valeurs possibles :<br>0 - exécuter sur l'agent Zabbix ;<br>1 - exécuter sur le serveur Zabbix ;<br>2 - *(par défaut)* exécuter sur le serveur Zabbix (proxy).| |menu\_path|string|Dossiers séparés par une barre oblique qui forment un menu comme la navigation dans le frontend lorsque l'on clique sur l'hôte ou l'événement.<br>Utilisé si `scope` est à `2` ou `4`.| |authtype|integer|Méthode d'authentification utilisée pour le type de script SSH.<br>Utilisé si `type` est `2`.<br><br>Valeurs possibles :<br>0 - mot de passe ;<br>1 - clé publique.| |username|string|Nom d'utilisateur utilisé pour l'authentification.<br>Requis si `type` est `2` ou `3`.| |password|string|Mot de passe utilisé pour les scripts SSH avec authentification par mot de passe et les scripts Telnet.<br>Utilisé si `type` est `2` et `authtype` est `0` ou `type` est `3`.| |publickey|string|Nom du fichier de clé publique utilisé pour les scripts SSH avec authentification par clé publique.<br>Requis si le type est `2` et `authtype` est `1`.| |privatekey|string|Nom du fichier de clé privée utilisé pour les scripts SSH avec authentification par clé publique.<br>Requis si le type est `2` et `authtype` est `1`.| |port|string|Numéro de port utilisé pour les scripts SSH et Telnet.<br>Utilisé si le type est '2' ou '3'.| |groupid|string|ID du groupe d'hôtes sur lequel le script peut être exécuté. Si la valeur est 0, le script sera disponible sur tous les groupes hôtes.<br><br>Par défaut : 0.| |usrgrpid|string|ID du groupe d'utilisateurs qui sera autorisé à exécuter le script. S'il est défini sur 0, le script sera disponible pour tous les groupes d'utilisateurs.<br>Utilisé si `scope` est `2` ou `4`.<br><br>Par défaut : 0.| |host\_access|integer|Autorisations de l'hôte requises pour exécuter le script.<br>Utilisé si `scope` est `2` ou `4`.<br><br>Valeurs possibles :<br>2 - *(par défaut)* lecture ;<br>3 - écriture.| |confirmation|string|Texte contextuel de confirmation. La fenêtre contextuelle apparaît lorsque vous essayez d'exécuter le script à partir de l'interface Zabbix.<br><br>Utilisé si `scope` est `2` ou `4`.| |timeout|string|Délai d'exécution du script Webhook en secondes. Les suffixes horaires sont pris en charge, par ex. 30s, 1m.<br>Requis si `type` est `5`.<br><br>Valeurs possibles :<br>1-60s<br><br>Valeur par défaut :<br>30s| |description|string|Description du script.| Notez que pour certaines méthodes (mise à jour, suppression) la combinaison de paramètres requise/optionnelle est différente. #### Script timeout #### Délai d'expiration du script # script.update # script.update #### Searchable attributes Hosts can be searched by the following properties: - Host name - Visible name - IP address - DNS name Host groups can be searched by name. Specifying a parent host group implicitly selects all nested host groups. Templates can be searched by name or visible name. If you search by a name that is different from the visible name (of a template/host), in the search results it is displayed below the visible name in parentheses. #### Attributs consultables Les hôtes peuvent être recherchés par les propriétés suivantes : - Nom d'hôte - Nom visible - Adresse IP - Nom DNS Les groupes d'hôtes peuvent être recherchés par nom. La spécification d'un groupe d'hôtes parent sélectionne implicitement tous les groupes d'hôtes imbriqués. Les modèles peuvent être recherchés par nom ou par nom visible. Si vous recherchez un nom différent du nom visible (d'un modèle/hôte), dans les résultats de la recherche, il s'affiche sous le nom visible entre parenthèses. #### Searching by host inventory data Retrieve hosts that contain "Linux" in the host inventory "OS" field. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": [ "host" ], "selectInventory": [ "os" ], "searchInventory": { "os": "Linux" } }, "id": 2, "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "host": "Zabbix server", "inventory": { "os": "Linux Ubuntu" } }, { "hostid": "10107", "host": "Linux server", "inventory": { "os": "Linux Mint" } } ], "id": 1 } ``` #### Recherche par données d'inventaire de l'hôte Récupérez les hôtes qui contiennent "Linux" dans le champ "OS" de l'inventaire de l'hôte. Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": [ "host" ], "selectInventory": [ "os" ], "searchInventory": { "os": "Linux" } }, "id": 2, "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10084", "host": "Zabbix server", "inventory": { "os": "Linux Ubuntu" } }, { "hostid": "10107", "host": "Linux server", "inventory": { "os": "Linux Mint" } } ], "id": 1 } ``` #### Searching by host tags Retrieve hosts that have tag "Host name" equal to "Linux server". Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectTags": "extend", "evaltype": 0, "tags": [ { "tag": "Host name", "value": "Linux server", "operator": 1 } ] }, "auth": "7f9e00124c75e8f25facd5c093f3e9a0", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10085", "tags": [ { "tag": "Host name", "value": "Linux server" }, { "tag": "OS", "value": "RHEL 7" } ] } ], "id": 1 } ``` Retrieve hosts that have these tags not only on host level but also in their linked parent templates. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "tags": [{"tag": "A", "value": "1", "operator": "0"}], "inheritedTags": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10623", "name": "PC room 1" }, { "hostid": "10601", "name": "Office" } ], "id": 1 } ``` #### Recherche par tags d'hôte Récupérez les hôtes dont le tag "Host name" est égale à "Linux server". Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["hostid"], "selectTags": "extend", "evaltype": 0, "tags": [ { "tag": "Host name", "value": "Linux server", "operator": 1 } ] }, "auth": "7f9e00124c75e8f25facd5c093f3e9a0", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10085", "tags": [ { "tag": "Host name", "value": "Linux server" }, { "tag": "OS", "value": "RHEL 7" } ] } ], "id": 1 } ``` Récupérez les hôtes qui ont ces tags non seulement au niveau de l'hôte, mais également dans leurs modèles parents liés. Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "tags": [{"tag": "A", "value": "1", "operator": "0"}], "inheritedTags": true }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10623", "name": "PC room 1" }, { "hostid": "10601", "name": "Office" } ], "id": 1 } ``` #### Searching by template tags Retrieve templates that have tag "Host name" equal to "{HOST.NAME}". Request: ```json { "jsonrpc": "2.0", "method": "template.get", "params": { "output": ["hostid"], "selectTags": "extend", "evaltype": 0, "tags": [ { "tag": "Host name", "value": "{HOST.NAME}", "operator": 1 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10402", "tags": [ { "tag": "Host name", "value": "{HOST.NAME}" } ] } ], "id": 1 } ``` #### Recherche par tags de modèle Récupérez les modèles dont le tag "Host name"" est égale à "{HOST.NAME}". Requête : ```json { "jsonrpc": "2.0", "method": "template.get", "params": { "output": ["hostid"], "selectTags": "extend", "evaltype": 0, "tags": [ { "tag": "Host name", "value": "{HOST.NAME}", "operator": 1 } ] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10402", "tags": [ { "tag": "Host name", "value": "{HOST.NAME}" } ] } ], "id": 1 } ``` #### Searching hosts by problem severity Retrieve hosts that have "Disaster" problems. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "severities": 5 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10160", "name": "Zabbix server" } ], "id": 1 } ``` Retrieve hosts that have "Average" and "High" problems. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "severities": [3, 4] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "20170", "name": "Database" }, { "hostid": "20183", "name": "workstation" } ], "id": 1 } ``` #### Recherche d'hôtes par gravité de problème Récupérez les hôtes qui ont des problèmes de gravité "désastre". Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "severities": 5 }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10160", "name": "Zabbix server" } ], "id": 1 } ``` Récupérez les hôtes qui ont des problèmes de gravité "moyenne" et "haute". Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "severities": [3, 4] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "20170", "name": "Database" }, { "hostid": "20183", "name": "workstation" } ], "id": 1 } ``` #### Searching host with tags and template tags Retrieve a host with tags and all tags that are linked to parent templates. Request: ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "hostids": 10502, "selectTags": ["tag", "value"], "selectInheritedTags": ["tag", "value"] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Response: ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10502", "name": "Desktop", "tags": [ { "tag": "A", "value": "1" } ], "inheritedTags": [ { "tag": "B", "value": "2" } ] } ], "id": 1 } ``` #### Recherche d'hôte avec des tags et des tags de modèle Récupérez un hôte avec des tags et tous les tags liées aux modèles parents. Requête : ```json { "jsonrpc": "2.0", "method": "host.get", "params": { "output": ["name"], "hostids": 10502, "selectTags": ["tag", "value"], "selectInheritedTags": ["tag", "value"] }, "auth": "038e1d7b1735c6a5436ee9eae095879e", "id": 1 } ``` Réponse : ```json { "jsonrpc": "2.0", "result": [ { "hostid": "10502", "name": "Desktop", "tags": [ { "tag": "A", "value": "1" } ], "inheritedTags": [ { "tag": "B", "value": "2" } ] } ], "id": 1 } ``` #### Search results Search results consist of three separate blocks for hosts, host groups and templates. {width="600"} It is possible to collapse/expand each individual block. The entry count is displayed at the bottom of each block, for example, *Displaying 13 of 13 found*. Total entries displayed within one block are limited to 100. Each entry provides links to monitoring and configuration data. See the [full list](/manual/web_interface/global_search#links_available) of links. For all configuration data (such as items, triggers, graphs) the amount of entities found is displayed by a number next to the entity name, in gray. **Note** that if there are zero entities, no number is displayed. Enabled hosts are displayed in blue, disabled hosts in red. #### Résultats de recherche Les résultats de la recherche se composent de trois blocs distincts pour les hôtes, les groupes d'hôtes et les modèles. {width="600"} Il est possible de réduire/développer chaque bloc individuellement. Le nombre d'entrées est affiché au bas de chaque bloc, par exemple, *Affichage de 13 sur 13 trouvés*. Le nombre total d'entrées affichées dans un bloc est limité à 100. Chaque entrée fournit des liens vers les données de surveillance et de configuration. Consultez la [liste complète](/manual/web_interface/global_search#links_available) des liens. Pour toutes les données de configuration (telles que les éléments, les déclencheurs, les graphiques), le nombre d'entités trouvées est affiché par un nombre à côté du nom de l'entité, en gris. **Notez** que s'il n'y a aucune entité, aucun nombre n'est affiché. Les hôtes activés sont affichés en bleu, les hôtes désactivés en rouge. #### Secure user for Zabbix agent In the default configuration, Zabbix server and Zabbix agent processes share one 'zabbix' user. If you wish to make sure that the agent cannot access sensitive details in server configuration (e.g. database login information), the agent should be run as a different user: 1. Create a secure user 2. Specify this user in the agent [configuration file](/manual/appendix/config/zabbix_agentd) ('User' parameter) 3. Restart the agent with administrator privileges. Privileges will be dropped to the specified user. #### Utilisateur sécurisé pour l'agent Zabbix Dans la configuration par défaut, les processus du serveur Zabbix et de l'agent Zabbix partagent un utilisateur 'zabbix'. Si vous souhaitez vous assurer que l'agent ne peut pas accéder aux détails sensibles dans la configuration du serveur (par exemple, les informations de connexion à la base de données), l'agent doit être exécuté en tant qu'utilisateur différent : 1. Créez un utilisateur sécurisé 2. Spécifiez cet utilisateur dans le [fichier de configuration](/manual/appendix/config/zabbix_agentd) de l'agent (paramètre 'User') 3. Redémarrez l'agent avec des privilèges d'administrateur. Les privilèges seront abandonnés à l'utilisateur spécifié. #### Security vulnerabilities ##### CVE-2021-42550 In Zabbix Java gateway with logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configuration files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers. Vulnerability to [CVE-2021-42550](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42550) has been fixed since Zabbix 5.4.9. However, as an additional security measure it is recommended to check permissions to the `/etc/zabbix/zabbix_java_gateway_logback.xml` file and set it read-only, if write permissions are available for the "zabbix" user. #### Vulnérabilités de sécurité ##### CVE-2021-42550 Dans la gateway Java Zabbix avec la version 1.2.7 de logback et versions précédentes, un attaquant disposant des privilèges requis pour modifier les fichiers de configuration pourrait créer une configuration malveillante permettant d'exécuter du code arbitraire chargé à partir de serveurs LDAP. La vulnérabilité à [CVE-2021-42550](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42550) a été corrigée depuis Zabbix 5.4.9. Cependant, comme mesure de sécurité supplémentaire, il est recommandé de vérifier les autorisations sur le fichier `/etc/zabbix/zabbix_java_gateway_logback.xml` et de le définir en lecture seule, si des autorisations d'écriture sont disponibles pour l'utilisateur "zabbix". ### See also 1. [Additional details about memory calculation in different OS](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size) ### Voir également 1. [Détails supplémentaires sur le calcul de la mémoire dans différents systèmes d'exploitation](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size) ### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858). ### Voir également 1. [Différences dans la configuration de l'agent Zabbix pour les vérifications actives et passives à partir de la version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858). #### See also 1. [Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858) #### Voir également 1. [Différences dans la configuration de l'agent Zabbix pour les vérifications actives et passives à partir de la version 2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858). ### See also 1. [How to configure optimal count of zabbix processes](http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457) ### Voir aussi 1. [Comment configurer le nombre optimal de processus zabbix](http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457) ### See also 1. [How to configure shared memory for Zabbix daemons](http://www.zabbix.org/wiki/How_to/configure_shared_memory) ### Voir également 1. [Comment configurer la mémoire partagée pour les démons Zabbix](http://www.zabbix.org/wiki/How_to/configure_shared_memory) ### See also - [Action filter](object#action_filter) - [Action operation](object#action_operation) ### Voir également - [Filtre d'Action](object#action_filter) - [Opération d'Action](object#action_operation) ### See also - [Action filter](object#action_filter) - [Action operation](object#action_operation) ### Voir également - [Filtre d'action](object#action_filter) - [Opération d'action](object#action_operation) ### See also - [Action filter](object#action_filter) - [Action operation](object#action_operation) - [Script](/manual/api/reference/script/object) ### Voir également - [Filtre d'action](object#action_filter) - [Opération d'action](object#action_operation) - [Script](/manual/api/reference/script/object) ### See also - [Alert](/manual/api/reference/alert/object) - [Item](/manual/api/reference/item/object) - [Host](/manual/api/reference/host/object) - [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) - [Trigger](/manual/api/reference/trigger/object) ### Voir également - [Alerte](/fr/manual/api/reference/alert/object) - [Élément](/fr/manual/api/reference/item/object) - [Hôte](/fr/manual/api/reference/host/object) - [Règle de découverte bas niveau](/fr/manual/api/reference/discoveryrule/object#regle_de_decouverte_bas_niveau) - [Déclencheur](/fr/manual/api/reference/trigger/object) ### See also - [Alert](/manual/api/reference/alert/object) - [Item](/manual/api/reference/item/object) - [Host](/manual/api/reference/host/object) - [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) - [Trigger](/manual/api/reference/trigger/object) ### See also - [Alerte](/manual/api/reference/alert/object) - [Elément](/manual/api/reference/item/object) - [Hôte](/manual/api/reference/host/object) - [Règle LLD](/manual/api/reference/discoveryrule/object#lld_rule) - [Déclencheur](/manual/api/reference/trigger/object) ### See also - [Audit log object](/manual/api/reference/auditlog/object) ### Voir également - [Objet Audit log](/manual/api/reference/auditlog/object) ### See also - [Authentication](/manual/api/reference/authentication) ### Voir également - [Authentification](/manual/api/reference/authentication) ### See also - [Authentication](/manual/api/reference/authentication) - [Media](/manual/api/reference/user/object#media) - [User group](/manual/api/reference/usergroup/object#user_group) - [Role](/manual/api/reference/role/object#role) ### Voir également - [Authentification](/manual/api/reference/authentication) - [Media](/manual/api/reference/user/object#media) - [Groupe d'utilisateurs](/manual/api/reference/usergroup/object#user_group) - [Rôle](/manual/api/reference/role/object#role) ### See also - [Correlation filter](object#correlation_filter