Zabbix

zabbix_export:

  version: '7.0'

  template_groups:

    - uuid: a571c0d144b14fd4a87a9d9b2aa9fcd6

      name: Templates/Applications

  templates:

    - uuid: 4958b76448d74ff1b6d7d6280449beee

      template: 'Proxmox VE by HTTP'

      name: 'Proxmox VE by HTTP'

      description: |

        This template is designed for the effortless deployment of Proxmox VE monitoring by Zabbix via HTTP and doesn't require any external scripts.

        Proxmox VE uses a REST like API. The concept is described in Resource Oriented Architecture (ROA).

        Check the API documentation for details:

        https://pve.proxmox.com/pve-docs/api-viewer/index.html

        Setup:

        1. Create an API token for the monitoring user. Important note: for security reasons, it is recommended to create a separate user (Datacenter - Permissions).

        Please provide the necessary access levels for both the User and the Token:

        * Check: ["perm","/",["Sys.Audit"]]

        * Check: ["perm","/storage",["Datastore.Audit"]]

        * Check: ["perm","/vms",["VM.Audit"]]

        2. Copy the resulting Token ID and Secret into the host macros '{$PVE.TOKEN.ID}' and '{$PVE.TOKEN.SECRET}'.

        3. Set the hostname or IP address of the Proxmox VE API host in the '{$PVE.URL.HOST}' macro. You can also change the API port in the '{$PVE.URL.PORT}' macro if necessary.

        Generated by official Zabbix template tool "Templator"

      vendor:

        name: Zabbix

        version: 7.0-2

      groups:

        - name: Templates/Applications

      items:

        - uuid: 75f8f8c507774f529ade4bc4255f5fd2

          name: 'API service status'

          type: SCRIPT

          key: proxmox.api.available

          delay: 5m

          params: |

            try {

              var params = JSON.parse(value);

              var req = new HttpRequest();

              req.addHeader('Authorization: PVEAPIToken=' + params.token + '=' + params.secret);

              req.get(encodeURI('https://' + params.url + ':' + params.port + '/api2/json/version'));

            } catch (error) {

                Zabbix.log(3, "Proxmox API failed: " + params.url + " Error: " + error);

                if (!Number.isInteger(error))

                    return 520;

            }

            return req.getStatus();

          description: 'Get API service status.'

          valuemap:

            name: 'HTTP response status code'

          preprocessing:

            - type: DISCARD_UNCHANGED_HEARTBEAT

              parameters:

                - 12h

          timeout: 10s

          parameters:

            - name: port

              value: '{$PVE.URL.PORT}'

            - name: secret

              value: '{$PVE.TOKEN.SECRET}'

            - name: token

              value: '{$PVE.TOKEN.ID}'

            - name: url

              value: '{$PVE.URL.HOST}'

          tags:

            - tag: component

              value: system

          triggers:

            - uuid: 7ef8290fd6e242339d0e56d5e8eedb1a

              expression: 'last(/Proxmox VE by HTTP/proxmox.api.available) <> 200'

              name: 'Proxmox VE: API service not available'

              opdata: 'Current value: {ITEM.LASTVALUE1}'

              priority: HIGH

              description: 'The API service is not available. Check your network and authorization settings.'

              tags:

                - tag: scope

                  value: availability

        - uuid: 4fe4fa1323cd481f8aff3bfb716eeae2

          name: 'Get cluster resources'

          type: HTTP_AGENT

          key: proxmox.cluster.resources

          delay: 5m

          history: '0'