Source of template_app_vmware.yaml - Zabbix

Raw file
Source viewDiff to previous
69.88 KB
xxxxxxxxxx
                  description: 'A cluster becomes overcommitted (yellow) when the tree of resource pools and virtual machines is internally consistent but the cluster does not have the capacity to support all resources reserved by the child resource pools. See also: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-resource-management/GUID-ED8240A0-FB54-4A31-BD3D-F23FE740F10C.html'
 
zabbix_export:  version: '7.0'  template_groups:    - uuid: a571c0d144b14fd4a87a9d9b2aa9fcd6      name: Templates/Applications  host_groups:    - uuid: a571c0d144b14fd4a87a9d9b2aa9fcd6      name: Applications  templates:    - uuid: 56079badd056419383cc26e6a4fcc7e0      template: VMware      name: VMware      description: |        You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/                Note: To enable discovery of hardware sensors of VMware Hypervisors, set the macro '{$VMWARE.HV.SENSOR.DISCOVERY}' to the value 'true' on the discovered host level.                Generated by official Zabbix template tool "Templator"      vendor:        name: Zabbix        version: 7.0-0      groups:        - name: Templates/Applications      items:        - uuid: 5ce209f4d94f460488a74a92a52d92b1          name: 'VMware: Event log'          type: SIMPLE          key: 'vmware.eventlog[{$VMWARE.URL},skip]'          history: 7d          trends: '0'          value_type: LOG          username: '{$VMWARE.USERNAME}'          password: '{$VMWARE.PASSWORD}'          description: 'Collect VMware event log. See also: https://www.zabbix.com/documentation/7.0/manual/config/items/preprocessing/examples#filtering_vmware_event_log_records'          tags:            - tag: component              value: log        - uuid: ee2edadb8ce943ef81d25dbbba8667a4          name: 'VMware: Full name'          type: SIMPLE          key: 'vmware.fullname[{$VMWARE.URL}]'          delay: 1h          history: 7d          trends: '0'          value_type: CHAR          username: '{$VMWARE.USERNAME}'          password: '{$VMWARE.PASSWORD}'          description: 'VMware service full name.'          preprocessing:            - type: DISCARD_UNCHANGED_HEARTBEAT              parameters:                - 1d          tags:            - tag: component              value: system        - uuid: a0ec9145f2234fbea79a28c57ebdb44d          name: 'VMware: Version'          type: SIMPLE          key: 'vmware.version[{$VMWARE.URL}]'          delay: 1h          history: 7d          trends: '0'          value_type: CHAR          username: '{$VMWARE.USERNAME}'          password: '{$VMWARE.PASSWORD}'          description: 'VMware service version.'          preprocessing:            - type: DISCARD_UNCHANGED_HEARTBEAT              parameters:                - 1d          tags:            - tag: component              value: system      discovery_rules:        - uuid: 16ffc933cce74cf28a6edf306aa99782          name: 'Discover VMware clusters'          type: SIMPLE          key: 'vmware.cluster.discovery[{$VMWARE.URL}]'          delay: 1h          username: '{$VMWARE.USERNAME}'          password: '{$VMWARE.PASSWORD}'          description: 'Discovery of clusters'          item_prototypes:            - uuid: 46111f91dd564a459dbc1d396e2e6c76              name: 'VMware: Status of "{#CLUSTER.NAME}" cluster'              type: SIMPLE              key: 'vmware.cluster.status[{$VMWARE.URL},{#CLUSTER.NAME}]'              history: 7d              username: '{$VMWARE.USERNAME}'              password: '{$VMWARE.PASSWORD}'              description: 'VMware cluster status.'